Avaya IP Office 3.2 Applications Installation & Administration Manual page 38

Applications Installation & Administration
5. Specify that the ASP.NET worker process will run under the new user account.

Open the \WINNT\Microsoft.NET\Framework\V1.0.XXXX\Config\Machine.config file.

In the <processModel> section, change the userName and password attributes to the
name and password of the new user account. For example:
userName="DomainName\ASPNETUSER" password="ASPNETUSERpassword".

Save the changes to the Machine.config file.
Problems Accessing Web Sites
Problem:
Although on the local PC http://127.0.0.1/AVECS and http://127.0.0.1/AVECSWEB both load their
respective pages correctly, http://pc_name/AVECS and http://pc_name/AVECSWEB does not load.
Possible Solution:
Ensure that the name of the PC does not contain an underscore or any other non-standard characters
prohibited from the standard PC naming conventions. Permissible characters include: a-z, A-Z, 0-9 and
hyphens (-).
Maximum Logon Attempts Exceeded
Problem:
When the AVECS page is loaded, a grey error message is loaded, clicking Refresh loads the page
successfully. However, after logging in, a message stating that the maximum logon attempts have been
exceeded is displayed.
Possible Solution:
Check that the user ASPNET exists on the local PC. If the user does not exist, create the user by going
into the Local Users and Groups setting via My Computer.
Network Service Error
Problem:
When logging into the Conferencing Center Scheduler an error message opens stating login failed for
user 'NT Authority\Network Service'. The error displayed on the grey background refers to
NTAuthority\Network Service and is followed by the Max logon attempts error. Similarly, if the error
states NTAuthority\Local Service, the corresponding procedure will need to be followed.
Possible Solution:
If this is running on a Windows 2003 Server, the following settings should be verified:
1. Right click on My Computer, click Manage.
2. Select IIS Manager > Local PC Name > Application Pools > DefaultAppPool
3. Select Properties
4. Select Identity and ensure Local System is set.
Page 34
15-601133 Issue 1 (7 June 2006)
Applications Installation & Administration Manual
IP Office 3.2