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 PCLI get command on UNIX client throws "could not read the information stored in the archive" error, but the desktop client GUI running on the same system has no problems getting this file
Please do not perform any operations that will update the repository (Put, AddFiles, etc.) while this variable is in effect unless you are certain the repository is File Server-based. ... as the user who installed Version Manager (a.k.a. the setuid user) or as a system administrator .
CMS-XML Exception thrown while trying to restore record from archive in SBM 10.1 and newer
Attempting to restore an item from archive in SBM 10.1 and newer after upgrading from a previous version can result in the following error message: "Exception thrown while trying to restore record from archive Insert Error: Column name or number of supplied values does not match table definition."
CMS-XML After making an archive update, user gets: Serena PVCS Version Manager could not read the information stored in the archive ""
As a result the actual archive was not changed, so there is no permanent damage, but the archive change the user tried to make has been lost.
CMS-XML "The item could not be found" error when trying to view item due to data truncated error
"We're sorry, but the last operation caused an error. The last operation resulted in an error, but the following unrecognized error code was received: The item could not be found."
CMS-XML Dim CM 14.1.x: MDHNCL4501155E Error: Failed to write metadata for file "//DIMADM.PDEV.DIM.DEV2.URTLIB(GL0UNEX)"(rc = 5 msg = Verb DimPutRecord had outcome rc-rea: 5-11;
A problem was reported writing metadata files during a deployment on Mainframe. The same set of items was successfully deployed to two other areas:
CMS-XML Dim10: VM2DIM: Warning:8005:Shared Archive is shared by the following items to be migrated: -or- Warning:8005:TestPdb
), each shared instance of an item is treated as a separate entity, and a separate Dimensions item will exist for each instance. For example, if a single Version Manager file is shared across three PDB locations being migrated, the resulting Dimensions repository will contain three separate items with the file contents .
CMS-XML VM Server Error: "Could not find directory. Check-in <workfile> Archive: <archive> File: <archive> Work Item: <file>"
I had him change this directory to one that granted him full access. It appears that the Start-In directory effect the put operation whether there is an event trigger defined or not. In UNIX environments, the "Start-In" directory would be the directory from which VM is launched.
CMS-XML Problem: Keyword Expansion produces unexpected results if the archive directory contains a Dollar character
No data is lost but the effect is not pretty and may lead to very long lines of text.
CMS-XML Dim10: LDAP: Failed to connect to the Dimensions server. LDAP Error: (49) Invalid credentials, LDAP Server Error: 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 52e, vece, PRG4500325E Error: User authentication failed - LDAP bind to server failed
6. Along with the above items ( results from the above steps), please provide the following: a. A copy of the current dm.cfg used for testing the above items. b. Verification of what OS the LDAP servers are running on.
CMS-XML Software Error: PVCS Answerline #517 The command line option -# does not result in proper output of info.
PROBLEM: The GUI writes Diagnostic = n, where n is 0 by default, to
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs