>I am running one Windows 2000 Server with Microsoft SQL Server 2000 RTM and
>one Windows 2003 Server with Microsoft SQL Server 2000 RTM currently and have
>not had any problems with viruses or applications or databases created for
>years. 
>
>Except that the other day I installed an application called TrackIt! and now
>the SQL Server 2000 on the Windows 2000 Server box is displaying the
>following in the SQL Server Logs(Complete Export after Installing Dell
>OpenManage and had to reboot):
>
>Date    Source    Message
>2007-04-16 13:43:01.09     server    Microsoft SQL Server  2000 - 8.00.194 (Intel
>X86) ...
>2007-04-16 13:43:01.10     server    Logging SQL Server messages in file
>'e:\MSSQLSERVER\DATA\MSSQL\log\ERRORLOG'.
>2007-04-16 13:43:01.10     server    Server Process ID is 1016.
>2007-04-16 13:43:01.10     server    All rights reserved.
>2007-04-16 13:43:01.10     server    Copyright (C) 1988-2000 Microsoft Corporation.
>2007-04-16 13:43:01.23     server    SQL Server is starting at priority class
>'normal'(2 CPUs detected).
>2007-04-16 13:43:02.20     server    SQL Server configured for thread mode
>processing.
>2007-04-16 13:43:02.24     server    Using dynamic lock allocation. [2500] Lock
>Blocks, [5000] Lock Owner Blocks.
>2007-04-16 13:43:02.39     server    Attempting to initialize Distributed
>Transaction Coordinator.
>2007-04-16 13:43:03.75     server    Failed to obtain
>TransactionDispenserInterface: Result Code = 0x8004d01b
>2007-04-16 13:43:04.04     spid4    Starting up database 'master'.
>2007-04-16 13:43:05.10     spid5    Starting up database 'model'.
>2007-04-16 13:43:05.10     server    Using 'SSNETLIB.DLL' version '8.0.194'.
>2007-04-16 13:43:05.32     spid4    Server name is 'PAC_APPS2'.
>2007-04-16 13:43:05.34     spid9    Starting up database 'pubs'.
>2007-04-16 13:43:05.34     spid8    Starting up database 'msdb'.
>2007-04-16 13:43:05.45     spid10    Starting up database 'Northwind'.
>2007-04-16 13:43:05.53     spid11    Starting up database 'passkey'.
>2007-04-16 13:43:05.54     spid12    Starting up database 'Clique'.
>2007-04-16 13:43:05.62     spid13    Starting up database 'ServiceReq'.
>2007-04-16 13:43:05.70     spid14    Starting up database 'Survey'.
>2007-04-16 13:43:05.74     server    SQL Server is ready for client connections
>2007-04-16 13:43:05.74     server    SQL server listening on 10.31.18.27:1433,
>127.0.0.1:1433.
>2007-04-16 13:43:05.74     server    SQL server listening on TCP, Shared Memory,
>Named Pipes.
>2007-04-16 13:43:05.76     spid15    Starting up database 'IER'.
>2007-04-16 13:43:06.59     spid5    Clearing tempdb database.
>2007-04-16 13:43:06.62     spid9    Starting up database 'wiseri'.
>2007-04-16 13:43:06.95     spid8    Starting up database 'MCI'.
>2007-04-16 13:43:07.28     spid11    Recovery is checkpointing database 'passkey'
>(7)
>2007-04-16 13:43:07.43     spid10    Starting up database 'IDSystem'.
>2007-04-16 13:43:07.79     spid11    Starting up database 'whosnext'.
>2007-04-16 13:43:08.18     spid13    Starting up database 'stopwatch2'.
>2007-04-16 13:43:08.31     spid10    Starting up database 'stopwatchTest'.
>2007-04-16 13:43:08.49     spid12    Starting up database 'SR_ICT'.
>2007-04-16 13:43:08.76     spid15    Recovery is checkpointing database 'IER' (11)
>2007-04-16 13:43:08.99     spid5    Starting up database 'tempdb'.
>2007-04-16 13:43:09.03     spid14    Starting up database 'SurfControl_WebFilter'.
>2007-04-16 13:43:09.24     spid15    Starting up database 'TRACKIT70_DATA'.
>2007-04-16 13:43:09.60     spid14    Starting up database 'SR_PAC'.
>2007-04-16 13:43:09.73     spid12    Starting up database 'SerReqQ'.
>2007-04-16 13:43:09.81     spid11    Recovery is checkpointing database 'whosnext'
>(15)
>2007-04-16 13:43:10.09     spid8    Starting up database 'CommerceDB11'.
>2007-04-16 13:43:12.24     spid13    0 transactions rolled back in database
>'stopwatch2' (16).
>2007-04-16 13:43:12.24     spid13    2 transactions rolled forward in database
>'stopwatch2' (16).
>2007-04-16 13:43:12.29     spid13    Recovery is checkpointing database
>'stopwatch2' (16)
>2007-04-16 13:43:16.26     spid15    Recovery is checkpointing database
>'TRACKIT70_DATA' (20)
>2007-04-16 13:43:54.29     spid56    Using 'xpstar.dll' version '2000.80.194' to
>execute extended stored procedure '
>2007-04-16 13:44:54.26     spid4    Recovery complete.
>2007-04-16 13:44:58.40     spid116    Using 'xpsqlbot.dll' version '2000.80.194'
>to execute extended stored procedure
>
>Should I upgrade to SP3a  or SP4 to try to fix the problem or just leave
>well enough alone?
>
>Thank You Very Much.
>
>
>Because we posted this question earlier and have not received a single
>response I've resorted to crossposting to the following groups:
>microsoft.public.sqlserver.server
>microsoft.public.sqlserver.tools
>microsoft.public.sqlserver.security
>microsoft.public.sqlserver.setup

"Sue Hoegemeier" wrote:

> I saw your first post but did not see any issues, problems or errors
> in the SQL Error log so what problems specifically are you trying to
> fix? The MSDTC entry is not unusual. I've had TrackIt on database
> servers before and I'm not seeing whatever it is you think TrackIt may
> be causing.
> Running SQL 2000 RTM is a security risk so it would not be
> recommended. I'm not sure why you would not want to be running on at
> least SP3. And then service pack 4 has been out for almost two years
> now. Is there a particular reason why you wouldn't want to be running
> the latest service pack? After two years, any issues with it probably
> would have surfaced by now.
>
> -Sue
>
> On Tue, 17 Apr 2007 11:04:03 -0700, Dave
> <D***@discussions.microsoft.com> wrote:
>
> >I am running one Windows 2000 Server with Microsoft SQL Server 2000 RTM and
> >one Windows 2003 Server with Microsoft SQL Server 2000 RTM currently and have
> >not had any problems with viruses or applications or databases created for
> >years. 
> >
> >Except that the other day I installed an application called TrackIt! and now
> >the SQL Server 2000 on the Windows 2000 Server box is displaying the
> >following in the SQL Server Logs(Complete Export after Installing Dell
> >OpenManage and had to reboot):
> >
> >Date    Source    Message
> >2007-04-16 13:43:01.09     server    Microsoft SQL Server  2000 - 8.00.194 (Intel
> >X86) ...
> >2007-04-16 13:43:01.10     server    Logging SQL Server messages in file
> >'e:\MSSQLSERVER\DATA\MSSQL\log\ERRORLOG'.
> >2007-04-16 13:43:01.10     server    Server Process ID is 1016.
> >2007-04-16 13:43:01.10     server    All rights reserved.
> >2007-04-16 13:43:01.10     server    Copyright (C) 1988-2000 Microsoft Corporation.
> >2007-04-16 13:43:01.23     server    SQL Server is starting at priority class
> >'normal'(2 CPUs detected).
> >2007-04-16 13:43:02.20     server    SQL Server configured for thread mode
> >processing.
> >2007-04-16 13:43:02.24     server    Using dynamic lock allocation. [2500] Lock
> >Blocks, [5000] Lock Owner Blocks.
> >2007-04-16 13:43:02.39     server    Attempting to initialize Distributed
> >Transaction Coordinator.
> >2007-04-16 13:43:03.75     server    Failed to obtain
> >TransactionDispenserInterface: Result Code = 0x8004d01b
> >2007-04-16 13:43:04.04     spid4    Starting up database 'master'.
> >2007-04-16 13:43:05.10     spid5    Starting up database 'model'.
> >2007-04-16 13:43:05.10     server    Using 'SSNETLIB.DLL' version '8.0.194'.
> >2007-04-16 13:43:05.32     spid4    Server name is 'PAC_APPS2'.
> >2007-04-16 13:43:05.34     spid9    Starting up database 'pubs'.
> >2007-04-16 13:43:05.34     spid8    Starting up database 'msdb'.
> >2007-04-16 13:43:05.45     spid10    Starting up database 'Northwind'.
> >2007-04-16 13:43:05.53     spid11    Starting up database 'passkey'.
> >2007-04-16 13:43:05.54     spid12    Starting up database 'Clique'.
> >2007-04-16 13:43:05.62     spid13    Starting up database 'ServiceReq'.
> >2007-04-16 13:43:05.70     spid14    Starting up database 'Survey'.
> >2007-04-16 13:43:05.74     server    SQL Server is ready for client connections
> >2007-04-16 13:43:05.74     server    SQL server listening on 10.31.18.27:1433,
> >127.0.0.1:1433.
> >2007-04-16 13:43:05.74     server    SQL server listening on TCP, Shared Memory,
> >Named Pipes.
> >2007-04-16 13:43:05.76     spid15    Starting up database 'IER'.
> >2007-04-16 13:43:06.59     spid5    Clearing tempdb database.
> >2007-04-16 13:43:06.62     spid9    Starting up database 'wiseri'.
> >2007-04-16 13:43:06.95     spid8    Starting up database 'MCI'.
> >2007-04-16 13:43:07.28     spid11    Recovery is checkpointing database 'passkey'
> >(7)
> >2007-04-16 13:43:07.43     spid10    Starting up database 'IDSystem'.
> >2007-04-16 13:43:07.79     spid11    Starting up database 'whosnext'.
> >2007-04-16 13:43:08.18     spid13    Starting up database 'stopwatch2'.
> >2007-04-16 13:43:08.31     spid10    Starting up database 'stopwatchTest'.
> >2007-04-16 13:43:08.49     spid12    Starting up database 'SR_ICT'.
> >2007-04-16 13:43:08.76     spid15    Recovery is checkpointing database 'IER' (11)
> >2007-04-16 13:43:08.99     spid5    Starting up database 'tempdb'.
> >2007-04-16 13:43:09.03     spid14    Starting up database 'SurfControl_WebFilter'.
> >2007-04-16 13:43:09.24     spid15    Starting up database 'TRACKIT70_DATA'.
> >2007-04-16 13:43:09.60     spid14    Starting up database 'SR_PAC'.
> >2007-04-16 13:43:09.73     spid12    Starting up database 'SerReqQ'.
> >2007-04-16 13:43:09.81     spid11    Recovery is checkpointing database 'whosnext'
> >(15)
> >2007-04-16 13:43:10.09     spid8    Starting up database 'CommerceDB11'.
> >2007-04-16 13:43:12.24     spid13    0 transactions rolled back in database
> >'stopwatch2' (16).
> >2007-04-16 13:43:12.24     spid13    2 transactions rolled forward in database
> >'stopwatch2' (16).
> >2007-04-16 13:43:12.29     spid13    Recovery is checkpointing database
> >'stopwatch2' (16)
> >2007-04-16 13:43:16.26     spid15    Recovery is checkpointing database
> >'TRACKIT70_DATA' (20)
> >2007-04-16 13:43:54.29     spid56    Using 'xpstar.dll' version '2000.80.194' to
> >execute extended stored procedure '
> >2007-04-16 13:44:54.26     spid4    Recovery complete.
> >2007-04-16 13:44:58.40     spid116    Using 'xpsqlbot.dll' version '2000.80.194'
> >to execute extended stored procedure
> >
> >Should I upgrade to SP3a  or SP4 to try to fix the problem or just leave
> >well enough alone?
> >
> >Thank You Very Much.
> >
> >
> >Because we posted this question earlier and have not received a single
> >response I've resorted to crossposting to the following groups:
> >microsoft.public.sqlserver.server
> >microsoft.public.sqlserver.tools
> >microsoft.public.sqlserver.security
> >microsoft.public.sqlserver.setup
>
>

>What I am referring to is the "Failed to obtain
>TransactionDispenserInterface: Result Code = 0x8004d01b" line in the log.
>
>Thanks for taking time to answer.
>
>
>
>"Sue Hoegemeier" wrote:
>
>> I saw your first post but did not see any issues, problems or errors
>> in the SQL Error log so what problems specifically are you trying to
>> fix? The MSDTC entry is not unusual. I've had TrackIt on database
>> servers before and I'm not seeing whatever it is you think TrackIt may
>> be causing.
>> Running SQL 2000 RTM is a security risk so it would not be
>> recommended. I'm not sure why you would not want to be running on at
>> least SP3. And then service pack 4 has been out for almost two years
>> now. Is there a particular reason why you wouldn't want to be running
>> the latest service pack? After two years, any issues with it probably
>> would have surfaced by now.
>>
>> -Sue
>>
>> On Tue, 17 Apr 2007 11:04:03 -0700, Dave
>> <D***@discussions.microsoft.com> wrote:
>>
>> >I am running one Windows 2000 Server with Microsoft SQL Server 2000 RTM and
>> >one Windows 2003 Server with Microsoft SQL Server 2000 RTM currently and have
>> >not had any problems with viruses or applications or databases created for
>> >years. 
>> >
>> >Except that the other day I installed an application called TrackIt! and now
>> >the SQL Server 2000 on the Windows 2000 Server box is displaying the
>> >following in the SQL Server Logs(Complete Export after Installing Dell
>> >OpenManage and had to reboot):
>> >
>> >Date    Source    Message
>> >2007-04-16 13:43:01.09     server    Microsoft SQL Server  2000 - 8.00.194 (Intel
>> >X86) ...
>> >2007-04-16 13:43:01.10     server    Logging SQL Server messages in file
>> >'e:\MSSQLSERVER\DATA\MSSQL\log\ERRORLOG'.
>> >2007-04-16 13:43:01.10     server    Server Process ID is 1016.
>> >2007-04-16 13:43:01.10     server    All rights reserved.
>> >2007-04-16 13:43:01.10     server    Copyright (C) 1988-2000 Microsoft Corporation.
>> >2007-04-16 13:43:01.23     server    SQL Server is starting at priority class
>> >'normal'(2 CPUs detected).
>> >2007-04-16 13:43:02.20     server    SQL Server configured for thread mode
>> >processing.
>> >2007-04-16 13:43:02.24     server    Using dynamic lock allocation. [2500] Lock
>> >Blocks, [5000] Lock Owner Blocks.
>> >2007-04-16 13:43:02.39     server    Attempting to initialize Distributed
>> >Transaction Coordinator.
>> >2007-04-16 13:43:03.75     server    Failed to obtain
>> >TransactionDispenserInterface: Result Code = 0x8004d01b
>> >2007-04-16 13:43:04.04     spid4    Starting up database 'master'.
>> >2007-04-16 13:43:05.10     spid5    Starting up database 'model'.
>> >2007-04-16 13:43:05.10     server    Using 'SSNETLIB.DLL' version '8.0.194'.
>> >2007-04-16 13:43:05.32     spid4    Server name is 'PAC_APPS2'.
>> >2007-04-16 13:43:05.34     spid9    Starting up database 'pubs'.
>> >2007-04-16 13:43:05.34     spid8    Starting up database 'msdb'.
>> >2007-04-16 13:43:05.45     spid10    Starting up database 'Northwind'.
>> >2007-04-16 13:43:05.53     spid11    Starting up database 'passkey'.
>> >2007-04-16 13:43:05.54     spid12    Starting up database 'Clique'.
>> >2007-04-16 13:43:05.62     spid13    Starting up database 'ServiceReq'.
>> >2007-04-16 13:43:05.70     spid14    Starting up database 'Survey'.
>> >2007-04-16 13:43:05.74     server    SQL Server is ready for client connections
>> >2007-04-16 13:43:05.74     server    SQL server listening on 10.31.18.27:1433,
>> >127.0.0.1:1433.
>> >2007-04-16 13:43:05.74     server    SQL server listening on TCP, Shared Memory,
>> >Named Pipes.
>> >2007-04-16 13:43:05.76     spid15    Starting up database 'IER'.
>> >2007-04-16 13:43:06.59     spid5    Clearing tempdb database.
>> >2007-04-16 13:43:06.62     spid9    Starting up database 'wiseri'.
>> >2007-04-16 13:43:06.95     spid8    Starting up database 'MCI'.
>> >2007-04-16 13:43:07.28     spid11    Recovery is checkpointing database 'passkey'
>> >(7)
>> >2007-04-16 13:43:07.43     spid10    Starting up database 'IDSystem'.
>> >2007-04-16 13:43:07.79     spid11    Starting up database 'whosnext'.
>> >2007-04-16 13:43:08.18     spid13    Starting up database 'stopwatch2'.
>> >2007-04-16 13:43:08.31     spid10    Starting up database 'stopwatchTest'.
>> >2007-04-16 13:43:08.49     spid12    Starting up database 'SR_ICT'.
>> >2007-04-16 13:43:08.76     spid15    Recovery is checkpointing database 'IER' (11)
>> >2007-04-16 13:43:08.99     spid5    Starting up database 'tempdb'.
>> >2007-04-16 13:43:09.03     spid14    Starting up database 'SurfControl_WebFilter'.
>> >2007-04-16 13:43:09.24     spid15    Starting up database 'TRACKIT70_DATA'.
>> >2007-04-16 13:43:09.60     spid14    Starting up database 'SR_PAC'.
>> >2007-04-16 13:43:09.73     spid12    Starting up database 'SerReqQ'.
>> >2007-04-16 13:43:09.81     spid11    Recovery is checkpointing database 'whosnext'
>> >(15)
>> >2007-04-16 13:43:10.09     spid8    Starting up database 'CommerceDB11'.
>> >2007-04-16 13:43:12.24     spid13    0 transactions rolled back in database
>> >'stopwatch2' (16).
>> >2007-04-16 13:43:12.24     spid13    2 transactions rolled forward in database
>> >'stopwatch2' (16).
>> >2007-04-16 13:43:12.29     spid13    Recovery is checkpointing database
>> >'stopwatch2' (16)
>> >2007-04-16 13:43:16.26     spid15    Recovery is checkpointing database
>> >'TRACKIT70_DATA' (20)
>> >2007-04-16 13:43:54.29     spid56    Using 'xpstar.dll' version '2000.80.194' to
>> >execute extended stored procedure '
>> >2007-04-16 13:44:54.26     spid4    Recovery complete.
>> >2007-04-16 13:44:58.40     spid116    Using 'xpsqlbot.dll' version '2000.80.194'
>> >to execute extended stored procedure
>> >
>> >Should I upgrade to SP3a  or SP4 to try to fix the problem or just leave
>> >well enough alone?
>> >
>> >Thank You Very Much.
>> >
>> >
>> >Because we posted this question earlier and have not received a single
>> >response I've resorted to crossposting to the following groups:
>> >microsoft.public.sqlserver.server
>> >microsoft.public.sqlserver.tools
>> >microsoft.public.sqlserver.security
>> >microsoft.public.sqlserver.setup
>>
>>

"Erland Sommarskog" wrote:

> Dave (D***@discussions.microsoft.com) writes:
> > I am running one Windows 2000 Server with Microsoft SQL Server 2000 RTM
> > and one Windows 2003 Server with Microsoft SQL Server 2000 RTM currently
> > and have not had any problems with viruses or applications or databases
> > created for years. 
>
> Consider yourself lucky. All versions prior to SP3 are open to the
> Slammer worm.
>
> SP3 is minimum to run SQL 2000 in my opinion. It's what you need if you
> would like to upgrade to SQL 2005, or if you want to move to Windows 2003.
>
> Some people reported performance issues with SP4, and there is a problem
> with SP4 if you use AWE, so SP4 does not seem to have caught on as well as
> one would expect. But I can't recommend against using SP4.
>
> Beware that SP3 introduces some changes to tighten security, that
> potentially could affect your applications, so I recommend that you
> run in a test environment before slapping it on to your production box.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>

"Erland Sommarskog" <esq***@sommarskog.se> wrote in message
news:Xns991E2CBD1223Yazorman@127.0.0.1...
> Dave (D***@discussions.microsoft.com) writes:
> > There are major changes in the Master, Model and MSDB databases that
> > worries me that if I do install SP4 our databases will not work.  I
> > think I will take your advise and just upgrade to SP3a.
>
> I can't recall any such major changes. Least of all I could think of
> any major changes that would affect a normal application.
>
> The one that does bring possibly breaking changes is SP3a, which by
> default turns off cross-database chaining. (But the Setup gives you
> the choice to leave it on.)
>
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

"Erland Sommarskog" <esq***@sommarskog.se> wrote in message
news:Xns99169E98EB45Yazorman@127.0.0.1...
> Dave (D***@discussions.microsoft.com) writes:
> > I am running one Windows 2000 Server with Microsoft SQL Server 2000 RTM
> > and one Windows 2003 Server with Microsoft SQL Server 2000 RTM currently
> > and have not had any problems with viruses or applications or databases
> > created for years.
>
> Consider yourself lucky. All versions prior to SP3 are open to the
> Slammer worm.
>
> SP3 is minimum to run SQL 2000 in my opinion. It's what you need if you
> would like to upgrade to SQL 2005, or if you want to move to Windows 2003.
>
> Some people reported performance issues with SP4, and there is a problem
> with SP4 if you use AWE, so SP4 does not seem to have caught on as well as
> one would expect. But I can't recommend against using SP4.
>
> Beware that SP3 introduces some changes to tighten security, that
> potentially could affect your applications, so I recommend that you
> run in a test environment before slapping it on to your production box.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx