Quantcast

MS SQL Server Spatial Provider - Unable to Connect

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

MS SQL Server Spatial Provider - Unable to Connect

Greg
Using Maestro ver 6.0.0.63 I am unable to connect to a MS SQL Server database on a remote server.  I am able to connect to a copy of the database on the localhost.  The error in Maestro is "The remote server returned an error: (559) MgFdoException". I am able to connect to the remote database using SqlSpatialTools build 3759 and query the table with spatial data.  The remote version is running on the default instance of sql server.  Using the same credentials for all connections.  Also tried with sa credentials and it still didn't work.  Log entry (shown below) says Native Client 10.0 required.  Native Client 10.0 is installed on both the local and remote sql servers.

Remote Server
Windows Server 2008 R2
MS SQL Server Standard Edition (64-bit) v 10.50.6000 SP3 (2008 R2)
Mapguide OS 3.1 (64bit)

Locahost
Windows 10
MS SQL Server Express Edition with Advanced Services (64-bit) v 10.50.4042 SP2
Mapguide OS 3.1 (64bit)

The Mapguide server logs the following error:

<2017-02-16T12:35:29> 2400 MapGuide Maestro v6.0.0.63 10.0.0.128 greg
 Error: An exception occurred in FDO component.
        Error occurred in Feature Source (Session:54099516-f47e-11e6-8000-90b11c34bb0b_en_MTI3LjAuMC4x0AFC0AFB0AFA//0479af0e-fb2f-437f-a5b3-5d603d362f26.FeatureSource): An exception occurred in FDO component.
        Please install 'SQL Server Native Client 10.0' or upper to be able to use the provider
       
        - MgFdoConnectionManager.Open() line 333 file c:\working\build_area\mapguide\3.1.0\x64\mgdev\server\src\common\manager\FdoConnectionManager.cpp
        - MgFdoConnectionManager.CacheFdoConnection() line 1097 file c:\working\build_area\mapguide\3.1.0\x64\mgdev\server\src\common\manager\FdoConnectionManager.cpp
        - MgFdoConnectionManager.Open() line 1089 file c:\working\build_area\mapguide\3.1.0\x64\mgdev\server\src\common\manager\FdoConnectionManager.cpp
         (Cause: , Root Cause: )
 StackTrace:
  - MgFeatureServiceHandler.ProcessOperation() line 83 file c:\working\build_area\mapguide\3.1.0\x64\mgdev\server\src\services\feature\FeatureServiceHandler.cpp
  - MgOpTestFeatureSourceConnection.Execute() line 100 file c:\working\build_area\mapguide\3.1.0\x64\mgdev\server\src\services\feature\OpTestFeatureSourceConnection.cpp
  - MgServerFeatureService.TestConnection() line 244 file c:\working\build_area\mapguide\3.1.0\x64\mgdev\server\src\services\feature\ServerFeatureService.cpp
  - MgFdoConnectionManager.Open() line 366 file c:\working\build_area\mapguide\3.1.0\x64\mgdev\server\src\common\manager\FdoConnectionManager.cpp
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: MS SQL Server Spatial Provider - Unable to Connect

Greg
For anyone who's interested here's the solution:

Sql server was installed on a separate machine from the mapguide server.  The slq server native client had to be installed on the mapguide server.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: MS SQL Server Spatial Provider - Unable to Connect

TabrizSoftware
This post was updated on .
Hi,
in most of windows server OS the firewalls block sql server network ports by default
you must allow TCP 1433 port in windows firewall in local and remote machine
Loading...