!Error Messages FAQ

When Analytics Edge encounters an error that it can’t handle automatically, the macro or query refresh stops running and the error message appears in the Task Pane or a popup dialog box. If the message is too long for the width of the task pane, you can click the message, and the full text will appear in a popup.

See Errors for a full listing of errors and actions.

Common Error Messages (2020-04):

!addin license failed or !addin not licensed. This usually appears when the trial Premium license has expired or otherwise has a problem. Open the License wizard to find out what the problem is.

Object reference not set to an instance of an object. This usually happens when an unexpected value is encountered. Make sure you are running the latest release, verify the settings and values selected in your query.

403 User does not have sufficient permissions for… This error usually appears when the account selected for a query no longer has access to the item referenced (profile, segment, etc). Verify the settings of your query and your access to the item.

400 Selected dimensions and metrics cannot be queried together. Although Analytics Edge attempts to show only valid combinations of columns or fields, the various APIs have a number of restrictions. Simplify your query until the error goes away, then add selections back one at a time to discover which one is not allowed.

Invalid/missing dates. Usually caused by referencing a cell that does not contain a proper date, or it contains a text representation that is not recognized (2016-10-31 is the recognized format). Note that some connectors (e.g. Google Search) are restricted by the API in the dates that can be queried (e.g. past 90 days).

Other Errors

UPDATE TO THE LATEST RELEASE: when problems occur, patches are posted quickly, so try the latest release and the problem may go away!  If not, please post a bug note in the support forum telling me what you did so I can track it down and correct it.

Connector Error Codes

The connectors make internet calls to various API servers, which may respond with an error code. The common error codes are listed below with typical causes:

400 and/or Bad Request or invalidParameter. The response from the server was not what was expected. Check your query and account credentials.

401 or authError Authorization or
Authentication failure. The login credentials or the API key being used have failed. Verify the API key and recreate (delete and add) the account using the Account wizard. Some APIs (like Moz) are time-sensitive, and your computer date/time MUST be accurate within 5 minutes.

403 and/or Forbidden. The login credentials or the API key being used have failed to provide access to the account configured in the query. Verify that the query is specifying the account you want and that the login credentials actually have access to that account.

Daily Limit Exceeded or dailyLimitExceeded or 
Quota errorAlthough Analytics Edge does not have any query limits, the various API services do. What may appear as a single query in Analytics Edge may actually be many queries to the API service to get all of the data you requested.

404 and/or Item not found. The query failed completely. Check the query parameters being used, such as the campaign id, or web property,

407 and/or Proxy Authentication Required. Your network environment includes a web proxy server. Configure the proxy account and/or password through Microsoft Internet Explorer — Analytics Edge uses those proxy settings automatically.

429 and/or Too many requests, RESOURCE_EXHAUSTED, or Quota exceeded. You have made too many queries and the API server itself has limited you from making more. This is not an Analytics Edge limit – it is an API limit. You may get this error if you are making requests for lots of data with the minimize sampling option enabled, especially when using large date ranges and Date (daily) reporting. Quotas are usually reset daily, some are hourly. With Google Analytics, there is an additional limit to be aware of: too many requests with errors — try too many (10) queries that fail for some reason, and the API will lock you out for an hour.

500 and/or Internal error. This indicates a problem with the server, but it could be that the query parameters created an unacceptable query. Check the query, and try again later.

502 and/or Bad Gateway. More than  one server is involved with your query, and one of them has failed to respond properly. Check your query and account credentials, or try again later.

503 and/or Service unavailable or
There was a temporary error. The server is currently unable to respond properly. Try again later.

504 and/or Gateway timeout. The server could not fulfill the query in the allotted time and has given up. It is likely that the server is overloaded; try again later.