I have a cluster SQL 2000 server running on Win2003
Because of a connection error, i found an article
http://support.microsoft.com/default.aspx?kbid=328306
in one section of this document, it suggests:
change the name pipe setting in server network utility to
\\.\pipe\sql\query
from my previous setting like
\\.\pipe\$$\virtualservername\sql\query
now my SQL service could not be started
and i can't access the server network utility to change back too
could someone help me out?
Thanks in advance...
this issue has been taken care by changing registry key back to default
and sql resource is back on line now...
"mike" wrote:
> I have a cluster SQL 2000 server running on Win2003
> Because of a connection error, i found an article
> http://support.microsoft.com/default.aspx?kbid=328306
> in one section of this document, it suggests:
> change the name pipe setting in server network utility to
> \\.\pipe\sql\query
> from my previous setting like
> \\.\pipe\$$\virtualservername\sql\query
> now my SQL service could not be started
> and i can't access the server network utility to change back too
> could someone help me out?
> Thanks in advance...
>
Wednesday, March 7, 2012
odbc sqldriverconnect failed
Labels:
cluster,
connection,
database,
error,
failed,
microsoft,
mysql,
odbc,
oracle,
running,
server,
sql,
sqldriverconnect,
win2003because
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment