After stopping and restarting MSSQLSERVER service, eCM cannot connect and receives error message [Microsoft][ ODBC SQL Server Driver]Communication link failure. The logical solution would be to stop and start vcs server service after MSSQLSERVER has been restarted. Unfortunately, this is not always appropriate and can be extremely bothersome if SQL is shut down on a daily basis.
After installing SBM , the following error is displayed when launching the SBM User Workspace at HTTP://servername/tmtrack/tmtrack.dll ? Calling GetProcAddress on ISAPI filter "C:\Program Files\Serena\SBM\Application Engine\bin\tmtrack.dll" failed This means that the tmtrack.dll was added to the list of ISAPI Filters, however, tmtrack.dll is not an ISAPI Filter; it is an ISAPI Extension and should appear under ISAPI and CGI Restrictions
