Search

An error was encountered. Please return to the previous page and try again. by Reza Wahadj

Closed
as Won't Fix Help for as Won't Fix

2
0
Sign in
to vote
Type: Bug
ID: 118567
Opened: 12/31/2005 12:53:43 PM
Access Restriction: Public
1
Workaround(s)
0
User(s) can reproduce this bug
when I create Personal web site and trying to access "ASP.net Web site Administration tool" from website menu or Solution explorer it give me the follwing error "An error was encountered. Please return to the previous page and try again. "

Details (expand)
Product Language
English
Version
Visual Web Developer 2005 Express
Category
Web Project
Operating System
Windows XP Professional
Operating System Language
English
Steps to Reproduce
nothing to do
Actual Results
nothing
Expected Results
there is no result
File Attachments
0 attachments
Sign in to post a comment.
Posted by Jason OB on 7/30/2011 at 7:34 PM
I've encountered this problem also. I ended up solving it by changing the path to a location without any spaces in the folder names. Alternatively you can specify the path in the URL like this:

http://localhost:<port>/asp.netwebadminfiles/default.aspx?applicationPhysicalPath=D:\VSWorkspaces\<path>\<to>\<project>\<dir>&applicationUrl=/

If there are spaces in your path make sure to escape them in the URL.

Hope this helps someone else.
Posted by Asad Chaudhry on 2/18/2011 at 10:11 AM
I had the same issue. I managed to get around it by creating a new directory under the c drive, c:\development, and I created my VS project in there and it worked. When it doesn't work, I think it's go to do with directory names having spaces and other such characters in the path.
Posted by sadeghhp62 on 9/7/2010 at 1:39 AM
i think it is just in web sites ! in web application , administrative tools work fine !
Posted by Echo Train on 6/3/2010 at 4:26 PM
Four years later, I am facing the same problem, made numerous attempts to fix it without success. I have not been able to find much in the forums or anywhere else. I have closed the Admin Tool and restarted it without effect. Uninstalled and reinstalled VS twice without effect. There are no unusual characters in my paths. If anyone has found an answer, I would love to know about it.
Posted by John I. _ on 5/10/2010 at 6:55 PM
Gideonr1, You saved my sorry ass.
Posted by ghostprocess on 10/15/2008 at 4:39 AM
brilliant work there "Gideonr1"
Posted by Bidware.com on 12/12/2007 at 6:02 PM
Thanks Gideonr1!! It solved my issue. Why didn't anyone have any solution to this for so long?
Posted by GidoenR on 12/11/2007 at 6:32 AM
Make sure you do not have any non Alphabet characters in your path (such as # or non English)
-> c:\c#\myProj won't work change to c:\css\MyProj .... and magic :-)
Posted by Microsoft on 7/20/2006 at 1:46 PM
Due to the way the feature is designed, unfortunately there isn't an easy way to address the issue you have reported.

To workaround the issue, it is recommended to close Website Administration Tool and launch it again, which usually resolves the conflict which the error is introduced by. Thanks for taking the time to provide us this feedback.

Web Development Tools Team
Posted by Microsoft on 1/2/2006 at 12:54 AM
Thank you for your feedback. We are investigating this issue.

Thank you, VS2005 Product Team.
Sign in to post a workaround.
Posted by Elenchikos on 6/17/2011 at 7:46 AM
Here's what worked partially for me. I was using Firefox. I saw a post on another forum that said changing the default browser to Internet Explorer worked. So I tried it, and it worked - one time. I am using Windows XP SP3. It never brought up IE, but it brought up the configuration page in Firefox. When I tried a second time it didn't work. When I went back into "Program Access and Defaults" "Use my Current Browser" was selected. When I selected IE again, it brought up Firefox again with the configuration page. But I have not found a way to make it stick yet. The only clue I have is that the other day, I told Firefox to check every time whether it was the default browser. Every time I started it, it was saying it was no longer the default browser. So I turned off the check. Firefox continued to be my browser, but now I have this problem with ASP.NET configuration page.