MSXML 4 - Access is Denied
            
        
                Sample Error
            
            
                msxml4.dll (0x80070005)
Access is denied.
            Access is denied.
                Solution or Workaround
            
            
            
                This error indicates a server configuration problem.  The MSXML server object PDshop is trying to access is not configured properly.  You would need to contact your web host or server admin to resolve this problem, this is not related to PDshop scripts or database/file permissions.  
If you are using the Advanced Edition of PDshop you can change the "Server Object" that PDshop uses from within PDAdmin, find this setting under the "Advanced" menu in PDAdmin.
RECOMMENDED SOLUTION:
See the Microsoft Article #820882 (link below). Contact Microsoft directly for assistance with this issue.
ALTERNATIVE SOLUTION:
Some server administrators have reported that changing a few registry entries has helped resolve this error. NOTE: We do not provide tech. support for server issues such as this, nor are we responsible for any side effects of using the Windows Registry Editor, use at your own risk. By changing/adding the values shown below in the registry, you may be able to workaround the MSXML security issue:
HKEY_LOCAL_MACHINE\Software\Policies\ Microsoft\Windows\CurrentVersion\Internet Settings\Security_HKLM_only (Dword value) = 1
HKEY_LOCAL_MACHINE\Software\Microsoft\ Windows\CurrentVersion\Internet Settings\Zones\3\1601 (Dword value) = 0
*** We do not recommend or support using the Windows Registry Editor. There is no guarantee this alternative solution will work. Use at your own risk.
            
            If you are using the Advanced Edition of PDshop you can change the "Server Object" that PDshop uses from within PDAdmin, find this setting under the "Advanced" menu in PDAdmin.
RECOMMENDED SOLUTION:
See the Microsoft Article #820882 (link below). Contact Microsoft directly for assistance with this issue.
ALTERNATIVE SOLUTION:
Some server administrators have reported that changing a few registry entries has helped resolve this error. NOTE: We do not provide tech. support for server issues such as this, nor are we responsible for any side effects of using the Windows Registry Editor, use at your own risk. By changing/adding the values shown below in the registry, you may be able to workaround the MSXML security issue:
HKEY_LOCAL_MACHINE\Software\Policies\ Microsoft\Windows\CurrentVersion\Internet Settings\Security_HKLM_only (Dword value) = 1
HKEY_LOCAL_MACHINE\Software\Microsoft\ Windows\CurrentVersion\Internet Settings\Zones\3\1601 (Dword value) = 0
*** We do not recommend or support using the Windows Registry Editor. There is no guarantee this alternative solution will work. Use at your own risk.
                Related Articles
            
            
            
            
                Other Resources
            
            
            
            
                Related Topics
            
            
            
            
                
        Article Applies to:
        ASP (classic Active Server Pages)
                
            
        
            Search for help...
        
        