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 ScanPDB does not detect PvcsID error / How to fix "Unable to read pvcsid file" error
000100 - Starting ScanPdb Processing : 000400 - Starting Project and Element Scan: 000500 - Project and Element Scan Completed: 0 errors detected.
CMS-XML java.lang.UnsatisfiedLinkError: C:\Program Files\Serena\vm\common\bin\win32\mljlib.dll: The specified procedure could not be found
java.lang.UnsatisfiedLinkError: C:\Program Files \Serena\vm\common\bin\win32\mljlib.dll: The specified procedure could not be found
CMS-XML Dim12: DOWNLOAD: When running the DOWNLOAD command, an error of "MDA4502721 Error: Failed to open file "C:\Users\dmsys\Application Data\plcd\plcd.dmdb": CreateFile() failed with 32 (The process can not access the file because it is being used by another process.)
Dim12: DOWNLOAD: When running the DOWNLOAD command, an error of "MDA4502721 Error: Failed to open file "C:\Users\dmsys\Application Data\plcd\plcd.dmdb": CreateFile() failed with 32 (The process can not access the file because it is being used by another process.)
CMS-XML Work Center Search Engine - Indexer Error in the SSF.log - Error in Commit ...The process cannot access the file because it is being used by another process
The below error can indicate that another process is conflicting. Typically we have seen this occur when the Indexing operation triggers an Antivirus to process the files.
CMS-XML Inability to Recover DELTA=Y file after MOVEGRP processing.
This causes orphaned DELTA records in the MASTER files. So the processing of the MOVEGRP needs to take into account of the objects DELTA's and there needs to be a way of recovering the orphaned DELTA's which are referencing the OLD GROUP. The message when the RECOVER takes place is as follows:
CMS-XML CM 12/14: Remote build returns: "FSY0004611E Error: Cannot open file C:\Users\dmsys\AppData\Local\Temp\tpl-1504164529-4-2684-2.log - the process can't access to the file because it is used by an other process"
Diagnosis: From the build monitor page showing below in the attached screenshot, clicking on the red button (located on the failing line - step 7 -) displays the following : Failed to read file : error.agent.read.file.failed:
CMS-XML KM-Dim9: Cannot issue CRDB: Error: Only the Dimensions DBA can create new base database. Error: Unable to open spool file 'setup_base_database.log' Error: detected in $DM_ROOT\dbms\common\setup_base_database.sql, line 213...will be passed for processing
Error: detected in c:\merant\dimensions\8.0\dbms\common\setup_base_database.sql, line 213 Called from c:\merant\dimensions\8.0\dbms\common\crdb.sql, line 258 The error will be passed to the caller for processing .
CMS-XML Can not stage (S1) HFS related files into package
Whenever the customer attempts to stage a UFS/HFS component from development (function S1) they receive a SER0344I Process initialization error and the component is not staged into the package. Effectively they cannot add any new HFS components into their ZMF system whilst this problem exists
CMS-XML Dim9: Cannot open file error while doing dmimport
During a dmimport process , the tool would return with an error similar to this: Importing Item "item-spec" ** Load POID Phase 1 (1) : <item-spec> Failed
CMS-XML Make procedure does not complete, unable to execute implementation scripts
A make procedure exists that creates four output target files. The target files get copied to a baseline area and versioned. However, when the target files get moved to the target baseline area there is a need to execute an implementation script for each file.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs