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 After upgrade from RLC 6.1 to RLC 6.2, new Release Package gives: File 'createDeploymenPath.groovy' not found in current ClassPath
After upgrade from RLC 6.1 to RLC 6.2, new Release Package gives: File 'createDeploymenPath.groovy' not found in current ClassPath
HTML Merant PVCS Version Manager Release Notes
If %TOMCAT_INSTALL% Is Set then VM I-Net will Not Serve Content Correctly [1036254] If you set a value for TOMCAT_INSTALL or CLASSPATH in your environment, those values could interfere with the correct operation of VM I-Net. The VM I-Net startup scripts have been modified to prevent this problem from occurring.
CMS-XML Build receiving error: /ecm/build/2955: syntax error at line 8;`$' unexpected
When executing a build on a UNIX server with a compile statement such as "$(JAVAPATH)/javac - classpath $(ECM_CLASS) *.java", Build receives error: /ecm/build/2955: syntax error at line 8;`$' unexpected. The exact same compile statement successfully built in previous versions of ChangeMan DS. JAVAPATH and ECM_CLASS variables are set in the root's environment.
CMS-XML DA: Process step fails gives error like java.lang.SecurityException: Prohibited package name: java.lang
The agent is running in a JRE. For security reasons, Java does not allow duplication of some class names, such as java.lang. If the Java CLASSPATH contains a file list that causes Java to load more than one instance of a reserved class such as java.lang, they this error is the result.
MS-WORD For VM Server installation on Windows:
%JAVA_HOME%\java - classpath "% CLASSPATH %" -Dpvcs.tempFiles=..\temp -Djava.path=. -Djava.library.path=. -Dpvcs.daemons.useDaemons=false
TEXT ReadmeVSS.txt
Please refer to the PVCS Version Manager Administrator's Guide for information about how to use this utility. Installation ~~~~~~~~~~~~ The installation of this product MUST be in the directory where Version Manager is installed. If the current location of Version Manager is different from where it was originally installed (i.e. moved to a different location or renamed), the installation will succeed but the Utility will fail to run unless you modify the CLASSPATH and PATH environment variables.
CMS-XML DA: Getting started with the groovy plugin
The process step includes properties for the script and also for the classpath containing groovy libraries. This would be the location on the agent machine where groovy classpath files can be found. You can simply use something like: C:\Program Files (x86)\Micro Focus\Deployment Automation Agent\core\lib\groovy-all-1.8.6.jar - where this represents the full path to the Groovy installed with the agent.
CMS-XML Problem: VMINET: JWS cannot handle environment variables with quoted strings.
The affected variables are PATH , JAVA_HOME , and CLASSPATH
CMS-XML SRA: Plugin: Groovy plugin issue
# Create the final classpath . Setting a classpath using the -cp or -classpath option means not to use the
CMS-XML MashupMgr does not work. Orchestrations do not work. Did JBOSS start correctly?
2014-12-16 16:31:34,731 INFO [main] [org.apache.catalina.startup.ClusterRuleSetFactory] [::] -- Unable to find a cluster rule set in the classpath . Will load the default rule set.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs