Whenever we restart sql server the following error appears:
2005-12-20 12:34:22.28 server Attempting to initialize Distributed
Transaction Coordinator.
2005-12-20 12:34:22.31 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
When I check the MSDTC service in the SQL service manager to see if is
running - the service says it is running. Do I still have anything to worry
about?
We are running SL server 2000 sp3a.
thanks
MeenalHi
Checking other posts it seems that this is a warning telling you that MSDTC
has not started at the time and most people seem to ignore it. You could mak
e
the SQL Service dependent on MSDTC although this is not a usual condition an
d
will slow down the bootup process.
John
"Meenal Dhody" wrote:
> Whenever we restart sql server the following error appears:
> 2005-12-20 12:34:22.28 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2005-12-20 12:34:22.31 server Failed to obtain
> TransactionDispenserInterface: Result Code = 0x8004d01b
> When I check the MSDTC service in the SQL service manager to see if is
> running - the service says it is running. Do I still have anything to wor
ry
> about?
> We are running SL server 2000 sp3a.
> thanks
> Meenal
>
>|||Many thanks
Meenal
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:ECF7845A-79A0-4D8E-91EC-0D367454B336@.microsoft.com...
> Hi
> Checking other posts it seems that this is a warning telling you that
MSDTC
> has not started at the time and most people seem to ignore it. You could
make
> the SQL Service dependent on MSDTC although this is not a usual condition
and[vbcol=seagreen]
> will slow down the bootup process.
> John
> "Meenal Dhody" wrote:
>
worry[vbcol=seagreen]|||Meenal Dhody Wrote:
> Many thanks
> Meenal
> "John Bell" <jbellnewsposts (AT) hotmail (DOT) com> wrote
THis won't cause any issue because SQL server starts earlier than DTC.
This happens due to chain process, that DTC depends on RPC and it takes
long time.
If you able to access SQL server once it is released for use then ok.
Else you can add depend on in the registry of regedt32 for sql server
Cheers,
muthu
Muthu
---
Muthu's Profile: http://www.dbtalk.net/m370
View this thread: http://www.dbtalk.net/t302909
Showing posts with label initialize. Show all posts
Showing posts with label initialize. Show all posts
Wednesday, March 21, 2012
Error in sql log when restarting SQL server
Whenever we restart sql server the following error appears:
2005-12-20 12:34:22.28 server Attempting to initialize Distributed
Transaction Coordinator.
2005-12-20 12:34:22.31 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
When I check the MSDTC service in the SQL service manager to see if is
running - the service says it is running. Do I still have anything to worry
about?
We are running SL server 2000 sp3a.
thanks
MeenalHi
Checking other posts it seems that this is a warning telling you that MSDTC
has not started at the time and most people seem to ignore it. You could make
the SQL Service dependent on MSDTC although this is not a usual condition and
will slow down the bootup process.
John
"Meenal Dhody" wrote:
> Whenever we restart sql server the following error appears:
> 2005-12-20 12:34:22.28 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2005-12-20 12:34:22.31 server Failed to obtain
> TransactionDispenserInterface: Result Code = 0x8004d01b
> When I check the MSDTC service in the SQL service manager to see if is
> running - the service says it is running. Do I still have anything to worry
> about?
> We are running SL server 2000 sp3a.
> thanks
> Meenal
>
>|||Many thanks
Meenal
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:ECF7845A-79A0-4D8E-91EC-0D367454B336@.microsoft.com...
> Hi
> Checking other posts it seems that this is a warning telling you that
MSDTC
> has not started at the time and most people seem to ignore it. You could
make
> the SQL Service dependent on MSDTC although this is not a usual condition
and
> will slow down the bootup process.
> John
> "Meenal Dhody" wrote:
> > Whenever we restart sql server the following error appears:
> >
> > 2005-12-20 12:34:22.28 server Attempting to initialize Distributed
> > Transaction Coordinator.
> > 2005-12-20 12:34:22.31 server Failed to obtain
> > TransactionDispenserInterface: Result Code = 0x8004d01b
> >
> > When I check the MSDTC service in the SQL service manager to see if is
> > running - the service says it is running. Do I still have anything to
worry
> > about?
> > We are running SL server 2000 sp3a.
> >
> > thanks
> > Meenal
> >
> >
> >|||Meenal Dhody Wrote:
> Many thanks
> Meenal
> "John Bell" <jbellnewsposts (AT) hotmail (DOT) com> wrote
THis won't cause any issue because SQL server starts earlier than DTC
This happens due to chain process, that DTC depends on RPC and it take
long time.
If you able to access SQL server once it is released for use then ok
Else you can add depend on in the registry of regedt32 for sql server
Cheers,
muth
--
Muth
----
Muthu's Profile: http://www.dbtalk.net/m37
View this thread: http://www.dbtalk.net/t30290
2005-12-20 12:34:22.28 server Attempting to initialize Distributed
Transaction Coordinator.
2005-12-20 12:34:22.31 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
When I check the MSDTC service in the SQL service manager to see if is
running - the service says it is running. Do I still have anything to worry
about?
We are running SL server 2000 sp3a.
thanks
MeenalHi
Checking other posts it seems that this is a warning telling you that MSDTC
has not started at the time and most people seem to ignore it. You could make
the SQL Service dependent on MSDTC although this is not a usual condition and
will slow down the bootup process.
John
"Meenal Dhody" wrote:
> Whenever we restart sql server the following error appears:
> 2005-12-20 12:34:22.28 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2005-12-20 12:34:22.31 server Failed to obtain
> TransactionDispenserInterface: Result Code = 0x8004d01b
> When I check the MSDTC service in the SQL service manager to see if is
> running - the service says it is running. Do I still have anything to worry
> about?
> We are running SL server 2000 sp3a.
> thanks
> Meenal
>
>|||Many thanks
Meenal
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:ECF7845A-79A0-4D8E-91EC-0D367454B336@.microsoft.com...
> Hi
> Checking other posts it seems that this is a warning telling you that
MSDTC
> has not started at the time and most people seem to ignore it. You could
make
> the SQL Service dependent on MSDTC although this is not a usual condition
and
> will slow down the bootup process.
> John
> "Meenal Dhody" wrote:
> > Whenever we restart sql server the following error appears:
> >
> > 2005-12-20 12:34:22.28 server Attempting to initialize Distributed
> > Transaction Coordinator.
> > 2005-12-20 12:34:22.31 server Failed to obtain
> > TransactionDispenserInterface: Result Code = 0x8004d01b
> >
> > When I check the MSDTC service in the SQL service manager to see if is
> > running - the service says it is running. Do I still have anything to
worry
> > about?
> > We are running SL server 2000 sp3a.
> >
> > thanks
> > Meenal
> >
> >
> >|||Meenal Dhody Wrote:
> Many thanks
> Meenal
> "John Bell" <jbellnewsposts (AT) hotmail (DOT) com> wrote
THis won't cause any issue because SQL server starts earlier than DTC
This happens due to chain process, that DTC depends on RPC and it take
long time.
If you able to access SQL server once it is released for use then ok
Else you can add depend on in the registry of regedt32 for sql server
Cheers,
muth
--
Muth
----
Muthu's Profile: http://www.dbtalk.net/m37
View this thread: http://www.dbtalk.net/t30290
Monday, March 19, 2012
Error in Reporting Services Configuration Manager
Hello
I've got an error when I want to initialize the Report Server by means of RS Configuration Manager.
All points are check in green except "Encryption Keys" that is in "Optionnal configuration" and "Initialization" that is in "Not Configured".
When I click on "Initialization" an error occured :
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable)
When I want to browse the report this error occured:
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) (rsRPCError). Cannot generate SSPI context.
Someone can help me ?
Thanks
Arnaud
I am having the same problem.
|||First make sure you have correctly entered and apply the information on the "database setup" panel. I think the "Cannot generate SSPI context" error may contain a clue. A quick search found the following kb: http://support.microsoft.com/?id=811889. Let us know if it helps.Error in Reporting Services Configuration Manager
Hello
I've got an error when I want to initialize the Report Server by means of RS Configuration Manager.
All points are check in green except "Encryption Keys" that is in "Optionnal configuration" and "Initialization" that is in "Not Configured".
When I click on "Initialization" an error occured :
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable)
When I want to browse the report this error occured:
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) (rsRPCError). Cannot generate SSPI context.
Someone can help me ?
Thanks
Arnaud
I am having the same problem.
|||First make sure you have correctly entered and apply the information on the "database setup" panel. I think the "Cannot generate SSPI context" error may contain a clue. A quick search found the following kb: http://support.microsoft.com/?id=811889. Let us know if it helps.
Subscribe to:
Posts (Atom)