[mapguide-users] RE: MapGuide connection to SQL Server through ODBC

[Warren Medernach]

Thanks for the speedy response Dave!

I think I should clarify more.

 

If I create a UDL, or ODBC, connection on the MG Server machine to the
SQL Server on the other machine it works fine.  I'm trying to create a
connection to SQL Server from Studio via the ODBC FDO Provider and
choosing the 'Connect to a database' and 'Microsoft SQL Server' and then
specifying the credentials and proper connection string.  This is
failing.  So I'm not sure what MG is doing differently to communicate
with the SQL Server?

 

As for port 1433, that would need to be open on both machines for the
'handshake' communications, correct?  I wonder if that's the problem...

 

Warren M

 

 

From: mapguide-users-bounces at lists.osgeo.org
[mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Dave Wilson
Sent: Monday, March 15, 2010 2:29 PM
To: MapGuide Users Mail List
Subject: [mapguide-users] RE: MapGuide connection to SQL Server through
ODBC

 

I have an instance in house where the connectivity fails because of a
setting to do with the port in the ODBC configuration.

 

When setting up the ODBC configuration there is a button for Client
Configuration, click this and uncheck the dynamically determine port.
1433 should be shown in a grayed out box.

 

That might be the issue.

 

Dave

 

From: mapguide-users-bounces at lists.osgeo.org
[mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Warren
Medermach (External)
Sent: Monday, March 15, 2010 2:16 PM
To: MapGuide Users Mail List
Subject: [mapguide-users] MapGuide connection to SQL Server through ODBC

 

Hello all,

I'm trying to make a connection to SQL Server through ODBC using MG
Studio.

This works fine on a local test system where MG server & SQL Server are
installed on the same machine.

 

When deployed, MG Server is NOT installed on the same machine as SQL
Server.

In this scenario, I can create a UDL on the MG server machine and
successfully connect to SS with no problems.

However, when I try to create a data connection in MG, it fails with the
following error:

response returned status code 502 (BadGateway)

 

It would seem that something on the SQL Server machine is blocking the
connection request from MG.  So the question is, what is MG doing
differently than a simple UDL connection to communicate with the SQL
Server machine? 

Any ideas, suggestions would be greatly appreciated.

 

MGE 2010

SQL Server 2005

 

Warren M

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20100315/eb344fee/attachment.html