There are two entries in the DNS for this. Not sure how you managed to do that (our system shouldn’t allow it). Basically, you added a web service with the name ‘mysql.reliancedamages.com’. You then added a MySQL database (on a different machine) with the SAME hostname. You can’t do that - the name has to be unique.
That said, the bug is on our side, because you’re not supposed to be able to do this. I’ll let our developers know, but in the meantime, remove the web service for ‘mysql.reliancedamages.com’, wait for the DNS to update again, and you’ll be fine. Alternately, change the MySQL hostname to something else.
Oops…rats, thought for once it would be something that wasn’t my fault!
Ok, removed the web service. Thanks!
I forced an update; should be totally working now in 2 hours or less.
[quote]Oops…rats, thought for once it would be something that wasn’t my fault!
Well it’s all a matter of perspective; I’d consider this mostly our fault, especially since it’s a problem we’ve fixed before. Just because something is obvious to us doesn’t mean someone else won’t find a way to break it.
Note… this bug should now be fixed (after CVS gets pushed out anyway). Customers… do your worst (and thanks to Sage for fixing the bug)!