Error Number: 110000 Access is denied

7 December 2018

Issue Description

After selecting a Crystal Report Web Goto in AnyView Browser, the following error is displayed:

Error in Page
Page: /Anyview/WebGotoName.asp
Error Number: 110000
Error Description: Access denied.
Additional Info:
AnyView Version: AnyView Build build number - date time

The AnyView Web Goto Setup Wizard requires the Crystal Report to reside on a UNC path. If this UNC path is not on the same machine as IIS, there can be permissions difficulties with the default "IUSER_MACHINENAME" IIS anonymous user not being able to read the report. This results in any anonymous web user receiving the error message.

Solution

Microsoft has a KnowlegeBase article (#207671) delineating how to overcome this type of problem. It outlines several methods of successfully sharing content that comes from a UNC path so that IIS can access it.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;207671

 

One of their suggestions is to keep files on the local computer. If you want to have the reports stored on the local IIS machine and referenced by drive letter notation instead of UNC path, then you must modify the Dex.ini file on the Great Plains Client used for setup. The setup path for the report must be a path that is valid on the IIS server, where it will be interpreted at run time. Please add the following line to the Dex.ini file:

ASILocalReports=TRUE

In a production environment, it may be more useful to keep the reports on a remote share. In this case, one will have to follow one of the other suggestions in the KB article. One example method of accomplishing this is to configure the anonymous account as a domain account.

This involves changing the IUSER_MACHINENAME under the 'Edit' button on the Directory Security tab of the AnyView Virtual Directory property sheet to a domain user (ex: DomainName\DomainUser) and unchecking the "synchronize password" box. Unlike IUSER_MACHINENAME, This domain user will be part of the 'Everyone' group on the machine with the remote share so will be able to read the .rpt files if the NTFS share and file permissions are set for 'Everyone' to read, or explicitly set for DomainName\DomainUser to read. This Domain user should be explicitly set up for this purpose with a password that does not expire - see another KnowledgeBase article referenced for additional security recommendations:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;280383