Standalone backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)
frankive
Service Provider
Posts: 877
Liked: 102 times
Joined: May 14, 2013 8:35 pm
Full Name: Frank Iversen
Location: Norway
Contact:

Error: Shared memory connection was closed

Post by frankive » Apr 15, 2015 1:38 pm

I have a SBS 2011 server I want to protect. Trying Veeam Endpoint Backup. Backing up to a usb-drive connected mapped to B:
The 10 other servers I have tested all work fine!

The error messiage I get is:

4/15/2015 3:25:42 PM :: Error: Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: The system cannot find the file specified. Failed to write data to the file [B:\VeeamBackup\Backup Job DC01\Backup Job DC012015-04-15T151952.vbk]. Failed to download disk.

I can confirm the b: (usb-drive) is online and works fine.

Dima P.
Product Manager
Posts: 9911
Liked: 789 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Error: Shared memory connection was closed

Post by Dima P. » Apr 15, 2015 1:43 pm

Hello Frank,
For an issue like this application logs are required for troubleshooting. Could you, please, open a support case thru the Veeam Endpoint Backup Control Panel > Support? Thank you in advance.

frankive
Service Provider
Posts: 877
Liked: 102 times
Joined: May 14, 2013 8:35 pm
Full Name: Frank Iversen
Location: Norway
Contact:

Re: Error: Shared memory connection was closed

Post by frankive » Apr 15, 2015 1:53 pm

Thanks. Opened a case. Looking forward to see what might cause this.

Dima P.
Product Manager
Posts: 9911
Liked: 789 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Error: Shared memory connection was closed

Post by Dima P. » Apr 15, 2015 2:29 pm

Frank,
Thanks. The error refers to the mechanism used for components to “talk” with each other. Might be a memory overrun, but, honestly, I am just guessing now. Let’s wait for support and QA investigation.

marius roma
Expert
Posts: 432
Liked: 3 times
Joined: Feb 01, 2012 12:04 pm
Full Name: Mario
Contact:

Re: Error: Shared memory connection was closed

Post by marius roma » May 05, 2015 8:38 pm

Maybe my experience can be of any help.
Aftare replacing the USB wireless network adapter on a Windows 8.1 64bit PC I started getting the following error, similar but not identical to yours:
04/05/2015 20.05.45 :: Error: Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Periodo di timeout del semaforo scaduto. Error code: 121 Failed to write data to the file [G:\VeeamBackup\Backup Job PCNAME\Backup Job PCNAME2015-05-04T195527.vbk]. Failed to download disk. (The semaphore timeout period has expired)..
I made several tests including removing and reinstalling VEB before deciding to remove the new USB wireless adapter.
At that point VEB started working again.
I presume the USB wireless network adapter is damaged because the brand and the model look to be the same as athe previous USB wireless network adapter and because the same device failed working on a Linux box (that's the reason because I swapped it with the working one).
Hope this helps...
Marius

Dima P.
Product Manager
Posts: 9911
Liked: 789 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Error: Shared memory connection was closed

Post by Dima P. » May 05, 2015 10:16 pm

Hello Mario,
Thanks for the heads up, but please next time do not forget to create a support case thru Veeam Endpoint Backup Control Panel. We offer free support at best effort and submitting issues will help us to improve the quality of the product :wink:

frankive
Service Provider
Posts: 877
Liked: 102 times
Joined: May 14, 2013 8:35 pm
Full Name: Frank Iversen
Location: Norway
Contact:

Re: Error: Shared memory connection was closed

Post by frankive » May 18, 2015 7:58 pm 2 people like this post

my issue was a bad hard drive. after placing the usbdrive the job went through.

Vitaliy S.
Product Manager
Posts: 22431
Liked: 1442 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Error: Shared memory connection was closed

Post by Vitaliy S. » May 18, 2015 8:21 pm

Thanks for coming back and updating the topic!

marius roma
Expert
Posts: 432
Liked: 3 times
Joined: Feb 01, 2012 12:04 pm
Full Name: Mario
Contact:

[MERGED]Problems after upgrading to Windows 10 (maybe)

Post by marius roma » Nov 23, 2015 6:23 am

After upgrading from Windows 8.1 to Windows 10 and formatting the target USB drive I was unable to complete any backup job.
The errors I get include:

Code: Select all

22/11/2015 22.33.35 :: Preparing for backup 
22/11/2015 22.35.22 :: Creating VSS snapshot 
22/11/2015 22.40.04 :: Unable to exclude files from snapshot: Shadow Copy Optimization Writer timed out (see Windows event log for more info). 
22/11/2015 22.40.13 :: Calculating digests 
(...)
23/11/2015 5.00.40 :: Failed to backup [<filename>] 
23/11/2015 5.00.55 :: Finalizing 
23/11/2015 5.01.34 :: Error: Shared memory connection was closed. Agent failed to process method {FileBackup.SyncDirs}. Exception from server: Failed to decompress LZ4 block: Bad crc (original crc: 18180b2f, current crc: 59bd69bf).  
                   :: Processing finished with errors at 23/11/2015 5.01.45 
I had a very similar error the night before, with the process closing while processing a different file of the same disk.
I executed chkdsk /f /r on the disk containing the file <filename> with no error reported.
Is the problem related to the installed program (should I reinstall it?), to the source drive, to the target or to what else?
Regards
marius

Mike Resseler
Product Manager
Posts: 5595
Liked: 584 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

[MERGED]Re: Problems after upgrading to Windows 10 (maybe)

Post by Mike Resseler » Nov 23, 2015 6:47 am 1 person likes this post

What version were you running at the moment you upgrades to windows 10? Was that a supported version already? Just to verify and to be sure you aren't running v1 which doesn't work in Windows 10.

From what I can see in the snippet, it looks like there is a problem with the vss. And after that, I see an issue with a crc... If you have a supported version, please log a support case through the control panel, our support guys will need more info to figure out what and where it went wrong

Thanks

Mike

Dima P.
Product Manager
Posts: 9911
Liked: 789 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Error: Shared memory connection was closed

Post by Dima P. » Nov 23, 2015 5:03 pm

Hey guys,

Test your source disk (and target repository as well) for bad blocks with any 3rd party tool (for example http://hddscan.com/) - check disk might be not that accurate to be honest.

marius roma
Expert
Posts: 432
Liked: 3 times
Joined: Feb 01, 2012 12:04 pm
Full Name: Mario
Contact:

Re: Error: Shared memory connection was closed

Post by marius roma » Nov 30, 2015 9:18 am 1 person likes this post

I made some further investigation and it looks like there was a problem with the USB ports on the PC and/or the drivers used to manage the USB disk.
I reinstalled the drivers and created a new job to copy only part of the source files and it run successfully.
I changed the settings to extend the data backed up by the job and it worked fine again.
Now it looks to work fine.
Thank you for your support.
Marius

Rageboom
Novice
Posts: 3
Liked: 1 time
Joined: Mar 02, 2016 3:45 pm
Contact:

[MERGED]Veeam Endpoint on B&R repository

Post by Rageboom » Mar 02, 2016 3:58 pm

Hi everyone,

I have a problem with a VEP backup onto a Backup & Replication repository.
I can configure my backup, but it always fails with the following message:

"02/03/2016 16:51:05 :: Error: Shared memory connection was closed. Agent failed to process method {FileBackup.SyncDirs}. Exception from server: There are no connections in the specified pool 3. "

My permissions are fine on my Backup&Replication repository.

Here are the versions of my software:
Veeam Endpoint: 1.1.2.119
Veeam Backup & Repository : 8.0.0.2084

Do you have any ideas?

Thanks!

JaxIsland7575
Veeam Vanguard
Posts: 385
Liked: 104 times
Joined: Apr 27, 2015 1:59 pm
Full Name: Ryan Jacksland
Location: NY, USA
Contact:

[MERGED]Re: Veeam Endpoint on B&R repository

Post by JaxIsland7575 » Mar 02, 2016 8:48 pm 1 person likes this post

Welcome Rageboom to the forums!

There is another thread relating to your issue over here

You may want to try and check the drivers or run a scan on the hard drive but the first thing I would suggest is going into the Control Panel of Veeam and submitting a case so they can review the log files of the backups.

Please post your case ID back here when you have it.

Cheers!
VMCE v9

Rageboom
Novice
Posts: 3
Liked: 1 time
Joined: Mar 02, 2016 3:45 pm
Contact:

[MERGED]Re: Veeam Endpoint on B&R repository

Post by Rageboom » Mar 03, 2016 8:17 am

Hi.

I saw this thread but didn't found any solutions, that's why I opened a new thread :).

I opened a case from my VEP, here is the ID : 01716163.

Cheers.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 12 guests