Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 980960 - Last Review: March 29, 2010 - Revision: 1.0
A BizTalk host instance does not start, and event IDs 10514 and 10536 are logged in the Application log
In a Microsoft BizTalk Server environment, a BizTalk host instance does not start. Additionally, events that resemble the following are logged in the Application log when this problem occurs:
Event ID: 10514
Source: ENTSSO
Description: An error occurred when trying to access the SSO database.
Function: LookupXp
File: lookupserver.cpp:328
Arithmetic overflow error converting IDENTITY to data type int.
Arithmetic overflow occurred.
SQL Error code: 0x00001FB3
Error code: 0xC0002A21, An error occurred while attempting to access the SSO database.
Event ID: 10536
Source: ENTSSO
Description:
SSO AUDIT
Function: GetConfigInfo
Tracking ID: GUID
Client Computer: computer_name
Client User: user_name
Application Name: application_name or GUID
Error Code: 0xC0002A21, An error occurred while attempting to access the SSO database.
Note This problem might also occur when you use Enterprise Single Sign-On (ENTSSO) with Host Integration Server.
This problem occurs when the
xl_identity column in the dbo.SSOX_AuditXpLookup table in the ENTSSO database reaches its maximum value. The
xl_identity column is defined to use an
INT data type that has a maximum value of 2,147,483,647. Therefore, when the number in this column exceeds the limit of the
INT data type, an arithmetic overflow error occurs.
We recommend and support the following solution for this problem. This solution changes the
xl_identity column to use a
BIGINT data type instead of an
INT data type.
To change the column's data type by using Microsoft SQL Server Management Studio (SSMS), follow these steps:
- Open SQL Server Management Studio.
- Connect to the SQL Server where the ENTSSO database is located.
Notes- You can confirm the name (SSODB is the default database name) and location of the ENTSSO database by using the BizTalk Server or Host Integration Server configuration tool.
- If the ENTSSO database exists on SQL Server 2008, you must disable the option that prevents saving changes that require table re-creation. To do this, follow these steps:
- Open SQL Server Management Studio.
- On the Tools menu, click Options.
- In the navigation pane of the Options window, click Designers.
- Click to clear the Prevent saving changes that require the table re-creation check box, and then click OK.
Note The Prevent saving changes that require the table re-creation option can be re-enabled after the following changes are made.
- Expand the Databases folder.
- Locate the Tables folder under the ENTSSO database.
- Expand the dbo.SSOX_AuditXpLookup table.
- Under the Columns folder, right-click xl_identity and then click Modify.
- In the middle pane, select the drop-down in the Data Type column for xl_identity.
- Select bigint as the new data type.
- On the File menu, click Save SSOX_AuditXpLookup to save the changes.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
APPLIES TO
- Microsoft BizTalk Server 2009 Branch
- Microsoft BizTalk Server 2009 Developer
- Microsoft BizTalk Server 2009 Enterprise
- Microsoft BizTalk Server 2006 Developer Edition
- Microsoft BizTalk Server 2006 Enterprise Edition
- Microsoft BizTalk Server 2006 Standard Edition
- Microsoft BizTalk Server 2006 R2 Branch Edition
- Microsoft BizTalk Server 2006 R2 Developer Edition
- Microsoft BizTalk Server 2006 R2 Enterprise Edition
- Microsoft BizTalk Server 2006 R2 Standard Edition
- Microsoft Host Integration Server 2006 Enterprise Edition
- Microsoft Host Integration Server 2006
- Microsoft Host Integration Server 2009
- Microsoft BizTalk Adapters for Host Systems
- Microsoft BizTalk Adapters for Host Systems 2.0
| kbtshoot kbbug kbexpertiseinter kbsurveynew kbprb KB980960 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate