Enterprise Vault cannot access the FSA Reporting Web Service at '<https://FSAReporting/FSAreporting.asmx>'

book

Article ID: 100021168

calendar_today

Updated On:

Description

Error Message

Enterprise Vault cannot access the FSA Reporting Web Service at ''

Cause

Within the EnterpriseVaultDirectory database there is a table called FSAReportingWSLocations. Within this table there should be one entry per Enterprise Vault (EV) server within the EV Site. The table has 3 columns named WSLocationID, SiteEntryID and WSLocation

In this instance, one entry did not have a value in the WSLocation column as shown below:

WSLocationID   SiteEntryId     WSLocation

1 1535FC45C56B3D3488FE092D5B92F40F21d10000evalias http://VAULT1

2 1535FC45C56B3D3488FE092D5B92F40F21d10000evalias http://VAULT2

3 1535FC45C56B3D3488FE092D5B92F40F21d10000evalias
 

Resolution

To correct this issue, the correct value needs to be added to the table.
This entry should be:  https://"Hostname of Vault Server" as shown in the above example.
Before making this change, backup the EnterpriseVaultDirectory database and run the query below:
 
-- If the third server is VAULT3 the update would be as follows. 
Use EnterpriseVaultDirectory
Update FSAReportingWSLocations
Set WSLocation = 'https://VAULT3' where WSLocationID = enter value from WSLocationID column
 
If the issue is not resolved, it may be necessary to use the FQDN of the server to resolve the issue.  All entries should be updated with the FQDN of the EV server. 
 
-- If FQDN is VAULT3.EVLOCAL.COM 
Use EnterpriseVaultDirectory
Update FSAReportingWSLocations
Set WSLocation = 'https://VAULT3.EVLOCAL.COM' where WSLocationID = enter value from WSLocationID column

 

Issue/Introduction

When accessing the properties of a file server target in the Vault Administration Console or at the File Servers level the error is returned. This can occur for both HTTP or HTTPS connections.
Powered by Wolken Software