| |
Results |
|
Don't see SBM login form or get prompted with a windows security login prompt. Access to SBM denied
|
Don't see SBM login form or get prompted with a windows security login prompt. Access to SBM denied
|
|
|
|
Running setup.exe for SBM installer and nothing happens other than windows installer command line options popup displays.
|
When you run the setup.exe file to install SBM you see the following screen and the install just stops.
|
|
|
|
SBM: SQL Server using Windows authentication fails with "OpenEx failed with connect string"
|
OpenEx failed with connect string 'DSN= SBM ;UID=SerenaSBMAccount'.
|
|
|
|
Remove SBM from IIS -After upgrading Windows/IIS or installing patches, it is possible for corruption to occur in the applicationhost.config file. This corruption can cause 500 errors or connection reset errors when accessing a particular IIS virtual application.
|
After upgrading Windows /IIS or installing patches, it is possible for corruption to occur in the applicationhost.config file. This corruption can cause 500 errors or connection reset errors when accessing a particular IIS virtual application.
|
|
|
|
SBM: Submit and other transitions randomly fail with error: The transition "Submit" was not completed. Error attempting to add item to database.
|
If the SBM server is running on Windows 2016 (which comes with IIS 10), try disable HTTP/2. Although HTTP/2 should work fine, in some specific combinations of browsers and client certificates, it can fail.
|
|
|
|
SBM is not HTTP/2 compatible -- Submit failure - Duplicate attachments
|
How-To disable HTTP/2 on Windows Server 2016 and 2019 Logon to the Windows Server Start the Windows Registry Editor.
|
|
|
|
SBM 11.4.2 - SBM 12.0: SECURITY BULLETIN - CVE-2021-44228 and CVE-2021-45046 - RCE 0-day exploit found in Log4J
|
: A serious security issue affecting SBM , RCE 0-day exploit, has been found for log4j 2.0 – 2.14.1. For further information on the vulnerability, you can follow the Apache Log4j site . See the resolution below to eliminate the vulnerability in SBM.
|
|
|
|
VM I-Net Web Client login fails with HTTP ERROR 403 for servlets using an SBM SSO server for authentication
|
This error can be the result of an SBM SSO security enhancement that was introduced in SBM 11.5.1, and then backported to SBM 11.4.2 . (For this reason the error can first occur if SBM was upgraded from either SBM SBM 11.5.0, SBM 11.4.1 or an older release.)
|
|
|
|
Where are the SBM JDBC connections stored in 11.x?
|
SBM contains both a Windows component (IIS) and a Java component. IIS uses the ODBC Administrator for its database connection. SBM 11.x and Tomcat stores its database connection information in the following file.
|
|
|
|
InitExtension - Error Opening Database while logging on the SBM User WorkSpace.
|
If you get the below error and all the settings seem to be correct and the internal web server also works then you may have accidentally ticked to use Windows Authentication for SQL Server. InitExtension Failed: The data source 'DSN=Mashup2009;UID=sa' could not be verified.
|
|
|
