📝 Note
This article applies to
OS: Windows 7, 8, 8.1, 10
Product edition: inSync Cloud
Problem description
Error 112 means there is not enough space on disk. Looks like the C:\ drive does not have enough disk space and needs to free up some space for any uninterrupted operation to be completed by the inSync Agent.
It is observed that system app settings backup fails or does not complete due to low disk space on the C:\ drive and existence of temporary profile in the Windows registry of the client machine.
Log location
To identify the error code, please browse to the following log location on the affected client machine.
C:\inSync4\SystemState\scan198053\scan\genconfig
Traceback
📝 Note
017-07-20 1255:00, Info [0x000000] -------------- USMT ERROR SUMMARY ---------------[gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] * One or more errors were encountered in migration (ordered by first occurence)[gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] +-----------------------------------------------[gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] | Error Code | Caused Abort | Recurrence | First Occurence [gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] | 112 | No | 87 | Write error 112 for C:\Users\miyang\AppData\Local\Microsoft\Office\15.0\OfficeFileCache.old [FSD-{2ABDA43C-E980-4173-A883-02F5A7697868}.FSD]. Windows error 112 description: There is not enough space on the disk.[gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] +-----------------------------------------------[gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] | Tips | Not enough disk space, please select another location[gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] +-----------------------------------------------[gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] *c[gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] +-----------------------------------------------[gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] | Software malfunction or Unknown exception, please check the following possible solutions:[gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] | - Check log for any errors found in loaded migxml files[gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] | - Verify config xml file is not loaded using /i[gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] | - If duplicate SID exists from temp profile – use environment variable or delete temp profile[gle=0x00000012]
2017-07-20 12:55:00, Info [0x000000] +-----------------------------------------------[gle=0x00000012]
You may also find the below traceback in the inSyncclient.log of the affected client machine:
📝 Note
2017-07-20 1255:00,178] [ERROR] Failed to create the sysstate process for cmd: C:\ProgramData\Druva\inSync4\SystemState\amd64\scanstate.exe "C:\ProgramData\Druva\inSync4\SystemState\scan568223\scan" /config:"C:\ProgramData\Druva\inSync4\SystemState\scan568223\scan\Config.xml" /i:"C:\ProgramData\Druva\inSync4\SystemState\amd64\568223_migsettings.xml" /o /c /v:13 /ue:*\* /ui:"VERINT\MIYANG" /nocompress /localonly /l:"C:\ProgramData\Druva\inSync4\SystemState\scan568223\scan\scan.log" /progress:"C:\ProgramData\Druva\inSync4\SystemState\scan568223\scan\scanprogress.log" /efs:copyraw /vsc.
[2017-07-20 12:55:00,290] [ERROR] System, App Settings: Failed to generate dump of the settings files.
[2017-07-20 12:55:00,290] [ERROR] System, App Settings: Failed to backup settings.
[2017-07-20 12:55:00,571] [ERROR] Failed to backup System, App Settings. (#100000070)
Cause
inSync basically uses the Windows built in USMT for System, App Settings backup or migration. The built in USMT fails to start the migration process.
Resolution
Increase the disk space on C:\ drive. inSync requires minimum of 8GB of free space on the C:\ drive for any operation to succeed.
Shutdown the machine, wait for a few minutes, and then boot the machine again to get rid of the temp profile.
Try the System Settings backup again from inSync.
If restarting the machine did not resolve the issue. Perform the following steps to delete the temporary profile from the windows machine.
Take a backup of the registry.
Click Start > click the Search icon > enter regedit in the Search box and then press ENTER.
If you are prompted for an administrator password or for confirmation, enter your password and click Continue.
If you are not prompted for administrator credentials, simply click Continue.
Locate the following registry subkey "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
Under the ProfileList subkey, delete the subkey that is named SID.bak.
SID is a placeholder for the security identifier (SID) of the user account that is experiencing the problem. The SID.bak subkey must contain a ProfileImagePath registry entry that points to the original profile folder of the user account that is experiencing the problem.
Exit Registry Editor.
Log out and log on to the system again.
Run a backup.
If the backup fails again, please contact Druva Support for further troubleshooting.