Windows 11 marks a big departure from Windows 10 in terms of design, but the two operating systems are very similar under the hood. Hopefully this helps at least one more person as I've had days of trial and error. New connections using the latest windows update. I have one user who was working fine before the latest Windows update who was unaffected. I have replicated this fix on 40 laptops (manually as this has ruined my silent install process for this app) as all have had the issue. Please note that testing the connection in ODBC data sources also doesn't work. If these ports don't work run netstat -ab in a command prompt on the db server to get a list of what is using what.Īfter the connection has worked for the first time you can remove the port number and save it and it will still work. Find out which port your DB is listening on (usually 49157 or 2638) and add that port in ODBC data sources (remember to run as admin). So it seems like Windows 10's ODBC data sources app doesn't like doing things in the first instance without a port number. I've had this issue when connecting to another DB in my network through a CRM app (Microdec Profile incase you're using it)Īfter a lot of frustration and trial and error I've found a reliable way of fixing it (in my case anyway, just sharing incase anyone is in the same boat)
"Wjy are we having disproportinate numbers of problems Trust in the new software is immediately lost among the userbase. It is difficult to move to newer versions when things like this continue to occur. Thankfully we have limited Windows 10 desktopĭeployments. The solution thus far is to revert to previous Windows build. Deactivating ALL Windows defender and Smart Screen options does not fix the issue. We are receiving Oracle TNS-12560 errors after the update to 1803. The application this could be the problem but I do not see what amounts to an ODBC breakage being caused by SMB version. The output from a working Windows 10 (1709) indicates it is using SMB 1.5. Copying the exe to the local workstation does not solve the issue. Number of things mentioned here to no success.
The application is hosted on a Windows 2003 server as is the database (separate server). We have an Oracle database that is unreachable after the update.
I have been tracking this issue for several days as our office is also affected.
0 kommentar(er)
