| |
Results |
|
Issues window is blank when using RIDE, VM 8.3 or 8.4 and SBM 2009 R2 or R3
|
Issues window and listing reports in SBM are blank when RIDE is used to link Version Manager 8.3 or 8.4, Visual Studio 2008 and SBM 2009 R1, R2 or R3. It has been determined that this problem only occurs if the IDE folder contains anything other than links to issues/items, like reports or other links. Another possible symptom is that while the window is not blank, the description field for anything other than an issue is blank.
|
|
|
|
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.)
|
|
|
|
Enabling IIS 7 for Version Manager I-Net breaks access to SBM on the same server
|
If VM I-Net is installed on a Windows server using IIS 7, enabling access through IIS will break access to SBM (and any other product using .dll in the URL). Attempting to go to http://server/tmtrack/tmtrack.dll? will show an error originating from Version Manager's Tomcat application server.
|
|
|
|
Using SourceBridge from the VM I-Net Web Client when the connection to the SBM server uses HTTPS (Secure Sockets Layer - SSL)
|
When using self-signed certificates, or when the JRE does not know the Certificate Authority that was used to sign the certificate, attempts to associate an issue (module association) from VM I-Net during checkout or checkin will yield errors similar to the following in the Tomcat logs (std*.log on Windows , catalina.out on UNIX):
|
|
|
|
VM 8.6.1+: Web Client shows SSLHandShakeException PKIX path building failed when trying to login to SBM to use Associate Issue
|
Log in to the machine running the VM Web Application Server as the user who installed Version Manager. On Windows open a Command Prompt on the server in Administrative mode (right-click | Run as administrator) Run the command:
|
|
|
|
Version Manager Rich IDE (RIDE) integrations fail to connect to SBM with error "Could not authenticate (Invalid user)"
|
Example: Restart IIS, for example by executing "iisreset" from an Command Prompt window The second variant of the error, where someone was able to get a working RIDE workspace with SBM integration, would normally indicate that the option was selected at the time the RIDE workspace was setup, but that it has since inadvertently been disabled.
|
|
|
|
How to set up associations between SBM records and PVCS Version Manager check in operations
|
for configuring servlets. For the Rich IDE (RIDE) integration to Eclipse on Windows and Linux or the RIDE integration to Visual Studio on Windows - there is a built in Issue Management component.
|
|
|
|
Version Manager Web Client logs off user and shows login screen after using Tracker / TeamTrack / SBM Association dialog
|
Windows : Go to Start -> Control Panel (or equivalent) and launch the Java Control Panel.
|
|
|
|
VM I-Net (web client) users can no longer perform module associations with TeamTrack or SBM after installing JRE 1.6.0 Update 22 (1.6.0_22) or newer
|
If the VM I-Net server is normally exclusively accessed using the Tomcat Web Server on one of its ports (e.g. 8080), an additional 3rd party Web Server will need to run on port 80 for the sole purpose of serving up the crossdomain.xml file. This could be IIS on Windows or Apache or UNIX.
|
|
|
|
Utility to update the SSO (Serena Single Sign-On) certificates used by PVCS Version Manager
|
Open a Command Prompt window on the SBM server and execute the following commands: SBM 10.1.3: cd "SBM_Installation_Directory\
|
|
|
