ODBC FDO connection to SQL Server fails with a password containing an ampersand

[warrenmedernach]

When attempting to connect to SQL Server via the ODBC FDO Provider, if the SQL Server username password contains an & (ampersand) character, the connection will fail.

If this is being tested in a localized environment with Studio on the same machine as the MG Server the following error message is returned if Bob&Doug is used as a password:

Feature Source - Unterminated entity reference, 'Doug'

If however, this is tested in an environment with MG and SQL Server on seperate machines and accessing with Studio on a client machine, the error returned is:

response returned status code 502 (BadGateway)

[jng]

This sounds like an issue with the editing clients moreso than the MG server. (ie. Maybe Studio is failing to properly escape this data before sending the updated document back to the MG server)

Does this affect Maestro as well?

[tomfukushima]

Good idea on checking with Maestro as well. If Maestro works, then we know the problem is most likely in Studio.

[warrenmedernach]

I've tried testing this in Maestro, but unfortunately, I cannot get Maestro to validate anything other than 'No credentials'. When I try to specify the credentials it reports:

The remote server returned an error: (559) MgResourceTagNotFoundException.:

Resource tag was not found: %MG_USERNAME%

[jng]

Definitely a tooling issue