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 VMINET: Windows Internal Error 0193: 1 is not a valid application
VMINET: Windows Internal Error 0193: 1 is not a valid application
CMS-XML VMINET: PVCS Version Manager Server 6.7.11 Service Pack 1 for Windows
VMINET: PVCS Version Manager Server 6.7.11 Service Pack 1 for Windows
CMS-XML How To: #1255 Make an Event Trigger call one program when triggered from Windows and another when triggered from DOS.
An Event Trigger in the Windows 3.1x Version Manager is best handled by a custom Windows program. The same Event Trigger in DOS command line Version Manager cannot use a Windows program. Instead it must use a DOS program or bat file.
MS-WORD For Windows (16 bit) follow steps 1-5 on EACH workstation
Operating System Windows 3.1 Windows 3.11 (enhanced mode only)
CMS-XML VM 8.0.0.2 HotFix 1a for Windows, Solaris & Linux
Extract the contents of the hotfix file into the root directory of your Version Manager installation. (By default on Windows , "C:\Program Files\Merant".)
CMS-XML VM 8.6.3: After installing the VM 8.6.3.2 patch on Windows, certool fails with java.lang.NoClassDefFoundError
at java.net.URLClassLoader$ 1 .run(URLClassLoader.java:369) at java.net.URLClassLoader$ 1 .run(URLClassLoader.java:363) ... at pvcs.vm.sso.certificate.manager.cmd.Client.<clinit>(Client.java: 20 )
CMS-XML The Merge tool window position obscures part or all of the window.
Windows Registry Editor Version 5.00 ... "NumberDerivatives"=" 20 " ... "FramesPosition"="- 20 ,7,931,452" "MergeState"=" 1 "
MS-WORD For VM Server installation on Windows:
1 ) tomcat.bat file in ...\vminet\tomact\bin directory. There are three parameters in this file that need to be modified.
CMS-XML VM: Install error 'Cannot run 16 bit Windows program'.
One possible cause for this error is a Windows operating system issue, which is explained on the Microsoft Knowledgebase in Document Q191690. http://support.microsoft.com/default.aspx?scid=kb;en-us;191690
CMS-XML vsplit on Windows fails to split very large archives
When splitting very large archives (actual size varies), it is possible that vsplit will fail with a message similar to this : <path-to-archive>:Failure failed err=- 1 , not converting This can happen because the connection from the client to the File Server timed out while the client (running vsplit) is processing the file.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs