Using special characters in the SQL connection string config.txt

This came to light recently and wanted to post here for others that might experience it.

A company set up AyaNova configured for use with SQL Express.

Their sa user password included the character &

When they ran AyaNova on the server for step #6 of the SQL networking steps, they received the following error (no splash screen came up, just went immediately to error message):

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: ayanova.exe
Problem Signature 02: 7.0.3.0
Problem Signature 03: 4d76755b
Problem Signature 04: System.Xml
Problem Signature 05: 4.0.0.0
Problem Signature 06: 4ba1dfec
Problem Signature 07: 710
Problem Signature 08: 27
Problem Signature 09: System.Xml.XmlException
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 3081
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

When I tested with SQL Express and a password that used the & character, if I replaced the & with &amp (as in a password that was passwrd& changed it to passwrd&amp) was able to connect with no further issue.

The company was not able to use even using &amp

Instead to resolve they would do either of the following:
1 - that the password for the sa user in SQL be changed to not include the & character;
2 - or another suggestion is to use integrated security=true; as per the bottom of step #7 of the SQL networking steps (after have set up the computer usernames in SQL of course)

  • Joyce