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 Deploy status says "waiting". Deploy log shows a hang after "Awaiting Callback from Application Engine"
A deploy can sometimes appear to be stuck or hang . In the Repository (Mashup Manager), on the Activities screen, the deploy will have a status of "waiting". The last line in the Activity log for this deploy, will show:
CMS-XML IIS hangs with message in the application logs "Unknown Exception occurred during cleanup"
IIS regularly hangs and the application log shows that a required field was needed and an "Unknown Exception occurred during cleanup" similar to below:
CMS-XML Asynch Orchestration doesn't log a failure anywhere if using SSL with a certificate/connection problem to the Target Server
If you use a SSL url for your Event Manager or BPEL server and you have a certificate or connection problem it's extremely hard to troubleshoot because there are no errors logged anywhere for Asynch Orchestrations. The logging you do get doesn't show a problem and it looks like the orch should have run but the event never makes it to the AlfEventManager log. We should either log this connection failure somewhere or at the least make the Test Connect button fail in the Repository when there is an SSL Connection issue.
CMS-XML When you have Windows authentication after session timeout, page hangs instead of getting logged back in.
1. Describe the problem & the customer's use case scenario? When user stays logged into SBM and the session expires from timeout, the page appears to be loading, but doesn't load. 2. What are the steps to reproduce the problem?
CMS-XML Authentication failure with error of user being disabled
Authentication failing with the following error in the Application Event Viewer Log even though the user account is not actually disabled:
CMS-XML Incorrect overall deploy time calculation in the Activity Log
Currently SBM takes the stop time as a time when the Application Engine deployment was finished. After this though the SDF/SLA/Resman/WorkCenter deployments still have to take place.
CMS-XML Promotion failure: 500: problem closing services
An Oracle tablespace that has run out of space will cause a promotion to fail. The Activity log returns the following error after attempting to promote. This error may occur in other circumstances.
CMS-XML Error "InitExtension Failure: An error occurred while publishing resources from database" when login
When logging into the web interface of SBM, the user is immediately presented with the error message: InitExtension Failed: An error occurred while publishing resources from the database.
CMS-XML Finding fatal errors in install logs
Locating the failure point of an SBM installation in the MSI install log can be difficult in the sea of text. Searching for return values with knowledge of their context makes finding fatal failures a snap.
CMS-XML SBM: Tomcat will not stay running. Console log gives: Failed upgrading SLA server schema
After an upgrade, Tomcat will start, run for a few seconds, and stop . When looking in the console.log, the following error displays:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs