tag:blogger.com,1999:blog-32696142.post5327046895687588395..comments2024-02-19T01:02:59.086-06:00Comments on ASP.Net, C#, SQL, JQuery, Sharepoint: Runtime Error while opening Sharepoint SiteUnknownnoreply@blogger.comBlogger4125tag:blogger.com,1999:blog-32696142.post-78104155881994384612009-03-19T13:52:00.000-05:002009-03-19T13:52:00.000-05:00Thank you very much, i do exactly what you wrote a...Thank you very much, i do exactly what you wrote and works fine , im from bolivia south america, and i try to find the solution in others blogs but this one is the most quickly and secure, than againEdwinhttps://www.blogger.com/profile/06196821384235654046noreply@blogger.comtag:blogger.com,1999:blog-32696142.post-72428373192902372532008-07-30T11:06:00.000-05:002008-07-30T11:06:00.000-05:00The comment from Andrew is irrelevant. If your ce...The comment from Andrew is irrelevant. If your central admin site is returning the server error then you can not use central admin to delete any web applications. He's answering a completely different problem.<BR/><BR/>Also, this article is not particularly helpful. Completely wiping your machine and starting over is a poor answer and one that we can all arrive at ourselves. <BR/><BR/>So.Nathan Andersenhttps://www.blogger.com/profile/16366319749360136875noreply@blogger.comtag:blogger.com,1999:blog-32696142.post-41756339677677215032008-02-29T08:14:00.000-06:002008-02-29T08:14:00.000-06:00HI try to give write access\ to the logged in user...HI <BR/><BR/>try to give write access\ to the logged in user to the following folder C:\windows\Microsoft.NET\Framework\v2.0.50727.Himani Sharmahttps://www.blogger.com/profile/01120735018189594482noreply@blogger.comtag:blogger.com,1999:blog-32696142.post-5338225489007239042008-01-22T05:25:00.000-06:002008-01-22T05:25:00.000-06:00HiWe also experienced this issue on our QA server ...Hi<BR/><BR/>We also experienced this issue on our QA server at a Clients offices, there is a way to fix this without doing a complete <BR/><BR/>uninstall and re-install.<BR/>The cause is still open to debate, but a developer was working on one of the user controls in the IIS wwwroot folder.<BR/>After the issue became known the changes where undone, but this not fix the issue.<BR/><BR/>OK, firstlyAndrew T-Shttps://www.blogger.com/profile/14297507480561119065noreply@blogger.com