03-12-2015 06:27 AM
Dear Forum,
I have a Windows Server 2008R2 Standard in English with Backup Exec 2012 (V.14.0 Rev.1798 64bit) with Service Pack 4 and all available Hotfixes installed - at least the Live Update doesn't offer any further updates.
Now I want to upgrade this Backup Exec installation to Backup Exec 2014 (V.14.1 SP2) (using this media Backup_Exec_2014_14.1_SP2_MultiPlatforms_Multilingual.iso) but am already struggling with the "Environment Check 2.0".
This check runs since hours and won't stop:
The only hint I found regarding such a problem is Article:TECH213591 but this article ends with "Upgrade or install with Backup Exec 2014 SP1 media".
But I'm already using a SP2 media...
So any idea what to do?
Thanks in advance!
Best regards,
SG
Solved! Go to Solution.
03-16-2015 12:49 AM
Finally I found a solution after disabling the AntiVirus software and running the Installer as Administrator (which I already did) didn't solve the issue.
I remembered that I had a similar situation lots of years ago with another version of Backup Exec. There a disabling of the network connection for some seconds solved the problem.
Now it was the same: Disabling the network connection for 5 seconds finished the environment check successfully and the installation itself also suceeded.
Isn't it a bit weird that it seems that this bug still exists since lots of years!?
Best regards,
SG
03-12-2015 06:49 AM
If running any AV, temporarily disable it. Also, rerun the installer with elevated privileges, i.e. using Run As Admin. you could cancel the current running setup via the task manager..
03-13-2015 02:52 PM
Hi,
If this is still a problem check BKUPINST.HTM in C:\ProgramData\Symantec\Backup Exec\Logs\ and post the errors
03-15-2015 03:30 PM
03-16-2015 12:49 AM
Finally I found a solution after disabling the AntiVirus software and running the Installer as Administrator (which I already did) didn't solve the issue.
I remembered that I had a similar situation lots of years ago with another version of Backup Exec. There a disabling of the network connection for some seconds solved the problem.
Now it was the same: Disabling the network connection for 5 seconds finished the environment check successfully and the installation itself also suceeded.
Isn't it a bit weird that it seems that this bug still exists since lots of years!?
Best regards,
SG