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 After upgrading to Mariner 2008 R3 get "Database specified in security token is not supported by this server" error or Dataset1 error when running reports.
After upgrading to Mariner 2008 R3 get "Database specified in security token is not supported by this server" error or Dataset1 error when running reports.
CMS-XML KM-Dim14: Eclipse-MAC: No value for $TERM and no -T specified git: 'credential-osxkeychain' is not a git command.
KM-Dim14: Eclipse-MAC: No value for $TERM and no -T specified git: 'credential-osxkeychain' is not a git command.
CMS-XML Investment tree won't sort after upgrading to Mariner 2008.
After upgrading to Mariner 2008 R1 or R1 the investment tree won't adhere to the sort order specified under the "Manage My Settings" screen.
CMS-XML Version Manager: PCLI errors when users forget to specify files or projects when using PCLI commands.
When a PCLI command operating on files or projects is not given a file or projec to work on, users will get one of the following errors depending on what command is being used: AddFiles: This command requires one or more files to add. AssignGroup: This command requires one or more projects or versioned items.
CMS-XML The documentation for JBuilder 8 integration doesn't clearly state that you should use the Status Browser to view the version control status of files
The Borland JBuilder chapter in the Serena ChangeMan Integrated Products Guide specifies for each SCM activity that the status of the files can be seen by options being enabled or disabled. It does not point out that you can use the Status Browser to see the visual indication of file status, although it does have a section called "Viewing the VCS Status".
CMS-XML How to find all reports that were created by users no longer in the system that still run on a schedule.
When you mark a user in Mariner/PPM as inactive or delete them completely from the system, any reports that user had created as scheduled reports won't be removed. Consequently, they continue to run on the specified schedule. You may want to stop these reports from running but aren't able to login as that user to delete them.
CMS-XML RA 3.3.x: Completion and other events from Serena Release Automation are not reported to Release Control (SBM)
To specify the Serena Release Automation server: 1 On the Serena Release Automation server, navigate to the Serena Release Automation
CMS-XML Member ULTIDVSA is not found in the MAC Distribution Library
Defines the maximum block size to be used when optimizing a data set residing on the specified device type. You can specify half track, full track, or user defined block size targets for the device. The maximum value that can be coded is 32760.
CMS-XML Beyond Firewall, Host name, DNS Alias, FQDN: Having a Firewall is not necessary
The name of this parameter is misleading as to its use. It is not necessary for a firewall to exist in the network infrastructure for this setting to be of value when configuring SBM. Beyond Firewall simply says whenever a client machine (web browser, Composer, etc.) needs to access SBM, send a URL to the client using the host name and port specified in the "Beyond Firewall" section, otherwise format the URL using the host name.
CMS-XML Get. "Could not load file or assembly 'Serena.SaaSUserDirectory.Mariner" error on login screen after installing patch.
Version=2009.3.3.309, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs