MSSQLSERVER service hangs on loading DTC

Am using SQL 2000 SP4
Whenever the system is re-booted, SQL service hangs while loading. The
last entry ion the startup log indicates is :
"Attempting to initialize Distributed Transaction Coordinator"
When I check the services, DTC is running.
To fix the problem I manually kill (pskill) the process, log off and
then log back in.
Once logged back in, I manually start the SQL server and agent.
SteveHi Steve
Do you have autostart DTC enabled, if so you may want to try removing it
(server properties page in EM).
John
"Steve Babcock" wrote:
> Am using SQL 2000 SP4
> Whenever the system is re-booted, SQL service hangs while loading. The
> last entry ion the startup log indicates is :
> "Attempting to initialize Distributed Transaction Coordinator"
> When I check the services, DTC is running.
> To fix the problem I manually kill (pskill) the process, log off and
> then log back in.
> Once logged back in, I manually start the SQL server and agent.
> Steve
>|||John - tried disabling DTC from starting up (which it did - service was not
running) this but the result was the same - last entry in startup log is :
"Attempting to initialize Distributed Transaction Coordinator"
Steve
John Bell wrote:
> Hi Steve
> Do you have autostart DTC enabled, if so you may want to try removing it
> (server properties page in EM).
> John
> "Steve Babcock" wrote:
> > Am using SQL 2000 SP4
> >
> > Whenever the system is re-booted, SQL service hangs while loading. The
> > last entry ion the startup log indicates is :
> > "Attempting to initialize Distributed Transaction Coordinator"
> >
> > When I check the services, DTC is running.
> >
> > To fix the problem I manually kill (pskill) the process, log off and
> > then log back in.
> > Once logged back in, I manually start the SQL server and agent.
> >
> > Steve
> >
> >|||Hi Steve
Have you tried making SQLServer and DTC manual services, then starting SQL
Server from a command line, to see what happens?
John
"Steve Babcock" wrote:
> John - tried disabling DTC from starting up (which it did - service was not
> running) this but the result was the same - last entry in startup log is :
> "Attempting to initialize Distributed Transaction Coordinator"
> Steve
> John Bell wrote:
> > Hi Steve
> >
> > Do you have autostart DTC enabled, if so you may want to try removing it
> > (server properties page in EM).
> >
> > John
> >
> > "Steve Babcock" wrote:
> >
> > > Am using SQL 2000 SP4
> > >
> > > Whenever the system is re-booted, SQL service hangs while loading. The
> > > last entry ion the startup log indicates is :
> > > "Attempting to initialize Distributed Transaction Coordinator"
> > >
> > > When I check the services, DTC is running.
> > >
> > > To fix the problem I manually kill (pskill) the process, log off and
> > > then log back in.
> > > Once logged back in, I manually start the SQL server and agent.
> > >
> > > Steve
> > >
> > >
>|||That's our next step - will have to do it later today outside of office hours.
John Bell wrote:
> Hi Steve
> Have you tried making SQLServer and DTC manual services, then starting SQL
> Server from a command line, to see what happens?
> John
> "Steve Babcock" wrote:
> > John - tried disabling DTC from starting up (which it did - service was not
> > running) this but the result was the same - last entry in startup log is :
> > "Attempting to initialize Distributed Transaction Coordinator"
> >
> > Steve
> >
> > John Bell wrote:
> >
> > > Hi Steve
> > >
> > > Do you have autostart DTC enabled, if so you may want to try removing it
> > > (server properties page in EM).
> > >
> > > John
> > >
> > > "Steve Babcock" wrote:
> > >
> > > > Am using SQL 2000 SP4
> > > >
> > > > Whenever the system is re-booted, SQL service hangs while loading. The
> > > > last entry ion the startup log indicates is :
> > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > >
> > > > When I check the services, DTC is running.
> > > >
> > > > To fix the problem I manually kill (pskill) the process, log off and
> > > > then log back in.
> > > > Once logged back in, I manually start the SQL server and agent.
> > > >
> > > > Steve
> > > >
> > > >
> >
> >|||John :
I disabled auto-startup of the 3 services from within EM, re-booted and loaded
each one from the SQL Manager in order for DTC, SQL, SQLA - all was OK.
Is there a way to see a more detailed log so that I can tell where it's hangin up
on loading. Even though it says it's waiting for DTC, DTC is running as a
service when SQL is trying to start up.
Steve
John Bell wrote:
> Hi Steve
> Have you tried making SQLServer and DTC manual services, then starting SQL
> Server from a command line, to see what happens?
> John
> "Steve Babcock" wrote:
> > John - tried disabling DTC from starting up (which it did - service was not
> > running) this but the result was the same - last entry in startup log is :
> > "Attempting to initialize Distributed Transaction Coordinator"
> >
> > Steve
> >
> > John Bell wrote:
> >
> > > Hi Steve
> > >
> > > Do you have autostart DTC enabled, if so you may want to try removing it
> > > (server properties page in EM).
> > >
> > > John
> > >
> > > "Steve Babcock" wrote:
> > >
> > > > Am using SQL 2000 SP4
> > > >
> > > > Whenever the system is re-booted, SQL service hangs while loading. The
> > > > last entry ion the startup log indicates is :
> > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > >
> > > > When I check the services, DTC is running.
> > > >
> > > > To fix the problem I manually kill (pskill) the process, log off and
> > > > then log back in.
> > > > Once logged back in, I manually start the SQL server and agent.
> > > >
> > > > Steve
> > > >
> > > >
> >
> >|||Hi
The SQL Server log will log each event in the same way as you should see how
when it manually started. You could add a dependency of SQL Server on DTC so
that it does not even try to start before DTC has started. I don't know if
the DTC service logs anywhere other than the event log.
John
"Steve Babcock" wrote:
> John :
> I disabled auto-startup of the 3 services from within EM, re-booted and loaded
> each one from the SQL Manager in order for DTC, SQL, SQLA - all was OK.
> Is there a way to see a more detailed log so that I can tell where it's hangin up
> on loading. Even though it says it's waiting for DTC, DTC is running as a
> service when SQL is trying to start up.
> Steve
> John Bell wrote:
> > Hi Steve
> >
> > Have you tried making SQLServer and DTC manual services, then starting SQL
> > Server from a command line, to see what happens?
> >
> > John
> >
> > "Steve Babcock" wrote:
> >
> > > John - tried disabling DTC from starting up (which it did - service was not
> > > running) this but the result was the same - last entry in startup log is :
> > > "Attempting to initialize Distributed Transaction Coordinator"
> > >
> > > Steve
> > >
> > > John Bell wrote:
> > >
> > > > Hi Steve
> > > >
> > > > Do you have autostart DTC enabled, if so you may want to try removing it
> > > > (server properties page in EM).
> > > >
> > > > John
> > > >
> > > > "Steve Babcock" wrote:
> > > >
> > > > > Am using SQL 2000 SP4
> > > > >
> > > > > Whenever the system is re-booted, SQL service hangs while loading. The
> > > > > last entry ion the startup log indicates is :
> > > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > > >
> > > > > When I check the services, DTC is running.
> > > > >
> > > > > To fix the problem I manually kill (pskill) the process, log off and
> > > > > then log back in.
> > > > > Once logged back in, I manually start the SQL server and agent.
> > > > >
> > > > > Steve
> > > > >
> > > > >
> > >
> > >
>|||How do I set up the dependency - I don;t see where in Services I can do this.
Steve
John Bell wrote:
> Hi
> The SQL Server log will log each event in the same way as you should see how
> when it manually started. You could add a dependency of SQL Server on DTC so
> that it does not even try to start before DTC has started. I don't know if
> the DTC service logs anywhere other than the event log.
> John
> "Steve Babcock" wrote:
> > John :
> >
> > I disabled auto-startup of the 3 services from within EM, re-booted and loaded
> > each one from the SQL Manager in order for DTC, SQL, SQLA - all was OK.
> >
> > Is there a way to see a more detailed log so that I can tell where it's hangin up
> > on loading. Even though it says it's waiting for DTC, DTC is running as a
> > service when SQL is trying to start up.
> >
> > Steve
> >
> > John Bell wrote:
> >
> > > Hi Steve
> > >
> > > Have you tried making SQLServer and DTC manual services, then starting SQL
> > > Server from a command line, to see what happens?
> > >
> > > John
> > >
> > > "Steve Babcock" wrote:
> > >
> > > > John - tried disabling DTC from starting up (which it did - service was not
> > > > running) this but the result was the same - last entry in startup log is :
> > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > >
> > > > Steve
> > > >
> > > > John Bell wrote:
> > > >
> > > > > Hi Steve
> > > > >
> > > > > Do you have autostart DTC enabled, if so you may want to try removing it
> > > > > (server properties page in EM).
> > > > >
> > > > > John
> > > > >
> > > > > "Steve Babcock" wrote:
> > > > >
> > > > > > Am using SQL 2000 SP4
> > > > > >
> > > > > > Whenever the system is re-booted, SQL service hangs while loading. The
> > > > > > last entry ion the startup log indicates is :
> > > > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > > > >
> > > > > > When I check the services, DTC is running.
> > > > > >
> > > > > > To fix the problem I manually kill (pskill) the process, log off and
> > > > > > then log back in.
> > > > > > Once logged back in, I manually start the SQL server and agent.
> > > > > >
> > > > > > Steve
> > > > > >
> > > > > >
> > > >
> > > >
> >
> >|||Hi Steve
Dependencies should be a tab on the properties dialog for the services
applet (from administrators on the start menu or control panel). If you
double clicking your SQL Server service it should appear.
John
"Steve Babcock" wrote:
> How do I set up the dependency - I don;t see where in Services I can do this.
> Steve
> John Bell wrote:
> > Hi
> >
> > The SQL Server log will log each event in the same way as you should see how
> > when it manually started. You could add a dependency of SQL Server on DTC so
> > that it does not even try to start before DTC has started. I don't know if
> > the DTC service logs anywhere other than the event log.
> >
> > John
> >
> > "Steve Babcock" wrote:
> >
> > > John :
> > >
> > > I disabled auto-startup of the 3 services from within EM, re-booted and loaded
> > > each one from the SQL Manager in order for DTC, SQL, SQLA - all was OK.
> > >
> > > Is there a way to see a more detailed log so that I can tell where it's hangin up
> > > on loading. Even though it says it's waiting for DTC, DTC is running as a
> > > service when SQL is trying to start up.
> > >
> > > Steve
> > >
> > > John Bell wrote:
> > >
> > > > Hi Steve
> > > >
> > > > Have you tried making SQLServer and DTC manual services, then starting SQL
> > > > Server from a command line, to see what happens?
> > > >
> > > > John
> > > >
> > > > "Steve Babcock" wrote:
> > > >
> > > > > John - tried disabling DTC from starting up (which it did - service was not
> > > > > running) this but the result was the same - last entry in startup log is :
> > > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > > >
> > > > > Steve
> > > > >
> > > > > John Bell wrote:
> > > > >
> > > > > > Hi Steve
> > > > > >
> > > > > > Do you have autostart DTC enabled, if so you may want to try removing it
> > > > > > (server properties page in EM).
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "Steve Babcock" wrote:
> > > > > >
> > > > > > > Am using SQL 2000 SP4
> > > > > > >
> > > > > > > Whenever the system is re-booted, SQL service hangs while loading. The
> > > > > > > last entry ion the startup log indicates is :
> > > > > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > > > > >
> > > > > > > When I check the services, DTC is running.
> > > > > > >
> > > > > > > To fix the problem I manually kill (pskill) the process, log off and
> > > > > > > then log back in.
> > > > > > > Once logged back in, I manually start the SQL server and agent.
> > > > > > >
> > > > > > > Steve
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > >
> > >
>

MSSQLServer dependent service startup

Hello,
I have some services that are dependent on MSSQLServer serivce but when the
computer is restarted, my services don't start and I get an error message
"Cannot open database requrent in login 'database name'. Login fails'.
It seems like to me that these services come up before SQL Server even
though I have the dependencies set right.
Any help is appreciated.
Thanks
Shipra,
From the error it looks like the sql server is up when your application
is trying to connect. Since it will not give login failure. if the SQL Server
is not up it will give a error "could not connect or something". Is your
application by default using any id to connect to the database. It seems that
the ID doesn't have access to the default database.
Neeraj
"Shipra Gupta" wrote:

> Hello,
> I have some services that are dependent on MSSQLServer serivce but when the
> computer is restarted, my services don't start and I get an error message
> "Cannot open database requrent in login 'database name'. Login fails'.
> It seems like to me that these services come up before SQL Server even
> though I have the dependencies set right.
> Any help is appreciated.
> Thanks
>
|||Yes, that's true. But the login ID being used has all the required
permissions, I think it is a timing issue because later when I start the
services, they all start without a problem.
Thanks
"Neeraj" wrote:
[vbcol=seagreen]
> Shipra,
> From the error it looks like the sql server is up when your application
> is trying to connect. Since it will not give login failure. if the SQL Server
> is not up it will give a error "could not connect or something". Is your
> application by default using any id to connect to the database. It seems that
> the ID doesn't have access to the default database.
> Neeraj
> "Shipra Gupta" wrote:
|||Its possible that database SQL Server is up but default database is going
through the recovery. Adding a bit of delay might help. In Sybase we can
chage the order in which the databases get recovered, i don't know if we can
do the same in sql server or not. If yes then you can set it such that the
database gets recovered before any other database.
Neeraj
"Shipra Gupta" wrote:
[vbcol=seagreen]
> Yes, that's true. But the login ID being used has all the required
> permissions, I think it is a timing issue because later when I start the
> services, they all start without a problem.
> Thanks
> "Neeraj" wrote:

MSSQLServer dependent service startup

Hello,
I have some services that are dependent on MSSQLServer serivce but when the
computer is restarted, my services don't start and I get an error message
"Cannot open database requrent in login 'database name'. Login fails'.
It seems like to me that these services come up before SQL Server even
though I have the dependencies set right.
Any help is appreciated.
ThanksShipra,
From the error it looks like the sql server is up when your application
is trying to connect. Since it will not give login failure. if the SQL Serve
r
is not up it will give a error "could not connect or something". Is your
application by default using any id to connect to the database. It seems tha
t
the ID doesn't have access to the default database.
Neeraj
"Shipra Gupta" wrote:

> Hello,
> I have some services that are dependent on MSSQLServer serivce but when th
e
> computer is restarted, my services don't start and I get an error message
> "Cannot open database requrent in login 'database name'. Login fails'.
> It seems like to me that these services come up before SQL Server even
> though I have the dependencies set right.
> Any help is appreciated.
> Thanks
>|||Yes, that's true. But the login ID being used has all the required
permissions, I think it is a timing issue because later when I start the
services, they all start without a problem.
Thanks
"Neeraj" wrote:
[vbcol=seagreen]
> Shipra,
> From the error it looks like the sql server is up when your applicati
on
> is trying to connect. Since it will not give login failure. if the SQL Ser
ver
> is not up it will give a error "could not connect or something". Is your
> application by default using any id to connect to the database. It seems t
hat
> the ID doesn't have access to the default database.
> Neeraj
> "Shipra Gupta" wrote:
>|||Its possible that database SQL Server is up but default database is going
through the recovery. Adding a bit of delay might help. In Sybase we can
chage the order in which the databases get recovered, i don't know if we can
do the same in sql server or not. If yes then you can set it such that the
database gets recovered before any other database.
Neeraj
"Shipra Gupta" wrote:
[vbcol=seagreen]
> Yes, that's true. But the login ID being used has all the required
> permissions, I think it is a timing issue because later when I start the
> services, they all start without a problem.
> Thanks
> "Neeraj" wrote:
>

MSSQLSERVER 2005 service failed to start only on Windows startup

MSSQLServer service will not start when I startup Windows Server 2003
Std, but when I start the service manually, it works.
Here is the event (ID: 7000, Source: Service Control Manager) recorded:
The SQL Server (MSSQLSERVER) service failed to start due to the
following error:
%%6057960
I don't see anything in the SQL Server Logs for the initial attempt to
startup. Anyone have any ideas? I had set the service's Recovery for
First Failure to "Restart the Service" with "Reset Service after" set
to 5 minutes, but it hasn't worked.
Any ideas?Hi
I have not seen your error, it seems like the error message is not well
formed!
Has the server been starting ok previously?
Have you installed any patches/updates since it was last re-started?
If you change the service account does it start?
Are any other services failing to start?
John
"ccjjharmon@.gmail.com" wrote:
> MSSQLServer service will not start when I startup Windows Server 2003
> Std, but when I start the service manually, it works.
> Here is the event (ID: 7000, Source: Service Control Manager) recorded:
> The SQL Server (MSSQLSERVER) service failed to start due to the
> following error:
> %%6057960
>
> I don't see anything in the SQL Server Logs for the initial attempt to
> startup. Anyone have any ideas? I had set the service's Recovery for
> First Failure to "Restart the Service" with "Reset Service after" set
> to 5 minutes, but it hasn't worked.
> Any ideas?
>|||John,
I was wondering if the message was complete or not too...
It is a relatively new server (few months old) - but it has been
happening really since we installed yet... I am not sure if it ever
started up as a service on reboot.
No patches/updates since last restart (but Windows Update has them
downloaded - they just haven't been installed yet).
I haven't tried changing the service account... but didn't think to
because it starts when I manually start it - just not when all services
normally startup automatically.
SQLServerAgent also doesn't start - but all other services set to
Automatic startup go fine.|||I also checked to make sure the recent event mirrored the same text as
previous events and it does ... BUT the same error was only recorded
two other times (twice on 4/7). Before then, this event was instead
recorded (but I believe SQL Server still wasn't started as a service
automatically):
The SQL Server Integration Services service failed to start due to the
following error:
Waiting for a process to open the other end of the pipe.
Hope this info helps...
Chris|||Hi
Have you tried installing SP1? Otherwise you may have to log a call with PSS.
John
"ccjjharmon@.gmail.com" wrote:
> I also checked to make sure the recent event mirrored the same text as
> previous events and it does ... BUT the same error was only recorded
> two other times (twice on 4/7). Before then, this event was instead
> recorded (but I believe SQL Server still wasn't started as a service
> automatically):
> The SQL Server Integration Services service failed to start due to the
> following error:
> Waiting for a process to open the other end of the pipe.
> Hope this info helps...
> Chris
>

MSSQLSERVER 2005 service failed to start only on Windows startup

MSSQLServer service will not start when I startup Windows Server 2003
Std, but when I start the service manually, it works.
Here is the event (ID: 7000, Source: Service Control Manager) recorded:
The SQL Server (MSSQLSERVER) service failed to start due to the
following error:
%%6057960
I don't see anything in the SQL Server Logs for the initial attempt to
startup. Anyone have any ideas? I had set the service's Recovery for
First Failure to "Restart the Service" with "Reset Service after" set
to 5 minutes, but it hasn't worked.
Any ideas?Hi
I have not seen your error, it seems like the error message is not well
formed!
Has the server been starting ok previously?
Have you installed any patches/updates since it was last re-started?
If you change the service account does it start?
Are any other services failing to start?
John
"ccjjharmon@.gmail.com" wrote:

> MSSQLServer service will not start when I startup Windows Server 2003
> Std, but when I start the service manually, it works.
> Here is the event (ID: 7000, Source: Service Control Manager) recorded:
> The SQL Server (MSSQLSERVER) service failed to start due to the
> following error:
> %%6057960
>
> I don't see anything in the SQL Server Logs for the initial attempt to
> startup. Anyone have any ideas? I had set the service's Recovery for
> First Failure to "Restart the Service" with "Reset Service after" set
> to 5 minutes, but it hasn't worked.
> Any ideas?
>|||John,
I was wondering if the message was complete or not too...
It is a relatively new server (few months old) - but it has been
happening really since we installed yet... I am not sure if it ever
started up as a service on reboot.
No patches/updates since last restart (but Windows Update has them
downloaded - they just haven't been installed yet).
I haven't tried changing the service account... but didn't think to
because it starts when I manually start it - just not when all services
normally startup automatically.
SQLServerAgent also doesn't start - but all other services set to
Automatic startup go fine.|||I also checked to make sure the recent event mirrored the same text as
previous events and it does ... BUT the same error was only recorded
two other times (twice on 4/7). Before then, this event was instead
recorded (but I believe SQL Server still wasn't started as a service
automatically):
The SQL Server Integration Services service failed to start due to the
following error:
Waiting for a process to open the other end of the pipe.
Hope this info helps...
Chris

MSSQLSERVER & SQLSERVERAGENT startup account

I'm currently using a domain account that has sysadmin rights; does this
account need to be an administrator unter Window's 2000 server? I'm confused
by everthing I've read.
It's not necessarily required. The following article lists
the necessary rights and permissions:
http://support.microsoft.com/?id=283811
The section on Windows user rights addresses your question.
-Sue
On Tue, 28 Sep 2004 09:41:28 -0700, "Jerrick D.H"
<JerrickDH@.discussions.microsoft.com> wrote:

>I'm currently using a domain account that has sysadmin rights; does this
>account need to be an administrator unter Window's 2000 server? I'm confused
>by everthing I've read.

MSSQLSERVER & SQLSERVERAGENT startup account

I'm currently using a domain account that has sysadmin rights; does this
account need to be an administrator unter Window's 2000 server? I'm confused
by everthing I've read.It's not necessarily required. The following article lists
the necessary rights and permissions:
http://support.microsoft.com/?id=283811
The section on Windows user rights addresses your question.
-Sue
On Tue, 28 Sep 2004 09:41:28 -0700, "Jerrick D.H"
<JerrickDH@.discussions.microsoft.com> wrote:
>I'm currently using a domain account that has sysadmin rights; does this
>account need to be an administrator unter Window's 2000 server? I'm confused
>by everthing I've read.