cancel
Showing results for 
Search instead for 
Did you mean: 

Installation of EPO 4.6 fails with Exception caught in ValidateAccountAndSQL

I'm trying to install on Windows Server 2008 R2.  I can connect to the MS SQL Server using SQL Authentication and the SQL Server Management console with the same username and password that I am using to install ePO.

Here is the last part of my EPO460-Install-CustomAction.LOG file:

17:44:15 ePO460CALog: End Prod_UI_GetSQLServerList

17:44:40 ePO460CALog: Start Prod_SetMFSDATABASENAME

17:44:40 ePO460CALog: Start calculateDatabaseNames

17:44:40 ePO460CALog: Setup is going to use the database name of [ePO4_JAVASRV1] for this installation.

17:44:40 ePO460CALog: End calculateDatabaseNames

17:44:40 ePO460CALog: End Prod_SetMFSDATABASENAME

17:44:40 ePO460CALog: Start Prod_UI_ValidateDBServerInfo

17:44:40 ePO460CALog: Start calculateDatabaseNames

17:44:40 ePO460CALog: Setup is going to use the database name of [ePO4_JAVASRV1] for this installation.

17:44:40 ePO460CALog: End calculateDatabaseNames

17:44:40 ePO460CALog: Loading the following DLL for Use: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:44:40 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:44:40 ePO460CALog: String converted successfully to Unicode Escaped format.

17:44:40 ePO460CALog: Unloading the following DLL: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:44:40 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:44:40 ePO460CALog: Loading the following DLL for Use: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:44:40 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:44:40 ePO460CALog: String converted successfully to Unicode Escaped format.

17:44:40 ePO460CALog: Unloading the following DLL: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:44:40 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:44:40 ePO460CALog: Loading the following DLL for Use: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:44:40 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:44:40 ePO460CALog: Unloading the following DLL: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:44:40 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:44:40 ePO460CALog: Loading the following DLL for Use: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:44:40 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:44:40 ePO460CALog: Unloading the following DLL: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:44:40 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:44:40 ePO460CALog: Loading the following DLL for Use: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:44:40 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:45:45 ePO460CALog: Unknown failure testing for UDP on the SQL server [192.168.40.20] for instance [] with return code [8].  Trying to connect using port [1433].

17:45:45 ePO460CALog: Successful connection to MSDE/SQL server [192.168.40.20] for instance [] on port [1433].

17:45:45 ePO460CALog: Unloading the following DLL: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:45:45 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:45:45 ePO460CALog: Loading the following DLL for Use: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:45:45 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:45:45 ePO460CALog: Successful connection to MSDE/SQL server [192.168.40.20] for instance [] on port [1433].

17:45:45 ePO460CALog: Unloading the following DLL: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:45:45 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:45:45 ePO460CALog: Loading the following DLL for Use: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:45:45 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:45:52 ePO460CALog: Exception caught in ValidateAccountAndSQL.

17:46:02 ePO460CALog: Unloading the following DLL: [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}\CommonSetup.DLL]

17:46:02 ePO460CALog: Setting the current directory to [C:\Users\sergio_g\AppData\Local\Temp\{73F1BDB7-11E1-11D5-9DC6-00C04F2FC33B}].

17:46:02 ePO460CALog: End Prod_UI_ValidateDBServerInfo[0].

Here is the bottom of my EPO460-Install-MSI.LOG file

Action start 17:44:39: ConvertDBInfoDialogToUnicodeEscaped.

MSI (c) (58:34) [17:44:39:660]: Invoking remote custom action. DLL: C:\Users\sergio_g\AppData\Local\Temp\MSI98FF.tmp, Entrypoint: ConvertDBInfoDialogToUnicodeEscaped

MSI (c) (58!7C) [17:44:39:675]: PROPERTY CHANGE: Adding MFSDATABASEUSERNAME_UE property. Its value is 'xxxxx'.

MSI (c) (58!7C) [17:44:39:675]: PROPERTY CHANGE: Adding MFSDATABASEPASSWORD_UE property. Its value is '**********'.

MSI (c) (58:34) [17:44:39:675]: NOTE: custom action ConvertDBInfoDialogToUnicodeEscaped unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.

Action ended 17:44:39: ConvertDBInfoDialogToUnicodeEscaped. Return value 1.

MSI (c) (58:00) [17:44:39:675]: Doing action: Prod_SetMFSDATABASENAME

Action 17:44:39: Prod_SetMFSDATABASENAME.

Action start 17:44:39: Prod_SetMFSDATABASENAME.

MSI (c) (58:FC) [17:44:39:691]: Invoking remote custom action. DLL: C:\Users\sergio_g\AppData\Local\Temp\MSI990F.tmp, Entrypoint: f35

MSI (c) (58!B8) [17:44:40:081]: PROPERTY CHANGE: Adding MFSDATABASENAME property. Its value is '

And finally my EPO460-CommonSetup.log

20131208180140 Connected to server 192.168.40.20 on port 1433.

20131208180140 Entered CanConnectToHostAndPort function to test host [192.168.40.20] with port [1433].

20131208180140 Calling getaddrinfo() to convert the host name [192.168.40.20] to an IP address.

20131208180140 Connected to server 192.168.40.20 on port 1433.

20131208180140 Entered ValidateAccountAndSQL function.

20131208180140 Calculating the DataSource for your SQL server.

20131208180140 UDP port is not enabled so configuring DataSource to use port number instead.

DataSource used: [192.168.40.20,1433]

20131208180140 Setting connection string DataSource to [192.168.40.20,1433].

20131208180140 Connection string set for SQL Authentication database connection.

20131208180140 SQL::connect to server 192.168.40.20

20131208180140 Testing SQL Authentication to SQL Server.

20131208180140 Connect to SQL server successful.

20131208180140 Validating SQL permissions for user [dbo] using validateUserIsDBO.

20131208180141 Passed function validateUserIsDBO.

20131208180141 SELECT @@VERSION returned: Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)

          Apr  2 2010 15:48:46

          Copyright (c) Microsoft Corporation

          Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

20131208180141 Found MSDE/SQL version to be [10.50.1600.1] for the selected server.

20131208180141 Setup has detected SQL 2008 SP 1 or higher so allow install.

20131208180141 sp_helpsort returned: Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode Data

20131208180141 Detected Case-Insensitive(CI) collation for SQL server.  Allowing setup to continue using this SQL server.

20131208180141 Passed function validSQLCollation

20131208180141 Server = [192.168.40.20]  Instance = [MSSQLSERVER]

20131208180141 Retreived the SQL Server with Instance Name as: [DEVFS]

20131208180141 IP Address [192.168.40.20] detected for server name so converting to host name.

Any help would be appreciated.

Thanks,

Sergio

10 Replies
ulyses31
Level 16
Report Inappropriate Content
Message 2 of 11

Re: Installation of EPO 4.6 fails with Exception caught in ValidateAccountAndSQL

Hi Sergio, it looks like ePO installer can connect to SQL as it can get its installed version, so wich error are you seeing during ePO install? Maybe some screenshot can help.

Re: Installation of EPO 4.6 fails with Exception caught in ValidateAccountAndSQL

Laszlo,

I get a popup that just says Exception caught in ValidateAccountAndSQL and it does not let me proceed from there.

If I try to continue, I get the same popup.  Cancelling and trying to reinstall results in the same thing.

Thanks,

Sergio

ulyses31
Level 16
Report Inappropriate Content
Message 4 of 11

Re: Installation of EPO 4.6 fails with Exception caught in ValidateAccountAndSQL

The password you're using for this user does it contain any special character?

Re: Installation of EPO 4.6 fails with Exception caught in ValidateAccountAndSQL

No.  Just standard alphanumeric. No special characters.

ulyses31
Level 16
Report Inappropriate Content
Message 6 of 11

Re: Installation of EPO 4.6 fails with Exception caught in ValidateAccountAndSQL

And the windows session you are logged when installing ePO is it using spcial chars in user or password?

Are you using the ePo's default SQL instance name (EPOSERVER) or a different one? You can also try (if you haven't done it yet) to use IP addres of SQL server instead of name

Re: Installation of EPO 4.6 fails with Exception caught in ValidateAccountAndSQL

I'm using SQL Server Authentication and not domain authentication.  I've tried using the IP address and the server name.  Same result in both cases.

I'm running the Custom Installation and connecting to an existing SQL Server.  I can connect to the SQL Server using the same credentials that I am passing to the ePO installer.  As you can see, the installer is trying to create a database called ePO4_JAVASRV1 on the SQL Server.  As you can also see, the connection to the server is successful.  It is somewhere farther along that the installation fails.  I have verified that the database is not created and does not already exist on the server.

rackroyd
Level 16
Report Inappropriate Content
Message 8 of 11

Re: Installation of EPO 4.6 fails with Exception caught in ValidateAccountAndSQL

if you have not found them already it's probably worth going through these two McAfee support articles first:

KB71825 - ePolicy Orchestrator 4.x installation / patch upgrade checklist for known issues.

KB75766 - SQL permissions required to install and use ePO.

You will find lots of useful notes between them about Sql account requirements and other things.

dnf
Level 10
Report Inappropriate Content
Message 9 of 11

Re: Installation of EPO 4.6 fails with Exception caught in ValidateAccountAndSQL

sgeralnik, did you find the solution?

Re: Installation of EPO 4.6 fails with Exception caught in ValidateAccountAndSQL

No.  In the end, I ended up creating a new SQL Server instance on the same server and installing to there.  That seemed to work without an issue.  This is being used for evaluation purposes so it is not a major issue at this time.