What compatibility mode are you running your SQL database in? The Server could be 2008 but it is possible to run the database in a lower compatibility mode. Are you running these the AR System databases in a lower compatibility mode? If so that could be a possible reason...
Using sa or and administrator login to SQL run the query use master; select compatibility_level from sys.databases where name = ‘NameOfDB’; This will return an integer that will let you know the compatibility level of the database. The various levels are: SQL Server 6.0 ==> 60 SQL Server 6.5==> 65 SQL Server 7.0==> 70 SQL Server 2000==> 80 SQL Server 2005==> 90 SQL Server 2008==> 100 Use the stored procedure sp_dbcmptlevel to change this if required. You should find the syntax for this online on msdn or other DB forums.. HOWEVER be warned that you need to check the compatibility matrix of the AR System before making such a change to the underlying database.. Setting the database to a compatibility mode that is not supported by the AR System could result in connection issues from the ARS to the database. Joe From: LJ LongWing Sent: Friday, September 30, 2011 3:32 PM Newsgroups: public.remedy.arsystem.general To: [email protected] Subject: Re: SQL Link Server Issue ** Rafael, Are you able to do an insert directly from a db client into that table?...it may be related to the permissions between the two db’s for the user in question. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rodriguez, Rafael J x23718 Sent: Friday, September 30, 2011 12:55 PM To: [email protected] Subject: SQL Link Server Issue ** Hello list, we are facing the following issue. We have 2 databases on the same SQL server. For this example ARS1 and ARS2. We have created a linked server so we can create a view form from ARS1 to ARS2. When we try to push data from a table on ARS1 to table on ARS2 using the view form created we get the following error: Transaction context in use by another session. (SQL Server 3910) I’ve looked up this error on Microsoft siete and it states that there was a hotfix for this on SQL7/SQL2000. We are currently using SQL2008 SP2. Has anyone seen this issue and has been able to resolve? Thanks in advance. Rafael Rodriguez|Manager Remedy/Mid-Tier Enterprise|Broadridge Financial Solutions 2 Journal Square Plaza|Jersey City, NJ 07306| 201.714.3718 p This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
<<image001.gif>>
