06-04-2013 09:22 AM
Greetings to the well of knowledge...
I have 10d running on a 2003R2 server (an environment I inherited when I was hired as IT manager). I am trying to install SP4. It seems to install fine up to the point where it wants to configure Veritas Backup Exec at which point it rolls back the installation and terminates. We do not run Veritas Backup Exec, so how can I install this SP without having to go through the Veritas process?
Regards,
Ken Carter
IT Manager
TILL, Inc.
Solved! Go to Solution.
06-05-2013 06:58 AM
Per the log errors, it seems you have installed BEDB on a remote SQL instance.
Try this ~
Copy the osql.exe and bcp.exe and bcp.rll files, typically located in the \Program Files\Microsoft SQL Server\80\Tools\Binn directory on the remote SQL server to the \Program File\Veritas\Backup Exec\NT folder of the Backup Exec server and then run the install of the Service Pack.
EDIT*
If the above doesn't work, try this then ~
06-04-2013 12:35 PM
Hi Ken,
It's probably some legacy entry that references Veritas, even though Symantec owned it by this stage.
If there is an antivirus installed on that server, stop it, and then run the installation again.
Thanks!
06-04-2013 01:03 PM
Antivirus was killed before doing the install.
K
06-04-2013 01:40 PM
...any error messages in Event Viewer or the Alerts tab within BE?
06-04-2013 01:44 PM
Nope, nothing at all.
06-04-2013 10:54 PM
See if this KB helps ~ http://www.symantec.com/business/support/index?page=content&id=TECH50267
If not, pls post the install log file.
06-05-2013 06:37 AM
As requested, the install log is attached.
06-05-2013 06:58 AM
Per the log errors, it seems you have installed BEDB on a remote SQL instance.
Try this ~
Copy the osql.exe and bcp.exe and bcp.rll files, typically located in the \Program Files\Microsoft SQL Server\80\Tools\Binn directory on the remote SQL server to the \Program File\Veritas\Backup Exec\NT folder of the Backup Exec server and then run the install of the Service Pack.
EDIT*
If the above doesn't work, try this then ~
06-17-2013 08:58 AM
Editing the PATH environment variable did the trick! Thank you!