 | |
ASP.NET CreateUserWizard, and Transaction scope issue on remote SQLServer
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
ASP.NET CreateUserWizard, and Transaction scope issue on remote SQLServer -
12-13-2008
, 10:11 AM
#2
| |||
| |||
|
|
Hi all, I wasn't sure if this is better as a dotnet question, or a dts question.. I have a user signup page that uses the createuserwizard. I need to add some additional information after the ASP user is created, so I thought I'd use Transaction scope to encapsulate the creation process so if anything fails, it will rollback everything. I create a private transactionscope in the page code behind, and instantiate it in the CreateUserWizard1_CreatingUser event. In the CreateUserWizard1_CreatedUser event, I am inserting a record into a separate table. Then I complete the transaction, and dispose of the transactionscope. If an error happens I dispose of the transactionscope without completing . This works fine when running SQLServer 2005 on my local dev box, but when I put it on a webserver pointing at a remote DB, it just hangs until the asp.net page gets a generic timeout error. Here's what I have come up with so far in my debug efforts: 1. Looking at the transaction in the component services, I can see the transaction gets created on the dbserver 2. Looking at the sql activity monitor, I can see the the spid that is executing the create user stored proc, it shows the last command executed as: testdb.dbo.aspnet_Membership_CreateUser;1 3. There does not appear to be any blocking at all going on, and since this is test only, there is only the one transaction on the server. 4. The SQL server logs show no indication of an error. If I remove the calls to transactionscope, then it works fine (albeit without the transaction of course). I am a bit stumped as to how to debug this issue since there are really no meaningful errors. If anyone can help me out on this, I would be very grateful. |
#3
| |||
| |||
|
|
Hi all, I wasn't sure if this is better as a dotnet question, or a dts question.. I have a user signup page that uses the createuserwizard. I need to add some additional information after the ASP user is created, so I thought I'd use Transaction scope to encapsulate the creation process so if anything fails, it will rollback everything. I create a private transactionscope in the page code behind, and instantiate it in the CreateUserWizard1_CreatingUser event. In the CreateUserWizard1_CreatedUser event, I am inserting a record into a separate table. Then I complete the transaction, and dispose of the transactionscope. If an error happens I dispose of the transactionscope without completing . This works fine when running SQLServer 2005 on my local dev box, but when I put it on a webserver pointing at a remote DB, it just hangs until the asp.net page gets a generic timeout error. Here's what I have come up with so far in my debug efforts: 1. Looking at the transaction in the component services, I can see the transaction gets created on the dbserver 2. Looking at the sql activity monitor, I can see the the spid that is executing the create user stored proc, it shows the last command executed as: testdb.dbo.aspnet_Membership_CreateUser;1 3. There does not appear to be any blocking at all going on, and since this is test only, there is only the one transaction on the server. 4. The SQL server logs show no indication of an error. If I remove the calls to transactionscope, then it works fine (albeit without the transaction of course). I am a bit stumped as to how to debug this issue since there are really no meaningful errors. If anyone can help me out on this, I would be very grateful. |
#4
| |||
| |||
|
|
Hi all, I wasn't sure if this is better as a dotnet question, or a dts question.. I have a user signup page that uses the createuserwizard. I need to add some additional information after the ASP user is created, so I thought I'd use Transaction scope to encapsulate the creation process so if anything fails, it will rollback everything. I create a private transactionscope in the page code behind, and instantiate it in the CreateUserWizard1_CreatingUser event. In the CreateUserWizard1_CreatedUser event, I am inserting a record into a separate table. Then I complete the transaction, and dispose of the transactionscope. If an error happens I dispose of the transactionscope without completing . This works fine when running SQLServer 2005 on my local dev box, but when I put it on a webserver pointing at a remote DB, it just hangs until the asp.net page gets a generic timeout error. Here's what I have come up with so far in my debug efforts: 1. Looking at the transaction in the component services, I can see the transaction gets created on the dbserver 2. Looking at the sql activity monitor, I can see the the spid that is executing the create user stored proc, it shows the last command executed as: testdb.dbo.aspnet_Membership_CreateUser;1 3. There does not appear to be any blocking at all going on, and since this is test only, there is only the one transaction on the server. 4. The SQL server logs show no indication of an error. If I remove the calls to transactionscope, then it works fine (albeit without the transaction of course). I am a bit stumped as to how to debug this issue since there are really no meaningful errors. If anyone can help me out on this, I would be very grateful. |
#5
| |||
| |||
|
|
Hi all, I wasn't sure if this is better as a dotnet question, or a dts question.. I have a user signup page that uses the createuserwizard. I need to add some additional information after the ASP user is created, so I thought I'd use Transaction scope to encapsulate the creation process so if anything fails, it will rollback everything. I create a private transactionscope in the page code behind, and instantiate it in the CreateUserWizard1_CreatingUser event. In the CreateUserWizard1_CreatedUser event, I am inserting a record into a separate table. Then I complete the transaction, and dispose of the transactionscope. If an error happens I dispose of the transactionscope without completing . This works fine when running SQLServer 2005 on my local dev box, but when I put it on a webserver pointing at a remote DB, it just hangs until the asp.net page gets a generic timeout error. Here's what I have come up with so far in my debug efforts: 1. Looking at the transaction in the component services, I can see the transaction gets created on the dbserver 2. Looking at the sql activity monitor, I can see the the spid that is executing the create user stored proc, it shows the last command executed as: testdb.dbo.aspnet_Membership_CreateUser;1 3. There does not appear to be any blocking at all going on, and since this is test only, there is only the one transaction on the server. 4. The SQL server logs show no indication of an error. If I remove the calls to transactionscope, then it works fine (albeit without the transaction of course). I am a bit stumped as to how to debug this issue since there are really no meaningful errors. If anyone can help me out on this, I would be very grateful. |
#6
| |||
| |||
|
|
Hi all, I wasn't sure if this is better as a dotnet question, or a dts question.. I have a user signup page that uses the createuserwizard. I need to add some additional information after the ASP user is created, so I thought I'd use Transaction scope to encapsulate the creation process so if anything fails, it will rollback everything. I create a private transactionscope in the page code behind, and instantiate it in the CreateUserWizard1_CreatingUser event. In the CreateUserWizard1_CreatedUser event, I am inserting a record into a separate table. Then I complete the transaction, and dispose of the transactionscope. If an error happens I dispose of the transactionscope without completing . This works fine when running SQLServer 2005 on my local dev box, but when I put it on a webserver pointing at a remote DB, it just hangs until the asp.net page gets a generic timeout error. Here's what I have come up with so far in my debug efforts: 1. Looking at the transaction in the component services, I can see the transaction gets created on the dbserver 2. Looking at the sql activity monitor, I can see the the spid that is executing the create user stored proc, it shows the last command executed as: testdb.dbo.aspnet_Membership_CreateUser;1 3. There does not appear to be any blocking at all going on, and since this is test only, there is only the one transaction on the server. 4. The SQL server logs show no indication of an error. If I remove the calls to transactionscope, then it works fine (albeit without the transaction of course). I am a bit stumped as to how to debug this issue since there are really no meaningful errors. If anyone can help me out on this, I would be very grateful. |
#7
| |||
| |||
|
|
Hi all, I wasn't sure if this is better as a dotnet question, or a dts question.. I have a user signup page that uses the createuserwizard. I need to add some additional information after the ASP user is created, so I thought I'd use Transaction scope to encapsulate the creation process so if anything fails, it will rollback everything. I create a private transactionscope in the page code behind, and instantiate it in the CreateUserWizard1_CreatingUser event. In the CreateUserWizard1_CreatedUser event, I am inserting a record into a separate table. Then I complete the transaction, and dispose of the transactionscope. If an error happens I dispose of the transactionscope without completing . This works fine when running SQLServer 2005 on my local dev box, but when I put it on a webserver pointing at a remote DB, it just hangs until the asp.net page gets a generic timeout error. Here's what I have come up with so far in my debug efforts: 1. Looking at the transaction in the component services, I can see the transaction gets created on the dbserver 2. Looking at the sql activity monitor, I can see the the spid that is executing the create user stored proc, it shows the last command executed as: testdb.dbo.aspnet_Membership_CreateUser;1 3. There does not appear to be any blocking at all going on, and since this is test only, there is only the one transaction on the server. 4. The SQL server logs show no indication of an error. If I remove the calls to transactionscope, then it works fine (albeit without the transaction of course). I am a bit stumped as to how to debug this issue since there are really no meaningful errors. If anyone can help me out on this, I would be very grateful. |
#8
| |||
| |||
|
|
Hi all, I wasn't sure if this is better as a dotnet question, or a dts question.. I have a user signup page that uses the createuserwizard. I need to add some additional information after the ASP user is created, so I thought I'd use Transaction scope to encapsulate the creation process so if anything fails, it will rollback everything. I create a private transactionscope in the page code behind, and instantiate it in the CreateUserWizard1_CreatingUser event. In the CreateUserWizard1_CreatedUser event, I am inserting a record into a separate table. Then I complete the transaction, and dispose of the transactionscope. If an error happens I dispose of the transactionscope without completing . This works fine when running SQLServer 2005 on my local dev box, but when I put it on a webserver pointing at a remote DB, it just hangs until the asp.net page gets a generic timeout error. Here's what I have come up with so far in my debug efforts: 1. Looking at the transaction in the component services, I can see the transaction gets created on the dbserver 2. Looking at the sql activity monitor, I can see the the spid that is executing the create user stored proc, it shows the last command executed as: testdb.dbo.aspnet_Membership_CreateUser;1 3. There does not appear to be any blocking at all going on, and since this is test only, there is only the one transaction on the server. 4. The SQL server logs show no indication of an error. If I remove the calls to transactionscope, then it works fine (albeit without the transaction of course). I am a bit stumped as to how to debug this issue since there are really no meaningful errors. If anyone can help me out on this, I would be very grateful. |
#9
| |||
| |||
|
|
Hi all, I wasn't sure if this is better as a dotnet question, or a dts question.. I have a user signup page that uses the createuserwizard. I need to add some additional information after the ASP user is created, so I thought I'd use Transaction scope to encapsulate the creation process so if anything fails, it will rollback everything. I create a private transactionscope in the page code behind, and instantiate it in the CreateUserWizard1_CreatingUser event. In the CreateUserWizard1_CreatedUser event, I am inserting a record into a separate table. Then I complete the transaction, and dispose of the transactionscope. If an error happens I dispose of the transactionscope without completing . This works fine when running SQLServer 2005 on my local dev box, but when I put it on a webserver pointing at a remote DB, it just hangs until the asp.net page gets a generic timeout error. Here's what I have come up with so far in my debug efforts: 1. Looking at the transaction in the component services, I can see the transaction gets created on the dbserver 2. Looking at the sql activity monitor, I can see the the spid that is executing the create user stored proc, it shows the last command executed as: testdb.dbo.aspnet_Membership_CreateUser;1 3. There does not appear to be any blocking at all going on, and since this is test only, there is only the one transaction on the server. 4. The SQL server logs show no indication of an error. If I remove the calls to transactionscope, then it works fine (albeit without the transaction of course). I am a bit stumped as to how to debug this issue since there are really no meaningful errors. If anyone can help me out on this, I would be very grateful. |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.