cgtyoder Posted September 7, 2006 Report Share Posted September 7, 2006 Duing a proactive backup of a laptop, I have gotten this twice in two days, from the logfile: T-29: MapError: unknown Windows error -2,147,217,406 T-29: W2dbWMIDbOp: pWMIRep->BackupREGDB failed, winerr -2147217406, error -1001 Can't back up WMI Repository, error 63184916 (unknown) I have searched for info on this, and can't come up with anything. Can anyone shed some light here? Using Retrospect Single Server 7.0.344, update v 7.0.12.105. -Conrad Link to comment Share on other sites More sharing options...
RonaldL Posted September 7, 2006 Report Share Posted September 7, 2006 It sounds like there's something wrong with the WMI Repository. You may want to run Microsoft's diagnosis tool to see if it can fix the problem or just rebuild it altogether. http://windowsxp.mvps.org/repairwmi.htm Link to comment Share on other sites More sharing options...
Horb Posted February 25, 2008 Report Share Posted February 25, 2008 Using Retropsect 7.5.508 with server update and hot fix of 7.15.13.100. I am getting WMI errors on the only XP PRO SP2 machines that I back up since the last update. All of my Server 2003 boxes, and Linux boxes are fine. "Can't back up WMI Repository, error 45916576: is the error for one machine "Can't back up WMI Repository, error -1101" is the error for the second. I have ran the WMI diagnosis utility provided by microsoft and came back with no errors. Tried the backups and continued to get WMI errors. I then tried the command lines referenced in the above articles to rebuild and then attempted another save and received the same errors. Both machines are fully updated with the most recent applicable Microsoft updates as of this date. Any suggestions would be appreciated. Link to comment Share on other sites More sharing options...
Mayoff Posted February 25, 2008 Report Share Posted February 25, 2008 What happens if you forget the XP Client and add it again to the client database? Link to comment Share on other sites More sharing options...
Horb Posted February 25, 2008 Report Share Posted February 25, 2008 Ok I forgot the client and added it back to the database. I still get WMI errors: Can't back up WMI Repository, error 51224992 Thank you for the response. Link to comment Share on other sites More sharing options...
Mayoff Posted February 25, 2008 Report Share Posted February 25, 2008 What is reported in the Windows Event log of the XP client when this failure happens? Link to comment Share on other sites More sharing options...
Horb Posted February 25, 2008 Report Share Posted February 25, 2008 The only thing I see on the XP client logs relative to WMI is the following warning: A provider, HiPerfCooker_v1, has been registered in the WMI namespace, Root\WMI, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests It occurs on both machines. I was reading about it around the net and tried the FIXWMI.cmd file found here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=193534&SiteID=1 Reboot both machines and attempted the save again and received: Can't back up WMI Repository, error 35365280 Link to comment Share on other sites More sharing options...
chadh Posted February 25, 2008 Report Share Posted February 25, 2008 I too am having the same problem with all of my XP clients. Script: Dell Client: DELL Date: 2/23/2008 Can't Backup WMI Repository, error 202219916 (Unknown) Running the latest patch for 7.5 on a Windows SBS server and latest Client on the XP sp2 systems. I've seen this error on multiple clients. The error number is different each time. Link to comment Share on other sites More sharing options...
IT Guy Posted February 29, 2008 Report Share Posted February 29, 2008 Hi There, I am also receiving the same error message. See Below Can't back up WMI Repository, error 27697548 (unknown) I am receiving this across all XP clients. This has only started since I installed the latest patch 7.5.5.508. Is there anyway of rolling back this update, if not when will there be a update to resolve this problem. I have also checked the Repository's on 2 machines and they were fine. Thanks in Advance Link to comment Share on other sites More sharing options...
Mayoff Posted February 29, 2008 Report Share Posted February 29, 2008 Our engineers have confirmed a bug in the 7.5.508 code that is causing the WMI errors for users. We will make a bug fix for this soon, along with fixes for a few other bugs introduced in .508 I also created a new KB document to help users troubleshoot general WMI errors: http://kb.dantz.com/article.asp?article=9647&p=2 Link to comment Share on other sites More sharing options...
IT Guy Posted February 29, 2008 Report Share Posted February 29, 2008 Hi Mayoff, Thanks for the quick responce Link to comment Share on other sites More sharing options...
jwright Posted March 1, 2008 Report Share Posted March 1, 2008 I am having the problem on all of my XP clients. I just downloaded the release and applied it around noon today. Pretty lame that EMC didn't pull the download before 8 am, since they seemed to be aware of the bug. Can the previous release of retrospect be posted for download so that I can reinstall? When can we expect a fix? Jeff Link to comment Share on other sites More sharing options...
Mayoff Posted March 1, 2008 Report Share Posted March 1, 2008 http://download.dantz.com/archives/Retro-EN_7_5_387.exe Link to comment Share on other sites More sharing options...
jwright Posted March 1, 2008 Report Share Posted March 1, 2008 Mayoff: Thanks for the link! I will reinstall today. Besides the error, what is the real impact of the problem? I mean, any idea how it impacts our ability to restore a system or file? Thanks again. Jeff Link to comment Share on other sites More sharing options...
Mayoff Posted March 1, 2008 Report Share Posted March 1, 2008 WMI Repository is a strange beast. If you google WMI repository you find what seems like 100's of link about how to back it up, how to restore it and how to fix it. Seems like it is easy to break. Not everyone uses it. Details can be found at http://www.microsoft.com/technet/scriptcenter/resources/wmifaq.mspx Link to comment Share on other sites More sharing options...
matsr Posted March 11, 2008 Report Share Posted March 11, 2008 How about the question from Jeff above, does the bug impacts our ability to restore? It affects all my xp clients and I'm not to eager to reinstall. Mats Link to comment Share on other sites More sharing options...
Mayoff Posted March 11, 2008 Report Share Posted March 11, 2008 Probably won't, but you have to check with Microsoft on that. I am no WMI expert. We will have a bug fix available very soon for this issue. Link to comment Share on other sites More sharing options...
jwright Posted March 13, 2008 Report Share Posted March 13, 2008 "Our engineers have confirmed a bug in the 7.5.508 code that is causing the WMI errors for users. We will make a bug fix for this soon, along with fixes for a few other bugs introduced in .508" Any word on a fix? BTW, what is the stance you guys are taking on this one? It sure sounds like you are saying that we are on our own to deal with the WMI issues. Since the WMI issue first occured the day that I installed .508, it can only mean one of two things: 1. The .508 install is reporting something that was already there, and retrospect was just not reporting before. OR 2. The .508 install caused the issue. Can you guys clarify? Last question, we have full warranty support, so should I go that route to get the fix, or will it be made available to all? Thanks, Jeff Link to comment Share on other sites More sharing options...
Mayoff Posted March 13, 2008 Report Share Posted March 13, 2008 what is the stance you guys are taking on this one? We will make a bug fix for this soon, along with fixes for a few other bugs introduced in .508. If you need an immediate solution, you can downgrade Retrospect to the .387 version. Users only need .508 if you are doing a backup of Exchange 2007 servers. Link to comment Share on other sites More sharing options...
Mayoff Posted March 17, 2008 Report Share Posted March 17, 2008 The bug fix for the WMI repository issue is found in our latest beta version: at http://download.dantz.com/archives/beta/Retro_EN_7_5_512.exe If the error continues, please let us know. Link to comment Share on other sites More sharing options...
Fulco Posted March 18, 2008 Report Share Posted March 18, 2008 How do I Downgrade (508->387)? The installer stops if there is a newer version already installed. Fulco Link to comment Share on other sites More sharing options...
Mayoff Posted March 18, 2008 Report Share Posted March 18, 2008 You may want to try and uninstall first from add and remove programs. If you are on Vista (I have no idea), then uninstall is a requirement. Link to comment Share on other sites More sharing options...
cgtyoder Posted March 29, 2008 Author Report Share Posted March 29, 2008 Any word on when 7.5.521 will go GM? Link to comment Share on other sites More sharing options...
Mayoff Posted March 30, 2008 Report Share Posted March 30, 2008 I don't know 7.5.521 has never existed, so it may be a very long time. Do you mean 7.5.512 beta? No date yet. It is still beta. Link to comment Share on other sites More sharing options...
helpdesk Posted April 2, 2008 Report Share Posted April 2, 2008 Date: 4/2/2008 Can't back up WMI Repository, error 34578848 (unknown) I have been getting this error daily on all my machines since the upgrade. It looks like a new upgrade is being released today. I will report back if that fixed the error. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.