I have the exact same problem and I don't see how the article Steve linked to helps. Did you solve the problem?
/Christian
Theres a conflict with the Manager and .Net versions > 2.0 (3.0 and 3.5), and it tries to invoke the aspnet_regiis from the wrong location.
Heres a (somewhat) ugly workaround:
1. Move the folders c:\windows\microsoft.net\frameworks\v3.0 and c:\windows\microsoft.net\frameworks\v3.5 to some other location (for example c:\temp)
2. run Manager as you normally would
3. after Manager is done, the folders can be moved back to their original location.
/johan
Duh!
Should have read the complete error description...
sorry about that.
/johan
Hi, I got the same problem after I got a new computer and with SP1 for Vista installed. The solution for me was to first install an empty site within the IIS7 and use the Default App.pool. Then install the site from the manager into that site. Then deleting the site again, install a new site in IIS7 then pointing the Physical Path to the site installd by the manager. After that you follow the steps in Ruwwens blog:
http://labs.episerver.com/en/Blogs/Ruwen/Dates/112201/112202/Run-EPiServer-Manager-under-Vista/
to get the site runnig with Default App.pool settings.
This worked for me so hopefully you will get your site up and runnig as well!?
/Eric
"Try to click on Back until you get to the first step in the wizard, then click Next again all the way to the end. Worked for me."
This actually worked for me as well! (on win7) :p
"Try to click on Back until you get to the first step in the wizard, then click Next again all the way to the end. Worked for me."
This actually worked for me as well! (on win7) :p
----------------------------------------------------------------
Worked for me aswell, funny!
Clicking back all the way to start of installation and start again worked for me too! Kinda strange but least it worked. :-)