Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 SP2 installed.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
Registry information
After you apply this hotfix, you must enable the hotfix. To have us enable the hotfix for you, go to the "
Fix it for me" section. If you would rather enable the hotfix yourself, go to the "
Let me fix it myself" section.
Fix it for me
To enable the hotfix automatically, click the
Fix this problem link. Then click
Run in the
File Download dialog box, and follow the steps in this wizard.
Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.
Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.
Now go to the "
Did this fix the problem?" section.
Let me fix it myself
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To enable the hotfix, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print
- On the Edit menu, point to New, and then click DWORD Value.
- Type SNMPLegacy, and then press ENTER.
- Right-click SNMPLegacy, and then click Modify.
- In the Value data box, type 1, and then click OK.
Note This hotfix does not work if the SNMPLegacy registry entry is set to 0. If this registry entry is set to 1, the print queue status is displayed as "Ready" instead of as "Offline" when a printer device does not respond to SNMP commands. - Exit Registry Editor.
Now go to the "
Did this fix the problem?" section.
Did this fix the problem?
Restart the Print Spooler service and check whether the problem is fixed. If the problem is fixed, you are finished with this article. If the problem is not fixed, you can
contact support.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the
Time Zone tab in the
Date and Time item in Control Panel.
Windows Server 2003 with Service Pack 1, x86-based versions
File name | File version | File size | Date | Time | Platform |
---|
Tcpmib.dll | 5.2.3790.3064 | 17,920 | 24-Dec-2007 | 14:50 | x86 |
Windows Server 2003 with Service Pack 2, x86-based versions
File name | File version | File size | Date | Time | Platform |
---|
Tcpmib.dll | 5.2.3790.4211 | 18,432 | 24-Dec-2007 | 15:06 | x86 |
Windows Server 2003 with Service Pack 1, Itanium-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|
Tcpmib.dll | 5.2.3790.3064 | 48,128 | 24-Dec-2007 | 13:34 | IA-64 | SP1 | Not Applicable |
Wtcpmib.dll | 5.2.3790.3064 | 17,920 | 24-Dec-2007 | 13:34 | x86 | SP1 | WOW |
Windows Server 2003 with Service Pack 2, Itanium-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|
Tcpmib.dll | 5.2.3790.4211 | 49,152 | 24-Dec-2007 | 13:35 | IA-64 | SP2 | Not Applicable |
Wtcpmib.dll | 5.2.3790.4211 | 18,432 | 24-Dec-2007 | 13:35 | x86 | SP2 | WOW |
Windows Server 2003, x64-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|
Tcpmib.dll | 5.2.3790.3064 | 25,600 | 24-Dec-2007 | 13:34 | x64 | SP1 | Not Applicable |
Wtcpmib.dll | 5.2.3790.3064 | 17,920 | 24-Dec-2007 | 13:34 | x86 | SP1 | WOW |
Windows Server 2003 with Service Pack 2, x64-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|
Tcpmib.dll | 5.2.3790.4211 | 26,112 | 24-Dec-2007 | 13:42 | x64 | SP2 | Not Applicable |
Wtcpmib.dll | 5.2.3790.4211 | 18,432 | 24-Dec-2007 | 13:42 | x86 | SP2 | WOW |