RSA Federated Identity Manager (FIM) Admin server of managed server startup failure
3 years ago
Originally Published: 2006-01-10
Article Number
000053771
Applies To
RSA Federated Identity Manager (FIM) 2.5
RSA Federated Identity Manager (FIM) 2.6
Microsoft Windows 2000 Server
Microsoft Windows Server 2003
BEA WebLogic 8.1
Issue
RSA Federated Identity Manager (FIM) Admin server of managed server startup failure
[Fatal Error] :-1:-1: Premature end of file
WebLogic Server 8.1 SP2  Fri Dec 5 15:01:51 PST 2003 316284 >
<Jan 10, 2006 3:00:16 PM EST> <Notice> <Management> <BEA-140005> <Loading domain
 configuration from configuration repository at C:\RSASecurity\FIM25\rsaappserver\config\csfdomain\config.xml.>
[Fatal Error] :-1:-1: Premature end of file.
***************************************************************************
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: error parsing configuration file - with nested exception:
[org.xml.sax.SAXParseException: Premature end of file.]'
Reason: weblogic.management.configuration.ConfigurationException: error parsingconfiguration file - with nested exception:
[org.xml.sax.SAXParseException: Premature end of file.]
***************************************************************************
Cause
A previous startup of RSA Federated Identity Manager (FIM) process fails and corrupts the config.xml file used to control the services
Resolution
A backup copy of the config.xml file should exist called config.xml.booted; this will be the last good copy. In some circumstances it is possible for this copy to have been overwritten by the corrupted copy as well. In this last case, another version called config.xml.original may be used, provided no changes have been made using the BEA WebLogic console.

If all these options fail, restore the system from the last known good backup.

Related Articles

Trending Articles

Don't see what you're looking for?