RE: WMI Error
- From: v-shshao@xxxxxxxxxxxxxxxxxxxx ("Shawn Shao [MSFT]")
- Date: Tue, 29 Jan 2008 10:57:43 GMT
Hi Barry,
Thank you for posting here!
From your post, I understand that WMI error message was encountered, the following message was also found in the eventviewer:
"Faulting application wmiprvse.exe, version 5.2.3790.3959, faulting module ntdll.dll, version 5.2.3790.3959, fault address
0x0001a379"
I also understand that some errors was received when using Symantec Backup Exec. If I am off base, please feel free to let
me know.
Please understand that as Backup Exec is a third party application, we are not sure how it works. Based on current
situation, we cannot conclude whether it is related to the WMI issue. To avoid confusion, let's focus on the WMI error first.
Before we go any further, I would like to confirm whether you have Windows Server 2003 SP2 installed. There is an hotfix for
the WMI issue, you can refer to the following article for more information.
The Wmiprvse.exe process stops unexpectedly, and event ID 1000 is logged in the Application log in Windows Server
2003
http://support.microsoft.com/kb/914831/en-us
Note: This hotfix has been included in Windows 2003 SP2. If you already have SP2 installed, that's no need to reapply this
hotfix. Let's continue with the remaining suggestions:
Suggestion 1: Clean Boot
============
Let's disable all startup items and third party services when booting. This method will help us determine if this issue is
caused by a loading program or service. Please perform the following steps:
1. Click Start, go to Run, and type "msconfig" in the open box to start the System Configuration Utility.
2. Click the Services tab, check the "Hide All Microsoft Services" box and click Disable All.
3. Click the Startup tab, click Disable All and click OK.
Then, restart your computer. When the "System Configuration Utility" window appears, please check the "Don't show this
message or launch the System Configuration Utility when Windows starts" box and click OK.
4. Please check this issue again.
Note: Temporarily disabling the Startup Group only prevents the startup programs from loading at startup. This shouldn't
affect the system or other programs. We may still manually run these programs later.
Suggestion 2: This issue can also be caused by some the third party print processors and print monitors. We can perform
the following steps to clear them from the system
================
Note: Please backup the following registry branch first:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print***
1. Start Registry Editor.
2. Locate the Local Port value under the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Local Port
3. Double-click the Driver subkey, and then edit the value. Change the string value to Localspl.dll, and then click OK.
4. Check the following registry key for third-party monitors. Remove any non-default monitors:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors
The default port monitors are:
AppleTalk Printing Devices (When Services for Macintosh is installed)
BJ Language Monitor
Local Port
PJL Language Monitor
Standard TCP/IP Port
USB Monitor
Microsoft Shared Fax Monitor
** LPR Port
NOTE: Do not remove LPR Port Monitor unless advised by a Microsoft Support Professional.
5. Check the following registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-3
- Remove any non-default print monitors from each key.
- For each driver look for Monitor Entry on the right pane.
- If there is non-default print monitor, delete the VALUE DATA not the VALUE i.e. Monitor Entry.
Change the third-party print processor to WinPrint. To do so, follow the steps below:
----------------------
6. Click Start, point to Settings, and then click Control Panel.
7. Double-click Printers, right-click the printer, and then click Properties.
8. On the Advanced tab, click Print Processor.
9. In the Print Processor box, click WinPrint.
10. Click OK two times.
Alternative Way to Set the Print Processor to WinPrint for all the printers: CMD > wmic printer set PrintProcessor = WinPrint
(ONLY APPLIES TO WINDOWS SERVER 2003)
11. Check the following registry key for third-party print processors. Remove any non-default print processors:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Print Processors
The default print processor is: WinPrint
To find out what printer is using the print processor, run the Microsoft Product Support Reporting Tool (MPS_REPORTS)
tool and open MachineName_PRINTDRIVERS.TXT, and then search for the third-party print processor and for the queues
that are using the print processor.
Support Reporting tool from the link below:
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_SETUPPerf.EXE
After you edit the registry, restart the print spooler. To do so, start Services.msc. Right-click Print Spooler Service, and click
Stop, right click the service again and then choose Start.
After that, please check if the WMI issue persists or not. If the issue still occurs, please use help me collect a MPS report
with the tool mentioned above:
1. Double-click on the MPSRPT_SETUPPerf.EXE file. [Note] This process may take some time; however, it will not have a
negative effect on the performance.
2. A CAB file will be generated in the %systemroot%\MPSReports\Setup\Reports\Cab directory called%
COMPUTERNAME%_MPSReports.CAB. The CAB file will contain the reports generated by the MPS Reporting Tool.
You can zip these log files and send them as attachments to my mailbox v-shshao@xxxxxxxxxxxxx
If anything is unclear or there are any questions about the steps, please do not hesitate to let me know. I will be glad to
help.
Best regards,
Shawn Shao
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better
post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. You can locate the
newsgroup here: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the "Notify me of replies" box to receive e-
mail notifications when there are any updates in your thread. When responding to posts via your newsreader, please
"Reply to Group" so that others may learn and benefit from your issue.
Microsoft engineers can only focus on one issue per thread. Although we provide other information for your reference, we
recommend you post different incidents in different threads to keep the thread clean. In doing so, it will ensure your issues
are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional
support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Prev by Date: Re: Cannot connect client pc to WSUS
- Next by Date: Re: Exchange filtering mails by subject
- Previous by thread: Re: Exchange filtering mails by subject
- Next by thread: Addng New Email address / Domain
- Index(es):
Relevant Pages
|
Loading
