ABCpdf AddImageUrl 할때 엑세스 거부의 원인

해당 사이트에서 확인 해보면 IIS 유저가 읽기까지는 권한이 있어야 한다
(이부분은 저도 따로 세팅 한건 없기 때문에 users 그룹으로 본다면 읽기까지는 가능할 듯합니다.)

그리고 확인 할 부분이
2003 Server같은 경우에는 IE 보안 정책이 있는데 이부분을 안해야지만 사용이 가능합니다.
2008 Server 같은 경우에는 서버 관리자에서 IE ESC를 관리자,사용자 둘다 체크 해제 하시면 됩니다.

6.7 - My code is throwing errors like 'HTML render is blank' or 'Unable to render HTML' or 'Unable to read file' or is producing a blank output.

First read the previous section carefully.

Firewalls, DNS and proxy servers can present particular problems for URL rendering because they may require some kind of logon. Your IIS user will most likely not have a logon. You need to allow ABCpdf to logon automatically.

Windows Authentication can produce a challenge that your IIS user may not be responding correctly to. You will find details of how to manage Authentication in the documentation.

Windows Serve 2003 defaults to an Internet Explorer Security policy which may interfere with HTML rendering. You may have to modify or disable the policy to allow access to the pages you want to render. If you wish to remove the security component you can do so using the "Windows Components" section of the "Add & Remove Programs" control panel.

In Windows Server 2008, open the Server Manager. From the Security Information section, choose "Configure IE ESC". You can then configure access separately for Administrators and Users.

If this doesn't help...

First work through some simple sanity checks and common causes of this type of issue.

1. Do ensure you can browse to the appropriate location using IE while logged on as Administrator. Make sure IE doesn't throw up any blocks or warnings. ABCpdf requires a clear route through to the page.
2. If you're rendering a URL on your localhost then ensure that the IIS user has read access to this location.
3. Lack of access of access to the windows/temp directory is a frequent cause of this type of issue. Ensure that your IIS user (eg ASP.NET or IUSR_MACHINENAME) has read/write permission and also (if it fits with your security policy) the ability to create folders. You may also find that ASP.NET is being denied access to its own preferences (eg C:\Documents and Settings\MACHINENAME\ASPNET or C:\Documents and Settings\NetworkService).
4. The default value of HtmlOptions.HostWebBrowser is true, which provides greater compatibility with a wider range of HTML and JavaScript. However this setting also requires a greater level of permission. If sufficient permissions are not available you may see errors like "Windows error 5" or "Access is denied" or "Unable to create memory-based MetaFile". If this is the case try setting the HostWebBrowser property to false prior to calling AddImageUrl/Html. If you do not have access to the source code you can change the default by entering a HostWebBrowser registry key - details in the ABCpdf .NET documentation. If you do this on an x64 server be sure to set both the 64 bit registry key and also the 32 bit Wow3264Node based key.
5. It is our experience that it is surprisingly common for web servers not to be able to resolve URLs to themselves. This means that when testing using an IP address your code will work but when you try and render a web page on the local server using a URL you may get issues.
6. If all this looks fine and you're still seeing problems we strongly suggest putting in ten minutes with ProcessMonitor. In most cases it will flag an obvious cause. We suggest you do not apply ProcessMonitor filters as problems may not always be quite where you expect them to be. You will find details on how to use ProcessMonitor on the "I'm having problems with Security." section of this page.

If this doesn't help...

You need to establish a test case to establish the boundaries of the problem.


출처: http://www.websupergoo.com/support.htm