Symptoms
After installation, you can't login to AgilePoint Enterprise Manager and/or the AgilePoint Tusca sample application.
When attempting to login, you may see one of the following error messages:
- a "Service Unavailable" error
- a "401 unauthorized" error
Cause
There are several possible causes for this problem, including:
- incorrect username and password
- incomplete product installation
- the user account of the user performing the installation may have insufficient security privileges
- multiple network adapters (simultaneously enabled on the same machine) cause the request to get misrouted
- Windows Internet Naming Service (WINS) is not configured properly
- proxy settings/server configuration issues
- multiple Web sites are configured in IIS to use the same port number
- .NET framework version incorrectly set in IIS
- DNS resolution issues and/or host file/header configuration
See below for suggestions on how to diagnose and fix the problem.
Resolution
Use the information below to help verify that your AgilePoint products were installed correctly:
The following is a check list that can help you troubleshoot the problem.
- Make sure you use local Administrator account to install the AgilePoint products.
- Make sure you have installed all the pre-requisites, especially the .NET framework.
- Make sure your Internet Information Services (IIS) was installed and setup prior to the installation of the .NET framework and AgilePoint.
- Make sure your Internet Information Services (IIS) is up and running.
- Make sure the Authentication Methods for the IIS web site for the AgilePoint Server has the "Anonymous access" unchecked. To access the Authentication Methods dialog, start Control Panel > Administrative Tools > Internet Information Services. In the IIS dialog, find the web site of where AgilePoint Server is installed, the default is under the "Default Web Site > AgilePointServer". Right mouse click and select "Properties" from the menu to bring the properties dialog for AgilePoint Server. Select the "Directory Security" tab and click "Edit" of " Anonymous access and authentication control". Uncheck the Anonymous access option and make sure the Integrated Windows authentication is checked.
- If Active Directory is being used and any of the following user accounts are "Windows domain accounts", you can try enabling
both Windows Integrated authentication and Digest authentication for the IIS web applications for AgilePoint Server and AgilePoint Enterprise Manager (or the entire web site, if desired):
- The Identity of the Application Pool used by AgilePoint Server and Enterprise Manager
- AgilePoint Server's configured System User
- The account that you are attempting to log into AgilePoint Enterprise Manager with
On machines where the above change resolves the problem, it is likely that the problem was caused by the Microsoft issue described in Microsoft KB article 871179:
- Make sure the .NET framework version configured in IIS for AgilePoint Server and Enterprise Manager are set to the correct version. To verify, select Control Panel > Administrative Tools > Internet Information Services. In the IIS dialog, find the web site of where AgilePoint Server is installed, the default is under the "Default Web Site > AgilePointServer". Right mouse click and select "Properties". If you see a tab called "ASP.NET", click that tab and make sure the ASP.NET Version is configured properly. If you installed the .NET 2.0 version of AgilePoint, the ASP.NET Version should be set to 2.0 (i.e. 2.0.XXXX).
- On the AgilePoint server, try updating the web.config file in the root of your AgilePoint EnterpriseManager web application (as shown in the fragment below). Change "localhost" to the actual IP address that the AgilePointServer application runs under, then save the change and attempt to login to AgilePoint Enterprise Manager again.
<appSettings> <add key="ServerUrl" value="http://localhost:81/AgilePointServer" />
You can also try using the special loopback IP address "127.0.0.1" instead of the machine's assigned IP address.
For example:
<appSettings> <add key="ServerUrl" value="http://127.0.0.1:81/AgilePointServer" />
On machines where the above change resolves the problem, the following explains why:
When an ASP.NET application calls an ASP.NET Web Service on the same machine (via localhost or machine name URL) IIS never receives the HTTP request. However, the same request is processed correctly when using an IP address. This is apparently an issue with the server's DNS resolution system.
If the problem still persists, you can try the following depending on what your system OS is:
Windows 2003 : Add an application pool such as "AgilePoint" and uses local Administrator as the identity. Then assign this application pool to both AgilePoint Server and Enterprise Manager websites and virtual directories in IIS. Reset IIS after the changes. If you are using a domain user as the identity, make sure this domain user is added to the local Administrators and IIS_WPG groups. The domain user must also be added to the database as db_owner if the windows authentication is used.
Windows 2000/XP : Locate the machine.config under the .NET framework such as:
c:\windows\microsoft.NET\Framework\v.1.1.4322\CONFIG\machine.config.
Make a copy before your modification. Look for the line with username="system" password="AutoGenerate", modify to username="administrator" password="your_administrator_password" where your_administrator_password is the actual password for your local Administrator account. Reset IIS after the changes.
Note : You should always consult your company's IT department for system security setting to make sure it follows your company's security policy. Please contact Ascentn support for additional information about AgilePoint security setting. For general information about Microsoft .NET and system security, please refer to Microsoft documentation.
