TSM Backup Client for Windows (v6.1.4) - 'WMI Writer' do(es) not exist

Anyone have an idea how to fix this?

dsmerror.log = 03/04/2011 12:05:17 ANS1705E System Writer(s) 'system writer' 'WMI Writer'  do(es) not exist.

Here is a list of writers. Am I missing something here?

C:\Users\conder.mike>vssadmin List Writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {e4ebeef4-0d9d-42fd-9395-fb1619a92a17}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {1aab3bfe-4ab8-458d-9f5d-c6c2330f2a3e}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {cfbe5d58-e2c7-4d00-bcd0-e68683064286}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {672c1228-92c1-49e4-9644-6d0254298791}
   State: [1] Stable
   Last error: No error
mconderAsked:
Who is Participating?
 
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
I assume you got to your current point from here:
http://www-01.ibm.com/support/docview.wss?uid=swg1IC67101

Looking here:
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/764791ff-ecb5-4716-9f1c-9e22852e0f6b

It would appear that 'sfc /scannow' is the suggestion on fixing possibly corrupted files...  In the case presented, the Windows 2008 lacked the necessary permissions on a critical directory.
0
 
mconderAuthor Commented:
I forgot. Windows 2008 Enterprise R2 64-bit
0
 
mconderAuthor Commented:
It does look like I am missing some of the writers. Any idea how to get them back?
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
mconderAuthor Commented:
I have a case open with MS on this. I will post the solution once we have determined root cause.
0
 
mconderAuthor Commented:
So, we were able to get the system writer back by following http://support.microsoft.com/kb/2009272. This was listed in the thread referenced above by Razmus, but still the WMI writer does not show up and TSM definitely seems to want it on this server. Interestingly, we have other 2008 servers backing up with TSM where the WMI writer does not show up, but they work just fine. I'm wondering under what circumstances the WMI writer is called for. The server in question here is clustered. I'm wondering if WMI us a requirement of the cluster config...?
0
 
mconderAuthor Commented:
OK, so after getting the system writer to show up with http://support.microsoft.com/kb/2009272, all that was needed is a restart of the WMI service and that fixed the issue completely.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.