I have a web service running on a Windows 2003 server (IIS). The server is a member server, not a domain controller. The service must run under a separate application pool because it needs to have additional permissions that the default application pool does not provide. The web service is setup to run under a separate domain user account name, and the application pool runs under the same account name.
Everything was working fine until the domain server crashed. Unfortunately, I did not have a backup domain controller, so I had to rebuild the domain controller (now I have a backup controller). I recreated all of my user accounts, including the one used to run the web service and its application pool. Now when I try to access the web service through a browser, I get "Service Unavailable". My web applications that use the service return error 503 Service Unavailable. If a change the web service to run under the default application pool, the web service will then run, but it does not have the necessary permissions.
I have tried to recreate the application pool and even give it a different name, but I still cannot get the web service to run under the separate application pool. Does any one know how to fix this?