OSQL is Unable to see SQL Server and MSDE 2000 on the same machine

I have installed SQL Server and MSDE 2000 on my laptop under Windows XP. But I am not able to access the MSDE 2000 instance via OSQL. When I issue the command "osql -L" it lists only the SQL server (named as VSDOTNET). The MSDE 2000 instance is named as M
SSQLSERVER. The enterprise manager does not see MSSQLSERVER either. When I use the command "osql -Slocalhost\mssqlserver -Usa" and enter the password, I get the error message "[DBNETLIB]Invalid Connection.." The SQLMODE is set to mixed mode. I can access
MSSQLSERVER through a third party software (DB2KManager) but not through OSQL. Any suggestion would be greatly appreciated.
hi
"Surya Yadav" <Surya.Yadav@.ttu.edu> ha scritto nel messaggio
news:ED1D3FFF-4398-4407-8676-A79A31018BC0@.microsoft.com...
> I have installed SQL Server and MSDE 2000 on my laptop under Windows XP.
But I am not able to
>access the MSDE 2000 instance via OSQL. When I issue the command "osql -L"
it lists only the SQL >server (named as VSDOTNET). The MSDE 2000 instance is
named as MSSQLSERVER. The >enterprise manager does not see MSSQLSERVER
either. When I use the command "osql ->Slocalhost\mssqlserver -Usa" and
enter the password, I get the error message "[DBNETLIB]Invalid
>Connection.." The SQLMODE is set to mixed mode. I can access MSSQLSERVER
through a third >party software (DB2KManager) but not through OSQL. Any
suggestion would be greatly appreciated.
when installing a named instance, it's full name is
ComputerName\InstanceName or (local)\InstanceName or LocalHost\InstanceName,
those , your instance will be known as
YourCoumpeterName\VSDOTNET
(Local)\VSDOTNET
Localhost\VSDOTNET
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi,
Can you please explain it again? What am I doing wrong when I type "osql -Slocalhost\mssqlserver -Usa" ? The service is running as MSSQLSERVER when I browse under the Services icon from the Administrative tools. At the installation time I did not specify
an instance name. Setup.exe created the default instance as MSSQLSERVER. Thanks.
|||hi,
"Surya Yadav" <surya.yadav@.ttu.edu> ha scritto nel messaggio
news:0ED30CB4-1E7C-4CDC-9BAF-FA3F0742C9F0@.microsoft.com...
> Hi,
> Can you please explain it again? What am I doing wrong when I type
"osql -Slocalhost\mssqlserver -
> Usa" ? The service is running as MSSQLSERVER when I browse under the
Services icon from the
> Administrative tools. At the installation time I did not specify an
instance name. Setup.exe created the
> default instance as MSSQLSERVER. Thanks.
you said your named instance was named VSDOTNET... in this case, the full
instance name is
ComputerName\InstanceName = YourComputerName\VSDOTNET
if the installed instance is the default instance, then it's name is just
(Local)
and/or
YourComputerName
c:\>osql -S(local) -Usa
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi I have the same problem:
Installed MSDE with default instance and could then connect to it from
QSQL.
Then I uninstalled it and installed with a named instance. Now I cant
connect:
With "osql -U sa -S servername\instancename" command... -
"[DBMSLPCN]SQL Server does not exist or access denied.
[DBMSLPCN]ConnectionOpen (Connect())."
But the SQL server Manager icon next to the clock indicate that it is
running...
Is the port 1050 correct - from the log file below..
Any help / ideas will be much appreciated. More detail follow below:
I use "MSDE2000A" with the service pack 3a
My install options was:
[Options]
INSTANCENAME="instancename"
TARGETDIR="E:\SQLServer_instancename"
SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0
In the error log file I found these:
====================================
2004-05-08 14:41:14.06 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-05-08 14:41:14.06 server All rights reserved.
2004-05-08 14:41:14.06 server Server Process ID is 2700.
2004-05-08 14:41:14.06 server Logging SQL Server messages in file
'E:\SQLServer_instancenameMSSQL$instancename\LOG\E RRORLOG'.
2004-05-08 14:41:14.06 server SQL Server is starting at priority
class 'normal'(2 CPUs detected).
2004-05-08 14:41:14.21 server SQL Server configured for thread mode
processing.
2004-05-08 14:41:14.21 server Using dynamic lock allocation. [500]
Lock Blocks, [1000] Lock Owner Blocks.
2004-05-08 14:41:14.26 spid4 Starting up database 'master'.
2004-05-08 14:41:14.32 server Using 'SSNETLIB.DLL' version
'8.0.766'.
2004-05-08 14:41:14.32 spid5 Starting up database 'model'.
2004-05-08 14:41:14.32 spid4 Server name is
'servername\instancename'.
2004-05-08 14:41:14.32 spid4 Skipping startup of clean database id
4
2004-05-08 14:41:14.34 server SQL server listening on 192.168.1.99:
1050.
2004-05-08 14:41:14.34 server SQL server listening on 127.0.0.1:
1050.
2004-05-08 14:41:14.37 spid5 Clearing tempdb database.
2004-05-08 14:41:14.40 spid5 Starting up database 'tempdb'.
2004-05-08 14:41:14.42 spid4 Recovery complete.
2004-05-08 14:41:14.42 spid4 SQL global counter collection task is
created.
2004-05-08 14:41:16.60 server SQL server listening on TCP, Shared
Memory, Named Pipes.
2004-05-08 14:41:16.60 server SQL Server is ready for client
connections