I have ten machines, managed using Site Manager, with agents on each.
They all backup to a Synology NAS.
Everything works except for two machines, which always fail with the following error.
"Image failed on [machine name] Error - Failure: User - No user - The network path was not found. Backup aborted! - None of the specified backup locations could be written to."
The image never really starts. It just sits in the dashboard queue for maybe 30 to 60 seconds and then fails.
Every other machine jumps right into the imaging routine with no such lag or failure.
The credentials are all correct, the paths are correct, the connections are tested and good. So I can't figure out why Macrium can't image these two machines.

At first I thought it might be NetNanny, because that is installed only on these two laptops. I disabled NetNanny and the images still fail.
On those two machines the macrium agent is installed in the admin user account and still fails when I am logged in on those machines as admin and while I have the agent interface open.

I also checked the link below

https://forum.macrium.com/10131/RE-None-of-The-Specified-Backup-Locations-Could-Be-Written-To#10132

And the one it links too, below

https://knowledgebase.macrium.com/display/KNOW/Backup+aborted!+-+None+of+the+specified+backup+locations+could+be+written+to

But those links didn't seem to help. Importantly, the macrium agent works fine on the eight other machines with nothing more than the "Default" entry in the Edit Defaults / Network tab. So it makes no sense that these two problem machines would need anything else in that tab. Something else must be causing this.

Please advise.

All machines, working and non-working, run both of the following services under the local system account:
(1) Macrium Agent Service and
(2) Macrium Service.

There is no local account on any of the machines that bears the same username and password as the shares on the NAS. So none of the ten machines has that kind of implicit access to the Macrium repository (NAS share).

Instead, the repository defined in Macrium (via Site Manager) contains the the information regarding the share, including UNC path, NAS user name and NAS user password.

So I'm still stuck.

+x

 

Cayman - 15 March 2021 3:30 AM

I have ten machines, managed using Site Manager, with agents on each.
They all backup to a Synology NAS.
Everything works except for two machines, which always fail with the following error.
"Image failed on [machine name] Error - Failure: User - No user - The network path was not found. Backup aborted! - None of the specified backup locations could be written to."
The image never really starts. It just sits in the dashboard queue for maybe 30 to 60 seconds and then fails.
Every other machine jumps right into the imaging routine with no such lag or failure.
The credentials are all correct, the paths are correct, the connections are tested and good. So I can't figure out why Macrium can't image these two machines.

At first I thought it might be NetNanny, because that is installed only on these two laptops. I disabled NetNanny and the images still fail.
On those two machines the macrium agent is installed in the admin user account and still fails when I am logged in on those machines as admin and while I have the agent interface open.

I also checked the link below

https://forum.macrium.com/10131/RE-None-of-The-Specified-Backup-Locations-Could-Be-Written-To#10132

And the one it links too, below

https://knowledgebase.macrium.com/display/KNOW/Backup+aborted!+-+None+of+the+specified+backup+locations+could+be+written+to

But those links didn't seem to help. Importantly, the macrium agent works fine on the eight other machines with nothing more than the "Default" entry in the Edit Defaults / Network tab. So it makes no sense that these two problem machines would need anything else in that tab. Something else must be causing this.

Please advise.

All machines, working and non-working, run both of the following services under the local system account:
(1) Macrium Agent Service and
(2) Macrium Service.

There is no local account on any of the machines that bears the same username and password as the shares on the NAS. So none of the ten machines has that kind of implicit access to the Macrium repository (NAS share).

Instead, the repository defined in Macrium (via Site Manager) contains the the information regarding the share, including UNC path, NAS user name and NAS user password.

So I'm still stuck.

Hi,

Firstly, I would advise getting in touch with our support team by opening a ticket at https://macrium.com/support - they should be able to help with collecting appropriate data and suggesting fixes. 

In general, there are some issues that crop up with repository access cases - some of these definitely don't apply to your case, but I'll include them for completeness:
 - The Site Manager agent creates it's own logs on the target computer - ProgramData\Macrium\SiteManager\agentNetwork.log and agentProcess.log will have some additional error codes with Win32 errors which may help diagnose the issue
 - Including a domain with the repository credentials: in Site Manager, you can specify a domain with the repository, in general you should always do this as without it, Windows can get authentication wrong. For example, if you specify "username", the repository connection may fail on a Windows installation that has a local (or domain) account named "username". If you are using a NAS, usually the NetBIOS or IP address of the NAS will work.
 - DNS lookup: There may be some issues with looking up DNS names on all Agent computers, especially with a mix of domain and non-domain computers. If you're using "\\NAS\Share", try "\\nas.fqdn.local\Share" or IP address. (We're adding some features to Site Manager 8 to improve this, by sending the resolved IPs down from server to agent)
- SMB versions - some NASes will disable SMB1 access which older OSes like XP require

One technique I have used in development is to use SysInternals 'psexec' tool to run a command line as SYSTEM on an affected system and try the "net use" commands to establish a connection to the repository - this often recreates any errors shown in the logs.

Kind Regards,

Alex

Macrium Development

See our reviews on