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 Login page gives "Internet Explorer cannot display the webpage" (404)
Login page gives "Internet Explorer cannot display the webpage" ( 404 )
CMS-XML SBM: Going to Work Center login gives 404 (Page can't be found)
When going to the work center login screen (such as http://localhost/workcenter), the browser will redirect to the full workcenter URL (such as http://localhost/workcenter/tmtrack.dll?shell=swc). However, then the browser returns:
CMS-XML Loading login page gives 404 error from the server
Users can log into SBM from their workstations, but when trying to open the login screen from a browser on the server, you get HTTP error 404 .
CMS-XML 404 error when trying to load SSO login page - server.log has error regarding "sbmSAML2SPConfigFilter"
SSO login page is getting a 404 error when trying to load the IDP URL. This particular issue has been seen in SBM 11.4.2, but it may exist in other versions as well. When looking at the Tomcat's server.log,
CMS-XML SBM: Error "HTTP Status 404 - Not Found" when trying to get to the Work Center login screen AND the Repository login screen (Nothing written to Tomcat logs)
With this use case, you may notice several problems: Both the Work Center login and the Repository login screens give a 404 error .
CMS-XML Dim14: Pulse: When attempting to access Pulse, a 404 error occurs with the an error of ORA-01017: invalid username/password; logon denied in the logfile
When attempting to access Pulse, a 404 error occurs. The logfile shows the following:
CMS-XML Cannot log into RM Browser after install or upgrade – IIS Error XML 404 – Dim RM 2009 R2
After installing RM 2009 R2 with an IIS web server attempts to login to the RM Browser result in an error "Error getting xml request: 404 ".
CMS-XML RLM to ZMF integration gives "We did not find any matches for your request (404)" and alm.log gives "Invalid byte 1 of 1-byte UTF-8 sequence"
The ZMF connector uses the SBM username as the login for ZMF, and this username does not exist in ZMF. In the example above, "admin" was logged into SBM, but this user does not exist in ZMF. Create the user in ZMF.
CMS-XML The request failed with HTTP status 404: Object Not Found.
"ISSUE: Errors every secong in the application log on the Portfolio Edge Application Server.
CMS-XML "Failed to contact Authentication Service", Repository Runtime Server URL is blank; gsoap gives 404; sbminternalservices72 gives 404
Error may be logged in the server.log file or sso-idp.log file when deploying to an environment.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs