Hello,

I am getting the following errors for BizTalk 2004 SQL Adapter:
1.  "Login failed for user"
2.  "Cannot Generate SSPI Context"

Because of the error thres hold growing too large BizTalk then shuts down
the adapters.  If I wait awhile then enable the adapters again the error
seems to go away.
1. Does anyone know why the SQL BizTalk Adapters are getting these errors et
c?
2. Also what can I do to keep the error thres hold from growing to large
causing the adapters to shut down?
Thank you in advance for your help!!! 
--
mj

[ Post a follow-up to this message ]

Hi mj,

There might be various of causes of this error. However if the first error
message is "Login failed for user 'null'". I suspected you may get into a
2-hop delegation problem which is related to MS DTC.

I suggest you verify the MSDTC setting on the biztalk server and your SQL
server. If they are using remote coordinator, I suggest you change one of
them to use local coordinator and point another to use this one as the
remote coordinator to have a test. This eliminates the possibility of a
third machine may lead to a 2-hop issue.

1. Launch Component Services Explorer. On the Start menu, point to
Programs, Administrative Tools, and then click Component Services.

2. Stop MS DTC services by right-clicking My Computer, and then clicking
Stop MS DTC.

3. Right-click My Computer. Click the Properties - MSDTC tab.

4. Change the Default Coordinator setting from Remote Host to Use local
coordinator.

5. On another server, change the Default Coordinator setting from Use local
coordinator to Remote Host and select the first machine as Remote Host
system.

If MSDTC isn't the root cause, I think you will have to open a service
incident to deeply diagnose this inconsistent issue. Thanks.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no rights.

[ Post a follow-up to this message ]

mj,
I have also seen this problem with the two hop issue, and in my reading
we found one solution that fit exactly for our problem.
The requirements art
you have two hops
you are using Active Directory (machines are members of a domain)

If so, you can try turning on the "Trusted for Delegation" flag on each
of the servers in the Active Directory to allow the calling computers
security context to be flowed from the calling server, through the
intermediate server to the SQL server.

This option is disabled by default.

Steps to Mark the Computer Account "Trusted for Delegation"
If the server process is running under a system account, the principal
account is the computer account in the Active Directory. Therefore, you
must make sure that you select the Trusted for delegation check box for
the computer account in the Active Directory. To do this, follow these
steps: 1. On the Domain controller, click Start, point to Programs,
point to Administrative Tools, and click Active Directory Users and
Computers.
2. Under your domain, click the Computers folder.
3. Under your computer account, click Properties.
4. On the General tab, select the Trusted for delegation check box.

http://support.microsoft.com/kb/283...=1&PA=1&SD=HSCH

This solved a nagging problem with MOM running WMI Scripts to start and
stop orchestrations. The MOM Server was starting the script on the BTS
Server, which then called API's to update state tables on the SQL
Server. This generated an error regarding the 'null' account attempting
to connect to the SQL Server.

Thanks,
Tom Canter

[ Post a follow-up to this message ]

mj,

One additional article that will help you resolve this:

How to troubleshoot the "Cannot generate SSPI context" error message
http://support.microsoft.com/kb/811...=1&PA=1&SD=HSCH

Thanks,
Tom Canter

[ Post a follow-up to this message ]

Hello Tom and WenJun,
Thank you both so much for your information and detailed reply.  This info
will help me and our network group troubleshoot the issue!

Have a great day! 

"Tom" wrote:

> mj,
>
> One additional article that will help you resolve this:
>
> How to troubleshoot the "Cannot generate SSPI context" error message
> http://support.microsoft.com/kb/811...=1&PA=1&SD=HSCH
>
> Thanks,
> Tom Canter
>
>

[ Post a follow-up to this message ]