Mozy documentation is also available in:
| Members | Liked |
|---|---|
| username_issues | 2428 |
| Owyn | 613 |
| Wayward | 200 |
| Invisiblade | 151 |
| KCj | 142 |
When attempting to install MozyPro client on SBS 2003 Server running Windows server 2003 I get the following error.
"MozyProshell.dll failed to register". I have installed all updates and patches to the server with no success. any ideas?
Solved! Go to Solution.
06-20-2012 08:32 AM
We seem to have a fix for this now. It seems that Mozy is advancing and needing more updated files on the machine to
operate properly with 2.14.x.x.
For your consideration; the Microsoft KB article:
http://support.microsoft.com/kb/2538243
The 32 bit fix:
http://download.microsoft.com/download/5/D/8/5D8C65CB-C849-4025-8E95-C3966CAFD8AE/vcredist_x86.exe
The 64 bit fix:
http://download.microsoft.com/download/2/d/6/2d61c766-107b-409d-8fba-c39e61ca08e8/vcredist_x64.exe
So far, this seems to be working on any and all machines that are experiencing this issue, however, any
feedback positive and otherwise would be appreciated in the forum.
Tech :-)
06-20-2012 11:51 AM
And it worked on this one too. All is well, Thanks
06-20-2012 12:35 PM
OK, you asked for feedback postive "and otherwise". The good news is "it worked". The bad news is this was a disaster for me. Please see my own thread here:
I have found the management of this issue to be sloppy. Sloppy in terms of the casual nature of your own post, sloppy in terms of the roll-out of a new version ("seems to need new software", "Mozy is advancing...") that breaks backups, sloppy in terms of having to discover all this for myself. But worst of all -- the re-install broke my existing backup, so I'm "naked" without a cloud backup for a day or two while the replacement upload happens. Please see my thread for more excoriation. Overall, you get an "F" - for "failure". Why? Because the single most important attribute of the Mozy service that should distinguish Mozy from other online backup cloud services -- all of which offer basic functionality -- is "reliability". When you break reliability, you break the single most important feature for which people buy Mozy. Now you have to work to regain trust. An online backup company does not want to be in the place of losing online trust. I suspect that this may end up being more important than you realize. As they say "honour can only be lost once . . . ."
06-24-2012 08:14 AM
The suggestion that anyone wants to read a MS KB article is ludicrous. Are you marketing or product management people paying attention? Seriously! Mozy is supposed to be something that individuals and families can use. I realize you have a big SMB market too. But none of the until now Mozy customers are the slightest bit interested in reading a MS KB article which "may" be relevant. Where was the testing in the lab with a couple of dozen test images to see what breaks? Did no one do testing to see what breaks????
06-24-2012 08:17 AM
JHMX wrote:.........Where was the testing in the lab with a couple of dozen test images to see what breaks? Did no one do testing to see what breaks????
The testing was done - maybe if you understood how/why the need for this patch was not discovered during that testing you would be a bit less upset - or maybe not :-)
The virtual machines used by Mozy's staff to test the new version probably had .NET 3.5 installed. That install includes the C++ update that is mentioned above. So they simply did not see the error that I first reported in this post:
http://community.mozy.com/t5/Mozy-for-Windows/Wind
In hindsight - I probably should have pushed them more to find the root cause before it hit the few customers that it did.
My guess is (because this issue) Mozy will do future testing with VMs that are not patched at all or only have non-optional patches installed.
06-24-2012 11:48 AM
If that is where the solution is... Yes
06-24-2012 02:58 PM