Video Screencast Help

Backup Exec 11d installation error message V-225-230: ERROR SQLExecDirectW() Failed

Created: 15 Jan 2008 • Updated: 21 May 2010 | 4 comments
Windows Server 2003 R2 Standard Edition (32 bit) with SP2
MS SQL 2005 with SP2
Backup Exec 11d  7170
 
I have had to create a second instance in SQL for the BE database because the default instance is using case sensitive collation (which BE doesn't like). The second instance is called BACKUPEXEC and the collation option was the default suggested (Dictionary order, case in-sensitive, for use with 1252 character set).
 
When I install BE 11d into the second SQL instance it seems to be working but starts "rolling back" and comes up with the "wizard was interrupted" message.
Looking at the log I can see the following errors:
 
.
.
.
01-15-2008,09:26:24 : Connected to SQL Server.
01-15-2008,09:26:24 : SQL Server version 9
01-15-2008,09:26:24 : Connected to SQL Server.
01-15-2008,09:26:24 : Registry key name for instance MSSQL.3, has been obtained.
01-15-2008,09:26:24 : V-225-230: ERROR - SQLExecDirectW() Failed ***To search for information about this error, click here
01-15-2008,09:26:24 : DRIVER={SQL Native Client};SERVER=GVL0002\BACKUPEXEC;Trusted_Connection=Yes;DATABASE=
01-15-2008,09:26:24 : Connected to SQL Server.
01-15-2008,09:26:24 : SQL Server version 9
01-15-2008,09:26:24 : Connected to SQL Server.
01-15-2008,09:26:24 : Registry key name for instance MSSQL.3, has been obtained.
.
.
.
.
01-15-2008,09:29:05 : Installing BE database.
01-15-2008,09:29:05 : Executing CLUS_InitData
01-15-2008,09:29:05 : InitData failed to open the cluster wrapper
01-15-2008,09:29:05 : Executing CLUS_InitData
01-15-2008,09:29:05 : InitData failed to open the cluster wrapper
01-15-2008,09:29:05 : m_bUseNativeClient = 1
01-15-2008,09:29:05 : Executing Attach_BEDB.
01-15-2008,09:29:05 : There is no MSSQL$BKUPEXEC Service
01-15-2008,09:29:05 : V-225-210: Unable to connect to SQL Server. ***To search for information about this error, click here
01-15-2008,09:29:05 : V-225-118: Error installing BEDB ***To search for information about this error, click here
01-15-2008,09:29:05 : Action ended 09:29:05: InstallFinalize. Return value 2.
01-15-2008,09:29:05 : Action 09:29:05: Rollback. Rolling back action:
01-15-2008,09:29:05 : Configuring Symantec Backup Exec. Please wait...
01-15-2008,09:29:05 : RB_ConfigInstall
01-15-2008,09:29:05 : Rolling back install of BE services.
01-15-2008,09:29:05 : Rolling back install of BE database.
.
.
.
 
 
Any suggestions would be greatly appreciated.
Thanks
 
 

Comments 4 CommentsJump to latest comment

Ben L.'s picture

This is a known issue that we are currently working on.  Please review the following technote.

http://support.veritas.com/docs/291039

If this response answers your concern, please mark it as a "solution"

Laminate's picture
But I have implemented the workaround according to the article.
I have installed a second SQL instance and specified case IN-SENSITIVE and I get the error in my first message.
 
Is there anything else I can be checking?
radicalsupport's picture
I'm having this exact same issue. Server 2003 std SP2, brand new install. 



Message Edited by radicalsupport on 01-17-2008 05:51 AM

radicalsupport's picture
Ok after more and more examination... I downloaded and installed the XML4 SP2 msi from MS and that installed fine. Trying again produced error:

error 1305. error reading from file BE~.msi verify that the file exists and that you can access it

Searching for that reveals that SYSTEM needs full control. Added it, All is good.

I did NOT have Exchange 2007 btw, only 2003.