You may not have associated it with being SQL related. The older DLLs, which I'm sure you would have used, picked up the database instance from the system registry files (as ScreamingFox mentioned) and having incorrect registry would have produced a similar response. This is less likely if you are using dlls following Gregoos' method of embedding the instance connection details; and that is (I suspect) more common these days. (it seems to resolve many similar issues as each string is only listed
once, so you can't make a typo in just one string... they are either all correct, or all wrong ^_^)
Also, it may not be the correct solution. I simply think it's a good and easily describable test to try. Once tried, you learn something, and discount a lot of possibilities you could otherwise waste time trying to debug when there is nothing wrong with them. If I where to make a decision diagram for troubleshooting login issues, with little knowledge of what is causing them, (ie. you haven't changed something recently which seems to have caused this issue where login worked fine before) that would often be my first choice diamond.
Can you log in?
Yes = It's all good. \o/
No =
: If you move the SQLdll and Clan dll files and restart the server, can you log in then?
Yes = Okay, so put them back. Now; Do you use registry configured DLLs or Gregoo style embedded DLLs?
Registry = Check the
sql.reg file details against MSSQLMS login details, re-apply and restart the server if there are any differences... Can you log in yet?
Yes = It's all good. \o/
No = Let's look at the actual account record ...
...
...
Embedded = Did you create these yourself (on
You must be registered to see links
or with
You must be registered to see links
) or are you using files someone gave you?
Someone gave me = That's your problem.
Go create your own, and then answer the previous diamond correctly.
Created them = You can try checking the details in a Hex Editor, but it's probably just as easy to re-run the creation process and be very careful to check, type and double-check the details carefully, now that you know how critical it is that they are correct. ^_^ Try again, and return to the beginning of this diagram if problems persist
No = Are you sure you have the ODBC connection set correctly? Can you connect using a standard ODBC client ...
...
...
etc.
And the diagram would go on and on and on with many branches and decisions, but listing them
all quickly becomes *very* confusing for new users, so let's KISS (Keep It Simple Stoopid
) and take each of them, one at a time, taking only the branches relevant to this particular person. ^_^
At least... that's the idea. Until someone starts pressing for TMI (Too Much Information) all at once.
ie. Stop being greedy swezid, you'll only confuse the poor child.