Backups successful but with warnings
I am using vmProtect7 and since I installed vmProtect7, all of my backups are succesfull but with warnings. Checking at the logs I am getting the below warnings.
Detailed message
The processor number is incorrect.
Additional info:
--------------------
Error code: 76
Module: 83
LineInfo: a859dd78cc91df67
Fields:
Message: The processor number is incorrect.
--------------------
I tried to search for it but I found nothing. Can you please advise?
Thanks

- Log in to post comments

Hi Yana,
I would like to send you the logs but everytime I try the save all to file, it creates an zip file with 0kb size
Please advise
Thanks
Attachment | Size |
---|---|
96051-100291.zip | bytes |
- Log in to post comments

Does http://kb.acronis.com/content/30926 probably allow you to collect logs?
- Log in to post comments

Hi Stefan,
I have tried the kb article but it still when i try to save the logs it creates a zip file with a 0kb xml file that is empty.
Any other suggestions?
Thanks
- Log in to post comments

Hi Kojak,
sorry for the late response.
It's hard to tell what's broken in your configuration.
I'd suggest to stop your Virtual Appliance and install a 2nd one in parallel - and but please use the latest build 5155, if you are running 5144 currently.
Even if the warnings persist then, it may at least allow you to send logs to support.
- Log in to post comments

Hi Stefan,
I will try that but at the moment the download link does not work on your website
Could you provide me alternative way to download?
Thanks
- Log in to post comments

The download does not work for me as well right now in MyAccount :-/
But the partner portal links do work:
http://download.acronis.com/trial/AVMP7_trial_en-US.exe
http://download.acronis.com/trial/AVMP7_trial_en-EU.exe
US/EU are with .com or .co.uk branding, the only difference to the full versions is the file name.
- Log in to post comments


chi-ltd, what build are you using?
I think anyone else who is affected and has aleady upgraded to build 5173 (Release date: 27-June-2012) should open a support case with a reference to this thread.
- Log in to post comments

To update you, this has been happening even since upgrading to v5173, but only on particular VM's. Could it be related to the fact that theses vm's are replicated also?
- Log in to post comments