| |
Results |
|
KM-Dim7: Visual Basic crashes when adding a project to Dimensions via SCC
|
Run IDE setup Create brand new item type definitions and remove the old item type defs IDE setup now points to item definitions that do not exist any more
|
|
|
|
KM-Dim9: Rhapsody: 2351-Error: Filename Documents\RhapsodyDiagrams\Project:12345678:12345678.rh contains one or more of the following invalid characters: "*|?<>:
|
The current workaround is to create a brand new Rhapsody project with the same project name and desired directory structure. This will create a .rh file for Dimensions. Now open the existing project that you originally were trying to add, select "Add to Archive" and then select the newly created .rh
|
|
|
|
Error: INT APPROVED: INT PB: REGISTRATION OF LIBRARY ENTRY FAILED
|
A user connects to the SCCAPI successfully, and creates a brand new config file. He set up his project and went to start registering his objects. It thinks about it for a few seconds, and then pops up the message. He clicks OK, and in his case, it kicked him back to PB Native mode. (I tested it, and could recreate the error, but for me it remained in SCC-PVCS mode.) It is only a few PBL's in this application, that cause this to happen.
|
|
|
|
Adding a workfile gives "Could not add the file because a versioned file already exists"
|
Delete the file and the archive from the project (File -> Delete) so it can be added again as a brand new file.
|
|
|
|
VM2DIM: Migration Console shows Error:2018: Project top-level config file "SomeConfigFile" not found for File Server-based Project Database
|
VM2DIM: Migration Console shows Error:2018: Project top-level config file "SomeConfigFile" not found for File Server- based Project Database
|
|
|
|
Dim12: New imported based, create project reports table cannot be found
|
A basedb was exported and re-imported using a different name. Now it is no longer possible to create new projects .
|
|
|
|
VM: File Server-based Project Database using SSO login source disconnects after successful login
|
When a File Server-based Project Database is using the SSO login source, it is possible for the Project Database to show up with a Red-X icon after the credentials check passed successfully. A PCLI command executed against the same Project Database may return: Access to this project has been denied because your login account, UserID
|
|
|
|
How to solve: Warning: file "Filename" was accessed from "EntityPath" in File Server-based Project Database "ProjectDatabasePath", but this path does not use a File Server.
|
To solve the problem, find the corresponding File Server-based location on the server and update the path accordingly. For incorrect Archive paths, either delete the file reference from the project and use Admin -> Import Archives to import them using a correct path. PCLI users can use the command:
|
|
|
|
Version Manager clients shows "sun.security.validator.ValidatorException: PKIX path building failed" while trying to connect to an SSO-based Project Database
|
Version Manager clients shows "sun.security.validator.ValidatorException: PKIX path building failed" while trying to connect to an SSO- based Project Database
|
|
|
|
Dim CM 14.x: Unable to connect to new Base Database created with Process Model export
|
COR3200878E Could not find any Lifecycle with specification COR3200879E Could not find any Project with UID 1 COR0005261E Error: Lifecycle not found
|
|
|
