July 7, 2016 at 8:16 am
Hi ,
I have .net c# 2.0 applications running fine on SQL 2005.
When I migrate to SQL 2008 r2 , I am getting below MSDTC issues. I tried DTC Ping which works fine between our app and sql servers. Also all the msdtc settings are matching with my old Sql server 2005 machines.
System.Web.Services.Protocols.SoapException System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Transactions.TransactionAbortedException: The transaction has aborted. ---> System.Data.SqlClient.SqlException: The transaction operation cannot be performed because there are pending requests working on this transaction.
Are there any known MSDTC issues on SQL Server 2008 r2 , any extra settings changes needed in SQL Server 2008 r2.?
Any views on this will be really helpful.
July 7, 2016 at 8:22 am
When you say "migrate", do you mean an in-place upgrade, a copy of a database to a new server, or something else?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
July 7, 2016 at 8:23 am
Is the .NET 3.5 Framework role installed on the Server?
If not, install it and retry.
July 7, 2016 at 9:04 am
No , moving it to new physical server where SQL Server 2008 r2 is installed ,its an clustered environment.
July 7, 2016 at 9:05 am
You mean just change the IIS .net framework to 3.5 and try? , we have not done this as all our .net dll's are built in .net 2.0 framework...
So we are not migrating to .net 3.5
July 7, 2016 at 9:18 am
GonnaCatchIT (7/7/2016)
You mean just change the IIS .net framework to 3.5 and try? , we have not done this as all our .net dll's are built in .net 2.0 framework...So we are not migrating to .net 3.5
Here is a link to the recommended settings for MSDTC.
as far as the .NET 3.5 issue. No don't change anything in IIS just add the role to the server. Of course I would not do this on a production server, do this in a test environment if possible. If not, it should not hurt anything to just turn a role on for Windows Server.
July 8, 2016 at 6:06 am
Yes, I will do it on test environment, I think the roles are already added , but let me cross check once.
July 8, 2016 at 6:21 am
The .net 3.5.1 role is already enabled on our App server.
July 8, 2016 at 9:54 am
GonnaCatchIT (7/8/2016)
The .net 3.5.1 role is already enabled on our App server.
Meant that for the SQL Server sorry for not specifying.
Have you run the BPA on your SQL Server?
July 8, 2016 at 2:33 pm
We have SQL Server hosted on different physical server managed entirely by different vendors.
You mean .net 3.5.1 is required on sql server box as well ?...
I have tried DTCPing between my app server and sql, which looks OK...
July 9, 2016 at 6:47 am
GonnaCatchIT (7/8/2016)
We have SQL Server hosted on different physical server managed entirely by different vendors.You mean .net 3.5.1 is required on sql server box as well ?...
I have tried DTCPing between my app server and sql, which looks OK...
Ok let me take a step back here for a moment...
#1. I did not see your reply about the 'migrated' server that GSquared asked you about earlier, until now.
#2. I gave you a quick check on the .NET 3.5.1 installed role on the SQL SERVER because I was thinking most likely your setup was a side by side installation. I have seen this error occur on those kinds of SQL Server installations.
#3. You stated that your SQL Server is in a clustered environment. MSDTC is most definitely a clustered resource and is about as rock solid a service as there is, with that said it is important to know the configuration of MSDTC on your SQL Server.
Now here is where I take the step back...
1. Find out from your vendor if your 2008 r2 SQL Server is indeed separate from your 2005 server. Get the hardware specs for your new server.
2. This is most likely a program code issue. Insure that your code is opening a connection, beginning a transaction, performing its work, and commit or rollback the transaction as soon as possible.
3. Have you tested this on a different 2008 r2 server?
4. Since you said your SQL Server is vendor controlled hopefully you have a service contract with them. I would engage their pros as that would lend to a quicker resolution than asking a forum person and waiting till I or they have free time to look here and try to provide meaningful feedback for your issue.
July 10, 2016 at 10:29 am
Many Thanks for your quick replies on my thread, below are inline comments...
1. Find out from your vendor if your 2008 r2 SQL Server is indeed separate from your 2005 server. Get the hardware specs for your new server.
-- Yes, the hardware specs are matching or are higher versions of our SQL 2005 box.
2. This is most likely a program code issue. Insure that your code is opening a connection, beginning a transaction, performing its work, and commit or rollback the transaction as soon as possible.
-- It works OK on our Dev environment where we have SQL 2008 r2.
However I must mention when we change the code to close the datareader , this error vanishes. But my concern is this happens only on SQL 2008 r2 ....
3. Have you tested this on a different 2008 r2 server?
-- Works fine on our Dev environment
4. Since you said your SQL Server is vendor controlled hopefully you have a service contract with them. I would engage their pros as that would lend to a quicker resolution than asking a forum person and waiting till I or they have free time to look here and try to provide meaningful feedback for your issue.
--Ofcourse, this is already highlighted and being looked into , I needed some inputs on what particular settings of clustered SQL environment needs to be looked for MSDTC.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply