Microsoft KB Archive/184291

= COM objects fail to print when called from ASP =

Article ID: 184291

Article Last Modified on 7/10/2006

-

APPLIES TO


 * Microsoft Active Server Pages 4.0
 * Microsoft Internet Information Server 4.0
 * Microsoft Internet Information Services 5.0

-



This article was previously published under Q184291



SYMPTOMS
A COM object that sends output to a printer fails when called from Active Server Pages (ASP) but functions correctly when called from an interactive application. This COM object could be either a commercial product such as a Microsoft Office application, or a custom third-party object. A common error message is "ClassName error '800a01e2' Printer error."



CAUSE
The standard APIs that most objects use to print depend on registry entries located in HKEY_CURRENT_USER. This registry hive is dynamic. Depending on which user context the process is running under, different information will be loaded into this hive. ASP pages run under IIS, which is running as the SYSTEM account. When you create an instance of a COM object in your ASP code, by default, it will also run as the SYSTEM account. By default, the SYSTEM account does not have any printers set up in the registry.



RESOLUTION
You can set up printers for the SYSTEM account to resolve this problem. To set up printers for the SYSTEM account, perform the following:

This method requires you to modify the registry using the Registry Editor.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.  Ensure that the user you are currently logged into on the server has the desired printers installed. Launch the Registry Editor (Regedit.exe).  Select the following key:

     HKEY_CURRENT_USER \Software\Microsoft\Windows NT\Current Version\Devices

 From the Registry menu, click Export Registry File. In the File Name text box, type c:\Devices.reg.  Select the following key:

<pre class="fixed_text">     HKEY_CURRENT_USER \Software\Microsoft\Windows NT\Current Version\PrinterPorts

</li> From the Registry menu, click Export Registry File.</li> In the File Name text box, type c:\PrinterPorts.reg.</li>  Select the following key:

<pre class="fixed_text">     HKEY_CURRENT_USER \Software\Microsoft\Windows NT\Current Version\Windows

</li> From the Registry menu, click Export Registry File.</li> In the File Name text box, type c:\Windows.reg.</li> From the Start button, select Run. Open Devices.reg in Notepad by typing Notepad Devices.reg in Run dialog box.</li> Replace the text HKEY_CURRENT_USER with HKEY_USERS\.DEFAULT</li> Save the file. Then import it into the registry by double-clicking the file in Windows Explorer.</li> Repeat steps 13 through 15 for PrinterPorts.reg and Windows.reg.</li></ol>

These steps only work for local printers.

To enable IIS to enumerate the network printers by using the SYSTEM account, follow these steps.

Note If the process is running under the Network Service account, explicit permissions to the newly created registry are required. <ol> Make sure that you are currently logged in to the server as a user who has the desired network printers installed.</li> Start Registry Editor.</li> Click the following key:

HKEY_CURRENT_USER\Printers\Connections

</li> On the Registry menu, click Export Registry File.</li> In the File Name box, type c:\printconns.reg .</li> To open the printconns.reg file in Notepad, click Start, click Run, type Notepad printconns.reg in the Open box, and then click OK.</li> <li>Replace the text HKEY_CURRENT_USER with the text HKEY_USERS\.DEFAULT.</li> <li>Save the file.</li> <li>To import the file into the registry, double-click the file in Windows Explorer.</li> <li>Restart the Print Spooler service.</li></ol>

<div class="references_section">