Error Message - Any HTTP 401 Errors, 404 Errors, or HTTP Request Failed 401 Access Denied Error

This is a compilation of known 401 and 404 errors that occur when attempting to run the system on some Windows and other internet platforms. 

These error messages are not specific to the Integral Accounting Enterprise system.

There are several causes for this error and several different solutions to the problem based upon the cause.


IMPORTANT NOTE:
IF YOU ARE GETTING A GENERIC YELLOW ERROR SCREEN, FIRST GO TO THE SERVER ITSELF AND REPRODUCE THE ERROR. 99% of the TIME the system will tell you right there on the screen what the EXACT error is and you can correct it! The real error ONLY appears on the server screen due to the way Dot Net Operates!

 

First Cause (Most Common)

Many times the person installing the software did not properly set the access permissions in the IIS manager for the application. Please go into the IIS manager, and for the "EnterprieASP", "EnterpriseWS", or "EnterpriseX" or "EnterpriseCloudMvc" and any other enterprise applications you are running open the properties form, select "Directory Security" then press the "edit" button next to the "Anonymous access and authentication control" icon. Make sure that "Anonymous access" checkbox is selected, and "allow IIS to control Password" is selected (if you have this option) and that "Integrated Windows Authentication" is selected at the bottom"

Restart IIS and try the application again.


 
Second Cause

An incorrect setting can cause this error in the "User Rights Assignment" under "local policies" in the "local security policies" Administration tool.

"Impersonate a client after authentication" needs to have the ASPNET account assigned to it. Check this setting and add the proper user if necessary

More details about this particular problem can be found on the Microsoft Support Website at: 

http://support.microsoft.com/default.aspx?scid=kb;en-us;817033&Product=NETFrame

 

Third Cause (Upgrade Problem)

If the second cause was not the issue, this cause may be the problem. Sometimes security patches from Microsoft change some settings that effect the way that the system handles Dot Net applications.

First, on any Windows Server Boxes, PLEASE be sure to use the Windows Update Tool to bring the system current before you begin your installation, or different errors can be introduced. If your system is running error free and you run the Windows Update then get the above error, then this error was most likely the one that was introduced.

Security can be reset using the following procedure:

Go to IIS, and go to the IIS web site Properties
Select Directory Security
Select Authentication and Access Control
Click the Click Edit Button and the Authentication Methods Tab comes up
Make sure that Enable Anonymous Access is ticked
User Name should be YOUR_SERVERNAME\IUSR_YOUR_SERVERNAME
The Password needs to be reset

Now go to Active Directory Users or [Computer Management - Local Users & Groups if not using Active Directory]

Select the User IUSR - Internet Guest Account
Reset the password to the one you just typed in under IIS - Authentication Methods

This should correct the problem. If not, proceed to the fourth cause.


Fourth Cause (User Issues)

When you install the Windows Server System, the system will create a system name and create users for the system with the proper permissions. However, if you change the system name at some point in the future, the system handles the name change properly, but does not recreate the system users with the proper permissions. As a result, many of the system accounts, including the one necessary for running Dot Net apps, will no longer work.

You should make sure that during Initial System Installation, you are selecting the correct system name and that this will not change.

If you do change the name of the system, you will need to do one of the following:

1) Re-Create all of the system users with their proper permissions

- or -

2) Re-Install Windows and give the proper system name at installation.

The Microsoft Knowledge Base also has a review of the errors of this type that you can find by searching the site for the exact error message displayed.

If the problem is not caused by the previous causes listed above, then the problem may be with the Dot Net framework. If you had an early Dot Net Framework installed on your computer and upgraded it to version 2.0, or you have 2.0 and have upgraded to a higher version, sometimes a problem occurs during the upgrade process that can cause errors. If you are getting the error mentioned above and other unexplained errors and problems with the newly installed Dot Net Framework, uninstall the Dot Net Framework and all the programs that depend upon it, re-install the dot net framework, then install the programs that depend upon the dot net framework. 


The "GetCompanies()" Variety of 401 Error
When you receive the 401 Error and in the body of the error message it is stated that the failure was with the "GetCompanies()" command, this means that the front-end ASP Dot Net app can not connect to either the web services or the web services could not connect to the back-end database. This error occurs if you change the configuration of the application, like changing the location of one of the application layers, or changing the default users or the default password without making the required adjustments in the web.config file or the application.config file. Please make the appropriate changes to the configuration files and the application will work fine.