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 Logging into Request Center and get "Error getting catalog: Forbidden"
Logging into Request Center and get " Error getting catalog : Forbidden"
CMS-XML Logging into Request Center get "Error getting catalog: Service Unavailable"
Logging into Request Center get " Error getting catalog : Service Unavailable"
CMS-XML Error getting catalog: Serena Security Token invalid or expired when logging into Request Center.
Error getting catalog : Serena Security Token invalid or expired when logging into Request Center.
CMS-XML Error getting catalog: Request entity too large OR Error getting Demand and Categories views: Request Entity too large
Error getting catalog : Request entity too large OR Error getting Demand and Categories views: Request Entity too large
CMS-XML Error Getting Catalog: No Service Catalogs Found. Contact your system administrator to make sure applications are promoted and services migrated.
Error Getting Catalog : No Service Catalogs Found. Contact your system administrator to make sure applications are promoted and services migrated.
CMS-XML Error "No service catalogs found" when trying to Customize the SSM catalog (Oracle only)
After performing all necessary steps to install SSM on a brand new Oracle database, we get the following error when attempting to "Customize" the Catalog . Error: No service catalogs found
CMS-XML User Workspace gives error "HTTP Error 500.19 - Internal Server Error", or SSM gives error "No Catalog Found: Internal Error"
When this problem happens, users may get error : HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid
CMS-XML ENCODE - DECODE gets error FILENAME DDELXXX.AE32B UNABLE TO ALLOCATE
FILENAME DDELXXX.AE32B UNABLE TO ALLOCATE IKJ56228I DATA SET DDELXXX.AE32B NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED RECORDS COPIED:
CMS-XML FDM batch job using PGM=IKJEFT01 issues RC=0 even when job gets error
DATA SET T250963.T250963.JCL.MLS.CNTL.TEST NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
CMS-XML Dim2009R2: Edit request get error: COR0005615E Another user is currently performing an operation on request
In this situation, once the problem is discovered, it may be possible to restore the change requests to a state where they may again be edited by moving the affected change requests from the primary catalog to the secondary catalog and then again back to primary.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Updating a work area from a stream (demonstration)
This Dimensions CM demonstration shows you how to update a work area from a stream, restrict the update to specific folders in the stream, and exclude files from the update.
Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes
Dimensions CM: Working with Items, Part 2 (demonstration)
This Dimensions CM demonstration shows you how to copy item revisions to a work area using the Get and Update commands, deliver a modified file from a work area to a stream using the Deliver command, and action an item revision

Additional Assistance

  • Submit a Case Online
  • FAQs