| |
Results |
|
SBM: Login screen redirects to idp but never loads and only displays a white screen
|
After the user entered the URL to the SBM login page, the URL will redirect to idp. However, the page is plain white and never loads.
|
|
|
|
SBM: Login screen shows error "java.lang.OutOfMemoryError: GC overhead limit exceeded"
|
Users get the login screen , but after entering their name/password, they get the following error: ALF Single Sign On error occurred while processing request Error message
|
|
|
|
Version Manager Web Client logs off user and shows login screen after using Tracker / TeamTrack / SBM Association dialog
|
Some users of the VM I-Net web client find that, after they have used the Association dialog during an Add Files, Checkout or Checkin operation, the requested operation is not performed, and the user is returned to the VM I-Net login screen instead. The behavior does not necessarily affect all users of the VM I-Net server. Although the behavior is fairly consistent for those users who are affected, sometimes operations complete without error.
|
|
|
|
Launching SBM System Administrator or SBM Login Screen give error "InitExtension Failed" "License Server XXXX could not be contacted"
|
This error indicates that the SBM could not communicate with the Serena License Manager process.
|
|
|
|
SBM Login screen just shows the "Loading" message and never moves.
|
HTTP Redirection If you are trying to login to SBM from the server check to see if you have "IE Enhanced Security" enabled like below. If this feature is enabled you can either.
|
|
|
|
How to brand the SBM Work Center login screen and UI (SBM 10.1.3 - SBM 11.7.1)
|
This document only covers Work Center on SBM 10.1.3 through SBM 11.7.1. For other versions, see these articles:
|
|
|
|
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.
|
|
|
|
After upgrade to SBM 10.1.4.x, login screen gives "Transport Error: 403 Error: Forbidden"
|
Transport Error: 403 Error: Forbidden If you check the SSO-IDP.LOG located in [ SBM INSTALL DIR]\common\jboss405\server\default\logs, you will see the error below. Error acquiring security token: Transport error: 403 Error: Forbidden
|
|
|
|
Can't get to SBM login screen on a client system but you are able to get to the login screen on the SBM server with Single Sign On enabled.
|
One reason this may happen is if the SBM server has the Windows Firewall enabled. By default there is an exception in the windows firewall to allow thw World Wide Web Services (HTTP Traffic) but with Single Sign On enabled you might also need to create a firewall rule to allow the Single Sign On port traffic through.
|
|
|
|
Adding a Logon Consent Banner/Notice to the SBM login screen with SSO enabled
|
oginnotice.jsp file that is located in the SBM Install directory: SBM 10.1.1.x and earlier:
|
|
|
