Find Answers

Filter Search Results
All Operating Systems:
All Others (379)
All Unix (816)
All Windows (1730)
All Products:
ChangeMan SSM (113)
ChangeMan ZDD (61)
ChangeMan ZMF (1570)
Development Manager (1853)
Dimensions CM (2624)
Dimensions RM (599)
PVCS Version Manager (603)
Project Portfolio Management (211)
Release Manager (1862)
SBM (2788)
Service Manager (1905)
StarTool FDM (221)
Agile (32)
Agile Planner (8)
Application Development Management (8)
Application Release Manager (12)
Builder (19)
ChangeMan DS (165)
ChangeMan ECP (6)
ChangeMan M+R (2)

More...
All Solution Types:
Documentation Update (412)
Error Message (916)
Installation & Customization (785)
Product Tips & Advice (2597)
Source:
Alerts (21)
Defects (6014)
Manuals (2188)
Patches (387)
Solutions (3953)
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Dim cm 14.5.2 : creation of JIRA external request provider => No attributes defined for this request provider
As a workaround it is proposed for the existing DB schema to start upgrade script in force mode: dmdba system/password@ dim 14 upgrade dbschema /force. After the upgrade, you can complete setup a Jira provider.
CMS-XML DIM: DTC: Error: Failed to Query Request Provider Instance Information NCL0004747E Error: Failed to execute RPC 135
When logging into the Desktop Client an error is occurring of: Error: Failed to Query Request Provider Instance Information NCL0004747E Error: Failed to execute RPC 135
CMS-XML Dim2009R2: SSO CAC: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.
Dim2009R2: SSO CAC: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.
CMS-XML Dim2009R1: Error: Failed to Query Request Provider Instance Information. NCL0004747E Error: Failed to execute RPC 135. occurs on login and/or after creating a new project in Desktop Client.
Error: Failed to Query Request Provider Instance Information. NCL0004747E Error: Failed to execute RPC 135. You can click OK to dismisses the error and continue without any problems.
CMS-XML Dim: How to trace an http request after a successful logon or logout in the Dimensions Web Client
•http://stackoverflow.com/questions/1112381/getting-active-session-counts-with-jmx-java-management-extensions-api •http://stackoverflow.com/questions/19827650/java-monitor-active-web-sessions As option, it is possible to use external monitoring tools like MoSKito or JavaMelody.
CMS-XML KM-Dim7: How to use Mime Types to Browse Change Documents via I-Net
NOTE: This configuration, of launching external applications from I-NET to browse change documents is not certified. This feature is only certified with HTML templates.
CMS-XML DIM9: Visual Studio 2005 Requires VSProvider Entry in Valid Set Definitions IDE_PROJECTS
Customer upgraded from Visual Studio 2003 to Visual Studio 2005 and now when they open source control they get the error: "The valid set ide_projects does not include an entry for the IDE vss provider "
CMS-XML Dim12: ALF Events: Relationship details are not being sent back to SBM
When attempting to use the ALF Events/Web Services to communicate with SBM and the Default IDM Provider has been set to SBM, the requests are being related to Items as an External Request Provider when we verify the relationship. However, when checking-out, creating a new item, etc., the Request/Issue is not being passed back to SBM.
Similar Answers
CMS-XML Dim CM 2009 R2: Double-synchronisation of defect with mandatory attributes gives error "Request with the same external identifier...already exists"
2. The new Request is created in CM, and has the correct "QualityCenter Project ID" and "QC Defect ID" attributes; 3. The affected Defect has the correct " Dim Link Name" and "DimensionsID" fields. Actual Result: -
PDF SERENA® DIMENSIONS® CM 12.2
At the present release, the only type of external request provider supported is Serena® SBM. This external request provider is supported in the Visual Studio and Eclipse Integrations, and the desktop client.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Title: Dimensions CM: Deploying Emergency Fixes (demonstration)
This demonstration shows you how to deploy an emergency fix to a live production environment in Dimensions CM. You will learn how to promote requests to any stage in the Global Stage Lifecycle, promote and deploy in the same operation, and browse deployment areas.
Title: Dimensions CM: Scheduling Deployment (demonstration)
This demonstration shows you how to schedule a deployment in Dimensions CM. You will learn how to set a deployment sequence, schedule a deployment, and use the Queue tab in the Deployment view

Additional Assistance

  • Submit a Case Online
  • FAQs