Now you know how to fix error e000fe30 - A communications failure has occurred in Backup Exec.“After the upgrading of Windows 10 version 1803, my system image backup keeps failing with the error message: 'The backup failed. If that doesn't help, light up support and move on with your day with more of a smile than a frown. In other words, Symantec has had some success with splitting the backups into two jobs, one for files and one for the Exchange Server. If you are backing up Exchange Server as part of a file backup job, one possible work-around is to separate those two resources. Work-Arounds for E000FE30 - A communications failure has occurred in Backup Exec. I'm happy to report that after loading the replacement Bedsmbox.dll, the backups complete successfully. However, the odds are that they will hook you up with the hotfix for Bedsmbox.dll required to solve your headaches. If your backup or restore jobs are crashing with "0xe000fe30 - A communications failure has occurred" in your Backup Exec logsġ - Follow the link given in the logs to verify those items (DCOM permissions, etc).Ģ - Call support. (Understood, it's an Alpha, Beta or whatever you want to call it, I just need a backup at this point.) They cautioned me repeatedly that it wasn't supported and I could lose my backup job definitions, etc. They simply told me dev would send me an email with the unsupported hot fix. Then, they mentioned it's a known issue and it was taking such a long time because they had to gather details for a hotfix for the Bedsmbox.dll file.Īdvanced Tech called back after about an hour and a half and acted as a go-between, communicating first with me, then silently (from my perspecitve) with development. Support spent a couple hours gathering information, running backup jobs (that of course failed), double-checking the most basic of things. This particular client has been having backup troubles on an old server for a while, so we're working without a net here on the new one. Tiring of the frustration, I did open a support incident after repeatedly bashing my head into a brick wall with protruding glass shards. OK folks, let's wrap up this dog and pony show. Nothing I've found fixed the problem of the pesky "E000FE30 - A communications failure has occurred" error. Time to search! The Internet is a wealth of knowledge (and stupidity of course), but I've gone though more than 1,000 results with no luck. I did all those things and still no good, nothing but e000fe30 - A communications failure has occurred.
The technote discusses running LiveUpdate, checking to make sure nothing is blocking TCP Port 10000 on the media server and remote machine and DCOM permissions as well as a few other (for my situation) far-fetched ideas. 0, time stamp 0x4b184ba1, faulting module bedsmbox.dll, version. "Faulting application beremote.exe, version. The service was indeed stopped, and the event logs showed Event ID 1000 from Source Application Error. Off to the event viewer and services applet.
I tried it anyway and was pointed to the Backup Exec Remote Agent for Windows Servers (RAWS) crashing.
But, it had a different problem description. The closest option had the same basic error message of V-79-57344-65072 - The connection to target system has been lost. That link gave about 7 specific situations, unfortunately none of which exactly applied to my situation. So, not to be outdone, I dutifully clicked on the link that Backup Exec provided for V-79-57344-65072. Backup set canceled.įor additional information regarding this error refer to link V-79-57344-65072. V-79-57344-65072 - The connection to target system has been lost. The backup job had crashed and the logs really left me without much - they only showed the following: Digging into the Backup Exec logs didn't help much.