backupper being run error
After using backupper, I now receive "backupper being run" and backup not occuring. Anyone else have this problem?
After using backupper, I now receive "backupper being run" and backup not occuring. Anyone else have this problem?
Comments
Johnpdwyer,
What version of Backupper are you running? What kind of backup job (new, full, differential, etc.)? Also, can you attach the log file from the backupper folder?
Can't tell what version because will not start. Had the program running since Oct 24th. Incremental backup has been working fine. Problem occurred on both computers about the same time. The log file for backup up folder, I don't now how to do that. Sorry.
c:\program files (x86)\aomei backupper ... version number\log is the path. There will be at least one, but probably two or three log files there.
Most recent log file. There are 4.
Module Path: C:\Program Files (x86)\AOMEI Backupper Standard Edition 2.0.2\Backupper.exe
Product Name: Windows 7 Home Premium (6.1.7601.2)
Service Package: Service Pack 1
OS Version: 6.1
Total Memory: 8070 MB
Available Memory: 2094 MB
System Root: C:\Windows
Processor Architecture: AMD64
Processor Number: 2
Current Time: 2014-11-14 10:7:30
This log doesn't have any useable information about the error. It does show, though, that you're not using the latest release of the software. I'd download the latest version and install it. Then try again.
Ok, thanks. Will try that
You're welcome. Let us know if that solves it. If not, we can take it a step further.
Thanks for your help. I had to reboot computer. It then allowed me to remove old program and reinstall new one. Selected backups and schedule again, and now everything appears to be running fine.
You're welcome. I'm glad that it's resolved.
I'm having the same problem on my wife's computer. Here's the current log:
AOMEI Backupper 2.1.0 log is as follows:
====================== System Information ======================
Module Path: C:\Program Files\AOMEI Backupper Standard Edition 2.1.0\Backupper.exe
Product Name: Windows 7 Professional (6.1.7601.2)
Service Package: Service Pack 1
OS Version: 6.1
Total Memory: 3036 MB
Available Memory: 1138 MB
System Root: C:\Windows
Processor Architecture: x86
Processor Number: 2
Current Time: 2014-12-8 16:57:53
================================================================
[0 ]!(::GetFileAttributesA(sCurPath) == INVALID_FILE_ATTRIBUTES) return code: 0x00000000, NetworkMgr.cpp(199).
[2 ]!(::GetFileAttributesA(sCurPath) == INVALID_FILE_ATTRIBUTES) return code: 0x00000000, NetworkMgr.cpp(199).
It may be because the path last used for backup has changed. But it won't run so I can change to a new path!
Hope this helps. I don't really want to have to totally reinstall just because I change my disk partitions.
Thanks.
Alan1250,
Are you having this problem only with a scheduled backup or can you manually run a backup without problem?
Alan1250 wrote: "It may be because the path last used for backup has changed."
I was suspecting the same since my automated backups (using the Windows Scheduler) quit working after changing the internal drive which was being used to store incremental backups. I even uninstalled/reinstalled Backupper Standard v3.0 and it wont work. I can perform a backup manually with no problem but it won't run on the Windows Scheduler even though I have properly enabled it to do so on AOMEI's "Advanced" tab. The Windows scheduler says the task ran successfully but no backup is produced.
AOMEI Backupper 2.8.0 log is as follows:
====================== System Information ======================
Module Path: C:\Program Files (x86)\AOMEI Backupper\Backupper.exe
Product Name: Windows 7 Ultimate (6.1.7601.2)
Service Package: Service Pack 1
OS Version: 6.1
Total Memory: 8103 MB
Available Memory: 6115 MB
System Root: C:\Windows
Processor Architecture: AMD64
Processor Number: 4
Current Time: 2015-8-3 12:37:34
==========================================================
[0 ]::GetFileAttributesA(sCurPath) != INVALID_FILE_ATTRIBUTES return code: 0x00000000, NetworkMgr.cpp(208).
[2 ]::GetFileAttributesA(sCurPath) != INVALID_FILE_ATTRIBUTES return code: 0x00000000, NetworkMgr.cpp(208).
diskinfo.h(451): Failed to init GPT style table.
diskinfo.h(451): Failed to init GPT style table.
[2 ]dyndisk.cpp(213): Failed to RegQueryValueEx on GetSysDgGuid.
[0 ]ldmio.cpp(89): No dynamic disks are found.
//////////////////////////////Dump Information////////////////////////////
Dump Disk:
==========================================================
Disk Index Total Sector Geometry Product Name
---------- ------------ -------- ------------
0 250069680 (119.24GB) (15566,255,63) PLEXTOR PX-128M3 (Basic Disk,MBR,Sig: 27532753)
1 1953525168 (931.51GB) (121601,255,63) WDC WD1002FAEX-00Y9A0 (Basic Disk,MBR,Sig: 9d9efe49)
Dump Volume:
==========================================================
ID Volume File System Total Sector Used Sector Free Sector Type Status Cluster Size Volume Label
----------------------------------------------------------------------
0.0 *: NTFS 110406 (53.91MB) 49536 (24.19MB) 60870 (29.72MB) Primary Ok,Act,Sys 8 System Reserved
0.1 C: NTFS 135506041 (64.61GB) 88430696 (42.17GB) 47075345 (22.45GB) Primary Ok,Boot 8
0.2 NTFS 114429067 (54.56GB) 11379296 (5.43GB) 103049771 (49.14GB) Primary Ok 8 DATA
1.0 F: NTFS 1953519615 (931.51GB) 1350595768 (644.01GB) 602923847 (287.50GB) Primary Ok 8 BACKUP
Dump Slice:
==========================================================
ID ParentID SequenceID Offset Sector Start Sector Slice Size Unallocated
-- -------- ---------- ------------- ------------ ---------- -----------
[2 ]bFind return code: 0x0132100B, MainWidget.cpp(306).
I finally fixed AOMEI's inability to run from the Windows Scheduler. I
don't know if every step taken below was necessary but here is what I did:
1) Uninstalled AOMEI Backupper & rebooted.
2) Used CCleaner to clean both files and registry, rebooted.
3) Changed target F: drive letter to G:, then back to F:
4) Installed AOMEI Backupper v3.0, scheduled task used "Advanced" tab
designating to use Windows Scheduler only.
5) Manually edited task to run whether user is logged in or not, and
changed "Configure for" to "Windows 7, Windows Server 2008 R2".
6) Tested task from Windows Scheduler by right-clicking it then clicking
"Run".