Problem installing pubs db in MSDE

On executing the following command:
osql -E -i instpubs.sql
I am getting the following error:
[Shared Memory] SQL Server does not exist or access denied.
[Shared Memory] ConnectionOpen (Connect())
The environment is:
1. Windows XP Professional
2. MSDE was installed using the download file 'SQL2kDeskSP3.exe' dated
5/24/2003.
3. Sample database scripts were installed using the download file
'SQL2000SampleDb.msi' dated 4/20/2004.
4. The osql command sequence was found in the
'ReadMe_SQL2000SampleDbScripts.htm', that was installed along with Sample DB
scripts.
I have done this successfully last year at my home computer. As far as I
remember, I have not used 'osql' to install the pubs and Nortwind databases.
But unfortunately, I don't remember how I did it earlier as my notes is
missing. Now I am doing it on a office computer. I am able to access the
MSDE server through VB.NET normally without any problem.
ThanQ...
Are you running OSQL on a local machine? Against a default instance?
Try specifying the server\instance name with the -S parameter.
This error doesn't have anything to do with the script you passed with the
-i parameter, it's an indication that SQL Server cannot be found (it isn't
started, name resolution isn't working, your protocol isn't accepted, etc.)
See: 328306 INF: Potential Causes of the "SQL Server Does Not Exist or
Access
http://support.microsoft.com/?id=328306
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thankyou for your prompt. Actually I tried -S parameter with either Computer
Name or Instance Name individually.
Now I tried with both of them separated by a back-slash. This is actually
the 3rd example in the read me doc. But I was interpreting the
'ComputerName/InstanceName' as 'Computer Name or Instance Name'.
Now it got installed. The syntax I used is:
osql -E -S <ComputerName>\<InstanceName> -i instpubs.sql
ThanQ...
"Cindy Gross (MSFT)" <cgross@.online.microsoft.com> wrote in message
news:iys4wrMKEHA.3048@.cpmsftngxa10.phx.gbl...
> Are you running OSQL on a local machine? Against a default instance?
> Try specifying the server\instance name with the -S parameter.
> This error doesn't have anything to do with the script you passed with the
> -i parameter, it's an indication that SQL Server cannot be found (it isn't
> started, name resolution isn't working, your protocol isn't accepted,
etc.)
> See: 328306 INF: Potential Causes of the "SQL Server Does Not Exist or
> Access
> http://support.microsoft.com/?id=328306
> Cindy Gross, MCDBA, MCSE
> http://cindygross.tripod.com
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>