Ok, I have an Exchange 2010 server that was running low on disk space as the logs weren't commiting due to backup failures because the backup exec 2010 agent wasn't working.
I took the opportunity to remove the BE agent using Programs and Features, rebooted the server etc and tried to re-push the agent getting the vague error 1603.
It looks like 1603 is a generic error for 'something went wrong in the install process and I'm rolling back'.
Before I really delved into the log files I followed the following article to remove the BE Agent manually:
http://www.symantec.com/business/support/index?pag...
Nothing,still 1603.
I also removed SEP and deleted everything related to Symantec (with a snapshot and reg backup), still nothing.
I looked at the log and noticed:
12-20-2014,13:27:48 : Application: {2E214FDB-1B99-4BF3-BEE4-43B82EB1D6AE}, Command line: UPGRADINGPRODUCTCODE={856D9205-4AA3-48FB-ADD2-CE6EFF23ED9E} CLIENTUILEVEL=3 REMOVE=ALL
12-20-2014,13:28:13 : No valid sequence could be found for the set of updates. C:\Windows\Installer\610eb.msi
12-20-2014,13:28:13 : CustomAction returned actual error code 1648 (note this may not be 100% accurate if translation happened inside sandbox)
+ 12-20-2014,13:28:13 : FATAL ERROR: Error 1714.The older version of Symantec Backup Exec Remote Agent for Windows cannot be removed. Contact your technical support group.
12-20-2014,13:28:13 : Action ended 13:28:13: RemoveExistingProducts. Return value 3.
The agent installer thinks there is an existing version of the BE agent installed but it cant remove it so it's bailing out.
OK, more poking about online revealed this article:
https://www-secure.symantec.com/connect/forums/can...
Windows installer may be preventing the new agent from going in.
Obviously MS has removed the Windows installer cleanup utility from support so I downloaded the x86 (its a 64 bit server) version from Majorgeeks (I don't like downloading vendor software from non-vendors but as needs must).
The msicuu2.exe installed fine and I ran it from the installed location at C:\Program Files (x86)\Windows Installer Clean Up\msicc.exe.
I found the BE agent reference at the end of the list and I removed it. After a minute the entry was gone.
I then re-ran the BE agent push and it went through with no issues!
This was driving me mad and it's now working!
Now there appear to be dozens of issues relating to 1603 and actually I have another on a SQl server that appears to be related to the agent's failure to install MS Visual C++ installers but that's another story!