Thursday, March 17, 2005

602.aspx

Fixing ASP.NET debug error 0x8013134b

I got the following error debugging an ASP.NET project earlier today:



Auto-attach to process '[2440] w3wp.exe' on machine '...' failed. Error code 0x8013134b.


The problem was that I had installed .NET 2.0 which had registered ASP.NET 2.0 on the Web Site I was trying to debug.


Fixing it is simple:



  • Run the IIS Manager

  • Right click on the web site with the problem

  • Click the ASP.NET tab

  • Change the ASP.NET version from 2.something to 1.something in the combo and debugging works again
Posted by at

127 comments:

  1. rajivpopatApril 19, 2005 at 4:52 AM

    Strangely enough, when i do this my VS 2003 is no longer able to create web projects! Any ideas?

    ReplyDelete
  2. rajivpopatApril 19, 2005 at 5:30 AM

    Turns out, i had to run aspnet_regiis -i again from my VS 2003 Command prompt and then do what you told. That did the trick! Thanks!

    ReplyDelete
  3. bwoodruffJune 9, 2005 at 5:20 PM

    Awesome...I went through many sites before finding yours with the right fix. Thanks!

    ReplyDelete
  4. kumaresanJune 21, 2005 at 2:55 PM

    Great For me it worked after doing the Following.



    I went to microsft.net\famework\v2.0.*\ in .net Command prompt

    and I uninstalled aspnet using aspnet_regiis -u adn I came to the Version ..\v1.1.4 * that I have to use and there I reinstalled it using aspnet_regiis -i

    After this I followed what u have said...



    Its really a nice tip.



    ReplyDelete
  5. MalikJuly 14, 2005 at 7:15 AM

    none of the above worked for me. using VS2003 and asp.net ver 1.1 and 2.0 any idea in the meanwhile i ll try to fix it.

    ReplyDelete
  6. maxsoftJuly 20, 2005 at 10:47 AM

    thank you very much.

    NOW WORK WELL PERFECT...

    MICROSOFT BASTARD!

    ReplyDelete
  7. MoshecJuly 25, 2005 at 4:29 PM

    thank you very much.



    I spent to hours to find out what the problem is and I fix it 2 seconds after I saw your message.



    MosheC

    ReplyDelete
  8. sriAugust 16, 2005 at 12:30 AM

    hey guys,



    i got the same error message but i am unable to find asp.net tad on iis manager. i am running both iis 1.1 and 2.0. i would like to switch to 1.1 now but on iis admin after right clicking the web site there is no asp.net tab on properties. could any body help me.

    ReplyDelete
  9. Egil HogholtAugust 17, 2005 at 3:04 PM

    You can switch ASP.NET version from the command line.



    To switch to ASP.NET version 1.1:

    - Go to the directory: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322

    - Run "aspnet_regiis.exe -i" to install ASP.NET version 1.1 for all sites



    You can apply it to specific web sites by running "aspnet_regiis.exe -s siteid". You get more help on the syntax by running "aspnet_regiis.exe" without any arguments.



    To be 110% safe, you can follow the tip by kumaresan and uninstall ASP.NET v2 first:

    - Go to the directory: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215

    - Run "aspnet_regiis.exe -u" to uninstall ASP.NET version 2.something from all sites

    ReplyDelete
  10. John MXAugust 28, 2005 at 2:37 AM

    Thank you, this was on great help, although it didn't worked for me, I guess it was because I selected 1.1.4322.OtherNumber instead of 1.1.4322.0.



    Anyway I decided to uninstall asp.net 2.0 and re-install ASP.NET 1.1 as mentioned in previous message and it worked fine.



    Thank you all

    ReplyDelete
  11. puspendraSeptember 22, 2005 at 11:40 AM

    when i m running asp.net page the error should come like, enable to find the path and local host could any one help me.



    Thanks & Regards.



    Puspendra

    ReplyDelete
  12. teSeptember 26, 2005 at 2:43 PM

    Thanks for the great help.



    I can now debug after running the following:

    C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322>aspnet_regiis -i



    Although now I have problems connecting to my SQL database that normally works fine under ASP.net v2... Any ideas?



    Thanks heaps

    ReplyDelete
  13. Egil HogholtSeptember 26, 2005 at 10:23 PM

    Can you post the error message(s) you are getting?



    Did you recompile the application after rolling back to .NET 1.1?

    ReplyDelete
  14. domNovember 3, 2005 at 4:44 PM

    Hey thanks for the help, i have this problem i never noticed that the programmer working on morning shift installed framework 2. shit thats why I recieved some hell 0x8013134b message..



    Dom

    ReplyDelete
  15. OferNovember 10, 2005 at 3:33 PM

    try and see if you have 2 Framework clr installed (ver 2, and ver 1.x), if so the iis is using the ver 2 and the visual.net is using ver 1.x (check inside visual studio at help->about to see whice ver of framework is in use), after i removed the ver 2 it worked just fine.

    ReplyDelete
  16. GarrettDecember 2, 2005 at 7:37 PM

    My VS.net help->about screen says it's still using ver 1.1. I have 2.0 installed on IIS and this is what I want to use. How do I get VS to use 2.0? It's really hard to debug without a debugger.

    ReplyDelete
  17. Egil HogholtDecember 3, 2005 at 11:43 PM

    You have to upgrade to Visual Studio 2005 in order to develop and debug .NET 2.0 applications with VS.NET.



    You can use the -free- .NET 2.0 SDK to compile your application but you cannot debug it with VS.NET 2003

    ReplyDelete
  18. GarrettDecember 5, 2005 at 5:49 PM

    that's pretty gay. thanks man.

    ReplyDelete
  19. AlvaroDecember 15, 2005 at 3:52 PM

    Thanks a bunch! I would have never figured it out myself.

    ReplyDelete
  20. nabrahamsonDecember 15, 2005 at 9:56 PM

    The command line tool is great, but does anyone know how to get the ASP.NET tab to show up in IIS?

    ReplyDelete
  21. ThierryDecember 21, 2005 at 1:10 PM

    Hi great blogg to help out.



    Had a lot of problems with it. The only way I was able to fix this was to unregister clr2 and register clr 1. Bit of a pain considering the amount of time wasted trying to figure this out.



    The only question remaining is how do you use the two without having to constantly unregister one and register the other.



    After unregistering 2 and registering 1, I also did an iisreset as listed above and I seem to be back in action.



    Thanks again.



    Thierry

    ReplyDelete
  22. Anurag SharmaDecember 28, 2005 at 9:15 AM

    Cool man, its working.

    ReplyDelete
  23. GuangweiDecember 29, 2005 at 1:59 PM

    Cheers, it works

    ReplyDelete
  24. kirienJanuary 13, 2006 at 4:25 AM

    Wow! cool , the solution is wonder, haha, thanks!

    ReplyDelete
  25. kirineJanuary 13, 2006 at 4:26 AM

    Wow! cool , the solution is wonder, haha, thanks!

    ReplyDelete
  26. DrCJanuary 14, 2006 at 6:42 PM

    Thanks for posting this tip - I was beginning to pull my hair out!

    ReplyDelete
  27. ShivJanuary 19, 2006 at 8:23 AM

    Thanks my Dear.... now working fine.

    ReplyDelete
  28. kynnJanuary 20, 2006 at 5:06 AM

    this solution is great. thankssssssssssssss`

    ReplyDelete
  29. Thomas JohnsonFebruary 1, 2006 at 8:49 PM

    Thanks for this tip. I too had spent a day and a half reading thru different NewsGroups. What got me into trouble was my anxious attemp to try and convert a VS2003 .Net appl to a VS2005 appl. The conversion went fine. Little did I know what was actually happening in the background. When I tried to return toi the VS2003 appl, I started to receive this 'Auto attach to process . . .' error message. I did some snoopying and decided that the folder in the c:\inet\wwwrot\ folder might have been causing my problem, so I saved this appl folder for the VS2005 appl in another location and rebuilt the VS2003 small application. NO LUCK, I got the same error message. I was bound and determined to not let this get me down. A stroke of luck thru Google led me to your solution. Thanks for this solution. . . .Tom J.

    ReplyDelete
  30. Tom McHughFebruary 8, 2006 at 2:45 PM

    same here thank you very much, you saved me hours if not days

    ReplyDelete
  31. Filo InformaticaFebruary 20, 2006 at 11:53 AM

    Grazie 1000

    Thank you, very much

    ReplyDelete
  32. guruFebruary 22, 2006 at 7:33 AM

    Thanks for your kindly information, this useful for me.



    Thanks and regards

    guru

    ReplyDelete
  33. sohanFebruary 22, 2006 at 9:28 AM

    thanks a lot for this tip

    ReplyDelete
  34. OdhranFebruary 27, 2006 at 2:14 PM

    thanks for the fix. saved me a lot of time.

    ReplyDelete
  35. NightmareedFebruary 28, 2006 at 8:46 PM

    Thnx i've never find an answer so quickly

    ReplyDelete
  36. COBMarch 1, 2006 at 6:48 AM

    This tip is simple but makes lots of "Gentleman" have headaches .... haha ....



    Thanks a lot,

    COB



    ReplyDelete
  37. Shadow WizardMarch 16, 2006 at 8:49 AM

    thanks, didn't figure it can be that simple. :D

    ReplyDelete
  38. GualbertoMarch 23, 2006 at 10:37 PM

    Thanks, really in 2 seconds...

    ReplyDelete
  39. KENMarch 30, 2006 at 5:59 PM

    I love you man.

    ReplyDelete
  40. 2ndChanceApril 13, 2006 at 3:45 PM

    It works. You're the best. Thanks man.

    ReplyDelete
  41. lolApril 18, 2006 at 6:03 AM

    thx

    ReplyDelete
  42. SteveApril 25, 2006 at 5:28 PM

    yet another thank you... wish I found this one earlier because I have keyboard keys imbedded in my head now.

    ReplyDelete
  43. RaviApril 27, 2006 at 7:37 PM

    Thanks a lot and its a good info which put me through my work today, else I would have been blocked at the beginning itself. Thanks a ton !! :-)

    ReplyDelete
  44. BrianMay 3, 2006 at 12:23 PM

    Thanks this saved me some fustration at 5:30 in the morning.

    ReplyDelete
  45. Pramod KaranjkarMay 8, 2006 at 10:48 AM

    Hi Friend,



    I was facing the same problem. I had search for the solution but finally got solution from your post.



    Thanks



    Pramod Karanjkar

    ReplyDelete
  46. Sameer SavantMay 28, 2006 at 10:34 PM

    Worked for over 2 hours to fix this issue...freakin Microsoft!!! Thanks for the tip. Saved my sanity.



    Sameer

    ReplyDelete
  47. David SchmidtMay 30, 2006 at 1:12 AM

    Love your work!

    ReplyDelete
  48. AndreasJune 5, 2006 at 10:46 PM

    Thank you very much for this great fix!!!!!



    This worked really well!!



    ReplyDelete
  49. jaysonJune 7, 2006 at 5:21 PM

    WAOHOOOOOOO!!

    ... me too...I went through many sites before finding yours with the right fix. Thanks!

    Are you accepting cheques ? have you got a paypal account ?

    ReplyDelete
  50. Egil HogholtJune 7, 2006 at 9:53 PM

    Glad to hear that it worked for you as well!



    At the end of each post there is a link to my "tip jar" (PayPal) where you can leave a few cents if you feel like it.



    Cheers,

    Egil

    ReplyDelete
  51. PritamJune 8, 2006 at 10:40 AM

    This worked. A quick fix... but tricky. Thanks!!

    ReplyDelete
  52. Hsin-wei HuangJune 10, 2006 at 6:52 AM

    Thank you very much.

    Though the document said a lot about this problem, I still could not fix the problem.

    No I solve it because of your simple guideline.

    Thank you and Google, the appreciation from Taiwan.

    ReplyDelete
  53. kristofJune 16, 2006 at 9:17 AM

    thanks man!!

    ReplyDelete
  54. RajJune 21, 2006 at 11:03 AM


    anyone please help



    I uninstalled v2.0 and v1.0 and then installed v1.0 and then reset iis. but no success for me.



    Am I doing anything wrong??



    I can see the four versions:

    v1.0.3705

    v1.1.4322

    v2.0.40607

    v2.0.50727



    aspnet_regiis -u in all 4 and then used

    aspnet_regiis -i in v1.1.4322 directory and no success at all.



    Plz help?

    ReplyDelete
  55. LA_osJune 22, 2006 at 6:56 AM

    Thank you so much



    I have tried every way but this very simple



    Thank you "" (^_^)

    ReplyDelete
  56. Ankur JindalJune 23, 2006 at 1:19 PM

    Thanks a lot



    I simply uninstalled v2.0.50727 and then intsalled v1.1.4322

    Although the ASP.NET tab disappeared from the Properties of Default Web Site in IIS but debugging is working fine.



    Thanks

    ReplyDelete
  57. Ankur JindalJune 23, 2006 at 1:22 PM

    VS2003 does not support debugging for ASP.NET version v2.0.50727

    So you have to uninstall this and install some other version lower than this.



    Also under ASP.NET tab in properties of the Default Web Site you have to select the proper version.

    It will surely work.



    Thanks

    ReplyDelete
  58. cjfJuly 11, 2006 at 11:39 PM

    thank you very much!

    ReplyDelete
  59. Hong SonJuly 12, 2006 at 11:23 AM

    Yeah. I have the same problem. Thanks very much!

    ReplyDelete
  60. ETJuly 23, 2006 at 12:25 AM

    I did exactly what you said and it worked. Thanks!

    ReplyDelete
  61. Donald KlopperJuly 28, 2006 at 3:37 PM

    Thank you - this post saved me time (I need to get a PayPal account!). I installed VS Express 2005, then VS 2005 (trial), then removed everything and installed VS 2003 (which we actually have the license for). IIS was still pointing to .Net 2.0 paths, and the suggestion did the trick. Breakpoints are now active.

    ReplyDelete
  62. ArunAugust 3, 2006 at 4:35 PM

    Wow, thanks a lot. I was trying a lot until I found this tip. Thanks again.

    ReplyDelete
  63. TonyAugust 16, 2006 at 5:12 AM

    Love you!

    ReplyDelete
  64. DSD-SICOAugust 18, 2006 at 1:43 PM

    Whew, good thing I found your post dude!

    It works! ^_^



    Thank You Very Much

    ReplyDelete
  65. siavashSeptember 5, 2006 at 5:26 PM

    great it works after changing Asp.Net Version.

    Thanks alot :).

    ReplyDelete
  66. killSeptember 7, 2006 at 5:00 AM

    You saved my day!!!

    Thank you for such a wonderful advice.

    ReplyDelete
  67. HowardSeptember 12, 2006 at 10:25 AM

    a 2 second fix to a 2 hour problem - thanks

    ReplyDelete
  68. Egil HogholtSeptember 14, 2006 at 2:52 PM

    A few questions to help you figure out what the problem is:

    * Do you get "file not found" errors for all files or only aspx files?

    * Do you have more than one web site configured?

    ReplyDelete
  69. A CSeptember 20, 2006 at 8:56 AM

    OMG it works!

    I didn't uninstall .NET 2.0. Just pick ASP.NET 1.1 for my application in IIS properties.

    I think VS 2003 not going to support .NET 2.0?

    ReplyDelete
  70. Egil HogholtSeptember 20, 2006 at 9:03 AM

    Correct; Visual Studio 2003 does not support .NET 2.0

    ReplyDelete
  71. Alvaro GuerreroSeptember 21, 2006 at 6:00 PM

    the framework 2.0 could be the reason???

    my app is dev in vs2003 with crystal reports for vs203 but in the server production (win2003s w framework 2.0) the reports don't display the data...really don't display anything...



    thanks 4 your help again!

    ReplyDelete
  72. IvanSeptember 27, 2006 at 9:31 PM

    Hi,



    I tried th following issues



    - aspnet_regiis.exe -u

    - aspnet_regiis.exe -i



    but unfortunately without sucscess



    the code of error that throw me is 0x8013134b



    can anybody help me?????



    Thanks in advance







    ReplyDelete
  73. Ramesh PandiSeptember 28, 2006 at 6:14 PM


    Awesome !! works great !!

    ReplyDelete
  74. Egil HogholtSeptember 28, 2006 at 10:48 PM

    Another comment to "A" (9/13/2006 3:54 AM)



    You will get "File not found" errors if the web site is configured to use ASP.NET version * on a site but you have not enabled ASP.NET version * in the IIS Manager as a "Web Service Extension"

    ReplyDelete
  75. Egil HogholtSeptember 28, 2006 at 10:51 PM

    Ivan; a few questions to identify your problem:

    - which version of ASP.NET did you unregister

    - which version of ASP.NET dir you register

    - which version of Visual Studio are you using?

    - which version of ASP.NET is configured in the "ASP.NET" tab in the IIS Manager for the web site?

    ReplyDelete
  76. Jorge FigueroaOctober 12, 2006 at 2:23 AM

    Thanks Egil, this solves my problem

    ReplyDelete
  77. Sander PoolOctober 12, 2006 at 4:36 PM

    Thanks for this. I had done the same thing a few days ago during my own tinkering and it didn't help a thing. I read your blog and figured, what the heck, let's try it again. Now it worked :) Awesome.

    ReplyDelete
  78. Steve MeerdterOctober 19, 2006 at 9:40 PM

    1 hour of troubleshooting, and frustration... I find your post, and it's fixed in 15 seconds. Thank you!

    ReplyDelete
  79. greenteaOctober 24, 2006 at 12:19 AM

    Yes, after installing Asp .Net 2.0, I got this error.

    After changing it back to 1.0, it works again!

    ReplyDelete
  80. Fabio BrandespimNovember 9, 2006 at 9:17 PM

    Thanks for the great help.

    Hist post help me a lot.

    ReplyDelete
  81. vasyaNovember 10, 2006 at 11:30 PM

    Add to my best sites! Really nice!

    ReplyDelete
  82. HarisNovember 14, 2006 at 9:35 AM

    U ROCK...

    ReplyDelete
  83. Joao nevesNovember 25, 2006 at 1:13 AM

    Thx Man... Was getting crazy with this.. U are the man

    ReplyDelete
  84. jamesDecember 10, 2006 at 8:44 AM

    bless u ...

    ReplyDelete
  85. gauravDecember 21, 2006 at 5:39 AM

    i hav seen lot of help but all in vain.thanks ,it has solved my problem

    ReplyDelete
  86. padmavathi.aJanuary 3, 2007 at 4:21 AM

    Hi,



    U R solution is very nice and easy to understand..I cleared my error..



    Thanks,

    padma

    ReplyDelete
  87. SatsumaJanuary 4, 2007 at 11:49 AM

    I love you!



    I was close to pulling my hair out but you have saved me from baldness!

    ReplyDelete
  88. timmyJanuary 16, 2007 at 12:52 AM

    i got this error.

    "you do not have permission to debug on this server. Verify that you are a member of the Debugger Users group on ther server."



    I got crazy with this error. I have tried all kinds of things. None works for me.



    ReplyDelete
  89. Egil HogholtJanuary 16, 2007 at 7:58 AM

    Hi timmy.

    Are you member of the "Debugger Users" group on the server? You can verify by running "Computer Management" and going to:

    - System Tools

    - Local Users And Groups

    - Groups



    Check if you are member of the group "Debugger Users"

    ReplyDelete
  90. NiallJanuary 18, 2007 at 10:58 AM

    thank you thank you thank you!

    ReplyDelete
  91. TR SimmsJanuary 25, 2007 at 6:34 PM

    Thank you.

    ReplyDelete
  92. maddyJanuary 29, 2007 at 6:26 AM

    thank you

    ReplyDelete
  93. EsamFebruary 3, 2007 at 8:51 AM

    The problem is Solved





    Thank you all

    ReplyDelete
  94. SVFebruary 4, 2007 at 1:24 PM

    I have same identical problem as described. When i press F5 in VS.NET 2003 web application, i get : "Error while trying to run project: Unable to start server. There is no managed code running in the process. In order to attach to a process with the .NET debugger, managed code must be running in the process before attaching", and in the Output window I get "Auto-attach to process '[1520] aspnet_wp.exe' on machine 'SV' failed. Error code 0x8004000e.



    I followed the exact steps with aspnet_regiis -u and -i and still get the same problem. Now even got so far as uninstalling .NET framework 2 completely. Still get same error.



    Another strange thing is that when i try to browse the site from IIS (right-click on website and Browse), I get error HTTP 403: "This error (HTTP 403 Forbidden) means that this program was able to connect to the website, but it does not have permission to view the webpage."



    This doesn't happen to all sites, but it happens to any NEW ASP.NET project that I create from VS.NET 2003.



    Wasted a whole day already on this! What could be the problem!

    ReplyDelete
  95. Egil HogholtFebruary 6, 2007 at 10:10 AM

    The problem is the "HTTP 403 Forbidden" error. The ASP.NET application is not able to run so Visual Studio is not able to attach to the process.



    Have you verified the security on the directory where your site is created? The account used by ASP.NET to run the site must have read access to the directory.

    Are you able to browse static contents on the site (html, gif, etc)?

    ReplyDelete
  96. SVFebruary 6, 2007 at 11:02 PM

    Apparently the HTTP 403 error when trying to browse the site from IIS was due to not having specified a default.aspx page, because once i did that it was ok.



    However I still can't debug because of the same error: "Error while trying to run project: Unable to start server. There is no managed code running in the process. In order to attach to a process with the .NET debugger, managed code must be running in the process before attaching"



    Same kind of error pops up when try to manually attach to aspnet_wp process.

    I've put all users (my user name, ASPNET which runs the aspnet_wp process, and the rest of the users created by ASP.nET) into the Administrators and the Debuggers groups to make sure it's not a problem of security.



    Thanks

    ReplyDelete
  97. AwaneeshFebruary 8, 2007 at 5:00 AM

    first thing ur error is different from the original post. so trying same solution is not the exact way. second, do u change ur IP, if so thats a big headache.

    thirdly try running services from Administrative Tools->Services and restart application.

    But first of all check for the correct solution, by googling, (as u'll get a variety of solutions), posting exactly ur Error Code, not similar message or similar error code.



    regards

    awansh

    ReplyDelete
  98. Manish JadhavFebruary 21, 2007 at 7:46 PM

    That worked like a charm. Thanks!!

    ReplyDelete
  99. BIMAL SHAHFebruary 28, 2007 at 12:57 PM

    Thanks for save us time and good solution but i want solution on framework2.0

    ReplyDelete
  100. Egil HogholtFebruary 28, 2007 at 9:11 PM

    Have you tried unregistering and registering ASP.NET 2.0 for the web site you have problems with?



    If it doesn't work; which version of Visual Studio are you using and which error message do you get?

    ReplyDelete
  101. shashwatMarch 12, 2007 at 8:37 AM

    really awsum.................................. it works thanks

    ReplyDelete
  102. LOUISMarch 13, 2007 at 4:16 PM

    VERY GOOD FOR ME. EVERYTHING WORKS FINE NOW

    ReplyDelete
  103. AmanMarch 19, 2007 at 1:16 AM

    Hi thanks for this great tip. I was also working on this error for the past day or two and your tip solved it in seconds.



    Thanks a lot

    ReplyDelete
  104. SSenthilMarch 22, 2007 at 7:24 PM

    Here is simple solution:

    For those who has VS 2003 and VS 2005 on XP.



    Goto - Control Panel- Administrative Tools - Internet Information Service.



    Then click on Local computer name - Web site - Default Web site



    Right click on Default Web site and select Properties



    Then go to ASP.net folder - AND CHANGE the version to 1.1.4322 say ok and try.



    Thanks.

    ReplyDelete
  105. VJMarch 25, 2007 at 11:19 PM

    Thanks Man, Thanks.

    ReplyDelete
  106. shailendraMarch 26, 2007 at 7:48 AM

    please explain me how i can run aspx program in my machine, whan i got the error---debug error 0x8013134b

    ReplyDelete
  107. Randel StewartMarch 27, 2007 at 10:37 PM

    Thank you for this tip... It worked like a champ!

    ReplyDelete
  108. Prasant Kumar RoutMarch 29, 2007 at 12:35 AM

    WOW..



    Thank you very much for this tip..



    Prasant

    ReplyDelete
  109. Alex SmotritskyMarch 31, 2007 at 12:53 AM

    Thank you, solved my problem.

    ReplyDelete
  110. RianApril 2, 2007 at 6:44 AM

    Your tip worked for me. Thanks a bunch

    ReplyDelete
  111. shahidApril 2, 2007 at 1:01 PM

    thanx for help me ..

    your tips that is first uninstall the visual studio 2005 with help of asp_regiis -u , and then go instal the visual studio 2003 with the help of asp_regiis -i at .net command prompt.

    and the my web page run smoothly..

    thanks for tips

    ReplyDelete
  112. mehmetApril 10, 2007 at 1:43 PM

    Thanks for the help;)

    ReplyDelete
  113. a friendApril 12, 2007 at 8:54 PM

    thank tou men, truly, that's the best solution to my problem.

    You know, I found wars on the net about that pb, but without a real solutions,



    but yours was simple, short , clear and it works!

    thanks again ;)

    ReplyDelete
  114. kishoreApril 20, 2007 at 2:37 AM

    ref: to them who found a fix for this bug..



    how did you even come up with such thing ( problem with version change ).. when the error is auto-attach process failed for aspnet...





    i am curious,, but yet you are the bst.



    thanks



    if you have anyting for me please reply to kishorekodru at gmail dot com.



    thanks once again, it solved the problem in 2 minutes... i was sitting whole day to figure out why?

    ReplyDelete
  115. Akhil PuriNovember 26, 2007 at 8:54 AM

    Thanks a lot man.. Its simple yet very nice..

    ReplyDelete
  116. Achin SaxenaNovember 27, 2007 at 9:03 AM

    Thanks A lot..... That was simply superb

    ReplyDelete
  117. Justin ZFebruary 15, 2008 at 4:56 PM

    Easily the best fix I have ever found on the internet. This could have taken me hours to figure out (thanks to Microsofts cryptic message) but this allowed me to solve the issue immediatly. Thank you very much.

    ReplyDelete
  118. TnoApril 30, 2008 at 9:58 PM

    Thanks a lot

    ReplyDelete
  119. MerlinMay 19, 2008 at 8:36 AM

    Hi,

    Iam not able to change the Asp.net version from IIS manager..That the combobox have only one value..I didnt see like 1. something like ..What can I do nv? plzz assist me ..





    Thanks in advance ,

    Merlin.

    ReplyDelete
  120. Egil HogholtMay 20, 2008 at 12:32 PM

    Which versions of ASP.NET do you have installed?



    You should have one sub directory here for each version:

    C:\WINDOWS\Microsoft.NET\Framework

    ReplyDelete
  121. JenniferJuly 1, 2008 at 8:09 PM

    Awesome fix! Thanks! I contacted Microsoft directly about this, and after 3 days of waiting with no response, I decided that they must not know the answer. Thank goodness Google brought up your post!

    ReplyDelete
  122. PraveenNovember 10, 2008 at 1:39 PM

    Thanks a lot... it solved my problem... thanks again

    ReplyDelete
  123. darylDecember 11, 2008 at 5:27 AM

    good it is ok

    ReplyDelete
  124. MustafaJanuary 22, 2009 at 10:58 PM

    Thanks. It solved my issue as well.

    ReplyDelete
  125. apanmanFebruary 25, 2009 at 2:20 AM

    Thank you very much. I had searched the solution for few days and now get it to work. Many thanks again ^^

    ReplyDelete
  126. pradeepMay 4, 2010 at 5:19 AM

    Error 2 'UpdatePanelUpdateMode' is ambiguous in the namespace 'System.Web.UI'.
    wat shud i do frnds suggest me

    ReplyDelete
  127. pradeepMay 4, 2010 at 5:37 AM

    UpdatePanel inmy design page is not working, n also there is an error showing that
    Error:
    'ScriptManager' is ambiguous in the namespace 'System.Web.UI'.
    What am soppose to do?

    Mail me ur ideas to this id pls
    pradi_vijay04@yahoo.co.in

    ReplyDelete

Subscribe to: Post Comments (Atom)