>-----Original Message-----
>I fit was a communication error with OLEDB then surely
even after you
>rebooted it would still be the same version of OLEDB and
the same connection
>method.
>
>Network Card ?
>
>--
>
>----------------------------
>Allan Mitchell (Microsoft SQL Server MVP)
>MCSE,MCDBA
>www.SQLDTS.com
>I support PASS - the definitive, global community
>for SQL Server professionals - http://www.sqlpass.org
>
>
>
>"Nurullah" <nurullah@infozech.com> wrote in message
>news:0ba001c367e5$2dea7e20$a501280a@phx.gbl...
>> Everything is fine. The same application connects to the
>> database once I restart the machine. Even restarting the
>> sql server is not enough.
>> Could it be an issue related with OLEDB? I am using ADO
>> for connection from VB application to SQL server 2000
>> database.
>>
>> Nurullah
>>
>> >-----Original Message-----
>> >Have you checked the name of the server that you pass
to
>> your connection
>> >string ? It could be that although you think it is
>> passing the name
>> >correctly there may be a space in there or the
>> connectionstring is not
>> >formatted properly.
>> >
>> >Just a thought.
>> >
>> >--
>> >
>> >----------------------------
>> >Allan Mitchell (Microsoft SQL Server MVP)
>> >MCSE,MCDBA
>> >www.SQLDTS.com
>> >I support PASS - the definitive, global community
>> >for SQL Server professionals - http://www.sqlpass.org
>> >
>> >
>> >
>> >"Nurullah" <nurullah@infozech.com> wrote in message
>> >news:0f6d01c36737$2ab568e0$a501280a@phx.gbl...
>> >> Hi,
>> >>
>> >> I have a client application written in VB, which is
>> >> connecting to a SQL server 2000 database running on
>> >> Windows 2000 server OS, using ADO.
>> >> I am facing problem in connecting to the the
database.
>> The
>> >> error i receive is "Specified SQL server no found". I
>> >> restarted the SQL server. I am able to connect to the
>> >> database through Query Analyzer. I am able to
connect to
>> >> other SQL server 2000 database throughg the same VB
>> >> application. So everything is fine with VB
application
>> and
>> >> SQL server. WHY DO I THEN RECEIVE this error message?
>> How
>> >> can I solve the problem without restarting the server
>> >> machine?
>> >>
>> >> Nurullah
>> >
>> >
>> >.
>> >
>
>
>.