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 Rest Grid fails to send request to server
Rest Grid fails to send request to server
CMS-XML SLM service fails to launch on UNIX - SerenaLicenseSerer.log has error "(lmgrd) merant exited with status 47 (Child cannot exec requested server)"
The SLM server refuses to launch on UNIX. Attempting to launch it via start_license_server
CMS-XML SSO server throws error: A request failed with the exception [com.ctc.wstx.exc.WstxLazyException] Unexpected character '(' (code 40) (expected a name start character)
When launching the Serena VM Web Application Server with the SSO server enabled, an error similar to the following can be thrown:
CMS-XML Dim2009R1: Error: Failed to Query Request Provider Instance Information. NCL0004747E Error: Failed to execute RPC 135. occurs on login and/or after creating a new project in Desktop Client.
Dim2009R1: Error: Failed to Query Request Provider Instance Information. NCL0004747E Error: Failed to execute RPC 135. occurs on login and/or after creating a new project in Desktop Client.
CMS-XML DIM: DTC: Error: Failed to Query Request Provider Instance Information NCL0004747E Error: Failed to execute RPC 135
The above error will occur if we are unable to find request provider definition in the database. By default, Dimensions CM Request Provider is defined for product '$GENERIC', it's definition is placed in ext_tool_catalogue and ext_tool_spec_catalogue. This can be verified by running the following through SQLPlus as the basedatabase user:
CMS-XML PCLI repeatedly requests the same license, causing the SLM License Server to (temporarily) fail for all users
Under certain circumstances it is possible for PCLI to flood the License Server with repeated request for the same User@Host combination. Even though this will only use a single license on that server, the sheer number of requests can effectively make SLM server stop working by using up all the available TCP ports on the operating system running SLM. Without available ports, SLM server clients (and clients of any other server process running on the OS) can no longer establish a new TCP connection.
CMS-XML Java Requirements For Fail Over Servers
One of the Unix Main Server Requirements is that we have Java 1.3.1 installed. If there is going to be a Fail Over server does it also need the same requirements.
CMS-XML Dim12: Change Request Report fails to run on Unix server and gives no error message
If a Dimensions CM Windows server is available, this report runs to completion on a Windows server . This problem has been forwarded to R&D for correction in a future version.
CMS-XML Multiple requests to detach and attach the impact analysis dataspace (IADS) eventually fail
In order to allow the dynamic reload of data into the Impact Analysis Dataspace (IADS) using the LDSLOAD job, customers can dynamically detach and re-attach the IADS to the active ZMF Server using modify commands. The first pair of detach (F task,CMN,DETACH,IADS
CMS-XML Dim10: Replicator: Replication of Requests fail because the project is not on the subordinate site
Dimensions 10.1.0.5 Windows Server During a Request Replication session requests failed to replicate because the project is not on the subordinate site.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Title: Dimensions CM: Deploying Emergency Fixes (demonstration)
This demonstration shows you how to deploy an emergency fix to a live production environment in Dimensions CM. You will learn how to promote requests to any stage in the Global Stage Lifecycle, promote and deploy in the same operation, and browse deployment areas.
Title: Dimensions CM: Scheduling Deployment (demonstration)
This demonstration shows you how to schedule a deployment in Dimensions CM. You will learn how to set a deployment sequence, schedule a deployment, and use the Queue tab in the Deployment view

Additional Assistance

  • Submit a Case Online
  • FAQs