Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML VM Web Application Server will not install as a service on Windows Server 2003 systems
However, when viewing the Services console, there is no service for the Serena VM Web Application Server anywhere in the console and the VM Web Client is not available.
CMS-XML The Serena VM Web Application Server no longer runs as a service after installing the VM 8.4.4 patch
After installing the VM 8.4.4 patch, the Serena VM Web Application Server service no longer starts up.
CMS-XML Error: VMINET 6.0: Cannot start service adminservice: Port 9090 is already in use.
Java Web Server ERROR: Cannot start service adminservice: Port 9090 is already in use. Change the port or shut down the other network service that is using it. Java Web Server UNRECOVERABLE ERROR: Cannot start services
CMS-XML VM: The Default JRun Service service failed to start due to the following error: The system cannot find the file specified. Error 0002
Re-install the Default Jrun Service . In the VM Server Configuration, select 'Remove NT Service', then select 'Install NT Service'.
CMS-XML Error 1053: The service did not respond to the start or control request in a timely fashion
This is a known defect in Windows 2003 Server. License Manager and VM Application Server service running as LocalSystem will return the error. Below is a link to the MS article with information about the defect including a link to get the hotfix.
CMS-XML No licenses are read by the License Manager ; hostid is ffffffff
Under some circumstances the SLM Server service / Serena License Server service doesn't start properly, because it cannot find any network adapters immediately following a system reboot. This can happen when using network adapters that need some time to initialize.
MS-WORD Run VM Server as an NT Service
This is a very important consideration for the following reason: When VM Server is running as a service with the default setup, it will start up as the Windows NT "System Account". This account has full access to the local drive, but no access to non-local drives and local drives mapped as network drives (i.e. mapping V: to the C: drive). Drive letter mappings are a function of a user login, and the service will start when no user is logged in.
CMS-XML Accessing file server in service mode
Prior to version 8.0 of PVCS Version Manager there is no real remedy for this problem, although you could write a batch file that creates the mapped drives and then starts the service . Running such a batch file as a scheduled task on system boot would allow the service to start with the knowledge of a mapped drive. This works for most people, although (according to Microsoft) its effectiveness is not guaranteed.
CMS-XML Any file based operation from the VM I-Net Web Client returns the error: Action was not performed because there were no items to process.
To solve this problem do the following: Stop the Serena VM Web Application Server service or application.
CMS-XML Version Manager Service vulnerability: Admin Tool (VPADMIN) should create Windows Service with quoted path to EXE
If the Version Manager server is installed in a directory that has a space in its path, the path to the executable that gets registered for the Serena VM Web Application Server service is not quoted.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs