OK, I seem to have uncovered a major issue with Carbonite. At least it's a major issue on my system.
I've been using the Carbonite trial on my notebook PC, which is connected to my desktop PC wirelessly via my home network, for a few days now. At the same time, my desktop PC has suddenly been throwing error messages at me and refusing to respond. (I was really glad for a while that I am getting a new PC built and it will be ready in about two weeks.)
The desktop would stop responding - first, I cannot open any new programs. Then it won't open any new Windows dialogs at all. After a few restarts I would finally get it going, but I could not diagnose the issue.
Event viewer showed the same few errors over and over: all with the event ID 32 or 59. They read as follow:
- Dependent Assembly Microsoft.VC80.MFCLOC could not be found and Last Error was The referenced assembly is not installed on your system.
- Resolve Partial Assembly failed for Microsoft.VC80.MFCLOC. Reference error message: The referenced assembly is not installed on your system.
- Generate Activation Context failed for C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e8e3b_8.0.50727.42 x-ww_dec6ddd2\MFC80U.DLL. Refernce error message: The operation completed successfully.
I researched the errors and found that they refer to RAS and/or PPP problems, but only for Windows Server 2003-based computers with Terminal Server enabled. Which was confusing as I am running XP Pro on both my PC's.
After several iterations of this problem suddenly appearing and then disappearing just as quickly, it finally dawned on me that this was only a problem while my notebook was up and running - and of course connected to Carbonite. As soon as I shut down the notebook, these errors on my desktop PC would immediately resolve.
I can replicate this at will; Start desktop PC, all is well. Start notebook PC, Carbonite starts, and the desktop goes to crap. Shut down the notebook PC, the desktop suddenly is fine. Start the notebook and shut down Carbonite and the desktop first goes nuts, then is cured as soon as Carbonite is shut down.
This drove me crazy... OK, crazIER - because the special hotfixes available from MS are only to be used on a Windows Server 2003-based OS, and I at first was not suspecting a connection on my networked notebook PC to cause such massive issues on my desktop PC!
I haven't notified Carbonite about this yet, but I will right after I post this. More important to let you all know about it first.
Has anyone else run into any such strange problems on a PC that is networked to the PC you are running Carbonite on?