installing 2nd instance

I am trying to install a second instance of sql server 2000. I am running xp
pro and using the developer edition. When I run the install, it completes
normally. The registry has entries for the new named instance. When I try
to register the new server using enterprise manager and add it to a group,
first the wizard does not list the new name. If I type in the name and
proceed, I eventually get an error message saying "sql server does not exist
or access denied. ..." The error log shows that it gets part way with
starting the service but then is stopped before completing. I don't remember
now the limitations on the Developer Edition, is this one of them or is there
another problem? I am using mixed mode with an sa login.
--
JBWhat did the error log say was the issue?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"JB" <JB@.discussions.microsoft.com> wrote in message
news:03A65A47-1ADD-42AD-86A5-B937A651A346@.microsoft.com...
I am trying to install a second instance of sql server 2000. I am running
xp
pro and using the developer edition. When I run the install, it completes
normally. The registry has entries for the new named instance. When I try
to register the new server using enterprise manager and add it to a group,
first the wizard does not list the new name. If I type in the name and
proceed, I eventually get an error message saying "sql server does not exist
or access denied. ..." The error log shows that it gets part way with
starting the service but then is stopped before completing. I don't
remember
now the limitations on the Developer Edition, is this one of them or is
there
another problem? I am using mixed mode with an sa login.
--
JB|||Here is the whole lot:
2006-09-24 20:56:50.54 server Copyright (C) 1988-2000 Microsoft
Corporation.
2006-09-24 20:56:50.54 server All rights reserved.
2006-09-24 20:56:50.54 server Server Process ID is 160.
2006-09-24 20:56:50.54 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$LJBUILDER_SC\log\ERRORLOG'.
2006-09-24 20:56:50.56 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2006-09-24 20:56:50.56 server SQL Server configured for thread mode
processing.
2006-09-24 20:56:50.56 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2006-09-24 20:56:50.59 server Attempting to initialize Distributed
Transaction Coordinator.
2006-09-24 20:56:50.60 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
2006-09-24 20:56:50.62 spid3 Warning ******************
2006-09-24 20:56:50.62 spid3 SQL Server started in single user mode.
Updates allowed to system catalogs.
2006-09-24 20:56:50.62 spid3 Starting up database 'master'.
2006-09-24 20:56:50.82 server Using 'SSNETLIB.DLL' version '8.0.311'.
2006-09-24 20:56:50.82 spid3 Server name is 'LJDESIGNS\LJBUILDER_SC'.
2006-09-24 20:56:50.82 spid5 Starting up database 'model'.
2006-09-24 20:56:50.82 spid7 Starting up database 'msdb'.
2006-09-24 20:56:50.82 spid8 Starting up database 'pubs'.
2006-09-24 20:56:50.82 spid9 Starting up database 'Northwind'.
2006-09-24 20:56:51.04 server SQL server listening on 127.0.0.1: 1032.
2006-09-24 20:56:51.06 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-09-24 20:56:51.06 server SQL Server is ready for client connections
2006-09-24 20:56:51.57 spid5 Clearing tempdb database.
2006-09-24 20:56:52.70 spid5 Starting up database 'tempdb'.
2006-09-24 20:56:52.84 spid3 Recovery complete.
2006-09-24 20:56:52.89 spid3 Warning: override, autoexec procedures
skipped.
2006-09-24 20:57:03.01 spid51 Error: 15457, Severity: 0, State: 1
2006-09-24 20:57:03.01 spid51 Configuration option 'allow updates'
changed from 0 to 1. Run the RECONFIGURE statement to install..
2006-09-24 20:57:03.09 spid51 Error: 15457, Severity: 0, State: 1
2006-09-24 20:57:03.09 spid51 Configuration option 'allow updates'
changed from 1 to 0. Run the RECONFIGURE statement to install..
2006-09-24 20:57:03.65 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
--
JB
"JB" wrote:
> I am trying to install a second instance of sql server 2000. I am running xp
> pro and using the developer edition. When I run the install, it completes
> normally. The registry has entries for the new named instance. When I try
> to register the new server using enterprise manager and add it to a group,
> first the wizard does not list the new name. If I type in the name and
> proceed, I eventually get an error message saying "sql server does not exist
> or access denied. ..." The error log shows that it gets part way with
> starting the service but then is stopped before completing. I don't remember
> now the limitations on the Developer Edition, is this one of them or is there
> another problem? I am using mixed mode with an sa login.
> --
> JB|||Have you tried applying SP3a or SP4? It's not clear what the build number
of SQL Server is. This is on Windows 2003, right?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"JB" <JB@.discussions.microsoft.com> wrote in message
news:1B35467F-FEA8-47E1-BB94-3DA14D172E97@.microsoft.com...
Here is the whole lot:
2006-09-24 20:56:50.54 server Copyright (C) 1988-2000 Microsoft
Corporation.
2006-09-24 20:56:50.54 server All rights reserved.
2006-09-24 20:56:50.54 server Server Process ID is 160.
2006-09-24 20:56:50.54 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$LJBUILDER_SC\log\ERRORLOG'.
2006-09-24 20:56:50.56 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2006-09-24 20:56:50.56 server SQL Server configured for thread mode
processing.
2006-09-24 20:56:50.56 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2006-09-24 20:56:50.59 server Attempting to initialize Distributed
Transaction Coordinator.
2006-09-24 20:56:50.60 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
2006-09-24 20:56:50.62 spid3 Warning ******************
2006-09-24 20:56:50.62 spid3 SQL Server started in single user mode.
Updates allowed to system catalogs.
2006-09-24 20:56:50.62 spid3 Starting up database 'master'.
2006-09-24 20:56:50.82 server Using 'SSNETLIB.DLL' version '8.0.311'.
2006-09-24 20:56:50.82 spid3 Server name is 'LJDESIGNS\LJBUILDER_SC'.
2006-09-24 20:56:50.82 spid5 Starting up database 'model'.
2006-09-24 20:56:50.82 spid7 Starting up database 'msdb'.
2006-09-24 20:56:50.82 spid8 Starting up database 'pubs'.
2006-09-24 20:56:50.82 spid9 Starting up database 'Northwind'.
2006-09-24 20:56:51.04 server SQL server listening on 127.0.0.1: 1032.
2006-09-24 20:56:51.06 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-09-24 20:56:51.06 server SQL Server is ready for client connections
2006-09-24 20:56:51.57 spid5 Clearing tempdb database.
2006-09-24 20:56:52.70 spid5 Starting up database 'tempdb'.
2006-09-24 20:56:52.84 spid3 Recovery complete.
2006-09-24 20:56:52.89 spid3 Warning: override, autoexec procedures
skipped.
2006-09-24 20:57:03.01 spid51 Error: 15457, Severity: 0, State: 1
2006-09-24 20:57:03.01 spid51 Configuration option 'allow updates'
changed from 0 to 1. Run the RECONFIGURE statement to install..
2006-09-24 20:57:03.09 spid51 Error: 15457, Severity: 0, State: 1
2006-09-24 20:57:03.09 spid51 Configuration option 'allow updates'
changed from 1 to 0. Run the RECONFIGURE statement to install..
2006-09-24 20:57:03.65 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
--
JB
"JB" wrote:
> I am trying to install a second instance of sql server 2000. I am running
> xp
> pro and using the developer edition. When I run the install, it completes
> normally. The registry has entries for the new named instance. When I
> try
> to register the new server using enterprise manager and add it to a group,
> first the wizard does not list the new name. If I type in the name and
> proceed, I eventually get an error message saying "sql server does not
> exist
> or access denied. ..." The error log shows that it gets part way with
> starting the service but then is stopped before completing. I don't
> remember
> now the limitations on the Developer Edition, is this one of them or is
> there
> another problem? I am using mixed mode with an sa login.
> --
> JB|||Per your suggestion. I first installed sp3a on the existing instance of SQL
Server(default instance). This ran without problems and the instance runs
ok. Then I ran the install for 2nd (named) instance. There aren't many
options during the install. I generally clicked Next. On one page, my user
name was displayed along with the domain. I entered my password. A page or
two later, I selected mixed mode and entered the sa password. The intall
seemed to go without any problems. When I then started Enterprise manager to
register the server, first it does not list the new instance in the select a
server page. If I type in the name and continue, I eventually get the
error, "sql server does not exist or access denied
ConnectionOpen(Connect()). Same as before. Then I tried to run sp3a on the
just installed named instance. The setup sees the new instance(i.e. it shows
in a list of instances to upgrade) but when I select the instance and
proceed, eventually I get the error "a service control operation failed for
MSSQL$LJDESIGNS_SC service: 1069 The service did not start due to a logon
failure." I am running windows xp pro sp 2.
--
JB
"Tom Moreau" wrote:
> Have you tried applying SP3a or SP4? It's not clear what the build number
> of SQL Server is. This is on Windows 2003, right?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> ..
> "JB" <JB@.discussions.microsoft.com> wrote in message
> news:1B35467F-FEA8-47E1-BB94-3DA14D172E97@.microsoft.com...
> Here is the whole lot:
> 2006-09-24 20:56:50.54 server Copyright (C) 1988-2000 Microsoft
> Corporation.
> 2006-09-24 20:56:50.54 server All rights reserved.
> 2006-09-24 20:56:50.54 server Server Process ID is 160.
> 2006-09-24 20:56:50.54 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$LJBUILDER_SC\log\ERRORLOG'.
> 2006-09-24 20:56:50.56 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2006-09-24 20:56:50.56 server SQL Server configured for thread mode
> processing.
> 2006-09-24 20:56:50.56 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2006-09-24 20:56:50.59 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2006-09-24 20:56:50.60 server Failed to obtain
> TransactionDispenserInterface: Result Code = 0x8004d01b
> 2006-09-24 20:56:50.62 spid3 Warning ******************
> 2006-09-24 20:56:50.62 spid3 SQL Server started in single user mode.
> Updates allowed to system catalogs.
> 2006-09-24 20:56:50.62 spid3 Starting up database 'master'.
> 2006-09-24 20:56:50.82 server Using 'SSNETLIB.DLL' version '8.0.311'.
> 2006-09-24 20:56:50.82 spid3 Server name is 'LJDESIGNS\LJBUILDER_SC'.
> 2006-09-24 20:56:50.82 spid5 Starting up database 'model'.
> 2006-09-24 20:56:50.82 spid7 Starting up database 'msdb'.
> 2006-09-24 20:56:50.82 spid8 Starting up database 'pubs'.
> 2006-09-24 20:56:50.82 spid9 Starting up database 'Northwind'.
> 2006-09-24 20:56:51.04 server SQL server listening on 127.0.0.1: 1032.
> 2006-09-24 20:56:51.06 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
> 2006-09-24 20:56:51.06 server SQL Server is ready for client connections
> 2006-09-24 20:56:51.57 spid5 Clearing tempdb database.
> 2006-09-24 20:56:52.70 spid5 Starting up database 'tempdb'.
> 2006-09-24 20:56:52.84 spid3 Recovery complete.
> 2006-09-24 20:56:52.89 spid3 Warning: override, autoexec procedures
> skipped.
> 2006-09-24 20:57:03.01 spid51 Error: 15457, Severity: 0, State: 1
> 2006-09-24 20:57:03.01 spid51 Configuration option 'allow updates'
> changed from 0 to 1. Run the RECONFIGURE statement to install..
> 2006-09-24 20:57:03.09 spid51 Error: 15457, Severity: 0, State: 1
> 2006-09-24 20:57:03.09 spid51 Configuration option 'allow updates'
> changed from 1 to 0. Run the RECONFIGURE statement to install..
> 2006-09-24 20:57:03.65 spid3 SQL Server is terminating due to 'stop'
> request from Service Control Manager.
> --
> JB
>
> "JB" wrote:
> > I am trying to install a second instance of sql server 2000. I am running
> > xp
> > pro and using the developer edition. When I run the install, it completes
> > normally. The registry has entries for the new named instance. When I
> > try
> > to register the new server using enterprise manager and add it to a group,
> > first the wizard does not list the new name. If I type in the name and
> > proceed, I eventually get an error message saying "sql server does not
> > exist
> > or access denied. ..." The error log shows that it gets part way with
> > starting the service but then is stopped before completing. I don't
> > remember
> > now the limitations on the Developer Edition, is this one of them or is
> > there
> > another problem? I am using mixed mode with an sa login.
> > --
> > JB
>|||What are you typing in for the name? ServerName\InstanceName
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"JB" <JB@.discussions.microsoft.com> wrote in message
news:C333117C-0509-4459-AD9D-5DEB8566E122@.microsoft.com...
> Per your suggestion. I first installed sp3a on the existing instance of
> SQL
> Server(default instance). This ran without problems and the instance runs
> ok. Then I ran the install for 2nd (named) instance. There aren't many
> options during the install. I generally clicked Next. On one page, my
> user
> name was displayed along with the domain. I entered my password. A page
> or
> two later, I selected mixed mode and entered the sa password. The intall
> seemed to go without any problems. When I then started Enterprise manager
> to
> register the server, first it does not list the new instance in the select
> a
> server page. If I type in the name and continue, I eventually get the
> error, "sql server does not exist or access denied
> ConnectionOpen(Connect()). Same as before. Then I tried to run sp3a on
> the
> just installed named instance. The setup sees the new instance(i.e. it
> shows
> in a list of instances to upgrade) but when I select the instance and
> proceed, eventually I get the error "a service control operation failed
> for
> MSSQL$LJDESIGNS_SC service: 1069 The service did not start due to a logon
> failure." I am running windows xp pro sp 2.
> --
> JB
>
> "Tom Moreau" wrote:
>> Have you tried applying SP3a or SP4? It's not clear what the build
>> number
>> of SQL Server is. This is on Windows 2003, right?
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> ..
>> "JB" <JB@.discussions.microsoft.com> wrote in message
>> news:1B35467F-FEA8-47E1-BB94-3DA14D172E97@.microsoft.com...
>> Here is the whole lot:
>> 2006-09-24 20:56:50.54 server Copyright (C) 1988-2000 Microsoft
>> Corporation.
>> 2006-09-24 20:56:50.54 server All rights reserved.
>> 2006-09-24 20:56:50.54 server Server Process ID is 160.
>> 2006-09-24 20:56:50.54 server Logging SQL Server messages in file
>> 'C:\Program Files\Microsoft SQL Server\MSSQL$LJBUILDER_SC\log\ERRORLOG'.
>> 2006-09-24 20:56:50.56 server SQL Server is starting at priority class
>> 'normal'(2 CPUs detected).
>> 2006-09-24 20:56:50.56 server SQL Server configured for thread mode
>> processing.
>> 2006-09-24 20:56:50.56 server Using dynamic lock allocation. [2500]
>> Lock
>> Blocks, [5000] Lock Owner Blocks.
>> 2006-09-24 20:56:50.59 server Attempting to initialize Distributed
>> Transaction Coordinator.
>> 2006-09-24 20:56:50.60 server Failed to obtain
>> TransactionDispenserInterface: Result Code = 0x8004d01b
>> 2006-09-24 20:56:50.62 spid3 Warning ******************
>> 2006-09-24 20:56:50.62 spid3 SQL Server started in single user mode.
>> Updates allowed to system catalogs.
>> 2006-09-24 20:56:50.62 spid3 Starting up database 'master'.
>> 2006-09-24 20:56:50.82 server Using 'SSNETLIB.DLL' version '8.0.311'.
>> 2006-09-24 20:56:50.82 spid3 Server name is 'LJDESIGNS\LJBUILDER_SC'.
>> 2006-09-24 20:56:50.82 spid5 Starting up database 'model'.
>> 2006-09-24 20:56:50.82 spid7 Starting up database 'msdb'.
>> 2006-09-24 20:56:50.82 spid8 Starting up database 'pubs'.
>> 2006-09-24 20:56:50.82 spid9 Starting up database 'Northwind'.
>> 2006-09-24 20:56:51.04 server SQL server listening on 127.0.0.1: 1032.
>> 2006-09-24 20:56:51.06 server SQL server listening on TCP, Shared
>> Memory,
>> Named Pipes.
>> 2006-09-24 20:56:51.06 server SQL Server is ready for client
>> connections
>> 2006-09-24 20:56:51.57 spid5 Clearing tempdb database.
>> 2006-09-24 20:56:52.70 spid5 Starting up database 'tempdb'.
>> 2006-09-24 20:56:52.84 spid3 Recovery complete.
>> 2006-09-24 20:56:52.89 spid3 Warning: override, autoexec procedures
>> skipped.
>> 2006-09-24 20:57:03.01 spid51 Error: 15457, Severity: 0, State: 1
>> 2006-09-24 20:57:03.01 spid51 Configuration option 'allow updates'
>> changed from 0 to 1. Run the RECONFIGURE statement to install..
>> 2006-09-24 20:57:03.09 spid51 Error: 15457, Severity: 0, State: 1
>> 2006-09-24 20:57:03.09 spid51 Configuration option 'allow updates'
>> changed from 1 to 0. Run the RECONFIGURE statement to install..
>> 2006-09-24 20:57:03.65 spid3 SQL Server is terminating due to 'stop'
>> request from Service Control Manager.
>> --
>> JB
>>
>> "JB" wrote:
>> > I am trying to install a second instance of sql server 2000. I am
>> > running
>> > xp
>> > pro and using the developer edition. When I run the install, it
>> > completes
>> > normally. The registry has entries for the new named instance. When I
>> > try
>> > to register the new server using enterprise manager and add it to a
>> > group,
>> > first the wizard does not list the new name. If I type in the name and
>> > proceed, I eventually get an error message saying "sql server does not
>> > exist
>> > or access denied. ..." The error log shows that it gets part way with
>> > starting the service but then is stopped before completing. I don't
>> > remember
>> > now the limitations on the Developer Edition, is this one of them or is
>> > there
>> > another problem? I am using mixed mode with an sa login.
>> > --
>> > JB
>>|||I typed in just the instance name. I am on the road for a day or two and
won't be able to try servername\instancename until I return to my office.
However, when I tried to run sp3a againt the new instance, it showed
instancename in the selection list. sp3a was then was unable to connect to
the instance and as a result, the sp3a upgrade failed to run. It that case,
there was no issue with servername\instancename since I didn't need to type
anything. In both the sp3a upgrade and register server cases, sql recognizes
that the instance is there, it just cannot make a connection. The failure
has to do with logon but I can't see what the problem is.
--
JB
"Roger Wolter[MSFT]" wrote:
> What are you typing in for the name? ServerName\InstanceName
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "JB" <JB@.discussions.microsoft.com> wrote in message
> news:C333117C-0509-4459-AD9D-5DEB8566E122@.microsoft.com...
> > Per your suggestion. I first installed sp3a on the existing instance of
> > SQL
> > Server(default instance). This ran without problems and the instance runs
> > ok. Then I ran the install for 2nd (named) instance. There aren't many
> > options during the install. I generally clicked Next. On one page, my
> > user
> > name was displayed along with the domain. I entered my password. A page
> > or
> > two later, I selected mixed mode and entered the sa password. The intall
> > seemed to go without any problems. When I then started Enterprise manager
> > to
> > register the server, first it does not list the new instance in the select
> > a
> > server page. If I type in the name and continue, I eventually get the
> > error, "sql server does not exist or access denied
> > ConnectionOpen(Connect()). Same as before. Then I tried to run sp3a on
> > the
> > just installed named instance. The setup sees the new instance(i.e. it
> > shows
> > in a list of instances to upgrade) but when I select the instance and
> > proceed, eventually I get the error "a service control operation failed
> > for
> > MSSQL$LJDESIGNS_SC service: 1069 The service did not start due to a logon
> > failure." I am running windows xp pro sp 2.
> > --
> > JB
> >
> >
> > "Tom Moreau" wrote:
> >
> >> Have you tried applying SP3a or SP4? It's not clear what the build
> >> number
> >> of SQL Server is. This is on Windows 2003, right?
> >>
> >> --
> >> Tom
> >>
> >> ----
> >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> >> SQL Server MVP
> >> Toronto, ON Canada
> >> ..
> >> "JB" <JB@.discussions.microsoft.com> wrote in message
> >> news:1B35467F-FEA8-47E1-BB94-3DA14D172E97@.microsoft.com...
> >> Here is the whole lot:
> >>
> >> 2006-09-24 20:56:50.54 server Copyright (C) 1988-2000 Microsoft
> >> Corporation.
> >> 2006-09-24 20:56:50.54 server All rights reserved.
> >> 2006-09-24 20:56:50.54 server Server Process ID is 160.
> >> 2006-09-24 20:56:50.54 server Logging SQL Server messages in file
> >> 'C:\Program Files\Microsoft SQL Server\MSSQL$LJBUILDER_SC\log\ERRORLOG'.
> >> 2006-09-24 20:56:50.56 server SQL Server is starting at priority class
> >> 'normal'(2 CPUs detected).
> >> 2006-09-24 20:56:50.56 server SQL Server configured for thread mode
> >> processing.
> >> 2006-09-24 20:56:50.56 server Using dynamic lock allocation. [2500]
> >> Lock
> >> Blocks, [5000] Lock Owner Blocks.
> >> 2006-09-24 20:56:50.59 server Attempting to initialize Distributed
> >> Transaction Coordinator.
> >> 2006-09-24 20:56:50.60 server Failed to obtain
> >> TransactionDispenserInterface: Result Code = 0x8004d01b
> >> 2006-09-24 20:56:50.62 spid3 Warning ******************
> >> 2006-09-24 20:56:50.62 spid3 SQL Server started in single user mode.
> >> Updates allowed to system catalogs.
> >> 2006-09-24 20:56:50.62 spid3 Starting up database 'master'.
> >> 2006-09-24 20:56:50.82 server Using 'SSNETLIB.DLL' version '8.0.311'.
> >> 2006-09-24 20:56:50.82 spid3 Server name is 'LJDESIGNS\LJBUILDER_SC'.
> >> 2006-09-24 20:56:50.82 spid5 Starting up database 'model'.
> >> 2006-09-24 20:56:50.82 spid7 Starting up database 'msdb'.
> >> 2006-09-24 20:56:50.82 spid8 Starting up database 'pubs'.
> >> 2006-09-24 20:56:50.82 spid9 Starting up database 'Northwind'.
> >> 2006-09-24 20:56:51.04 server SQL server listening on 127.0.0.1: 1032.
> >> 2006-09-24 20:56:51.06 server SQL server listening on TCP, Shared
> >> Memory,
> >> Named Pipes.
> >> 2006-09-24 20:56:51.06 server SQL Server is ready for client
> >> connections
> >> 2006-09-24 20:56:51.57 spid5 Clearing tempdb database.
> >> 2006-09-24 20:56:52.70 spid5 Starting up database 'tempdb'.
> >> 2006-09-24 20:56:52.84 spid3 Recovery complete.
> >> 2006-09-24 20:56:52.89 spid3 Warning: override, autoexec procedures
> >> skipped.
> >> 2006-09-24 20:57:03.01 spid51 Error: 15457, Severity: 0, State: 1
> >> 2006-09-24 20:57:03.01 spid51 Configuration option 'allow updates'
> >> changed from 0 to 1. Run the RECONFIGURE statement to install..
> >> 2006-09-24 20:57:03.09 spid51 Error: 15457, Severity: 0, State: 1
> >> 2006-09-24 20:57:03.09 spid51 Configuration option 'allow updates'
> >> changed from 1 to 0. Run the RECONFIGURE statement to install..
> >> 2006-09-24 20:57:03.65 spid3 SQL Server is terminating due to 'stop'
> >> request from Service Control Manager.
> >>
> >> --
> >> JB
> >>
> >>
> >> "JB" wrote:
> >>
> >> > I am trying to install a second instance of sql server 2000. I am
> >> > running
> >> > xp
> >> > pro and using the developer edition. When I run the install, it
> >> > completes
> >> > normally. The registry has entries for the new named instance. When I
> >> > try
> >> > to register the new server using enterprise manager and add it to a
> >> > group,
> >> > first the wizard does not list the new name. If I type in the name and
> >> > proceed, I eventually get an error message saying "sql server does not
> >> > exist
> >> > or access denied. ..." The error log shows that it gets part way with
> >> > starting the service but then is stopped before completing. I don't
> >> > remember
> >> > now the limitations on the Developer Edition, is this one of them or is
> >> > there
> >> > another problem? I am using mixed mode with an sa login.
> >> > --
> >> > JB
> >>
> >>
>
>