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
Article Product Downloads and Documentation Link
Please visit our products downloads page to obtain documentation on your product. For particular articles regarding your issue, try making your search more specific.
CMS-XML VM desktop client GUI shows error "ttsourcebridge.dll is not compatible to work with SSO token"
If you are using TrackerLink then you must migrate to SBM before you can use module associations from an SSO-enabled Project Database (see SourceBridge notes above). Whether you want to continue using Issue Management integration through SBM or not, the TrackerLink component must be disabled:
CMS-XML Migrating projects already in Version Manager to VS2005 / VM 8.1.3 Rich Integration
13. Go back to Visual Studio and re-open the solution by selecting File | Source Control | Open Project from Source Control. 14. Select the database , enter the login information, and click <next>. 15. Select a workspace and click <next>.
CMS-XML VM: How to copy or move a Version Manager Project Database (PDB) to another location
There are virtually no downsides to using the PVCS VM File Server data migration method. Only if Client Name happens contains the name of the old server might users be confused as the Client Name cannot
CMS-XML PVCS(J): Some double-byte characters cannot be used for file/folder/project names in File Server-based Project Databases
_normal"><font color="black" face="Verdana" size="2"><span style="font-size: 10pt;"><img src="http://knowledgebase.serena.com/library/KNOWLEDGEBASE/ Migrated /kbimages/5007748/1.GIF" border="0" /></span
CMS-XML VM 8.0.0.3 to Mover 1.0 migration. Moving to new server. Login failed errors.
Mover - Mover | System | users and groups | Authentication setup - Make sure the installation path and project database have the correct paths. If they do not, you will consistently get a login error, even if you are able to login as admin (but no one else).
CMS-XML VSS2VM: When running a migration and the VSS project structure is nested ~11+ levels deep the migration gives Java Hotspot errors
VSS2VM: When running a migration and the VSS project structure is nested ~11+ levels deep the migration gives Java Hotspot errors
CMS-XML KM-Dim9: Dim/VM: Migration from Version Manager into Dimensions - 2330-Error: No such attribute defined : VCS_REVISION
KM-Dim9: Dim/VM: Migration from Version Manager into Dimensions - 2330-Error: No such attribute defined : VCS_REVISION
CMS-XML Provide a way to enable pcli Get -ce by default, to ease migration from pre-VM 8.6.0.
Provide a way to enable pcli Get -ce by default, to ease migration from pre-VM 8.6.0.
CMS-XML VM: How to "migrate" from VM 6.5 to VM 6.6.
VM: How to &quot; migrate &quot; from VM 6.5 to VM 6.6.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs