RE: HELP on New request is not allowed to start because [1264822]
- From: Geraldo Thomaz Jr. <GeraldoThomazJr@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 16 Feb 2006 07:14:31 -0800
I hear them back, but they didn't find a solution or a workarround until that
moment. I am interacting with Microsoft via a support case, on the support
site.
I will copy your message to them.
"Jeff Glenn" wrote:
Did you ever hear back from MS?.
Do you have a link to the bug? Is it on labs.* or somewhere where I can
follow its progress?
This is making me and MS look very bad with the client since this problem
existed in a CTP (every request) then went away in the Sept bits and then
came back (ocassionally-even worse) for RTM. In our case, we annecdotally
believe that network issues (address conflict, connection lost, timeout?,
etc.) lead to the problem.
Jeff Glenn
MS Partner [1264822]
"Geraldo Thomaz Jr." wrote:
Hi Jeff,
We have posted a simple code reproducing the behavior to Microsoft. They
confirmed to be a issue in ASP.NET 2.0 and asked to wait for a couple of
weeks until they find a way to fix it.
Meanwhile, you can try to avoid this exception by garanteeing that your
application doen't raise any exception during a distributed transaction. Once
this happens, the "New request" exceptions pops up through all your
application until you restart the IIS.
Regards,
"Jeff Glenn" wrote:
We haven't seen this since an IP address conflict was found on the network
so that may be the problem. I'll repost if it shows itself again. If this
is caused by an IP address conflict it is still a MS bug that the transaction
or connection was left in this state requiring an IIS restart to fix the
problem.
Jeff
"Jeff Glenn" wrote:
Did you ever figure this out?
I just finished our migration from
Visual Studio Beta 2 and SQL Server Beta 2 to RTM
These have started poping up in our application as well. I haven't been
able to determine if there is a cause in our application since I don't see
any exceptions that preceed this error. However, once we start to get this
error it randomly continues until we restart the web service.
Our application uses
-web services and
-ServiceDomain.Enter/Leave logic
This error always occurs when we issue the command to SQL Server.
We have had issues with interim builds and transactions so this certainly
seems like it could be related.
Any help would be appreciated,
Jeff
"Geraldo Thomaz Jr." wrote:
I am getting the following error in my application:
New request is not allowed to start because it should come with valid
transaction descriptor.
This is happening under a very singular circustance:
I have just migrated to SQL server 2005 and ASP.NET 2.0.
It is not happening all the time. It happens occasionally in all my pages
that are working correctly, and once in a while, throw this kind of exception.
When it happens, it happens on the first Connection.Open of the page.
I am using Windows 2003 Enterprise.
Please, somebody help me. I trusted Microsoft, migrated all my systems and
now these errors are killing my application.
And the message is a kind of message that doesn`t give me any clue of what
is wrong.
Thanks a lot.
- Follow-Ups:
- References:
- RE: HELP on New request is not allowed to start because [1264822]
- From: Jeff Glenn
- RE: HELP on New request is not allowed to start because [1264822]
- Prev by Date: Re: Advatages of Stored Procedures?
- Next by Date: Re: Advatages of Stored Procedures?
- Previous by thread: RE: HELP on New request is not allowed to start because [1264822]
- Next by thread: RE: HELP on New request is not allowed to start because [1264822]
- Index(es):
Relevant Pages
|
