12.5 to 2012 upgrade failing

[ddorton]

Hello,

I have been trying to upgrade from 12.5 to 2012 without any luck for hours now.  I am getting the following errors in the install log:

+ 12-24-2013,17:29:17 : Could not load resdll

+ 12-24-2013,17:31:05 : V-225-206: Connection attempt 3 failed: SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. Login timeout expired ***To search for information about this error, click here 

+ 12-24-2013,17:31:05 : V-225-226: Unable to connect to SQL Server. ***To search for information about this error, click here 

Any advice?

[pkh]

Make sure that the old SQL instance BKUPEXEC is running when you do the upgrade.

[ddorton]

Yes I have tried with all SQL instances running and stopped as well as all BE services started and stopped.  

It seems to be hanging up on a SQL instance that isn't involved with BE:

12-24-2013,17:50:28 : DRIVER={SQL Native Client};SERVER=XXXXXXX\MICROSOFT##SSEE;Trusted_Connection=Yes

[ddorton]

I actually do not think this is my problem, I read through the log file and found a different problem.  After searching for it online I found this:

http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TECH193392

[Vishal_Shinde]

one of the probable reason for the failure could be as documented in this article:

SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF], error reported in the installation log while in place upgrading from Backup Exec version 12.5 to 2010.
http://www.symantec.com/docs/TECH78403

if the above article is not a match, then the issue seems to be related to client components, network libraries or even the ports used by SQL.

the exact cause can be found from the SQL ERRORLOG.

The default location for the SQL Server error log varies by version.  You can find the paths here:

http://support.microsoft.com/kb/966659

additionally, if it seems to be exactly the same as mentioned in the last post:
http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TE...

then I may insist you to open a ticket with support.

Kind regards,
S