Cannot create INSTANCENAME

SVR: W2KADV SP4
MSDE is already running supporting Veritas Backup exec and another
application.
Attempting to configure WSUS.
Need to create a new INSTANCENAME=WSUS
Command line setup SAPWD="oursapwd" INSTANCENAME="WSUS"
What I get is this a blackened screen with "Windows 2000 Setup" in the upper
right hand corner. In the center of the screen is a blank menu box entitled
"Usage"
ERRORLOG: entries
2005-07-06 15:33:40.19 server Microsoft SQL Server 2000 - 8.00.818
(Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
2005-07-06 15:33:40.19 server Copyright (C) 1988-2002 Microsoft
Corporation.
2005-07-06 15:33:40.20 server All rights reserved.
2005-07-06 15:33:40.20 server Server Process ID is 9384.
2005-07-06 15:33:40.20 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
2005-07-06 15:33:40.20 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2005-07-06 15:33:40.31 server SQL Server configured for thread mode
processing.
2005-07-06 15:33:40.31 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-06 15:33:40.34 spid3 Starting up database 'master'.
2005-07-06 15:33:40.45 spid5 Starting up database 'model'.
2005-07-06 15:33:40.45 server Using 'SSNETLIB.DLL' version '8.0.818'.
2005-07-06 15:33:40.47 spid3 Server name is: "Left Blank".
2005-07-06 15:33:40.47 spid3 Skipping startup of clean database id 4
2005-07-06 15:33:40.47 spid3 Skipping startup of clean database id 5
2005-07-06 15:33:40.47 spid3 Starting up database 'SUSDB'.
2005-07-06 15:33:40.53 server SQL server listening on Shared Memory.
2005-07-06 15:33:40.53 server SQL Server is ready for client connections
2005-07-06 15:33:40.56 spid5 Clearing tempdb database.
2005-07-06 15:33:40.56 spid3 3 transactions rolled forward in database
'SUSDB' (6).
2005-07-06 15:33:40.58 spid3 0 transactions rolled back in database
'SUSDB' (6).
2005-07-06 15:33:40.58 spid3 Recovery is checkpointing database 'SUSDB'
(6)
2005-07-06 15:33:40.76 spid5 Starting up database 'tempdb'.
2005-07-06 15:33:40.80 spid3 Recovery complete.
2005-07-06 15:33:40.80 spid3 SQL global counter collection task is
created.
2005-07-06 15:33:43.64 spid51 Starting up database 'SUSDB'.
2005-07-06 15:48:59.22 spid52 Starting up database 'msdb'.
2005-07-06 15:48:59.44 spid52 Using 'xpsqlbot.dll' version '2000.80.760'
to execute extended stored procedure 'xp_qv'.
hi,
Lokton wrote:
> SVR: W2KADV SP4
> MSDE is already running supporting Veritas Backup exec and another
> application.
> Attempting to configure WSUS.
> Need to create a new INSTANCENAME=WSUS
> Command line setup SAPWD="oursapwd" INSTANCENAME="WSUS"
> What I get is this a blackened screen with "Windows 2000 Setup" in
> the upper right hand corner. In the center of the screen is a blank
> menu box entitled "Usage"
> ERRORLOG: entries
this is the error log of the default MSDE instance probably used by Veritas
and other sw...
if you are using the new sp4 ugraded MSDE installation package, please try
omitting the quotes surrounding "oursapwd" and "WSUS"
then please add the
/L*v "c:\msdelog.txt"
parameter to your call to setup.exe boostrap installer, in order to allow
verbose logging of the installation process.. should error(s) be raised a
RETURN VALUE 3
will be written to the log, and about 10/15 lines before each entry some
(sometime criptic) description of the problem will be reported...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Cannot Connect to Instance

Ok, I can connect to the sql server instances using
tcp:ServerName,PortNumber. However; I still cannot connect using
ServerName\InstanceName. This would not be a big deal, if I could get
Enterprise Manager on a remote machine to register the instance using the
tcp:ServerName,PortNumber format. I would still like to be able to register
the server in Enterprise Manager on a remote computer.sounds like a DNS issue...can you register using IPaddress\instance name?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Travis Lingenfelder" <TravisLingenfelder@.discussions.microsoft.com> wrote
in message news:DE60DF84-A796-4219-A2CE-86B7F99D4B0A@.microsoft.com...
> Ok, I can connect to the sql server instances using
> tcp:ServerName,PortNumber. However; I still cannot connect using
> ServerName\InstanceName. This would not be a big deal, if I could get
> Enterprise Manager on a remote machine to register the instance using the
> tcp:ServerName,PortNumber format. I would still like to be able to
> register
> the server in Enterprise Manager on a remote computer.
>|||Or...could be trying to use named pipes (or some other protocol) when you
are not specifying tcp...what protocols is theSQL server listening on?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Travis Lingenfelder" <TravisLingenfelder@.discussions.microsoft.com> wrote
in message news:DE60DF84-A796-4219-A2CE-86B7F99D4B0A@.microsoft.com...
> Ok, I can connect to the sql server instances using
> tcp:ServerName,PortNumber. However; I still cannot connect using
> ServerName\InstanceName. This would not be a big deal, if I could get
> Enterprise Manager on a remote machine to register the instance using the
> tcp:ServerName,PortNumber format. I would still like to be able to
> register
> the server in Enterprise Manager on a remote computer.
>|||I'm having the exact same problem. I can connect using this in my connectio
n
string:
Source=tcp:ServerName,1130
I know to use port 1130 because that's what the ERRORLOG file for that named
instance says it's currently listening on, but I don't think it's a good ide
a
to specify the port when it can change the next time the server is rebooted.
I know it's not a DNS issue, I can ping myDBserver.acme.com, or even just
myDBserver and get replies. Not only that, the the above source parameter
obviously resolves properly to the right IP address.
The server is listening on TCP/IP and Named Pipe.
Trying to connect using the following do not work:
Source=ServerName\InstanceName,1130
Source=ServerName\InstanceName
Source=192.168.10.4\InstanceName
Source=192.168.10.4\InstanceName,1130
I'm trying to connect to SQL Server 2000 SP4 from a web server (classic ASP
on IIS 5.0). The strange thing is that I can run Query Analyzer from the we
b
server and connect using ServerName\InstanceName. The web site can't.
According to MDAC component checker, the web server is running MDAC 2.7 SP1.
I'll run the SQL Server SP4 on the web server to update the SQL Tools.
Unless I'm mistaken, that should also update MDAC to 2.8. We'll see if that
fixes it.
Anyone can add to this? Any ideas as to what else I can do to troubleshoot
this?
Thanks,
Francois
"Kevin3NF" wrote:

> Or...could be trying to use named pipes (or some other protocol) when you
> are not specifying tcp...what protocols is theSQL server listening on?
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Travis Lingenfelder" <TravisLingenfelder@.discussions.microsoft.com> wrote
> in message news:DE60DF84-A796-4219-A2CE-86B7F99D4B0A@.microsoft.com...
>
>|||Well, updating MDAC to the latest, by applying SQL Server SP4, didn't change
anything.
What else can I do to troubleshoot this?
Any help would be greatly appreciated...
Francois
"Francois" wrote:
[vbcol=seagreen]
> I'm having the exact same problem. I can connect using this in my connect
ion
> string:
> Source=tcp:ServerName,1130
> I know to use port 1130 because that's what the ERRORLOG file for that nam
ed
> instance says it's currently listening on, but I don't think it's a good i
dea
> to specify the port when it can change the next time the server is reboote
d.
> I know it's not a DNS issue, I can ping myDBserver.acme.com, or even just
> myDBserver and get replies. Not only that, the the above source parameter
> obviously resolves properly to the right IP address.
> The server is listening on TCP/IP and Named Pipe.
> Trying to connect using the following do not work:
> Source=ServerName\InstanceName,1130
> Source=ServerName\InstanceName
> Source=192.168.10.4\InstanceName
> Source=192.168.10.4\InstanceName,1130
> I'm trying to connect to SQL Server 2000 SP4 from a web server (classic AS
P
> on IIS 5.0). The strange thing is that I can run Query Analyzer from the
web
> server and connect using ServerName\InstanceName. The web site can't.
> According to MDAC component checker, the web server is running MDAC 2.7 SP
1.
> I'll run the SQL Server SP4 on the web server to update the SQL Tools.
> Unless I'm mistaken, that should also update MDAC to 2.8. We'll see if th
at
> fixes it.
> Anyone can add to this? Any ideas as to what else I can do to troubleshoo
t
> this?
> Thanks,
> Francois
>
> "Kevin3NF" wrote:
>

Cannot Connect to Instance

Ok, I can connect to the sql server instances using
tcp:ServerName,PortNumber. However; I still cannot connect using
ServerName\InstanceName. This would not be a big deal, if I could get
Enterprise Manager on a remote machine to register the instance using the
tcp:ServerName,PortNumber format. I would still like to be able to register
the server in Enterprise Manager on a remote computer.
sounds like a DNS issue...can you register using IPaddress\instance name?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Travis Lingenfelder" <TravisLingenfelder@.discussions.microsoft.com> wrote
in message news:DE60DF84-A796-4219-A2CE-86B7F99D4B0A@.microsoft.com...
> Ok, I can connect to the sql server instances using
> tcp:ServerName,PortNumber. However; I still cannot connect using
> ServerName\InstanceName. This would not be a big deal, if I could get
> Enterprise Manager on a remote machine to register the instance using the
> tcp:ServerName,PortNumber format. I would still like to be able to
> register
> the server in Enterprise Manager on a remote computer.
>
|||Or...could be trying to use named pipes (or some other protocol) when you
are not specifying tcp...what protocols is theSQL server listening on?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Travis Lingenfelder" <TravisLingenfelder@.discussions.microsoft.com> wrote
in message news:DE60DF84-A796-4219-A2CE-86B7F99D4B0A@.microsoft.com...
> Ok, I can connect to the sql server instances using
> tcp:ServerName,PortNumber. However; I still cannot connect using
> ServerName\InstanceName. This would not be a big deal, if I could get
> Enterprise Manager on a remote machine to register the instance using the
> tcp:ServerName,PortNumber format. I would still like to be able to
> register
> the server in Enterprise Manager on a remote computer.
>
|||I'm having the exact same problem. I can connect using this in my connection
string:
Source=tcp:ServerName,1130
I know to use port 1130 because that's what the ERRORLOG file for that named
instance says it's currently listening on, but I don't think it's a good idea
to specify the port when it can change the next time the server is rebooted.
I know it's not a DNS issue, I can ping myDBserver.acme.com, or even just
myDBserver and get replies. Not only that, the the above source parameter
obviously resolves properly to the right IP address.
The server is listening on TCP/IP and Named Pipe.
Trying to connect using the following do not work:
Source=ServerName\InstanceName,1130
Source=ServerName\InstanceName
Source=192.168.10.4\InstanceName
Source=192.168.10.4\InstanceName,1130
I'm trying to connect to SQL Server 2000 SP4 from a web server (classic ASP
on IIS 5.0). The strange thing is that I can run Query Analyzer from the web
server and connect using ServerName\InstanceName. The web site can't.
According to MDAC component checker, the web server is running MDAC 2.7 SP1.
I'll run the SQL Server SP4 on the web server to update the SQL Tools.
Unless I'm mistaken, that should also update MDAC to 2.8. We'll see if that
fixes it.
Anyone can add to this? Any ideas as to what else I can do to troubleshoot
this?
Thanks,
Francois
"Kevin3NF" wrote:

> Or...could be trying to use named pipes (or some other protocol) when you
> are not specifying tcp...what protocols is theSQL server listening on?
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Travis Lingenfelder" <TravisLingenfelder@.discussions.microsoft.com> wrote
> in message news:DE60DF84-A796-4219-A2CE-86B7F99D4B0A@.microsoft.com...
>
>
|||Well, updating MDAC to the latest, by applying SQL Server SP4, didn't change
anything.
What else can I do to troubleshoot this?
Any help would be greatly appreciated...
Francois
"Francois" wrote:
[vbcol=seagreen]
> I'm having the exact same problem. I can connect using this in my connection
> string:
> Source=tcp:ServerName,1130
> I know to use port 1130 because that's what the ERRORLOG file for that named
> instance says it's currently listening on, but I don't think it's a good idea
> to specify the port when it can change the next time the server is rebooted.
> I know it's not a DNS issue, I can ping myDBserver.acme.com, or even just
> myDBserver and get replies. Not only that, the the above source parameter
> obviously resolves properly to the right IP address.
> The server is listening on TCP/IP and Named Pipe.
> Trying to connect using the following do not work:
> Source=ServerName\InstanceName,1130
> Source=ServerName\InstanceName
> Source=192.168.10.4\InstanceName
> Source=192.168.10.4\InstanceName,1130
> I'm trying to connect to SQL Server 2000 SP4 from a web server (classic ASP
> on IIS 5.0). The strange thing is that I can run Query Analyzer from the web
> server and connect using ServerName\InstanceName. The web site can't.
> According to MDAC component checker, the web server is running MDAC 2.7 SP1.
> I'll run the SQL Server SP4 on the web server to update the SQL Tools.
> Unless I'm mistaken, that should also update MDAC to 2.8. We'll see if that
> fixes it.
> Anyone can add to this? Any ideas as to what else I can do to troubleshoot
> this?
> Thanks,
> Francois
>
> "Kevin3NF" wrote: