WebGate plug-in is unable to contact any Access Server

One of the most common error in OAM is "WebGate plug-in is unable to contact any Access Server".

First of all, there are many reasons for this error to happen. Most of the time it is environment specific and hence, there is no straight forward/standard solution to this error.

However, the issue must be resolved if following points are verified to be working

1. As the error clearly states that webgate is not able to connect Access Server. There could be a connection problem between webgate & Access Server. check if firewall is terminating the connection between webgate & Access Server.

2. Check if the Access Server is up & running by issuing netstat command and look for the Access Server ip and port number.

3. Check if other webgates connected to Access Server is able to connect. If other webgates are connecting then it rule out the problem with Access Server.

4. Restart Access Server and Webserver. If restarting resolves the issue it means that while restarting Access Server terminates the old connections and new connection is being established.

5. Make sure all the components involved in OAM architecture is working fine for ex: directory server, load balancer, firewalls, database etc.

6. If it is a new installation, then verify the clock settings of Access Server host and webgate host. Access Server clock must be running ahead of webgate.

7. Verify the webgate diagnostic page. http(s)://hostname:port/access/oblix/apps/ webgate/bin/webgate.cgi?progid=1. If the page is not opening then webgate is not installed correctly.

8. If the Access Server and Webgate are configured in CERT mode then check if certificate is Valid.

9. Change the log level to TRACE and diagnose the oblog.log file for Access Server and Webgate.

Enable or Disable WebGate Plug-In on IIS 7.5

1.    Go To Internet Service Manager.
2.    Expand the local computer by clicking +, in the left panel.
3.    Click to expand the required Web Sites tab.
4.    Right-click Web Sites in the Internet Information Services tab, click Properties, and perform the following steps:
a.    From the Internet Information Services tab, click the Edit button.
b.    Locate the ISAPI filter tab to confirm (or add) the filter DLLs, as follows:

Filter: If you updated the IIS Web server configuration file, webgate.dll should be properly located. –

Disable : Stop IIS, remove the existing WebGate entry and Start the IIS for changes to take effect

Enable : Stop and Add the WebGate entry as follows and Restart the IIS for changes to take effect

No Filter: Add the webgate.dll filter from Webgate_install_dir\oblix\access\apps\webgate\bin\webgate.dll

E.g: OracleWebGate - Webgate_install_dir\oblix\access\apps\webgate\bin\webgate.dll
c.    Save and apply any changes.