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 Version Manager could not open the access control database, "ACDB Path". Please contact your PVCS administrator for further assistance.
Version Manager could not open the access control database, "ACDB Path". Please contact your PVCS administrator for further assistance.
CMS-XML VM Make Secure: Serena PVCS Version Manager could not open the VCONFIG file "". Please contact your Serena Administrator for further details.
VM Make Secure: Serena PVCS Version Manager could not open the VCONFIG file "". Please contact your Serena Administrator for further details.
CMS-XML Error: Version Manager could not read the configuration file "..\master.cfg". Please contact your PVCS Administrator for further assistance.
Error: Version Manager could not read the configuration file "..\master.cfg". Please contact your PVCS Administrator for further assistance.
CMS-XML RIDE clients shows [INFO] Server-side processing can not be used with pre 8.4.1 server, switching to Client-side processing / Desktop Client cannot contact File Server
RIDE clients shows [INFO] Server-side processing can not be used with pre 8.4.1 server, switching to Client-side processing / Desktop Client cannot contact File Server
CMS-XML Can not login into SBM when use EVAL license - Licensing failure. No licenses are available. Please contact your administrator or try again later.
Can not login into SBM when use EVAL license - Licensing failure. No licenses are available. Please contact your administrator or try again later.
CMS-XML VMINET: JRUN shuts down when accessing VMINET.HTML. Returns: Could not connect to JRun Connector Proxy. Please contact the System Administrator for this web site.
VMINET: JRUN shuts down when accessing VMINET.HTML. Returns: Could not connect to JRun Connector Proxy. Please contact the System Administrator for this web site.
CMS-XML Launching SBM System Administrator or SBM Login Screen give error "InitExtension Failed" "License Server XXXX could not be contacted"
This error indicates that the SBM could not communicate with the Serena License Manager process.
CMS-XML DA: "Windows could not start the Agent Relay on the Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to the service-specific error code 0"
DA: "Windows could not start the Agent Relay on the Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to the service-specific error code 0"
CMS-XML If you create an auxiliary report via a reference link to the contacts table on SaaS and then include as an embedded report you get the error - Could not read report. The report was probably deleted.
If you create an aux report via a reference link to the Contacts table on SaaS, then include as an embedded report on a form in Composer. You get this error when displaying the form.
CMS-XML Logging into Repository or Composer gives "Authentication Failed: Unable to contact Authentication Service"
The error from the Mashup Repository was: Could not access Repository. Please ensure that your username and password are correct.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs