Skip to main content

ATI 2018 nonstop backup a nonstarter

Thread needs solution

On a Surface Pro 4 with Win 10, I can't create a nonstop backup job. 

I'm trying to set my Desktop and Documents folders to nonstop backup to a microSD card in the slot behind the Surface's kickstand.  (NTFS formatted card; plenty of capacity available.) 

This is what I get after creating the job and clicking "Back up now":

 

"An error occurred while opening Acronis Nonstop Backup session.

More information about this error and solutions may be available online in the Acronis Knowledge Base.
To access the online resource manually, enter the event code at: http://kb.acronis.com/errorcode/
Event code: 0x00640160+0x00E4002D+0x00E40021+0x0000FFF0+0x800706BA"

 

The Acronis Nonstop Backup Service is set to Automatic startup, but it will not start. It is set to logon as Local System account.  No error is logged for it during Windows boot, but if I try to start it myself, this error is logged:

 

"Log Name:      Application
Source:        Application Error
Date:          11/22/2017 6:23:28 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      (redacted)
Description:
Faulting application name: afcdpsrv.exe, version: 3.0.1.4328, time stamp: 0x59c8f9a6
Faulting module name: afcdpsrv.exe, version: 3.0.1.4328, time stamp: 0x59c8f9a6
Exception code: 0xc0000005
Fault offset: 0x000f4496
Faulting process id: 0x1c94
Faulting application start time: 0x01d363e8e1f9fd0a
Faulting application path: C:\Program Files (x86)\Common Files\Acronis\CDP\afcdpsrv.exe
Faulting module path: C:\Program Files (x86)\Common Files\Acronis\CDP\afcdpsrv.exe
Report Id: cc895573-f808-4e9d-a3c7-cb12da4c3d27
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-11-22T23:23:28.456080600Z" />
    <EventRecordID>1787</EventRecordID>
    <Channel>Application</Channel>
    <Computer>JGiardel102393N</Computer>
    <Security />
  </System>
  <EventData>
    <Data>afcdpsrv.exe</Data>
    <Data>3.0.1.4328</Data>
    <Data>59c8f9a6</Data>
    <Data>afcdpsrv.exe</Data>
    <Data>3.0.1.4328</Data>
    <Data>59c8f9a6</Data>
    <Data>c0000005</Data>
    <Data>000f4496</Data>
    <Data>1c94</Data>
    <Data>01d363e8e1f9fd0a</Data>
    <Data>C:\Program Files (x86)\Common Files\Acronis\CDP\afcdpsrv.exe</Data>
    <Data>C:\Program Files (x86)\Common Files\Acronis\CDP\afcdpsrv.exe</Data>
    <Data>cc895573-f808-4e9d-a3c7-cb12da4c3d27</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>"

 

 

Any ideas?  I have the MVP Log Viewer, if anyone wants to see a log. 

Thanks. 

0 Users found this helpful

Robin, welcome to these User Forums.

Please open a Support Case direct with Acronis Support for this NSB issue and reference this forum topic in your case.

The initial error codes are caused because the NSB Service is not running, which is a consequence of the second issue that the NSB Service cannot be started and made to stay running.

I can recreate the same issue on my laptop but cannot submit a case for this because I am running on the latest Windows Insider build 17046 on this computer which Acronis do not support for reporting problems.  I am not in a position to test this on a different computer at this time as am currently travelling.

2017-11-23 11_14_05.png

Thank you.  I just submitted a ticket with a system report upload.  I see that a new update is available, but the release notes don't address any nonstop backup issues.  I'll update later.

BTW, I appreciate the friendly informality of you addressing me as "Robin," but I must insist that you use the full Sir Robin.  As in The Brave Sir Robin.  Otherwise I don't get to hear the clip-clopping of the coconut shells.  ; - } 

Well Sir Robin... I just turned by computer back on this afternoon and was told I had an update for ATI 2018 Update 2 with build # 10410.  

After installing the new build, my problems with NSB were gone and the new task I setup ran successfully, plus the NSB Service remained running!

2017-11-23 16_08_25.png

Updating from ATI 2018 v9850 to v10410 fixed it. 

I notified Acronis Support thru the ticket I submitted. 

Thank you!!!

Minor bug: when I was creating the backup job (new and only job), when I clicked on the words "Change Destination," nothing happened.  I had to click in the empty space above the words to select my new  destination. 

Now that the job was able to be saved and it ran, if I go back to click on the words "Change Destination" it now works. 

Strange. 

Glad to hear that all is ok for your NSB too.  Guess strange things happen when you are waiting "to hear the clip-clopping of the coconut shells.  ; - }" Sir Robin!