Access to OData datasets fail after changing the default TCP/IP ports used by Compliance Accelerator or Discovery Accelerator

book

Article ID: 100045109

calendar_today

Updated On:

Description

Error Message

In a web browser:

The website cannot display the page   HTTP 500

This page can't be displayed

Cause

The default TCP/IP ports used by CA and DA can be changed to any other port that is not used by another application.  These port changes allow access to the top level datasets exposed for OData use but going to the Customer level or below fails.  For example, access to http://localhost/CAReporting/OData/$metadata succeeds but access to http://localhost/CAReporting/OData/Customers fails.

A workaround exists to allow access to the OData datasets when the default ports are changed.

Workaround steps:

1. Log onto the CA / DA server using an account that has local Administrator privileges, such as the Vault Service Account (VSA).
2. Open an Administrative Command Prompt.
3. Type into the prompt window and execute the command net stop "Enterprise Vault Accelerator Manager Service" to stop the Enterprise Vault Accelerator Manager Service (EVAMS).
4. Type into the prompt window and execute the command iisreset /stop to stop all IIS services.
          Note, leave this Administrative Command Prompt open until instructed to close it.
5. Launch Windows Explorer.
6. Navigate to the CAReporting / DAReporting folders located in the CA / DA installation folder.
     For CA, the default location is C:\Program Files (x86)\Enterprise Vault Business Accelerator\CAReporting
     For DA, the default location is C:\Program Files (x86)\Enterprise Vault Business Accelerator\DAReporting
7. Locate and select the file web.config.
8. Make a backup copy of this file.
9. Edit this file in a text editor such as Notepad.
10. Locate the section that should be near the top of the file or by using the Find feature to search for .
11. Add the following line before the section end line of :
         
12. Change the port number 8086 to the new port number used for the CA / DA Client access to the server.  For example. if the default TCP/IP port 8086 is changed to 15051, change "8086" to "15051".
13. Save and close this file.
14. Return to the Administrative Command Prompt window.
15. Type into the prompt window and execute the command iisreset /start to start all IIS services.
16. Type into the prompt window and execute the command net start "Enterprise Vault Accelerator Manager Service" to start the Enterprise Vault Accelerator Manager Service (EVAMS).
17. Close the Administrative Command Prompt and Windows Explorer.
18. Log off of the CA / DA server.
19. Restart the application used to access the OData datasets.

Upon successful completion of the above steps, access to the datasets exposed for OData use should be returned.

 

Resolution

This issue is fixed in EV 12.4.2, which is available in the Download Center, please go to support.veritas.com to obtain this update.

 

Issue/Introduction

Compliance Accelerator (CA) and Discovery Accelerator (DA) use TCP/IP ports 8085 and 8086 for communications between servers and client installations. Access to the datasets that have been exposed for OData use also uses TCP/IP port 8086. These ports can be changed by editing certain configuration files in the event the default ports are used by another application. When these default ports are changed, access to the CA and DA datasets that have been exposed for OData use fails when attempting to access the Customer and below data.

Additional Information

JIRA: CFT-1859 SW Download: UPD699547