Multiple users cannot print from 32-bit applications on a 64-bit operating system by using the "runas" command (923357)
The information in this article applies to:
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows XP Professional 64-Bit Edition (Itanium) 2003
- Windows Vista Business
- Windows Vista Enterprise
- Windows Vista Home Basic
- Windows Vista Home Premium
- Windows Vista Starter
- Windows Vista Ultimate
Beta InformationThis article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.
No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location where you downloaded the release.Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows registry SYMPTOMSYou cannot use the runas command with different user accounts to print from 32-bit applications on a same computer that has the 64-bit Microsoft Windows operating system installed.CAUSEThis problem occurs because the system uses the Splwow64.exe process to translate between 32-bit applications and the driver model of the 64-bit operating system. When the Splwow64.exe process has completed, this process remains in memory for a specified time-out period to increase system performance. When you use the runas command to start the 32-bit application, the Splwow64.exe process is only available to the first user until the time-out expires. The time-out value is set by using a registry entry.WORKAROUNDTo work around this problem, use either of the following methods. Method 1Avoid using the runas command to print. Method 2Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. Follow these steps to change the registry entry that controls the time-out value: - Click Start, click Run, type regedit, and then click OK.
- Locate and then right-click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print - Point to New, and then click DWORD Value.
- Type SplWOW64TimeOut for the registry entry name, and then press Enter.
- Double-click the SplWOW64TimeOut entry that you created in step 4.
- Enter a value in the Value Data box.
Note The value that you enter in the Value Data box is the number of minutes that the system will wait until it unloads the Splwow64.exe process. For the time-out to expire more frequently, you can specify a small value. For example, you can enter 1 to indicate that the system will wait one minute before it unloads the Splwow64.exe process. - Click OK.
STATUS
This behavior is by design.
Modification Type: | Major | Last Reviewed: | 8/14/2006 |
---|
Keywords: | kbtshoot kbprb KB923357 kbAudITPRO |
---|
|