3/31/2024 0 Comments Sql error 18456 windows 7That might explain how the app is able to connect with a null password.ĭo you see any references to registry entries or file names in YourApp. If it just ignores the error, then you would end up with an empty variable that should contain the password. Update: if you don't find the password in the C:\temp\ YourApp.txt then maybe the app is looking for a registry entry or a file that contains the pswd and does not exist on the new server. OConn.Open "driver= server=YourSQLServer database=YourSQLDB uid=xxxxxxx pwd=xxxxxxxx" Set oRs = CreateObject("ADODB.Recordset") Set oConn = CreateObject("ADODB.Connection") VB6 is 32 bit so you need to use c:\windows\syswow64\cscript.exe to run the test script. strings -n 8 YourApp.exe > C:\temp\YourApp.txt If you don't have the source code, then you can try using the strings utility to see if can find the connect string in the. We should be able to use VB script to test the connection.ĭo you know what the password should be? Or what the connect string is? Does the app use an ODBC DSN by chance? Doing a "CreateObject" made it more portable, so I would expect that's what your app is doing if the program can at least launch. If you know of any other ones let me know. Password might have expired and probably several other reasons. If you use SSMS you might have to run as different user to use this option). Windows login was provided for SQL Authentication (change to Windows Authentication. I remember that I could "dim objConnection as ADODB.Connection" (or something like that) but that added a reference to a specific version at compile time and I had problems when I tried to run the app on other machines. less common errors: The userID might be disabled on the server. not sure that any of this will help, but here's what pops up.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |