We just upgraded from SQL 2000 to SQL 2005. To do so we had to uninstall SQL
and install 2005 from scratch.
The problem now is we get this error:
Msg 3910, Level 16, State 2, Line 1
Transaction context in use by another session.
When trying to Exececute a SP on a remote server where that SP has code
accessing the original server. Example:
ServerA has a Stored Procedure called SP1 in which there is a select to
serverB
ServerB execute SP1 has ServerA.MyDB.Dbo.SP1.
Any help would be greatly appreciated.
ThanksHartco schrieb:
> We just upgraded from SQL 2000 to SQL 2005. To do so we had to uninstall S
QL
> and install 2005 from scratch.
> The problem now is we get this error:
> Msg 3910, Level 16, State 2, Line 1
> Transaction context in use by another session.
> When trying to Exececute a SP on a remote server where that SP has code
> accessing the original server. Example:
> ServerA has a Stored Procedure called SP1 in which there is a select to
> serverB
> ServerB execute SP1 has ServerA.MyDB.Dbo.SP1.
> Any help would be greatly appreciated.
> Thanks
>
You should debug the SP and see which exact line causes the error.
There is also an older DTS Bug in SQL Server 7/8:
http://support.microsoft.com/?scid=...id=2852&sid=150
(that does not directly apply to your problems, but maybe its usefull..)
hth
Gregor Stefka|||Thanks for your answer Gregor
This problem is Not in DTS nor SSIS.
The problem exist only since SQL 2005.
The SP is debuged. Here's more details:
On ServerA create a StoreProcedure called SP1 that Simply does Select name
From ServerB.Master.Sys.Sysdatabases
On ServerB
Forgot to mention (Sorry it's very important) To get the error you have to
do:
Create Table #MyTempTable (Name Varchar(100))
Insert into #MyTempTable
Exec ServerA.FileUploader.Dbo.GateProc
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment