Link to home
Start Free TrialLog in
Avatar of Metaltree
MetaltreeFlag for United States of America

asked on

The identity of application pool is invalid event 5021

I'm doing a stand alone install of a budgeting business application. I have a brand new 2008 R2 server with IIS  7.5 and .NET 4.0.

The problem I'm running into is that after it installs and creates its website and application pool, if I don't change the identity, I get a SQL Exception error that says: "Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'DOMAIN\SERVERNAME$'."

If I do update the identity on the application pool to the domain user account I want to use , it gives me Error 503 and Stops the BizApp application pool. It spits out the event pasted at the bottom.


I've already updated the Application Pool Identity to the domain user service account I created. The user is part of the local IIS_USRS group and also the domain IIS_WGP group.

The SQL database this WILL point to is not created yet. During the step it asks me for a server and instance name and I provide it, assuming it will create the datasbase for me.

I'm stuck, thoughts?


The identity of application pool BizApp is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request.  If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.
ASKER CERTIFIED SOLUTION
Avatar of xDUCKx
xDUCKx

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Metaltree

ASKER

Good call DUCK.

I added the account to "Log on as a Service" on the LOCAL group policy of the BizApp server and the SQL server.

Then I discovered in the Default Domain Policy, the "Log on as a Batch job" had two entries specified for backups. I added the BizApp user to this policy.

After that I updated group policy on both servers, making sure changes were reflected, and it worked!