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 User Error: #427 OPTIONS|SECURITY GPF - USER, GROUP AND PRIVILEGE WITH SAME NAME
User Error : #427 OPTIONS|SECURITY GPF - USER, GROUP AND PRIVILEGE WITH SAME NAME
CMS-XML Error: Cannot open file. Either you do not have network privileges to open the file, or the path name to the file does not exist.
Error : Cannot open file. Either you do not have network privileges to open the file, or the path name to the file does not exist.
CMS-XML ERR: Directory name is not a directory
ERR: Directory name is not a directory the customer was getting the following error when running a script on a certain file..
CMS-XML Mover transfers files to incorrect location if VM folder has the same name as a project
Mover transfers files to incorrect location if VM folder has the same name as a project
CMS-XML VM: SSO Login gives error "First Element must contain the local name, Envelope , but found html"
While attempting to login to an SSO enabled Project Database, the following error is shown: PCLI commands will have the error: First Element must contain the local name, Envelope , but found html
CMS-XML Mover transfers VM files to an incorrect location if the folder in VM has the same name as a project name
Mover transfers VM files to an incorrect location if the folder in VM has the same name as a project name
CMS-XML Random "Could not find a revision named XXX" errors when using a Version Label that starts with a number for a Get operation
Random "Could not find a revision named XXX" errors when using a Version Label that starts with a number for a Get operation
CMS-XML Checkout or Get by a Version Label which starts with a number will give the error: "Could not find a revision named [LabelName] in the archive [ArchivePath]"
When performing a Check Out or Get by Version Label using a label with the same layout as a Revision Number (#.#, #.#.#, etc.), or, when running a VM release prior to 8.1.1, using a label that just starts with a number, the operation fails with the error : Could not find a revision named LabelName in the archive
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 VM 8.6.0: HTTP 400 error in the VM I-Net Web Client when browsing for labels from projects with a space in their name
When using the Label browser feature, to pick a label that already exists on another file, the VM I-Net Web Client will throw an HTTP 400 error if the project you are trying to select a file from has a space in its name .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs