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 Error: #1082 PvcsGetRevision returns Error 37: PVCS_E_PROMO_NO_NODE
Error : #1082 PvcsGetRevision returns Error 37: PVCS_ E _PROMO_NO_NODE
CMS-XML How To: #611 Error Messages following PVCS_E_INTERNAL - PVCS_E_NO_ATTRIBUTE
How To: #611 Error Messages following PVCS_ E _INTERNAL - PVCS_ E _NO_ATTRIBUTE
CMS-XML Error: Error 16 - PVCS_E_NO_MEMORY (Oracle Dev2000
when checking out from Developer 2000. This error was produced because there was a
CMS-XML Solving the errors PVCS_E_WORKDIR_NOT_FOUND / could not write to the project "WorkDir" directory / PVCS_E_ARCHIVEWORK_DIR_NOT_FOUND / could not write to the project "ArchiveWork" directory
While performing a Version Manager operation, one of the following error messages is displayed: You have encountered an internal processing error: 119 (PVCS_E_WORKDIR_NOT_FOUND: The "WorkDir" directory does not exist or is not writeable.) The "WorkDir" directory does not exist or is not writeable.
CMS-XML How To: #614 Error Messages following PVCS_E_CANT_DELETE_SEMAPH - PVCS_E_SCRIPT_NOT_
Internal error number 67. Call INTERSOLV Answerline."
CMS-XML History Report on Label gives PVCS_E_NO_USER_ID error when LOGIN = VCSID, VLOGIN
This works well for all operations, except Show History and PCLI vlog operations involving a version label (eg. GUI Actions -> Show History -> Report type: List revisions with version label, or the PCLI command "pcli vlog -bv"). For those operations, roughly every other file in the report fails with the error :
CMS-XML How To: #612 Error Messages following PVCS_E_CANT_LOCK - PVCS_E_GROUP_LOCKED
Internal error number 33. Call INTERSOLV AnswerLine."
CMS-XML Software Error: #757 Parentheses in filenames
PROBLEM: When trying to create archive from a file with parentheses in the name, e .g., FUNDS(1).DAT, Version manager returns an error "Can't find workfile."
CMS-XML Incorrect REFERENCEDIR set by desktop interface
If a reference directory is configured on a sub-project with the option "keep a reference directory for each archive directory" starting from the root of a network drive ( e .g. L:\) an error on check in (cannot write to L:\/*) is received - a backslash gets added to L: and the project.cfg
CMS-XML Incorrect Operation: DTK: Error #33 when doing a PvcsPutRevision
Description: The following sample code returned an error code of 33: PVCS_ E _PROMPT /* * PvcsPutRevision Example
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs