Some have encountered that when trying to install ServiceDesk, the requirements check for ASP.NET fails. Often, the server logs will show the following error: "The identity of application pool Default App Pool 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." This behavior has been noted with ServiceDesk 7.1, but may be relevant to prior builds of ServiceDesk, as well.
Often, the server logs will show the following error: "The identity of application pool Default App Pool 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." This behavior has been noted with ServiceDesk 7.1, but may be relevant to prior builds of ServiceDesk, as well.
1. Add the service account to the IIS_Users group on the ServiceDesk server.
2. Make sure that the service account is not denied "logon as batch" and "logon as service" in AD. You may need to have your Active Directory administrator allow this for the service account. Please note that these changes may need time to replicate; consult your AD administrator for replication schedules. In some cases, a reboot of the ServiceDesk server may be required to proceed.
Often, the server logs will show the following error: "The identity of application pool Default App Pool 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." This behavior has been noted with ServiceDesk 7.1, but may be relevant to prior builds of ServiceDesk, as well.
To resolve the issue, you will need to do two thiSome have encountered that when trying to install ServiceDesk, the requirements check for ASP.NET fails. Often, the server logs will show the following error: "The identity of application pool Default App Pool 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." This behavior has been noted with ServiceDesk 7.1, but may be relevant to prior builds of ServiceDesk, as well
Causes:
Assuming the installation documentation for the appropriate version was followed, there are a couple things that can cause this. These both involve the service account used to run the Default App Pool in IIS. Here they are:
1. The service account is not added to the IIS_USRS group on the ServiceDesk Server.
2. There are domain policies in place that prevent the account from performing its function.
Solution:
To resolve the issue, you will need to do two things:
1. Add the service account to the IIS_Users group on the ServiceDesk server.
2. Make sure that the service account is not denied "logon as batch" and "logon as service" in AD. You may need to have your Active Directory administrator allow this for the service account. Please note that these changes may need time to replicate; consult your AD administrator for replication schedules. In some cases, a reboot of the ServiceDesk server may be required to proceed.