Shimon Krokhmal's blog

or, What have the latest windows 2003 service pack 2 has done to my sql server ?

Today i scheduled for my self some working time on the NightDuck project (Coming Soon),
but suddenly something went wrong, the sql server, which installed on a physically different machine than the development rig, gave me the following message:

"Sql server does not exist or access denied ConnectionOpen(Connect())"

what could have go wrong ?

the interesting part is when i tried to connect to the server remotely (remote desktop) and connecting to the Sql server from the localhost, it had no problems what so ever.
Since the sql server machine is not a dependency of a production application or something like that, i went wild on the experiments to try and fix the problem

• Lets restart the sql server service - no good.
• Router configurations and port forwarding - nothing has changed since the last time i worked on the project, thats not the problem either
• SQL SERVER user - defining a new user did not solved the problem either

so i started googling on the subject, and found a few things, like this one for example at the Microsoft site :
Potential causes of the "SQL Server does not exist or access denied" error message

this article has a list of things that may cause this problem (hard to guess by it's name).
checking the relevant ones, i came across this article about ports needed by the sql server.
i made a little test to check if the ports are ok, i tried to telnet the machine from the dev PC on the 1433 port, but with no luck,
in an effort to isolate the problem i tried that from the localhost of the server, telneting to the localhost on port 1433, which gave me an error "could not connect...".
this is what i was looking for !
At this point the problem is completely isolated, why ?

• the router configuration is not an issue (request does not go out from the machine)
• the development rig is not part of the equation anymore
• firewall is not the problem

based on these symptoms, I've searched once more, and stumbled upon a forum thread about a very similar issue, when installing service pack 2 on windows XP causes the same effect.
Apparently, if you have an out of date version of the file DBNETLIB.dll ,the Service Pack 2 disables TCP/IP access to MS SQL Server.
This is a defense against the Slammer worm. (some ugly work around by Microsoft a have to say...)

the solution is installing the SQL Server 200 security tools , which sets things back to normal.

since the windows 2003 service pack 2 is quite new, i guess this thread will be useful

update :
Just wondering how many others encountered this specific problem,
if you find this info useful, please leave a comment.

No, I'm no retiring from the coding field...
actually I'm in the opposite direction.
the last few months I've been working on a new system thats about to go online in the next few months.
busy as hell in architecture issues, coding issues and more...
i decided to take the opportunity of this project and Finlay get into the asp.net 2.0 .
so i tried to do some coding here

Convert.ToDotNet2(Shimon);

but that only returned an exception of InvalidCasting.
so, i sat on my bottom and started to learn all that is to know to introduce myself to the new features (yes, i know it's about time).

from what i can see, asp.net 2.0 will introduce to the world a lot of "drag&drop" programmers.
take for example the login controls that come built-in:

• it's great for the beginner programmer.
• this is one well of a !#@#!!# for an architect.

i mean, they coupled a GUI to a "generic" DB structure, Why ???
what if i want to manage my roles and permissions in other manner (say hierarchical roles...),
or just manage the user in my DB with all the other tables so i can do some easy data mining ?
to do that i need to write some providers to the controls that equals to implementing the business logic from scratch.
i will extent later on that matter (some other post...)

building this project as a one man show gave me an oppertunity of a vast view on a system besides playing with one module.
from now on, i'll continue update here the progress of the project.