IMPORTANT NOTICE: As of 21 February, anything posted in this community WILL NOT BE MIGRATED to our new community site. We have pulled all user information and data from this site and are now in an approximately week long process of importing users, roles, and data to our new site. We are leaving this site open and active so you can post and hopefully get a response until the migration is complete. Once complete, the URL that currently takes you to this site will take you to our new site so your bookmarks will work as always. Please read the information on a New Login Process
The following error message has been reported by a number of customer running SilkTest Workbench 13.5 with SQL Server 2005 Database. The error tends to occur when launching or closing the Workbench, or some individual Test Assets. It has never been possible to reproduce it by restoring an affected customer Database in-house; indicating that the cause is related to some configuration issues within SQL Server.
It has never been possible to reproduce this error outside the customer environment. Research has shown that the error can occur if a SQL Server installation was relocated to a different Server, or if the Server name has been modified after deployment. The following SQL queries can be executed to confirm if this is the root cause; the output should be identical in all cases:select @@servernameThe servername should be not NULL select * from sysserversThe “srvname” field must correspond to your server name exec sp_helpserverThe "name" field must correspond to your server name If the first test returns null or the output for all 3 tests is not identical; then the following Stored Procedures will need to be executed to resolve the problem, per the advice in the following article:https://support.actividentity.com/LiveTime/WebObjects/LiveTime.woa/wa/ArticleView?kbaId=1622exec sp_helpserver: To get the current name of the SQL Serverexec sp_dropserver '<servername>': To drop the old SQL Servernameexec sp_addserver '<servername>', local: To add the new name as the local serverexec sp_serveroption '<servername>', 'Data Access', 'True': Configures the server for Data Access* You must stop and then restart the SQL Server service for these changes to take effect. After restarting the Service; please run "select @@servername" to verify that the changes have been applied. This should return the name of your local server with a server id of 0.
Support Incident: 2610308