TAM Integration Errors

Description

When you test the WSAPI Web Services you get the following error message:

Connection Failed

Resolution

To resolve the connection failure, verify the below options:

1. Is your TAM Web Services credential case sensitive? BenefitPoint requires that the user id, password, and operator id needs to be entered in all CAPS.
2. Is your TAM In-House Web Services license still active? Was there a recent upgrade to the TAM In-House server? If the BenefitPoint paid TAM license has expired a new license should be obtained from Applied customer support.
3. Was there a successful run of TAM In-House Demo Test connection applet?
4. When was the last time the user able to make a successful BenefitPoint to TAM Web Services connection?
5. What version of TAM In-house is being used? What's the version of TAM In-House WSAPI Web Services?

Follow the steps below to test the connectivity:

In some situations , the TAM In-House Web Services endpoint can be executed within a browser outside of your network to determine if the Connexion's page is accessible.This test can also confirm that your SSL security certificate is valid.

1. Click on the Pad Lock icon next to the URL within Internet Explorer's browser.
2. Click on View Certificate.
3. Click on Certification Path - confirm the TAM Web Services URL matches the URL used in BenefitPoint.
4. In addition to using a browser connection, using a Windows TELNET connection can confirm if the site is accessible outside the customer's network. For Example: From a Command/DOS window, type TELNET customers URL 443. (TAM webserver.CustomerDomainName.com 443).
5. If it returns a window with a blinking cursor, the connection is successful. If it returns , "Connecting To . . ." , telnet is unable to connect.
6. To confirm that it is not a firewall, DNS, and/or PROXY issue, request that the security can be temporarily opened for their TAM WSAPI endpoint to be access outside of their network from a browser.
7. Log on as a BenefitPoint User, download the BenefitPoint Error Log file to search for connectivity errors.

Description

When posting a RTM Statement that integrates with TAM, you notice a message similar to the following in the error log:

Number: 00190

Description: null

Source: AXT::Failed to insert transaction

TAMErrorNumber: 10006

TAMSource: ASBPOL.TamPolicy.InitObject

TAMDescription: Unable to find record

Resolution

This error can occur when the Account or the Plan/Product are not correctly mapped to TAM.

First verify if the TAM Policy Index matches with the Policy ID in TAM:\.

1. Note Account ID and Product ID for the transaction that logged into the error log.
2. Log on to BenefitPoint as a Broker user.
3. Using the Global Search drop-down list select BP Internal Plan/Product ID.
4. Enter the BP Internal Plan/Product ID and click Search.
5. Compare the TAM Policy Index in BenefitPoint with the Policy ID in TAM, ensure these match.
6. If they match, in the Global Search drop-down list select BP Internal Account ID.
7. Enter the Account ID and click Search.
8. Compare the TAM Customer ID in BenefitPoint with the Client ID in TAM.
9. If all information is correct, save the account, and check if any further errors are logged into the error log.
   
   

If the integration ID’s do not match, change them in TAM. And then, correct the TAM Customer ID in BenefitPoint.

1. Log on to BenefitPoint as a Broker Admin user.
2. On the top navigation bar click Brokerage Info.
3. On the top navigation bar submenu click Applied TAM Integration.
4. Click the Associations tab.
5. Search for the account.
6. Update the TAM Customer Code.
7. Click Save.