This article provides a list of the common errors you may encounter while connecting to or working with the EDW.
For a list of frequently asked questions, see this article.
Connection Errors
"IP address is not authorized"
Error message pattern:
IP address xx.xx.xxx.xxx is not authorized...
Cause: The connecting IP address has not been added to the Betterview allowlist.
Resolution:
- Note the IP address shown in the error message.
- Submit the IP address to Nearmap support for whitelisting. Our Data Engineering team will add it to the allowlist.
"The server <EDW server name> cannot be found"
Cause: Your company's firewall is likely blocking the connection.
Resolution: Work with your internal IT team to investigate. Common causes and fixes are:
1. Outbound IP not whitelisted by your network
Run the following command to resolve the current IP address of the EDW server:
bash
nslookup <EDW server name>
Add the returned IP address to your network's outbound allowlist.
The IP address returned by nslookup can change periodically and is outside our control. If your connection breaks unexpectedly, re-run nslookup and update your allowlist with the new value.
If your organization requires a full IP range for firewall rules, contact Nearmap support to request the available range. Be aware that the range is large.
2. Outbound traffic on Port 1433 is blocked
The EDW uses the standard SQL Server port (1433). If your network restricts outbound SQL traffic, work with your IT team to open a specific exception for the EDW database on port 1433.
Database Name not recognized / connection string errors
Cause: The database name BVDW was not explicitly included in the connection string.
Resolution: Ensure your connection string includes the database name. For example:
Server=<EDW server name>;Database=<EDW database name>;User Id={username};Password={password};
Data Issues
Data is missing or has not refreshed
Before contacting support, confirm the following:
- The relevant batch orders were submitted and completed before 3:00 PM the previous day.
- You are querying after the nightly refresh window (2:00 AM PST / 5:00 AM EST).
If the issue persists:
- Collect the Client Name and Bulk Order ID(s) for the affected records.
- Include any SQL queries being used to test for the missing data.
- Submit to Nearmap support for our Data Engineering team to investigate and provide a root cause and possible resolution..
Subscription change not reflected in the EDW
Cause: Subscription changes do not automatically trigger an update in the EDW.
Resolution: Contact Nearmap support for our Data team Engineering to perform a manual refresh.
Getting further help
For issues not covered here, contact us, and include as much detail as possible including:
- Error message or screenshot
- IP address (for connection issues)
- Client name and Bulk Order ID (for data issues)
- SQL query being run (for data or refresh issues)