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 User gets: Unable to access. The filename may be illegal, the filename may already exist as a directory, part of the directory path may already exist as a file, the TEMP directory may not exist, or there may be insufficient privileges.
If the problem only happens during an Add Files operation, and the repository is located on a PVCS VM File Server, check both the Project DB path directory and
CMS-XML "Application Repository !Unable to load relation "import". Method not allowed (405) when importing SSM / SRC solutions
This can occur if SBM is setup to Use IIS to proxy all connections and the WebDav component is installed.
CMS-XML "Unexpected exception while creating deployment backup - Could not find a part of the path" error in Composer
To resolve the issue, edit the environment in the Application Repository and remove the trailing space after the name.
CMS-XML Login attempt to SBM 10.1 Application Repository fails with no error message
You must use a POST request to get answer from gsoap ! see WebWare gsoap ISAPI module documentation. If the URL cannot be reached because it is incorrect or needs a fully-qualified domain name, the server name can be changed in the Host field on the Component Servers tab in SBM Configurator in most cases.
CMS-XML Troubleshooting communication among SBM Components using Wireshark
SBM consists of components which can be installed on one or more servers. For example, SBM components include the Application Engine (or IIS component ), the Orchestration Engine, Application Repository and Common Services the last three components all running under JBOSS and Java. At times, it is necessary to capture communications between these components for troubleshooting purposes.
CMS-XML Application Repository receives Method Not Allowed (405) error when proxied through IIS
For Use Case 1, make sure that IIS does not have the WebDAV component installed. This component blocks the PUT and DELETE methods. This feature can be removed in the IIS Roles setup area under the Common HTTP Features section called "WebDAV Publishing".
CMS-XML "Failed to contact Authentication Service", Repository Runtime Server URL is blank; gsoap gives 404; sbminternalservices72 gives 404
In the SBM setup, JBoss and Tomcat components need to make calls to the GSOAP web services on the AE or IIS server. If the SBM Java setup does not have the SSL certificate trust chain in the Java trust store, you can get this message. To resolve this issue, import each certificate authority SSL certificate in the SSL trust chain using "Manage Trusted Certificates" on the JBoss/Tomcat tab in SBM Configurator.
CMS-XML Symptoms of Common Services being mis-configured. Generally see odd behavior in Work Center. Branding changes two systems at once, missing applications from menus etc.
Let's say you have two environments setup in SBM ( Prod and Test ). When you open Configurator on each box and look at the Components Server screen the only component that should technically be shared between envronments is Application Repository . In this situation you might have all the components setup and running on the Prod box but on the Test box you might have Common Services pulled out onto another box.
CMS-XML Invoking import callback: End of file or no input -- deploy activity is waiting forever
Find the location of the second Application Repository server and remove the repository component or make sure that it never connects to the same database as your production Application Repository database. For more information including how to remove the Repository component, see KB S140157 - Application Repository component and database setup .
CMS-XML Error on deploy: The endpoint reference (EPR) for the Operation not found is /mashupmgr/services/sbmimportcallback72 and the WSA Action = null or Invoking import callback failed: End of file or no input: The handle is invalid.
To resolve permanently, if scheduled deploys is something you regularly do, you can make the change below on the Server hosting the "Application Admiinstrator/Mashup Manager/Application Repository " (name of component depends on the version you are running). Locate the following file depending on if you use JBoss or Tomcat JBoss:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Comparing files (demonstration)
This Dimensions CM demonstration shows you how to compare two item revisions in the repository, and compare an item revision in the repository with a file in a work area
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 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
Dimensions CM: Viewing work area and repository changes (demonstration)
This Dimensions CM demonstration shows you how to use the Windows Explorer integration to view the changes made to a work area and a repository.

Additional Assistance

  • Submit a Case Online
  • FAQs