sudden backup failure

tscrrenshoot error message

Hello Wolfgang, the error message looks to suggest an authority issue here, 'the user name or password is incorrect' - have any user credentials on either the NAS or the PC hosting the USB drive changed recently?

Is the path \\192.168.8.6 referring to the NAS or to the PC, as that seems to correspond with where the authority issue is being reported for?

Try using the new Service Log Viewer tool that one of our MVPs has provided to check if there are any other error messages being given in the Acronis backup task where these error messages are being given?  
Note: there is both an installable and a standalone version of the log viewer tool that can be used.

Hello Steve,thank you for your answer. I know the problem, but why? The job run 2 times per week and had no problems but suddenly the message appears. I haven't thnce any user or password regarding the NAS (192.168.8.6) By the way oder shares on the NAS still works, so I have only probloems with one share on the NAS.

Now I will try your recomendation and will check this with the service log user. Them I will post the result. May beyou or someone els can help me.

I would say you definately have a logon credentials mismatch with the target device(s).  As Steve mentioned this is usually caused by a change in credentials.

Here's something to try, when you select the destination for the backup instead of browsing to the location enter the path to the share by IP address in the path field at the top of the destnation screen.  The format for doing this is

Example: //192.168.8.6/foldername/

Now look to the right side of the path field for a carat that looks like this (>)

Click on the carat and you should get a logon cedentials popup box to appear.  Enter the credentials used to access the target location and select Test Connection.  If the credential matches you will get a confirmation.  After that you should be able to access the target destination again.

Hello,

thanx for info. Yes I know, but first I have nothing chanced.  2nd the NAS \\192.168.8.6/Folder ist the source and 3rd jobs from source \\192.168.8.6/folder2 works.

I enter the path to the share (NAS \\192.168.8.6\Shared_Pictures\) but there is no carat. Do you mean this one (see attaches screenshoot (yellow field?) If click on this I get no logon popup.

fyi: Other jobs with source e.g  \\192.168.8.6\Shared_Viedos work correct

So maybe the is a way to delete this Authentication Seetings for my source NAS 192.168.8.6 ? Any ideas?

Wolfgang, take a look at your Windows Credential Manager to see what you have set for your NAS credentials.

At the Windows Run prompt, type Credentials, then select the Credentials Manager from the list of options shown

FYI, I was helping another forum user recently and actually did some checking on his direct system.  Ultimately, network shares/permissions were correct (verified read/write access from windows first).  However, Windows keeps the "old" credentials in a number of places.  It was only after we removed all of them first, then created a NEW task in Acrons, that it finally prompted for user credentials in Acronis again, allowed us to check the credentials, and then started working.  The first time it connected, it stopped at about 38MB and sat there for a few minutes (either scanning the system and verifying the remote destination, or maybe a hiccup on the network). After about 1-2 minutes, the backup then started chugging along. 

First, close out of Acronis and stop acronis services in computer management / services...  Then:

1) Delete/remove any and all mapped drives in Windows to the backup destination - if multiple mappings (different folders) are there, remove all of them for now

2) Delete any/all credentials to the backup destination in Windows Credential Manger

3) Delete the saved credentials in the registry for Acronis 

HKEY_USERS\SID ID\SOFTWARE\Acronis\Connections\smb  

(note that the SID ID will be a long string of characters to a specific user - need to use the correct one.  Under "SMB", you should see any mapped shares - delete the entire folder key under the SMB folder for the remote mapped shares that apply to the destination location that is not working.

After that, start your Acronis services and launch the Acronis application again. Create a NEW backup task and point it to the remote destination.  When prompted for credentials enter them  (these are the credentials for the share that allow remote modify access - may not necessarily be your current logon in Windows unless the share was setup that way).  Test the connection - if "successful" your pretty much good to go.  Then initiate the backup.  Note that it may hang for a bit at first around 38mb - I've seen this behavior on my own system.  Give it a few minues if it does and hopefully the backup picks up after that and completes. 

Hallo Steve,

I allready checked the credential manager, but no way, still the same problem. The system / ATR remeber a old credential or destroyed the actual credential for this job or ... the funny thing is, that other jobs with the same NAS source and same destination (bu8t aber folder) make no problem.

Hi, this is the same situation.

Now I deleted every entry in the registry and ATI ask me for the credentials and now it works with your perfect hint. One püont I didn't delete the mapped drives and got the right result.

I guess the point is, that ATI "damage" the registry entry and with "delete saved credentials in the registry for Acronis" you get a fresh job in ATI.

Thank you for your hint and help!

Maybe the situation here is that your windows session and its programs are trying to access the NAS with different combinations of credentials for the NAS. Windows doesn't allow that. So if you have different software accessing the NAS for a given Windows user in a given Windows session, make sure they use the same credentials, otherwise some access will fail. A typicaly case is when user A accesses the NAS with User A's credentials for the NAS with mapped drives, but ATI is set to backup using the NAS admin's credentials.

To prevent this type of issue, make sure ATI is using the same credentials as the Windows user would use to map network shares, or access network shares.