Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.

Disable pesky warning about about SQLOLEDB

Adelred's profile image Adelred posted 1 month ago in General Permalink

Hello everybody,

I have a question: Is there any way to disable the warning which will appear every time I want to access our SQL database? I have to click OK every time it appears and it is just bothersome (see the pic in the attachment).

I am using HeidiSQL portable, version 12.0.0.6507

Thanks for the info.

1 attachment(s):
  • warning2
Adelred's profile image Adelred posted 1 month ago Permalink

Additional info: I have that Microsoft OLE DB Driver installed, and when it tries to download that version in the link, during installation it says I already have it installed, in newer version, so I do not understand why is there a warning in the first place.

ansgar's profile image ansgar posted 1 month ago Permalink

Once it's installed, you should try to use it, in the "Library" dropdown. If it does not work please report back.

The old OLE DB driver is deprecated, and has security issues. For example it cannot handle TLS 1.2 and 1.3 as far as I know.

Adelred's profile image Adelred posted 1 month ago Permalink

I do have the MSOLEDBSQL there, but when I select it, it says there is timeout problem:

2 attachment(s):
  • 00
  • 01
Adelred's profile image Adelred posted 1 month ago Permalink

All right, I am at my wits end.

I have followed the link in the "Connection failed" picture and it brought me here:

I have read the whole thing, I was able to run portqry.exe and it did return information and contained my target instance, so I can rule out points 4 and 5.

That leaves me with first 3. My hostname and IP, as written is: "USER\SQLEXPRESS" where "USER" is my pc username all in capital (I am trying to connect to my localhost db), so I can rule out point 1. and I have tried out point 2. ("USER\SQLEXPRESS" or "USERSQLEXPRESS") to no avail. Point 3 - I was able to ping myself in CLI with command "ping user" so I can rule out point 3. as well and thus have no idea, what causes that timeout.

Does anybody have any idea what might be causing this?

Adelred's profile image Adelred posted 1 month ago Permalink

If it will be any help, portqry.exe result was:

"querying...

UDP port 1434 (ms-sql-m service): NOT LISTENING"

Please login to leave a reply, or register at first.




Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.