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  
CMS-XML SBM: Repository Runtime URL is blank; gsoap gives 404; sbminternalservices72 gives 404; error: "Failed to contact Authentication Service"
This error typically means that the Repository cannot connect to the runtime gsoap for this envrionment. You can verify this by going into the Repository under Environment > select the problem environment > Select the Details tab (General tab in older versions) > Look at the " Runtime URL " field. This should fill in automatically when there is a valid entry in the "URL" field.
CMS-XML The Application Repository uses host name for the runtime URL
The Application Repository uses host name for the runtime URL
CMS-XML Repository gives error "Unable to contact the server at the url http://server/gsoap/gsoap_ssl.dll?sbminternalservices72"
On the Details tab (called "General" in older versions), verify that the URL and the Runtime URL are valid. If you are unsure, edit the environment and use the Test Connection button to verify.
CMS-XML Changing the Application Engine Port Number When SSO Is Enabled
URL: http://ServerName:80/gsoap/gsoap_ssl.dll?aewebservices71 Runtime URL : http://ServerName:80/tmtrack/tmtrack.dll? c. Click Edit
CMS-XML When trying to promote a snapshot there are no SLA's to choose from.
Another good way to see that you may be having this problem is to look at the Environment in Application Repository. If the Runtime URL field for any of your environments is using http instead of https and you're setup to require SSL in IIS this will happen. The runtime URL field pulls its value from the AE server and unless you have port 80 disabled the runtime url will continue to try and use port 80.

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs