Skip to main content

Common Issues

Unable to Connect Even After Whitelisting Agave's Static IP Addresses​

If you have whitelisted Agave's static IP addresses and you still cannot connect, there are a few steps you can take:

Step 1: Allow Remote Connections to the Server​

  1. On your Windows machine, open Microsoft SQL Server Management Studio and log in:

  2. Right-click on the server, and select Properties:

  3. Select Connections, then check "Allow remote connections to this server":

  4. Re-try authenticating with your Foundation/Spectrum/Vista credentials in Agave Link. If you are still encountering issues, try Step 2.

Step 2: Enable TCP/IP in SQL Server Configuration Manager​

  1. On your Windows machine, open SQL Server Configuration Manager:

  2. Expand SQL Server Network Configuration Protocols and select the database you are using (e.g. SAGE100CON). Right-click on TCP/IP and set to "Enabled":

  3. If you have firewall rules enabled, right-click on TCP/IP and select Properties:

  4. Select the IP Addresses tab, then scroll down to IPAll. Map the external port you are using for the Agave Link connection to either the "TCP Dynamic Ports" or "TCP Port" (whichever is being used for the Agave Link connection):

  5. Re-try authenticating with your Foundation/Spectrum/Vista credentials in Agave Link. If you are still encountering issues, contact support@agaveapi.com.

Unauthorized After Creating a User and Enabling Write Permissions​

If you are still unable to execute stored procedures or make write requests after creating a user and enabling write permissions, it's possible your user might not have the correct database role membership(s).

To confirm:

  1. In Microsoft SQL Server Management Studio, go to Security --> Logins.

  2. Right click the relevant login (e.g. "Agave") and select Properties.

  3. Go to User Mapping and confirm they have the following database role membership for the database you are using:

    • db_datareader
    • db_datawriter
caution

Make sure that the option for db_denydatawriter is unchecked as well.