span8
span4
span8
span4
The FME log file message starts reporting with:
"MS SQL Server Reader: Failed to connect using SQL Server 2012 Native Client,trying to use SQL Server 2008 Native Client."
This message is shown when there is a problem with the connection being bad with the SQL Server database.
It can be followed by numerous Provider Error messages.Some of those reported are:
There are several causes for the Provider Error messages:
For causes 1-5: Ensure the user can connect to the SQL Server system with another client application and ensure they can access the table(s).
For cause 6: Ensure that the drivers for SQL Server are in the same bit version of FME.This is less likely to be the issue as usually 32bit and 64bit drivers are installed on 64bit Microsoft Systems.
For cause 7: Ensure you visit the link found in the log message and install the drivers.If you get a message that the drivers are already installed consider testing the opposite FME bit version then the one installed or find the other bit version of the SQL Server Native Client drivers.
For causes 6 and 7you'll need to install a SQL Server Native Client.You can confirm the version of your existing Native Client by looking for theCurrentVersioninformation in the registry.If you have a 64 bit client it will be here - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server Native Client xx.x A 32 bit client will be here HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server Native Client xx.x
For cause 9 (**)you'll need to get the correct bit version installed of Microsoft System CLR for SQL Server 2012 or Microsoft System CLR for SQL Server 2012 (x64).Both can be installed.
FME Desktop and FME Server should install the appropriate SQL Server Native Client.If a specific version of the SSNC is needed then this linkhttps://www.microsoft.com/en-us/search/result.aspx...returns a list of SQL Server Feature Packs.
[At the time of creating this article the URL above returns the list of SQL Server Feature Packs in the image.Let us know via the comments if the URL stops working.]
Click the appropriate version and locate theInstall Instructionsbutton
In the expanded list locate theSQL Server Native Clientyou wish to install.Consider the bit version of your FME software you are using and download that SQL Server Native Client software.Not all Clients have separate installers for 32bit and 64bit software.
Here is an example of the SQL Server 2012 Native Client information:
For cause 8: The known issue in the Joiner has been fixed in FME 2015.1.1.Download FME Build 15515 or greater.
NOTES: There is no SQL Server 2014 Native Client.Use the SQL Server 2012 Native Client for connecting to SQL Server 2014 instances.
host,port ex: --> proserve1,1234OR
host\instance,portex: --> proserve1\support,1234If you are using the Microsoft SQL Server Non-Spatial (JDBC) also try the above syntax.However,you may need to use a colon (:) for JDBC depending on the version of FME.
host:port ex: --> proserve1:1234I believe we have standardized on a comma in more recent versions of FME.
FME is loading features with invalid geometries into my Database
Performing spatial queries on database tables using the FeatureReader
Converting to PostGIS: Write to an Existing Table
Viewing and Inspecting PostGIS Data
Viewing and Inspecting SQL Server Data
Converting to PostGIS: Create,Drop or Truncate a Table
Writing to Database Tables that contain Multiple Geometry Columns
Converting to SQL Server: Create,Drop or Truncate a Table
© 2019 亚搏在线Safe Software Inc |Legal