by David Crowther
Question:
When running an import into an SQL Spatial Database I receive the error below in the Error Log for the Spatial Importer tool. What is causing this error?
Answer:
This issue relates to the available Drivers on the machine that is running the Spatial Importer tool.
The Error log records that the default driver which is trying to make the connection to your SQL Database is – SQL Server Native Client 11.0.
By searching for ODBC Data Sources on your machine…..
you can then check which Drivers you currently have installed and therefore available to you:
In this example the default Driver that the Spatial Importer uses - SQL Server Native Client 11.0 - is not available in the list. As such the import fails to make a successful connection to the SQL Database.
To resolve this issue, you can define which SQL Driver you wish the Spatial Importer to use.
From the location where the Spatial Importer is installed – likely C:/programdata/Cadline/Spatial Importer/ open the STATIMP file in a notepad.
Within the notepad edit the line item that refers to the MSODBC DRIVER.
For example, I have edited this to now use a SQL Driver that is installed on my machine - ODBC Driver 11 for SQL Server
Save the changes to the STATIMP file and then re-run the Spatial Importer tool, and this time the import will be successful as the Importer uses an available SQL Driver to connect to your SQL Database.
Comments (0 comments)