DNN 3.2.2
on our dev site, I installed the way DNN said to, with a virtual DotNetNuke folder. Now we are stuck with that in every path.
I want to move the DNN files up to the root and get rid of that folder; I am not finding much help for doing this on the DNN sites.
I have set up a new test DNN site on a virtual IIS service to try to figure this out.
Our setup:
*.wbtdev.net points to one IP on the Server: ...50.
That server has a default IIS site with no host header defined so it will catch all requests
dnn.wbtdev.net points to the same IP, and there is a second IIS server instance with host header of dnn.wbtdev.net
on this second server, I installed DNN on the root, to a new SQL db just for this test.
this runs fine.
the alias list on the default portal is:
Edit dnn.wbtdev.net/dotnetnew/
dnn.wbtdev.net
Edit dnn.wbtdev.net/test2/
Now I want to move the DNN files to a new folder: /test2/
have the ASP.NET machine account set to full permissions on the root and all folders of this site.
I stop and restart this virtual server; I clear the cache of my browser (actually shut down the browser and start it up again, but then clear cache and cookies). (cookies because I just found a post that suggested that)
then sent the browser to dnn.wbtdev.net/test2/
and I get a yellow screen with this error:
Server Error in '/' Application
I tried changing the <customErrors mode="Off"/> tag in web.config as that page suggests for getting error messages but it never makes any difference.
I drag the files back to the root, stop/start the IIS server, clear the brower, reload and all is well on the original site again.
any thoughts on where I might find what is locking the site to the original folder (root)?
Would I be able to edit that to get it all to work?
thanks for looking at this with me.
tomvw |