| |
Results |
|
Dim10: After upgrade to Dimensions 10.1.2, error of PRG5401204E Failed to initialize server context occurs when logging into Desktop Client and Web Client
|
Dim10: After upgrade to Dimensions 10.1.2, error of PRG5401204E Failed to initialize server context occurs when logging into Desktop Client and Web Client
|
|
|
|
DimCM: SSO: When using the SBM SSO Server with SmartCard authentication and Dimensions CM, users are unable to log into the Clients and AdminConsole
|
When using SBM SSO Server with SmartCard authentication and Dimensions CM, the following error may occur showing the SBM Logo Page:
|
|
|
|
KM-Dim9: Dimensions 9.1.3: Failed to connect to the Dimensions Server after upgrading.
|
Check that logging is turned off or that the -tracedir variable points to a location accessible by all users such as /tmp.
|
|
|
|
KM-Dim7: How to save temporary log files generated when using Dimensions commandline utility?
|
The first option is editing the Dimension configuration file (pcms.cfg) and comment out the PCMS_DELETE parameter. Therefore preventing the operation from cleaning up after running. Please be advised that commenting the above parameter will apply system wide and you may need to continuously monitor and clear the temporary folder locations defined on the server and the client you are issuing the command from.
|
|
|
|
DimCM: SSO Server: Enabling additional logging for the Dimensions CM SSO Server
|
ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF 4. Change the uncommented lines from INFO to TRACE. 5. Restart Tomcat which will restart the SSO Server .
|
|
|
|
VM 8.6: Resetting the workfile location to "." not logged correctly in change.log
|
Old values, computed and as stored in the PDB: C:\FS_PDBs\SampleDB\archives>pcli gwl /chess/ server /server.bat Serena PVCS Version Manager (PCLI) v8.6.0.0 (Build 370) for Windows/x86_64
|
|
|
|
MCLG: ''Links pointing to the unmapped root: System are unresolved. A deploy location needs to be associated with this root.'' in the deploy log
|
This error occurs because one of the pages being deployed has a Collage nexus component in it that has been remarked out in the html. For instance , the code in the aforementioned error for the RemmedComponent.html file looks like this.
|
|
|
|
Error: #1122 Unable to access Project file/Server Not prepared when logging into Tracker Admin
|
Checked the trkw300.ini file to make sure the relevant entries in it (servername=, server_name=, [login.dBase.<path to db dir>]) were all pointing to the new location - they were.
|
|
|
|
MCLG: When creating a new project, the screen is blank, and error "Unable to read project options from server" is in the Tomcat log
|
If you still cannot find the file, contact Support and request a copy of this file. The Support team will need to know the exact version of Collage you are running. Once the file is in place , you should be able to create new projects.
|
|
|
|
How to change location, size or number of iterations of log files for Tomcat
|
C:\Program Files\Micro Focus\SBM\Common\tomcat\ server \default\webapps\notificationsrv\WEB-INF\notificationsrv.log4j.properties. log4j.appender.notificationsrv.File=${server.log.dir}/ns.log log4j.appender.notificationsrv.MaxFileSize=5024KB
|
|
|
