Microsoft KB Archive/836461

= You receive an &quot;An error occurred while creating the Single Sign-On (SSO) database&quot; error message when you run the BizTalk Server 2004 Configuration Wizard =

Article ID: 836461

Article Last Modified on 3/9/2004

-

APPLIES TO


 * Microsoft BizTalk Server 2004 Developer Edition
 * Microsoft BizTalk Server 2004 Enterprise Edition
 * Microsoft BizTalk Server 2004 Partner Edition
 * Microsoft BizTalk Server 2004 Standard Edition

-





SYMPTOMS
When you run the Microsoft BizTalk Server 2004 Configuration Wizard (Configureframework.exe) to configure Microsoft BizTalk Server 2004, you may experience the following symptoms:  You receive an error message that is similar to the following:

An error occurred while creating the Single Sign-On (SSO) database  on   (Could not create default log file because the name was too long. Error code 0X80040E14).

 If you click Retry, you receive the same error message. If you click Cancel, the installation is rolled back, and the following information appears in the BizTalk Server 2004 Configuration Wizard:

Configuration failed
The configuration failed and no settings were applied.

A Logfile has been created in your temp directory.

  If you click the Logfile link, information that is similar to the following appears in the log file: [4:28:37 PM Info SSOServerCfg] Entering function: CSSOServerCfg::ConfigureFeature [4:28:37 PM Info SSOServerCfg] Writing Single Sign-On (SSO) registry settings [4:28:37 PM Info SSOServerCfg] Searching for Single Sign-On (SSO) database databaseName on ComputerName [4:28:37 PM Info ConfigHelper] Did not find existing database: databaseName on computer: ComputerName [4:28:37 PM Info SSOServerCfg] Single Sign-On (SSO) database databaseName does not exist on ComputerName [4:28:37 PM Info SSOServerCfg] Creating Single Sign-On (SSO) database databaseName on ComputerName [4:28:38 PM Error ConfigHelper] Could not create default log file because the name was too long. [4:28:38 PM Error ConfigHelper] SQL error: 42000 Native error code: 1819 [4:28:38 PM Error ConfigHelper] c:\depot4000\jupiter\source\private\common\configwizard\confighelper\sqlhelper.cpp(1450): FAILED hr = 80040e14 [4:28:38 PM Error ConfigHelper] c:\depot4000\jupiter\source\private\common\configwizard\confighelper\sqlhelper.cpp(1389): FAILED hr = 80040e14 [4:28:38 PM Error ConfigHelper] c:\depot4000\jupiter\source\private\common\configwizard\confighelper\sqlhelper.cpp(572): FAILED hr = 80040e14 [4:28:38 PM Error ConfigHelper]    Failed to create SQL database: databaseName on computer: ComputerName collation: Default [4:28:38 PM Error ConfigHelper] Could not create default log file because the name was too long. [4:28:38 PM Error SSOServerCfg] c:\depot4000\jupiter\source\private\mozart\source\sso\ssoconfiguration\ssoservercfg\ssoservercfgimpl.cpp(1048): An error occurred while creating the Single Sign-On (SSO) database databaseName on ComputerName (Could not create default log file because the name was too long. Error code 0X80040E14). [4:28:38 PM Info SSOServerCfg] Leaving function: CSSOServerCfg::ConfigureFeature 



CAUSE
This problem occurs if you try to configure a database that has more than 123 characters in its name. Microsoft SQL Server 2000 supports database names that are 127 characters in length. However, when you configure BizTalk Server 2004, the default transaction log file is configured with the same name as the database with _log appended to it. If the database name is more than 123 characters in length, the appending of _log exceeds the permitted length of an SQL Server 2000 database name.



WORKAROUND
To work around this issue, do not specify a database name that is more than 123 characters in length.

Additional query words: kbBTSSso

Keywords: kbsetup kbprb kbdeployment kbbtshat kbbtssso KB836461

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.