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 High CPU on Common Services Tomcat server and Work Center search not finding new items - reindex of table automatically happening
High CPU on Common Services Tomcat server and Work Center search not finding new items - reindex of table automatically happening
CMS-XML Symptoms of Common Services being mis-configured. Generally see odd behavior in Work Center. Branding changes two systems at once, missing applications from menus etc.
Symptoms of Common Services being mis-configured. Generally see odd behavior in Work Center. Branding changes two systems at once, missing applications from menus etc.
CMS-XML JBoss starts and immediately stops with error "The Serena Common JBoss service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs."
The SBM\ Common \jboss405\lib\ folder must contain all of the jboss jar files. Specifically, jboss-system.jar must exist. The exact number of files in this folder will differ by version.
CMS-XML How to capture additional data received between the SBM RESTCaller and REST service. This is in addition to that captured by default in the Common Log.
SBM 10.1.4.X does not capture the actual data sent and received between the RESTCaller and the REST service so you can use one or more of the techniques in the attached document on how capture the actual traffic between OE, RESTCaller and REST service . ... Please schedule for the deletion of Common Log entries n the Application Repository when using. ... to SBM\ Common \jboss405\server\default\conf\jboss-log4j.xml
CMS-XML Get the following error in the common log using the RESTCaller web service connecting to an HTTPS url.
<faultcode>S:Server</faultcode> <faultstring>IO error from REST service </faultstring> <detail>
CMS-XML Service could not be installed. Verify that you have sufficient privileges to install system services
Executing op: ServiceInstall(Name=SERENAJBOSSSVC,DisplayName=Serena Common JBoss,ImagePath="C:\Program Files\Serena\SBM\ Common \jboss405\bin\jbosssvc.exe" -r SERENAJBOSSSVC,ServiceType=16,StartType=3,ErrorControl=0,,Dependencies=AFD[~]Tcpip[~][~],,,Password=* *********,Description=Serena common JBoss Application Server)
CMS-XML Common errors in server.log when JBoss or Tomcat can't communicate with the database server.
The most common place to look for errors related to JBoss or Tomcat having a hard time communicating with the database server is to look in the server.log. You will most likely see the following errors when these services start.
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 After installing RLM 4.x, the ALM configurator page displays a token service error.
truststore.jks And place them here: C:\Program Files\ Common \tomcat\6.0\alfssogatekeeper\conf
CMS-XML Orchestrations not running even though Event Manager receives the event - "The service cannot be found for the endpoint reference (EPR)" error in server.log
This has been resolved in the past by stopping the SBM Tomcat service , deleting the contents of the "SBM\ Common \tomcat\server\default\work" directory, and restarting the SBM Tomcat service to let it recreate the contents of that directory. If that does not resolve the issue, re-deploying the process app with the orchestration may resolve the issue.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs