Oh you know it Jason, extremely frustrating...
I did think about submitting it as a defect, but then I thought is it really a defect? After reading up a bit on SS password policies, it does state that non-alphanumeric characters such as: exclamation point (!), dollar sign ($), number sign (#), or percent (%) are valid, it just doesn't specifically say that an ampersand (&) is invalid. So, having said all of that... it would have been nice if MG provided a more description error message, but the question remains, is this a defect? I can definitely submit a defect, if you feel it is. Thanks Warren From: [email protected] [mailto:[email protected]] On Behalf Of Jason Birch Sent: Tuesday, April 06, 2010 5:46 PM To: MapGuide Users Mail List Subject: Re: [mapguide-users] RE: MapGuide connection to SQL Server through ODBC Warren, have you entered a defect ticket for this yet? I _hate_ the problems that take forever to track down and turn out to be something stupid like that. Jason On 6 April 2010 13:34, Warren Medernach wrote: Well... A couple weeks and many testing scenarios later, we have figured out what was happening in this instance of connecting to SQL Server through ODBC. So I thought I would post my findings in the event that it might help somebody at some other time. The SQL Server username password that we were using contained 'special characters' like &, @, !, and MapGuide apparently could not pass these properly.
_______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
