KCS Backup always fails to execute a backup task on a Windows Server 2012 R2
Article # 3035990 - Page views: 27
Issue
- I installed KCS Backup on a fresh Windows 2012 R2 machine, but when I create a new Backup task, it will always fail.
- The Trace file C:\TCOSS\Trace\KCSBackupSrv.log file shows following trace output:
2014-09-15 13:49:59,859 DEBUG [Thread=Worker] [KCSBackupSrv] Init complete
2014-09-15 13:49:59,939 ERROR [Thread=Worker] [KCSBackupSrv] KCSObjectsBackupMgr.ctor:Object reference not set to an instance of an object.
- Increasing the tracelevel in C:\TOPCALL\KCSBackup\KCSBackupSrv.log4net.config to e.g. DEBUG does not give any more information.
- What is the reason for this problem and can it be solved somehow?
Cause
The problem is caused by a known bug
KCSBackup: NullPointerException while retrieving Win32_Registry WMI class
Solution
You can use the following workaround to solve the problem:
- Copy the attached WMIReadValues.vbs and WMICorrectValues.vbs to any local folder on the machine where KCSBackup is installed
- Login with a local Administrator user
- Right-click the start button and select the menu option Command Prompt (Admin)
- Within this command prompt window nagivate with the cd command to the folder, where the these two vbs files are located Within this command prompt window execute the command: cscript WMIReadValues.vbs
- Check the values reported after MaximumSize and ProposedSize. If MaximumSize is empty and ProposedSize is 0 as shown below, it is most likely the reason for the problem with KCSBackup.
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
Caption: Registry
CurrentSize: 102
MaximumSize:
ProposedSize: 0
Status: OK - In this case execute the following command: cscript WMICorrectValues.vbs
- Both values "MaximumSize" and "ProposedSize" should now show a value of 2048 as shown below:
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
Caption: Registry
CurrentSize: 109
MaximumSize: 2048
ProposedSize: 2048
Status: OK
Afterwards it is recommended to reboot the whole machine and check then to create a backup task with KCSBackup.
Level of Complexity
Moderate
Applies to
Product | Version | Build | Environment | Hardware |
---|---|---|---|---|
KCS Backup | (tested with KCS Backup from KCS 10.0, because this is the first KCS Version supporting Windows Server 2012 R2 |
References
Keywords: KCS Backup, Object reference not set to an instance of an object, Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.