Hi everyone! Today I found a new bug and the page at symantec does not exist yet.
I decided to create it for them, as it can be a error other will see. It happened on Windows Server 2012 R2 in case it has an importance.
Note: The log show the link http://entsupport.symantec.com/umi/V-225-302. At this time this error is not classified.
Symptom: You install BE2014 on a new system and the installation fail with the error code V-225-302
Error: V-225-302: ERROR: Failed to install SQL Express BKUPEXEC instance with error -2067922940.
Corrective Step: Pre-install the SQLExpress with the /SKIPRULES=PerfMonCounterNotCorruptedCheck parameter.
– Locate the SQL install string in the error log; it would look like that (see there for the location);
“G:\BE\WINNT\INSTALL\SQLExpress\SQLEXPR_x86_ENU.exe” /ACTION=Install /Q /Hideconsole /SkipRules=RebootRequiredCheck /FEATURES=SQL /INSTANCENAME=BKUPEXEC /SQLSVCACCOUNT=”AUTORITE NT\Système” /SQLSVCStartupType=Automatic /ENABLERANU=0 /TCPENABLED=”1″ /NPENABLED=”0″ /INSTANCEDIR=”C:\Program Files\Microsoft SQL Server” /SQLSYSADMINACCOUNTS=”BUILTIN\ADMINISTRATORS” /IACCEPTSQLSERVERLICENSETERM
– In my case change the account information, /SQLSVCACCOUNT=”AUTORITE NT\Système” for /SQLSVCACCOUNT=”NT AUTHORITY\System”. A setup error for localisation.
– Add the new command line and launch the full command. From run
“G:\BE\WINNT\INSTALL\SQLExpress\SQLEXPR_x86_ENU.exe” /ACTION=Install /Q /Hideconsole /SkipRules=RebootRequiredCheck /FEATURES=SQL /INSTANCENAME=BKUPEXEC /SQLSVCACCOUNT=”NT AUTHORITY\System” /SQLSVCStartupType=Automatic /ENABLERANU=0 /TCPENABLED=”1″ /NPENABLED=”0″ /INSTANCEDIR=”C:\Program Files\Microsoft SQL Server” /SQLSYSADMINACCOUNTS=”BUILTIN\ADMINISTRATORS” /IACCEPTSQLSERVERLICENSETERMS /SKIPRULES=PerfMonCounterNotCorruptedCheck
– Run and wait, as it will run silent.
– Re-run the BE setup after.
5 thoughts on “Symantec new technote ! V-225-302 for BackupExec 2014”
Thanks! Worked for me. You are correct about it being a silent install. You just have to wait 10 minutes to be safe.
Thx, same error from BE2012 to BE2015 on Windows Server 2012.
This solved it.
How will I know when the SQL server is done installing and do I do a custom install and point to this instance or do I just do the typical installtion?
Please check in your task manager. The sql setup will close and the service will be published in your service mmc’s applet.
I would do that way as it push option.
For you log location please check that link https://support.symantec.com/en_US/article.TECH50493.html
This worked for me, upgrading backup exec 15 to 21.3 on Server 2012