It may be blocked by another applictation
after an update of the Fritz router which also brings a new protocol SMB3, I have problems to save data on the NAS. Although I can select the file path in the network as a source but when starting the backup then the message "Failed to back up file or folder \\ Fritz \ fritz.nas \ Fritz_NAS \ KeePass \ Martin." It may be blocked by another application "
What is it broken again? Use Windows 10 1809
thanks for the tip
Unfortunately, this did not lead to success.
strangely enough, it can access the NAS via the network drive from the desktop.
Only in TI 2019 comes after the update of the FritzBox this message.
The network password and user are stored in TI 2019 after polling. I can also select everything in the directory of the FritzBox. Only just the backup then stops.
Martin Scheffler wrote:strangely enough, it can access the NAS via the network drive from the desktop.
Only in TI 2019 comes after the update of the FritzBox this message.
The network password and user are stored in TI 2019 after polling. I can also select everything in the directory of the FritzBox. Only just the backup then stops.
When you attempt to backup to the NAS does TI 2019 show a credentials box that is already populated? If yes what happens when you click on the connect button? Do you get a message that you are connected or Connection failed?
Correct is:
I had already deposited these credentials and they worked.
After the Fritz Update, this log-in window jumped again, but was empty. I re-entered the data and tested the connection as successful.
it looks as if AVM has changed the network name of the box internally with the update. The path was always fritz-nas and then the path came through the user. Now the first path is Fritz and then comes the UserPath.
You can also see it in the registry of Acronis:
Computer \ HKEY_CURRENT_USER \ Software \ Acronis \ Connections \ smb
There was the old entry "fritz-nas \ fritz.nas"
Now there is the new entry "Fritz \ fritz.nas
It looks like fritz-nas has changed against Fritz.
Unfortunately, my backup is no longer because allegedly another application accesses the files.
29.01.2019 14:38:41: 00 10660 I00000000: ATI Demon started. Version: 23.4.1.14690.
29.01.2019 14:38:41: 00 10660 I00640000: Attribute für Backup-Reservekopie: format tib; need_reserve_backup_copy false;
29.01.2019 14:38:41: 00 10660 I00640002: Aktion test wurde per Planung gestartet.
29.01.2019 14:38:43: 00 10660 I00640000: Attribute für Backup-Reservekopie: format tib; need_reserve_backup_copy false;
29.01.2019 14:38:43: 00 10660 I013C0000: Aktion: Backup
29.01.2019 14:38:43: 00 10660 I0064000B: Priorität geändert in 'Niedrig'
29.01.2019 14:38:43: 00 10660 I0017001A: Error 0x17001a: Erstellen des Snapshots für das Backup fehlgeschlagen.
29.01.2019 14:38:43: 00 10660 I000B03F0: Backup-Archiv erstellen Von: \\Fritz\fritz.nas\Fritz_NAS\KeePass\
In Datei: test_full_b1_s1_v1.tib Komprimierung: Maximum Exclude: Durch Ausschlussmaske erfasste Dateien Passendes Kriterium: hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\Martin\AppData\Local\Temp, C:\Users\Martin\AppData\Local\Microsoft\Windows\INetCache, C:\Users\Martin\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\Martin\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\Martin\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\Martin\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\Martin\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\WINDOWS\CSC
29.01.2019 14:38:43: 00 10660 E00170027: Failed to back up file or folder '\\?\UNC\Fritz\fritz.nas\Fritz_NAS\KeePass\Martin'. It may be blocked by another application.
Fehler beim Backup der Datei. (0x170027)
Path = "\\?\UNC\Fritz\fritz.nas\Fritz_NAS\KeePass\Martin",
$module = "ti_demon_vs_14690"
Archive::BackupOperationContext::OnError:
c:\bs_hudson\workspace\646\archive\backuper.cpp(825)
Fehler beim Lesen der Datei. (0x40001)
$module = "ti_demon_vs_14690"
ChunkNTBackupStream:
c:\bs_hudson\workspace\646\core\file\ntstream_chunker.cpp(244)
Fehler beim Lesen der Datei. (0x40001)
$module = "ti_demon_vs_14690"
`anonymous-namespace'::ReadStreamHeader:
c:\bs_hudson\workspace\646\core\file\ntstream_chunker.cpp(54)
Backup der Datei (des Verzeichnises) fehlgeschlagen. (0x40019)
Path = "\\?\UNC\Fritz\fritz.nas\Fritz_NAS\KeePass\Martin",
Hints = 1),
$module = "ti_demon_vs_14690"
`anonymous-namespace'::NTBackupStream::Read:
c:\bs_hudson\workspace\646\core\file\windows\winnt_backup.cpp(817)
Element nicht gefunden (0xFFF0)
code = 80070490),
$module = "ti_demon_vs_14690"
Common::Error::AddWindowsError:
c:\bs_hudson\workspace\646\core\common\error.cpp(307) : Kein(e)
29.01.2019 14:40:16: 00 10660 W00170019: Error 0x170019: Das Element wurde übersprungen.
29.01.2019 14:40:16: 00 10660 W00170019: Error 0x170019: Das Element wurde übersprungen.
29.01.2019 14:40:16: 00 10660 I00640000: Schreibe vollständige Version zu Datei: test_full_b1_s1_v1.tib
29.01.2019 14:40:16: 00 10660 I00640000: Die folgenden Backups wurden erfolgreich erstellt: I:\TrueImage\test_full_b1_s1_v1.tib
29.01.2019 14:40:16: 00 10660 I013C0006: Aktion erfolgreich.
Start: 29.01.2019 14:38:41
Stop: 29.01.2019 14:40:16
Total Time: 00:01:35
In regedit delete the keys for the NAS:
"fritz-nas \ fritz.nas"
"Fritz \ fritz.nas
Close regedit and restart your computer.
Upon restart run the backup again and it should immediately display the credentials box again. Username and Password fields should be blank. Enter the appropriate credentials and test connection. If it passes then you have successfully updated the login.
The backup should function now.
you mean the old entries under smb?
I have already deleted, but it is still not.
I have TI even uninstalled and reinstalled again.
even without success
Now I even cleaned up TI with the Clean Up Tool and re-installed it.
Is TI not capable of SMB 2 and 3?
It can only be related to it or?
Here is an excerpt from the lab of AVM:
Quote:
[2] Notes on changing the access to FRITZ! NAS content via the SMB protocol
SMBv1 and NTLMv1 currently not supported
With the current laboratory, the SMB access method has been changed from the protocol version SMBv1 to the modern and powerful SMBv3.
SMBv1 and the outdated authentication method NTLMv1 are currently not supported.
Therefore, please switch your devices that you want to access to FRITZ! NAS via SMB to SMBv3.
Use of SMBv3 on Windows and Linux PCs
New installations of Windows 10 have been using SMBv3 and NTLMv2 ex works since the end of 2017.
After the update to the FRITZ! Laboratory, you can activate or deactivate the support for SMBv1 via the function "Activate or deactivate Windows features" ->
Disable "SMB 1.0 / CIFS file sharing support".
On Linux PCs, it may be necessary to manually configure the use of SMBv3 / 2.
To do this, add the lines in the "etc / samba / smb.conf" configuration file in the "Global Settings" area
client min protocol = SMB2
client max protocol = SMB3
added.
Set up network drives can no longer be used after the update
By changing the access method, it may be necessary to rebuild existing network drives once.
New system events
If the access to FRITZ! NAS content via SMB does not work after the update to the FRITZ! Laboratory, you can access the system events
the FRITZ! Box get an indication of the cause, e.g. wrong username / password, users with missing NAS rights or access with
a device that supports only SMBv1 or NTLMv1.
Now I even cleaned up TI with the Clean Up Tool and re-installed it.
Is TI not capable of SMB 2 and 3?
It can only be related to it or?
Here is an excerpt from the lab of AVM:
Quote:
[2] Notes on changing the access to FRITZ! NAS content via the SMB protocol
SMBv1 and NTLMv1 currently not supported
With the current laboratory, the SMB access method has been changed from the protocol version SMBv1 to the modern and powerful SMBv3.
SMBv1 and the outdated authentication method NTLMv1 are currently not supported.
Therefore, please switch your devices that you want to access to FRITZ! NAS via SMB to SMBv3.
Use of SMBv3 on Windows and Linux PCs
New installations of Windows 10 have been using SMBv3 and NTLMv2 ex works since the end of 2017.
After the update to the FRITZ! Laboratory, you can activate or deactivate the support for SMBv1 via the function "Activate or deactivate Windows features" ->
Disable "SMB 1.0 / CIFS file sharing support".
On Linux PCs, it may be necessary to manually configure the use of SMBv3 / 2.
To do this, add the lines in the "etc / samba / smb.conf" configuration file in the "Global Settings" area
client min protocol = SMB2
client max protocol = SMB3
added.
Set up network drives can no longer be used after the update
By changing the access method, it may be necessary to rebuild existing network drives once.
New system events
If the access to FRITZ! NAS content via SMB does not work after the update to the FRITZ! Laboratory, you can access the system events
the FRITZ! Box get an indication of the cause, e.g. wrong username / password, users with missing NAS rights or access with
a device that supports only SMBv1 or NTLMv1.
Is TI not capable of SMB 2 and 3?
ATI sits on top of the OS and is definitely capable of working with SMB 2 & 3 devices.
I have SMB 1 removed on my own Windows 10 box and have my Synology NAS set to accept only SMB 2 or 3 and all works fine for my backups to the NAS.
MarSche,
I just disabled SMB 1 / CIFS in Windows 10, rebooted and ran my NAS backup. All went well on this end, so it does appear that Acronis is capable of connecting with the higher protocol.
Really not sure what's going on with the Fritz connection in this case. I've seen NAS shares not work if the file access is available at a higher level, but not at the folders/levels before it. Try connecting manually to the root of your NAS share with a new backup using the IP (i.e. \\192.168.x.x) and see if it connects at all after you provide credentials. If so, then keep navigating the folder structure in Acronis and see if it can step through to the desired end-folder you want the backup to write too.
Also, maybe, just as a test, disable any 3rd party firewalls or antivirus in case they are preventing traffic as well. We have seen AV programs block traffic at times too - I seem to vaguely recall a fritz box being a culprit a few years ago too. Can't find that forum though.
Maybe send a PM to MVP G. Uphoff (he helps a lot in the German portion) and he seems to have some experience in the forums with others using Fritz equipment. I can't follow the thread since it's all in German, but.. for instance:
MarSche,
Windows 10 supports SMB 3.1.1 currently and as Steve mentions ATI uses Windows connections I notice in your post with the AVM quoted it mentions " By changing the access method, it may be necessary to rebuild existing network drives once." By changing the access method, it may be necessary to rebuild existing network drives once." Not sure what that means, if it applies only to Linux or Windows and Linux. You might have to do that however to get things working.
Can you log into the Fritz box using a browser? Has you password changed to gain access that way? I am confident you face a credentials problem and it is likely to be the Fritz box that is preventing the access. You might have to contact them to get a solution.
first of all many thanks for your great help
I will contact Mr. uphoff
but for further information
yes I can access the NAS via browser.
I can synonymous over the browser files from the NAS copy, everything is only Acronis it can not be the laboratory update of the Fritz on 7:08
I had already reconnected the network drives and only later read this note from AVM, that one would have to, so that was okay
Then I tried the tip with connection by IP in Acronis and before of course in the registry under SMB the registration data deleted.
Have entered the IP and there was the login window for the user and password I could also enter and tested the connection. She went. I can also read in the directory but as soon as I have selected the desired files or to test synonymous other files for backup and start the backup comes the message that these files would be blocked by another application.
I have now selected a source file from the PC and saved it as a backup to the NAS.
This works fine.
Then I create a new backup in which I then take this new file from the NAS as a source and select the destination on the PC and the backu then start again comes the error message that the source file is blocked by another application.
This can only be a bug in the Fritz firmware?
Open an Administrator Powershell window and type the command: Get-SmbConnection
This will list what version of SMB you are using on your Windows OS to any systems you have connections to. On my own computer I see:
PS E:\powershell> get-SmbConnection ServerName ShareName UserName Credential Dialect NumOpens ---------- --------- -------- ---------- ------- -------- TCEdge71-1 IPC$ DELLSTUDIO\smiths DELLSTUDIO\smiths 3.1.1 0 TCEdge71-1 IPC$ WORKGROUP\DELLSTUDIO$ WORKGROUP\DELLSTUDIO$ 3.1.1 0 TCEdge71-1 print$ DELLSTUDIO\smiths DELLSTUDIO\smiths 3.1.1 1
This shows my SMB level being used is 3.1.1 for any network connections.
Next, use the command: Get-SmbServerConfiguration and check the value for the EnableSMB1Protocol setting - this should be set to False.
PS E:\powershell> Get-SmbServerConfiguration AnnounceComment : AnnounceServer : False AsynchronousCredits : 64 AuditSmb1Access : False AutoDisconnectTimeout : 15 AutoShareServer : True AutoShareWorkstation : True CachedOpenLimit : 10 DurableHandleV2TimeoutInSeconds : 180 EnableAuthenticateUserSharing : False EnableDownlevelTimewarp : False EnableForcedLogoff : True EnableLeasing : True EnableMultiChannel : True EnableOplocks : True EnableSecuritySignature : False EnableSMB1Protocol : False EnableSMB2Protocol : True EnableStrictNameChecking : True EncryptData : False IrpStackSize : 15 KeepAliveTime : 2 MaxChannelPerSession : 32 MaxMpxCount : 50 MaxSessionPerConnection : 16384 MaxThreadsPerQueue : 20 MaxWorkItems : 1 NullSessionPipes : NullSessionShares : OplockBreakWait : 35 PendingClientTimeoutInSeconds : 120 RejectUnencryptedAccess : True RequireSecuritySignature : False ServerHidden : True Smb2CreditsMax : 2048 Smb2CreditsMin : 128 SmbServerNameHardeningLevel : 0 TreatHostAsStableStorage : False ValidateAliasNotCircular : True ValidateShareScope : True ValidateShareScopeNotAliased : True ValidateTargetName : True
MarSche,
I just found a report from another user experiencing much the same issue with you using another backup product whom has been in contact with AVM about this. This user reports that they were told this is a know bug in the Fritz firmware. Apparently a later version of firmware is available that fixes the issue.
I went back to the official firmware in the fritz box 7:01 and acronis goes again. this is 100% due to a faulty firmware in the router.
The new beta firmwares have completely new SMB 2 and 3 implemented and I think there is still the worm in it.
Under 7.01 SMB 1 is again active and it works flawlessly.
Glad to hear that you fixed the issue. I would recommend that you keep an eye on the firmware and once it is out of beta stage and released officially I would once again update to it. It would be much better for SMB support to be at 2.0 and higher.
Thanks for posting back.