Having started the transition to the AJAX controls, I noticed I was, occasionally, getting the above error.
I mailed support and Maria at telerik towers pointed me to this article.
Reading it, it seemed to me that only one of the listed possible causes of the error could apply in my case; using the Server Trace.
Now, this isn't something I had knowingly enabled but I did notice that TRACE appeared as a flag on the build line for my project.
I had a look around in the VS IDE for a way to disable it. I looked in vain as it doesn't appear to be possible to alter the build command line from within VS.
A bit more investigation suggested I'd find the flags in the project file. So, how do you get at the project file?
I found this MSDN article that tells you how to gain access to the project file in the VS IDE. Of course you can just open the project file using your favourite editor, but you need to make sure that the project isn't open in VS.
To disable Server Trace you, I believe, have to remove the TRACE flag from the list of flags passed to the compiler.
You're looking for the
Note that if your solution has multiple projects, you have to do this for each project in the solution. At least, I think, for each project that accesses controls within an AjaxPanel.
As to whether or not this actually solves the problem at the start of this thread, we'll have to wait and see.
It is possible, given just how far behind the curve I usually am, that you all have all this knowledge readily to hand. But on the off-chance that someone is trying to deal with the same issue, I hope this will reduce your research time.
If, on the other hand, I've got all of this wrong, then hang around and you'll get to giggle at the fat boy getting scolded by a grown up for making up stories.
--
Stuart
I mailed support and Maria at telerik towers pointed me to this article.
Reading it, it seemed to me that only one of the listed possible causes of the error could apply in my case; using the Server Trace.
Now, this isn't something I had knowingly enabled but I did notice that TRACE appeared as a flag on the build line for my project.
I had a look around in the VS IDE for a way to disable it. I looked in vain as it doesn't appear to be possible to alter the build command line from within VS.
A bit more investigation suggested I'd find the flags in the project file. So, how do you get at the project file?
I found this MSDN article that tells you how to gain access to the project file in the VS IDE. Of course you can just open the project file using your favourite editor, but you need to make sure that the project isn't open in VS.
To disable Server Trace you, I believe, have to remove the TRACE flag from the list of flags passed to the compiler.
You're looking for the
<DefineConstants>element. There'll be one for each build configuration you have defined (2 by default; "Release" and "Debug"). Just remove the word TRACE.
Note that if your solution has multiple projects, you have to do this for each project in the solution. At least, I think, for each project that accesses controls within an AjaxPanel.
As to whether or not this actually solves the problem at the start of this thread, we'll have to wait and see.
It is possible, given just how far behind the curve I usually am, that you all have all this knowledge readily to hand. But on the off-chance that someone is trying to deal with the same issue, I hope this will reduce your research time.
If, on the other hand, I've got all of this wrong, then hang around and you'll get to giggle at the fat boy getting scolded by a grown up for making up stories.
--
Stuart
2 Answers, 1 is accepted
0
Joel Johnston
Top achievements
Rank 1
Rank 1
answered on 12 Mar 2009, 04:04 PM
Stuart,
What became of this? We are getting similar "hang" errors with AJAX - relatively new to it - did your solution work? Did you discover anything else? Thanks.
Joel
What became of this? We are getting similar "hang" errors with AJAX - relatively new to it - did your solution work? Did you discover anything else? Thanks.
Joel
0
Dan
Top achievements
Rank 1
Rank 1
answered on 12 Mar 2009, 05:17 PM
> did your solution work?
Yes and no.
I continued to get the errors during the development phase on my XPPro machine. I'm unaware of any incidents of the problem occurring once the application had been deployed on a server. Whether this is due to the changes I made or not is a matter for speculation, I'm afraid.
--
Stuart
Yes and no.
I continued to get the errors during the development phase on my XPPro machine. I'm unaware of any incidents of the problem occurring once the application had been deployed on a server. Whether this is due to the changes I made or not is a matter for speculation, I'm afraid.
--
Stuart