Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Repository / Mashup Manager won't load and you see this error in the mashupmgr.log file "Failed to load user infomation from AE"
Repository / Mashup Manager won't load and you see this error in the mashupmgr.log file "Failed to load user infomation from AE"
CMS-XML SBM: Logging into Repository gives error: "org.xml.sax.SAXParseException; Premature end of file."
The login screen opens, and the user is able to enter login name/password, but then receives the following error: Error authenticating user "XXXX": Web Services "http://XXXX/gsoap/gsoap_ssl.dll?sbminternalservices72" returned an error "org.xml.sax.SAXParseException; Premature end of file ."
CMS-XML HTTP 500 Internal Server Error opening Application Repository. String index out of range: 68 in server.log file.
HTTP 500 Internal Server Error opening Application Repository . String index out of range: 68 in server.log file.
CMS-XML Get Internal Server Error (500) when logging into the Application Repository.
When you attempt to login to the Application Repository you see an error "Internal Server Error (500)" Look for the following errors in the followng two files on the SBM server. C:\Program Files\Serena\SBM\Common\jboss405\server\default\log\server.log
CMS-XML Logging into Repository gives error "Authentication error: A Soap fault occurred while contacting the authentication service"
Check the Application Repository log (Program Files \Serena\SBM\Common\jboss405\server\default\work\jboss.web\localhost\mashupmgr\ log \mashupmgr. log ) for additional errors. Common errors that we have seen are below:
CMS-XML SBM: Error "HTTP Status 404 - Not Found" when trying to get to the Work Center login screen AND the Repository login screen (Nothing written to Tomcat logs)
Only the console. log and Tomcat. log files are being updated. All other Tomcat logs are zero bytes. (You can verify this by stopping Tomcat, deleting all of the Tomcat\log files, then starting Tomcat.) At first glance, the Console.log and Tomcat.log do not give any errors and appear to be fine.
CMS-XML Invalid Setting Can Break Application Repository Log
Open the mashupmgr.log4j.properties file located in the installDir \Common\jboss405\server\default\deploy\mashupmgr.war\WEB-INF
CMS-XML Confusing Error message in Application Repository Log
Changed from error to warn in the case if the application does not contain *-sdf.xml/*-sla.xml file . Status check was added before processing response from SDF/SLA servers for deploy/undeploy cases in 10.1.1.1
CMS-XML High CPU on database for Application Repository at midnight and also when selecting to purge the "Audit History log"
(1) Instead of every day at midnight you can run this event every 3 months. To change the cron job from a nightly to 3-monthly cycle please open the following file and make the changes as below: In SBM\Common\tomcat\server\default\webapps\mashupmgr\WEB-INF\mashupmgr.cfg changeAR_MONITORING_CRON=0 0 0 * * ?
CMS-XML The Global assets should be updated in the repository once the deployment completes
When promoting Global Application between environments, the Activity Logs throws the following message:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Comparing files (demonstration)
This Dimensions CM demonstration shows you how to compare two item revisions in the repository, and compare an item revision in the repository with a file in a work area
Dimensions CM: Viewing work area and repository changes (demonstration)
This Dimensions CM demonstration shows you how to use the Windows Explorer integration to view the changes made to a work area and a repository.

Additional Assistance

  • Submit a Case Online
  • FAQs