Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML "Failed to contact Authentication Service", Repository Runtime Server URL is blank; gsoap gives 404; sbminternalservices72 gives 404
Response You must use a POST request to get answer from gsoap ! If you do not get the response above, try the following known use cases.
CMS-XML When users try to login, they get error "Invalid User ID or password" even when the information is correct
Copy the URL from the error and put it in your browser. A successful message will say "You must use a POST request to get answer from gsoap !" Any other message is an error.
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 "Premature end of file" error in sso-idp.log or mashupmgr.log
"You must use a POST request to get answer from gsoap !" In this instance the error shown was the following: "HTTP Error 403" You Don't have authorization to view this page.
CMS-XML Invalid user name or password with SSO enabled, cannot log into Application Repository if SSO is disabled
If you do not get an invalid post request , and instead get an internal 500 error referencing the sbmproxy, then set the gsoap virtual directory to use the same application pool that the tmtrack virtual directory uses. This will be fixed in a later release, but is a valid workaround in current versions of SBM.
CMS-XML How to get more logging when the SBM GSOAP web service is called
You can use the attached registry keys to enable some very basic logging about the soap request and response that gets sent and received from notifications or other web services. This can be particularly helpful when a soap request or response is too large and gets chopped of in the Common log. This logging will show the entire request and response envelope.
CMS-XML RLC: After upgrade, release packages that were left in one of several states require additional post-upgrade transitions
deployed - if an release package (RP) has a child RP, deployment execution information is incorrect after unlinking because QA Result and QA Complete are missing deployment error - error on Retry; it has the incorrect environment picker, and therefore you can't select and deselect tasks If you cannot complete them before upgrading, you must use the provided transition to get the release package to the correct place in the workflow to move forward.
CMS-XML Failed to obtain security token: Web Services "http://serverName/gsoap/gsoap_ssl.dll?sbminternalservices72" returned an error: "java.lang.IllegalArgumentException"
Here is the output in the notification log after submitting an new item to the system using outlook for the creation of the request .
CMS-XML Environment server is not accessible on URI: http://stal-vrtxp:80/gsoap/gsoap_ssl.dll?aewebservices70.
Server.log shows messages along the lines of : 2009-07-14 12:48:07,369 INFO [STDOUT] 12:48:07,369 INFO [HttpMethodDirector] Retrying request 2009-07-14 12:48:28,306 INFO [STDOUT] 12:48:28,306 INFO [HttpMethodDirector] I/O exception ( caught when processing request: Connection timed out: connect
CMS-XML Using SBM web service with Visual Studio or Visual Web Developer gives The request failed with HTTP status 404: Not Found when run.
<service name="aewebservices71"> <documentation> gSOAP 2.7.17 generated service definition</documentation> <port name="aewebservices71" binding="tns:aewebservices71">
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
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

Additional Assistance

  • Submit a Case Online
  • FAQs