This corruption can cause 500 errors or connection reset errors when accessing a particular IIS virtual application. Sometimes the failed virtual application is GSOAP which will hide the root cause in SBM logs while the SBM User Workspace appears to work in most cases . Use standard IIS troubleshooting to make sure that you can access files in the gsoap virtual directory.
*This error will appear if you have a couple records in the table (but is still incomplete from the required 33). If this is the case , truncate the table and rerun the script.
In some cases , an upgrade of HP Quality Center (ALM) or another change can cause web service calls to the qcbug web service that gets installed by the Quality Center Connector for SBM to fail with a fault string of "Class not registered."
Stop web server. Edit properties and change the port to port 81 in case the service gets started again, it won't affect SBM on IIS. * This internal web server is only used for troubleshooting only and is not meant to be run in a production environment.
This built in webserver can conflict with IIS as they both use Port 80 by default. We often recommend changing the default here to something other than 80 in case this built in web service gets started accidentally.
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 .
This will typically happen when there is another application such as Version Manager occupying Tomcat's SHUTDOWN port 8005. In such a case modify either the SBM Tomcat SHUTDOWN port or the SHUTDOWN port of the other product to something else so that there is no conflict. The SHUTDOWN port is configured in ...\Tomcat 7.0\server\default\conf\server.xml file.
Edit the value in the "Database Hostname" to be the server name (or IP address) of the server hosting the Oracle Database (in some cases the server name will need to be the fully qualified server name).
You will see this error if your SBM database is using a collation that is Case Sensitive. One of the pre-requisites for SBM is that the database be Case Insenstive. To fix this change the Collation of the SBM database to be non- case sensitive.
