The Microsoft BizTalk Server 2004 Configuration Wizard
(Configframework.exe) fails and generates an error message that is similar to
the following:
An error occurred while granting access to
Domain\SSO Administrators to the Single Sign-On
database SSODB on SQL Server (Error code
0X8007007A). Return Code: 2
Additionally, when you receive this error
message, the following
error message may be logged in the log file that is created by the Configuration Wizard:
[3:48:03 PM Info SSOServerCfg] Granting login access to
Single Sign-On (SSO) database SSODB on SQL Server
for Domain\SSO Administrators account
[3:48:03 PM Error SSOServerCfg]
c:\depot4000\jupiter\source\private\mozart\source\sso\ssoconfiguration\ssoservercfg\ssoservercfgimpl.cpp(1068):
An error occurred while granting access to
Domain\SSO Administrators to the Single Sign-On
database SSODB on SQL Server (Error code
0X8007007A).
Note In the error messages in this section,
Domain is a placeholder for the actual domain name
that contains the SSO Administrators group.
SQL
Server is a placeholder for the name of the computer that is running Microsoft SQL Server that
houses your BizTalk Server 2004 databases.
This problem occurs if the domain name for the user account that is used for the
SSO Administrator(s) is longer than 15 characters.
If the domain name that is used for the domain is longer than 15 characters,
the Configuration Wizard truncates the domain name. This behavior causes the
error messages that are mentioned in the "Symptoms" section.
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
888751Â
(http://kbalertz.com/Feedback.aspx?kbNumber=888751/
)
How to obtain the latest BizTalk Server 2004 service pack
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
File information
The English
version of this hotfix has the file attributes (or later) that are listed in
the following table. The dates and times for these files are listed in
coordinated universal time (UTC). When you view the file information, it is
converted to local time. To find the difference between UTC and local time, use
the
Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
-------------------------------------------------------------
02-Apr-2004 21:38 3.0.5270.0 31,232 Entsso.exe
02-Apr-2004 21:38 3.0.5270.0 67,584 Ssoadminserver.dll
02-Apr-2004 21:38 3.0.5270.0 37,376 Ssocsserver.dll
02-Apr-2004 21:38 3.0.5270.0 67,072 Ssolookupserver.dll
02-Apr-2004 21:38 3.0.5270.0 55,296 Ssomappingserver.dll
02-Apr-2004 21:38 3.0.5270.0 134,656 Ssoservercfg.dll
Microsoft has confirmed that this is a bug in the Microsoft
products that are listed in the "Applies to" section of this
article.
This problem was corrected in BizTalk Server 2004 Service Pack 1.