DTC problems connecting to server 2003

I have all the symptoms of KB article 839279:
"When you run a distributed transaction against an instance of SQL Server,
you may receive an error message that is similar to the following:
Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider
'SQLOLEDB' was unable to begin a distributed transaction. [OLE/DB provid
er
returned message: New transaction cannot enlist in the specified
transaction coordinator. ] OLE DB error trace [OLE/DB Provider 'SQLOLEDB
'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
This problem may occur when one of following conditions is true:
Microsoft Windows Server 2003 or Microsoft Windows XP Service Pack 2
(SP2) is installed on the computer that initiates the distributed
transaction.
Microsoft Windows Server 2003 or Microsoft Windows XP SP2 is installed on
the remote computer that is running Microsoft SQL Server 2000, and that
computer is linked to the computer that initiates the distributed
transaction."
In my case, Windows server 2003 is running SQL server 2000, and I am trying
to do an INSERT INTO <table> EXEC <storedproc> from another computer that
has SQL server 2000 installed.
I can link the remote server, and run the stored proc and look at the
resulting records, but I can't do the INSERT INTO using the result of the
stored procedure -- I get the message:
Server: Msg 8501, Level 16, State 1, Line 1
MSDTC on server 'server\database' is unavailable.
Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider
'SQLOLEDB' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d01c].
In the "workaround" section of the KB article, Step 2, substeps g-i are not
possible on Windows server 2003 (non-SP1). It says to select Allow
Inbound and Allow Outbound, and also to check No Authentication Required in
the Transaction Manager Communication box. I can't! Those choices do not
appear in the dialog boxes.
Any suggestions on how to set the DTC "No Authentication Required" option?
David WalkerSEE http://support.microsoft.com/defaul...kb;en-us;827805
from http://support.microsoft.com/?kbid=555017
Disable RPC Security for MSDTC Service on SQL Server
This step requires accessing and modifying the registry. If you have
not already done so, it is highly recommended that you back up the
registry at this time.
1. Click Start, click Run, type in "Regedt32", and click OK.
2. Select HKEY_LOCAL_MACHINE, then SOFTWARE, then Microsoft.
3. Right-click on MSDTC, point to Add, then select DWORD Value.
4. Rename the key from the default New Value #1 to
TurnOffRpcSecurity.
5. Double-click the new key and change the value to 1.
6. Close the Registry Editor and restart the SQL Server

DTC problems connecting to server 2003

I have all the symptoms of KB article 839279:
"When you run a distributed transaction against an instance of SQL Server,
you may receive an error message that is similar to the following:
Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider
'SQLOLEDB' was unable to begin a distributed transaction. [OLE/DB provider
returned message: New transaction cannot enlist in the specified
transaction coordinator. ] OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
This problem may occur when one of following conditions is true:
Microsoft Windows Server 2003 or Microsoft Windows XP Service Pack 2
(SP2) is installed on the computer that initiates the distributed
transaction.
Microsoft Windows Server 2003 or Microsoft Windows XP SP2 is installed on
the remote computer that is running Microsoft SQL Server 2000, and that
computer is linked to the computer that initiates the distributed
transaction."
In my case, Windows server 2003 is running SQL server 2000, and I am trying
to do an INSERT INTO <table> EXEC <storedproc> from another computer that
has SQL server 2000 installed.
I can link the remote server, and run the stored proc and look at the
resulting records, but I can't do the INSERT INTO using the result of the
stored procedure -- I get the message:
Server: Msg 8501, Level 16, State 1, Line 1
MSDTC on server 'server\database' is unavailable.
Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider
'SQLOLEDB' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d01c].
In the "workaround" section of the KB article, Step 2, substeps g-i are not
possible on Windows server 2003 (non-SP1). It says to select Allow
Inbound and Allow Outbound, and also to check No Authentication Required in
the Transaction Manager Communication box. I can't! Those choices do not
appear in the dialog boxes.
Any suggestions on how to set the DTC "No Authentication Required" option?
David Walker
SEE http://support.microsoft.com/default...b;en-us;827805
from http://support.microsoft.com/?kbid=555017
Disable RPC Security for MSDTC Service on SQL Server
This step requires accessing and modifying the registry. If you have
not already done so, it is highly recommended that you back up the
registry at this time.
1. Click Start, click Run, type in "Regedt32", and click OK.
2. Select HKEY_LOCAL_MACHINE, then SOFTWARE, then Microsoft.
3. Right-click on MSDTC, point to Add, then select DWORD Value.
4. Rename the key from the default New Value #1 to
TurnOffRpcSecurity.
5. Double-click the new key and change the value to 1.
6. Close the Registry Editor and restart the SQL Server

DTA Common Error and sp1

Does anyone know if sp1 resolves the common DTA error "failed to initialize CRT"? I found this KB article on it http://support.microsoft.com/Default.aspx?kbid=913395, yet this resolution did not work for my boxes (i have both a laptop and desktop with 2005/build 1399 developer). I did not notice this error being listed in the http://support.microsoft.com/kb/916940

Thanks,

Derek

Guys,

2.Also please check if an environment variable __COMPAT_LAYER is set?
"set __COMPAT_LAYER=" , basically disabled the compat layer and dta
ran OK

i added this EV and DTA now works, but I shouldnt have to do this. Does sp1 resolve and if not I assume sp2?

|||I went ahead and applied sp1 all common components (this DOES INCLUDE CLIENT COMPONENTS) of sp1/x86 and sure enough it works? Where is this listed in the sp1 fixes?|||for the sake of clarity, the first fix (environmental variable) was applied to my laptop. the second fix (sp1 common components) was applied to my desktop.

DST and Notification Services

I need some clarification on Daylight Saving Time changes for SQL
Server 2005.
I read MicroSoft Article 931815.
Per the doc, I have determined that I have Notification Services
installed (determined via registry).
However, I do not seem to have any Notification Services to stop (step
1) and not sure what name to use for NSMainDatabase (running the osql
script in step 5).
>From the SQL Server Management Studio, I can determine that I have
version 9.0.242.0 of Notification Services, but it tells me that NO
instances are registered on this machine.
So, please advise if you have any input. I am about 80% confident that
I don't need to do this fix.
Thanks,
RogerIf you do not have an instance of Notification Services deployed, then you
do not have to worry about patching. The binary files of Notification
Services are not affected. You have to apply the update only when you create
an instance. If there are no services running and no NS* databases, then
really nothing to do. Also, for instances deployed after SQL Server 2005 SP2
is installed you do not have to do anything, as instances created with SP2
will have the correct DST info.
HTH,
Plamen Ratchev
http://www.SQLStudio.com|||On Mar 6, 2:59 pm, "Plamen Ratchev" <Pla...@.SQLStudio.com> wrote:
> If you do not have an instance of Notification Services deployed, then you
> do not have to worry about patching. The binary files of Notification
> Services are not affected. You have to apply the update only when you crea
te
> an instance. If there are no services running and no NS* databases, then
> really nothing to do. Also, for instances deployed after SQL Server 2005 S
P2
> is installed you do not have to do anything, as instances created with SP2
> will have the correct DST info.
> HTH,
> Plamen Ratchevhttp://www.SQLStudio.com
I thank you for your comments. Much appreciated.

DST and Notification Services

I need some clarification on Daylight Saving Time changes for SQL
Server 2005.
I read MicroSoft Article 931815.
Per the doc, I have determined that I have Notification Services
installed (determined via registry).
However, I do not seem to have any Notification Services to stop (step
1) and not sure what name to use for NSMainDatabase (running the osql
script in step 5).
>From the SQL Server Management Studio, I can determine that I have
version 9.0.242.0 of Notification Services, but it tells me that NO
instances are registered on this machine.
So, please advise if you have any input. I am about 80% confident that
I don't need to do this fix.
Thanks,
RogerIf you do not have an instance of Notification Services deployed, then you
do not have to worry about patching. The binary files of Notification
Services are not affected. You have to apply the update only when you create
an instance. If there are no services running and no NS* databases, then
really nothing to do. Also, for instances deployed after SQL Server 2005 SP2
is installed you do not have to do anything, as instances created with SP2
will have the correct DST info.
HTH,
Plamen Ratchev
http://www.SQLStudio.com|||On Mar 6, 2:59 pm, "Plamen Ratchev" <Pla...@.SQLStudio.com> wrote:
> If you do not have an instance of Notification Services deployed, then you
> do not have to worry about patching. The binary files of Notification
> Services are not affected. You have to apply the update only when you create
> an instance. If there are no services running and no NS* databases, then
> really nothing to do. Also, for instances deployed after SQL Server 2005 SP2
> is installed you do not have to do anything, as instances created with SP2
> will have the correct DST info.
> HTH,
> Plamen Ratchevhttp://www.SQLStudio.com
I thank you for your comments. Much appreciated.