KB913580 & SQL Server 2000 Problem

I applied the Microsoft patch MS06-018 (KB913580) Vulnerability in Microsoft
Distributed Transaction Coordinator Could Allow Denial of Service on the
13th (4 days after it was issued) to my dedicated server (at a hosting site)
running SQL2K SP4. Since then, on two occasions, I needed to reboot my
server (Win 2K Server SP4) and the server took exceptionally long to boot
and then when I finally gained access to the server SQL Server EM could not
find my server (my databases were gone), I couldn't access Internet sites
with IE, and I couldn't even open the Control Panel to look at network
services. In the Services menu, it just said mssql.exe "Starting...". When
that service was stopped, the network stuff all happened and I could restart
SQL Server.
Excerpts from the SQL Server Log:
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
Attempting to initialize Distributed Transaction Coordinator.
(12 -30 minutes later)
Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b
Could not set up Net-Library 'SSNETLIB'..
Unable to load any netlibs.
SQL Server could not spawn FRunCM thread.
So, it seems a Microsoft patch has screwed up my life again (it took many
long reboots, calls to tech support, many hours of production server
downtime) with a patch. I plan to uninstall the patch (if I can).
How would I contact MS to resolve this issue? Have others experienced this
same issue? If I uninstall the patch won't that leave the server vulnerable?
Thanks for any help.Hi Don
For SQL Server 2000 support try http://tinyurl.com/gp56z
as you are on basic SP4 you may want to think about upgrading to 2187
http://support.microsoft.com/kb/916287. You may want to check that
SSNETLIB.dll is ok and that MDAC is consistent.
John
"Don Miller" wrote:
> I applied the Microsoft patch MS06-018 (KB913580) Vulnerability in Microsoft
> Distributed Transaction Coordinator Could Allow Denial of Service on the
> 13th (4 days after it was issued) to my dedicated server (at a hosting site)
> running SQL2K SP4. Since then, on two occasions, I needed to reboot my
> server (Win 2K Server SP4) and the server took exceptionally long to boot
> and then when I finally gained access to the server SQL Server EM could not
> find my server (my databases were gone), I couldn't access Internet sites
> with IE, and I couldn't even open the Control Panel to look at network
> services. In the Services menu, it just said mssql.exe "Starting...". When
> that service was stopped, the network stuff all happened and I could restart
> SQL Server.
> Excerpts from the SQL Server Log:
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> Attempting to initialize Distributed Transaction Coordinator.
> (12 -30 minutes later)
> Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b
> Could not set up Net-Library 'SSNETLIB'..
> Unable to load any netlibs.
> SQL Server could not spawn FRunCM thread.
> So, it seems a Microsoft patch has screwed up my life again (it took many
> long reboots, calls to tech support, many hours of production server
> downtime) with a patch. I plan to uninstall the patch (if I can).
> How would I contact MS to resolve this issue? Have others experienced this
> same issue? If I uninstall the patch won't that leave the server vulnerable?
> Thanks for any help.
>
>|||> For SQL Server 2000 support try http://tinyurl.com/gp56z
I went there, but everything looks like it costs money for answers. I
thought MS had some toll-free line for all security update problems (like
this) although I can't find it anywhere.
> as you are on basic SP4 you may want to think about upgrading to 2187
> http://support.microsoft.com/kb/916287.
My previous server crashed, so I JUST did a clean install of SQL Server and
applied SP4 THREE weeks ago. I assumed that everything in 2187 would have
been included in the SP4 available three weeks ago.
> You may want to check that
> SSNETLIB.dll is ok and that MDAC is consistent.
I don't know what that means. Everything seems to be working with SQL Server
and my web application once I did not have SQL Server start during the
reboot.
Thanks for your help.
> "Don Miller" wrote:
> > I applied the Microsoft patch MS06-018 (KB913580) Vulnerability in
Microsoft
> > Distributed Transaction Coordinator Could Allow Denial of Service on the
> > 13th (4 days after it was issued) to my dedicated server (at a hosting
site)
> > running SQL2K SP4. Since then, on two occasions, I needed to reboot my
> > server (Win 2K Server SP4) and the server took exceptionally long to
boot
> > and then when I finally gained access to the server SQL Server EM could
not
> > find my server (my databases were gone), I couldn't access Internet
sites
> > with IE, and I couldn't even open the Control Panel to look at network
> > services. In the Services menu, it just said mssql.exe "Starting...".
When
> > that service was stopped, the network stuff all happened and I could
restart
> > SQL Server.
> >
> > Excerpts from the SQL Server Log:
> >
> > Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
> > May 3 2005 23:18:38
> > Copyright (c) 1988-2003 Microsoft Corporation
> > Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> >
> > Attempting to initialize Distributed Transaction Coordinator.
> > (12 -30 minutes later)
> > Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b
> > Could not set up Net-Library 'SSNETLIB'..
> > Unable to load any netlibs.
> > SQL Server could not spawn FRunCM thread.
> >
> > So, it seems a Microsoft patch has screwed up my life again (it took
many
> > long reboots, calls to tech support, many hours of production server
> > downtime) with a patch. I plan to uninstall the patch (if I can).
> >
> > How would I contact MS to resolve this issue? Have others experienced
this
> > same issue? If I uninstall the patch won't that leave the server
vulnerable?
> >
> > Thanks for any help.
> >
> >
> >|||Hi
With PSS you will not be charged if the issue is recognised as a bug.
http://support.microsoft.com/kb/916287 is a post SP4 hotfix.
MDAC component checker can be downloaded from http://tinyurl.com/b9ua
John
"Don Miller" wrote:
> > For SQL Server 2000 support try http://tinyurl.com/gp56z
> I went there, but everything looks like it costs money for answers. I
> thought MS had some toll-free line for all security update problems (like
> this) although I can't find it anywhere.
> > as you are on basic SP4 you may want to think about upgrading to 2187
> > http://support.microsoft.com/kb/916287.
> My previous server crashed, so I JUST did a clean install of SQL Server and
> applied SP4 THREE weeks ago. I assumed that everything in 2187 would have
> been included in the SP4 available three weeks ago.
> > You may want to check that
> > SSNETLIB.dll is ok and that MDAC is consistent.
> I don't know what that means. Everything seems to be working with SQL Server
> and my web application once I did not have SQL Server start during the
> reboot.
> Thanks for your help.
> > "Don Miller" wrote:
> >
> > > I applied the Microsoft patch MS06-018 (KB913580) Vulnerability in
> Microsoft
> > > Distributed Transaction Coordinator Could Allow Denial of Service on the
> > > 13th (4 days after it was issued) to my dedicated server (at a hosting
> site)
> > > running SQL2K SP4. Since then, on two occasions, I needed to reboot my
> > > server (Win 2K Server SP4) and the server took exceptionally long to
> boot
> > > and then when I finally gained access to the server SQL Server EM could
> not
> > > find my server (my databases were gone), I couldn't access Internet
> sites
> > > with IE, and I couldn't even open the Control Panel to look at network
> > > services. In the Services menu, it just said mssql.exe "Starting...".
> When
> > > that service was stopped, the network stuff all happened and I could
> restart
> > > SQL Server.
> > >
> > > Excerpts from the SQL Server Log:
> > >
> > > Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
> > > May 3 2005 23:18:38
> > > Copyright (c) 1988-2003 Microsoft Corporation
> > > Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> > >
> > > Attempting to initialize Distributed Transaction Coordinator.
> > > (12 -30 minutes later)
> > > Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b
> > > Could not set up Net-Library 'SSNETLIB'..
> > > Unable to load any netlibs.
> > > SQL Server could not spawn FRunCM thread.
> > >
> > > So, it seems a Microsoft patch has screwed up my life again (it took
> many
> > > long reboots, calls to tech support, many hours of production server
> > > downtime) with a patch. I plan to uninstall the patch (if I can).
> > >
> > > How would I contact MS to resolve this issue? Have others experienced
> this
> > > same issue? If I uninstall the patch won't that leave the server
> vulnerable?
> > >
> > > Thanks for any help.
> > >
> > >
> > >
>
>|||I do not know if you solved your problem but I ran into a different problem
and it turned out to be a conflict between Veritas v10d tape drive drivers
and kb913850. The symptoms were network access problems and lengthy times for
various windows to display and also logout and shutdown problems. I removed
the veritas tape driver and resorted back to the microsoft tape driver for my
HP dlt drive and rebooted the server and all was back to normal. This was
repeatable and happened on two different servers. So, if you have a tape
drive attached to your server and have veritas tape drivers loaded it could
very well be the source of your problem.
"Don Miller" wrote:
> I applied the Microsoft patch MS06-018 (KB913580) Vulnerability in Microsoft
> Distributed Transaction Coordinator Could Allow Denial of Service on the
> 13th (4 days after it was issued) to my dedicated server (at a hosting site)
> running SQL2K SP4. Since then, on two occasions, I needed to reboot my
> server (Win 2K Server SP4) and the server took exceptionally long to boot
> and then when I finally gained access to the server SQL Server EM could not
> find my server (my databases were gone), I couldn't access Internet sites
> with IE, and I couldn't even open the Control Panel to look at network
> services. In the Services menu, it just said mssql.exe "Starting...". When
> that service was stopped, the network stuff all happened and I could restart
> SQL Server.
> Excerpts from the SQL Server Log:
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> Attempting to initialize Distributed Transaction Coordinator.
> (12 -30 minutes later)
> Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b
> Could not set up Net-Library 'SSNETLIB'..
> Unable to load any netlibs.
> SQL Server could not spawn FRunCM thread.
> So, it seems a Microsoft patch has screwed up my life again (it took many
> long reboots, calls to tech support, many hours of production server
> downtime) with a patch. I plan to uninstall the patch (if I can).
> How would I contact MS to resolve this issue? Have others experienced this
> same issue? If I uninstall the patch won't that leave the server vulnerable?
> Thanks for any help.
>
>|||Hi Scott
Out of interest were you using the SQL Server plug-in? I gave up some time
ago on backup solutions that used a plug-in as they always seemed to mess up
at some point.
Thanks
John
"Scott Johnston" wrote:
> I do not know if you solved your problem but I ran into a different problem
> and it turned out to be a conflict between Veritas v10d tape drive drivers
> and kb913850. The symptoms were network access problems and lengthy times for
> various windows to display and also logout and shutdown problems. I removed
> the veritas tape driver and resorted back to the microsoft tape driver for my
> HP dlt drive and rebooted the server and all was back to normal. This was
> repeatable and happened on two different servers. So, if you have a tape
> drive attached to your server and have veritas tape drivers loaded it could
> very well be the source of your problem.
> "Don Miller" wrote:
> > I applied the Microsoft patch MS06-018 (KB913580) Vulnerability in Microsoft
> > Distributed Transaction Coordinator Could Allow Denial of Service on the
> > 13th (4 days after it was issued) to my dedicated server (at a hosting site)
> > running SQL2K SP4. Since then, on two occasions, I needed to reboot my
> > server (Win 2K Server SP4) and the server took exceptionally long to boot
> > and then when I finally gained access to the server SQL Server EM could not
> > find my server (my databases were gone), I couldn't access Internet sites
> > with IE, and I couldn't even open the Control Panel to look at network
> > services. In the Services menu, it just said mssql.exe "Starting...". When
> > that service was stopped, the network stuff all happened and I could restart
> > SQL Server.
> >
> > Excerpts from the SQL Server Log:
> >
> > Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
> > May 3 2005 23:18:38
> > Copyright (c) 1988-2003 Microsoft Corporation
> > Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> >
> > Attempting to initialize Distributed Transaction Coordinator.
> > (12 -30 minutes later)
> > Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b
> > Could not set up Net-Library 'SSNETLIB'..
> > Unable to load any netlibs.
> > SQL Server could not spawn FRunCM thread.
> >
> > So, it seems a Microsoft patch has screwed up my life again (it took many
> > long reboots, calls to tech support, many hours of production server
> > downtime) with a patch. I plan to uninstall the patch (if I can).
> >
> > How would I contact MS to resolve this issue? Have others experienced this
> > same issue? If I uninstall the patch won't that leave the server vulnerable?
> >
> > Thanks for any help.
> >
> >
> >|||I have been using an MSDE instance for Backup Exec as I did not want to take
a chance on blowing up my SQL server!
"John Bell" wrote:
> Hi Scott
> Out of interest were you using the SQL Server plug-in? I gave up some time
> ago on backup solutions that used a plug-in as they always seemed to mess up
> at some point.
> Thanks
> John
> "Scott Johnston" wrote:
> > I do not know if you solved your problem but I ran into a different problem
> > and it turned out to be a conflict between Veritas v10d tape drive drivers
> > and kb913850. The symptoms were network access problems and lengthy times for
> > various windows to display and also logout and shutdown problems. I removed
> > the veritas tape driver and resorted back to the microsoft tape driver for my
> > HP dlt drive and rebooted the server and all was back to normal. This was
> > repeatable and happened on two different servers. So, if you have a tape
> > drive attached to your server and have veritas tape drivers loaded it could
> > very well be the source of your problem.
> >
> > "Don Miller" wrote:
> >
> > > I applied the Microsoft patch MS06-018 (KB913580) Vulnerability in Microsoft
> > > Distributed Transaction Coordinator Could Allow Denial of Service on the
> > > 13th (4 days after it was issued) to my dedicated server (at a hosting site)
> > > running SQL2K SP4. Since then, on two occasions, I needed to reboot my
> > > server (Win 2K Server SP4) and the server took exceptionally long to boot
> > > and then when I finally gained access to the server SQL Server EM could not
> > > find my server (my databases were gone), I couldn't access Internet sites
> > > with IE, and I couldn't even open the Control Panel to look at network
> > > services. In the Services menu, it just said mssql.exe "Starting...". When
> > > that service was stopped, the network stuff all happened and I could restart
> > > SQL Server.
> > >
> > > Excerpts from the SQL Server Log:
> > >
> > > Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
> > > May 3 2005 23:18:38
> > > Copyright (c) 1988-2003 Microsoft Corporation
> > > Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> > >
> > > Attempting to initialize Distributed Transaction Coordinator.
> > > (12 -30 minutes later)
> > > Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b
> > > Could not set up Net-Library 'SSNETLIB'..
> > > Unable to load any netlibs.
> > > SQL Server could not spawn FRunCM thread.
> > >
> > > So, it seems a Microsoft patch has screwed up my life again (it took many
> > > long reboots, calls to tech support, many hours of production server
> > > downtime) with a patch. I plan to uninstall the patch (if I can).
> > >
> > > How would I contact MS to resolve this issue? Have others experienced this
> > > same issue? If I uninstall the patch won't that leave the server vulnerable?
> > >
> > > Thanks for any help.
> > >
> > >
> > >