I added the DesktopModules folder, but IIS WP account already had access to the that folder because it inherited it from the folder above it. I still have the same problem.

It seems strange that you can get it working when I can't. I wonder if it is the web.config? Are you creating a new web.config for the subdomain? I think I remember the web.config containing keys that allowed passwords to work properly. I created a new web.config from the release.config for the subdomain, was that incorrect?

Right now Network Service, System, Plesk IIS User, Plesk IIS WP User, and Plesk Domain user all have correct rights....am I missing one? This has to be something simple that is failing.

Thanks

So tonight I figured out how to do it properly. The proper way to set this up is not with subdomains, but with domain aliases.

Select the domain from the control panel and look for the domain aliases button.
Create an alias name (i.e. subdomain.mydomain.com)
Then go to your host portal on that domain and create the portal using that new alias.
It works right away with no problems no errors.


So what the catch right?

The catch is 3essentials only allows one alias per domain that you are hosting to prevent you from hosting hundreds of subportals off your main portal. They will sell aliases for $1 per month, but I am not sure it there is a limit there. I personally think they need to offer a few per domain...but thats really because i need them as previews for sites.

I see what you mean. On my old host I used a redirector code to send my subdomains to the same location as the main install essentially turning my subdomains into portals. I may try again later if I need more installs of the software. Until then I will just use my one lonely alias. I suppose $1 per month isn't horrible if I am using them.

thanks for the help though. I am glad I can use these forums and have people respond....it always very helpful.