If a user attempts to log in to the SBM 10.1 Application Repository and they do not get an error message while the " Sign In " button remains disabled, this could be caused by the gsoap virtual directory in IIS not being accessible or the wrong URL being used for sbminternalservices72. This will write an error message in the "sso-sts.log" located in the "Program Files\Serena\SBM\Common\jboss405\server\default\log" directory.
Using ttAuthUID and ttAuthPWD with report URL authentication fails to display report sometimes: e.g. http://rm5695:82/tmtrack/tmtrack.dll?ReportPage&Template=reports%2Flistframe&ReportId=9&ttAuthUID=bill&ttAuthPWD=
There are conditions when using SBM 2008 R2 up to R2.05 where Single Sign On will force the user to login again, even if everything is setup correctly when using IE. Problem does not occur in FireFox.
Windows 7 Client installation, when trying to work in 'online' mode from windows 7 to windows 2008R2 the following error is received. Connection attempt Failed . Failed to retrieve valid security token from
If you try to update via sbmadminservices72.UpdateUsers the login Id of a user [ ] to an existing login id held by another user , the update will fail but there will be no error message repsonse.
