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 stops working for a Process App - no errors - just never ends
If you have a Process App which suddenly (without any environment changes) now seems to hang on deploy a deploy then please check the activity log . Does it stop directly after the below and never continue?
CMS-XML 12.2.0.2 : RC of MVS post-deploy script is not returned in the log of the deployment consol
add in the dm.cfg of the sever the new variable then as follow : DM_WAIT_FOR_MVS_DEPLOYMENT_SCRIPT Y (and stop /start the server) do a test by forcing a rc=8 and status=failed in the command rstat of the post-event script. this status is well displayed in the remote job as well but in the deployment console still get the same message :
CMS-XML Notification server - faulty template encoding causes error loop and hanging
Seconds after starting the Notification Server, it hangs. It can't be stopped through "Manage Services" any more and no notifications are being sent either. In the Windows Application Event Log an error of this kind will appear multiple times:
CMS-XML Purging the audit log history impossible to cancel permanently on SQL Server and can cause deadlocks with Oracle - java.exe CPU 100% even after restarting
If you purge an audit log in application administrator and then decide to cancel it then the purge activity keeps restarting itself ( Stopping JBOSS and rebooting server makes no difference). Contact Support for information on how to stop this activity permanently.
CMS-XML Invalid Setting Can Break Application Repository Log
To work around this problem: Stop the JBoss service. Open the mashupmgr.log4j.properties
CMS-XML SBM filling event logs with LDAP authentication messages
LDAP bind authentication failure with ou=people,o=test.com,o=SDS(uid=P4DTI-replicator0): 32
CMS-XML Terms.htm error in application event log
The workaround for stopping the error messages is to create a blank file called Terms.htm in the location that is in the error message.
CMS-XML JBoss service does not stop in some cases
The JBoss service wrapper was changed in SBM 2009 R4 and in some instances, the service does not stop gracefully. Errors will be recieved in the service_shutdown.log located in "Program Files\Serena\SBM\Common\jboss405\server\default\ log ".
CMS-XML Dim 12.1.1 - Event Call-Out Pre-Op Event Return of PCMS_FAIL Fails to Stop CM
Logged as a defect
CMS-XML Improving Common Log Performance when Debug Logging Is Enabled for Orchestrations
Save your changes. Stop and start the Serena Common JBOSS Service.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs