|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
WTF? SVRNETCN.dll => ...80\tool\binn instead of ...\80\toolS\binnOur company has 1 licensed SQL Server, which is currently being used on our internal sharepoint site. It was an upgrade from MSDE to enable full-text, so the instance name is SHAREPOINT...not that I believe that matters. Having been asked to evaluate a help-desk package with a SQL Server back-end, I installed it to our server. I couldn't get it to connect, (because I forgot about the SHAREPOINT instance name) so I immediately uninstalled the package. Next, I opened OSQL to make sure the database it created got dropped properly... Well OSQL -S (local)\SHAREPOINT -E would not connect. Not only that, our portal site was down. I tried running SVRNETCN.exe to check on connectivity, and maybe try another protocol...and I kept getting a module not found error. I installed SP4 in the hope it would patch up whatever'd gone wrong... no luck there... Finally, I got out Depends.exe, and figured out that it couldn't load SVRNETCN.DLL Here's the deal... I was running: "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\SVRNETCN.exe" but it was looking to load "C:\Program Files\Microsoft SQL Server\80\Tool\Binn\SVRNETCN.dll" (for the tired eyes, the S in TOOLS is missing) I was able to get everything running again by creating a copy of the Tools folder called Tool But what happened? What's the real fix? |
|||||||||||||||||||||||