Tip for those who see any of these EV Deployment Scanner Errors

[LarryW]

If you see any of the following errors:

EV10SQL: Unable to determine if SQL Server Reporting Services are installed. Reason: Unable to connect to the server.

EV10SQL: Unable to determine the version of the MXSML component. Enterprise Vault requires MSXML 6.0 or later. Without this FSA Reporting cannot be configured. Reason: Access is denied.

EV10SQL: Unable to determine the version of the SQLXML component. Enterprise Vault requires SQLXML 4.0 or later. Without this FSA Reporting cannot be configured. Reason: Access is denied.

EV10SQL: Unable to determine whether FIPS is enabled. If FIPS is enabled and you are planning to use Enterprise Vault Reporting, see the following technical note on the Symantec Support Web site: http://www.symantec.com/docs/TECH171120. Error returned: Access is denied.

TIP:  Go to your Microsoft SQL server.  Click Start/Administrative Tools/Computer Management, go into System Tools/Local Users and Groups/Groups, double click onto the Administrators group and add your vault admin domain account to this group.  When running deployment scanner you should be logged in with this same account.

[JesusWept3]

Just be aware that when you do that, the EVAdmin account will now be an SA in SQL Server and may negate a companies policy that no account can be a SysAdmin in SQL

[GertjanA]

Hello JW.

Are you sure that if an account is placed in the Local Administratos group, it is SA in SQL?

I thought that needed specifically to be set in SQL

[ia01]

I have checked SQL 2008 R2. By default, the local Windows Group BUILTIN\Administrators is no longer included in the SQL Server sysadmin server role on new SQL Server 2008 R2 installations.