I had a DSN that, for some reason, would stop working after I restarted MX. When I would go in an edit the DSN, I noticed the wrong data was set in the fields. At first, I thought it was Mozilla and it's "auto-form" fill-in thing, but it turns out I was wrong. Steven Erat of Macromedia suggested that I check out my jrun-resources.xml file and see if any DSNs were duplicated. Sure enough, I had multiple copies of multiple DSNs. I removed the duplicates (after first shutting down MX of course), and when I restarted, my DSN worked just fine. Steven gave a long explanation of why this is so, but for now, I'll just post this tip as something to look for. Of course, the usual warnings apply when working w/ MX's native XML files.
(This post is more than 2 years old.)
DSN and MX Restart Problems
Hire Me!
I'm currently looking for my next role in developer evangelism and advocacy. I have a long history of helping companies work with developers and love to write, create demos, and present at confereneces. You can find my resume to learn more and drop me an email (raymondcamden@gmail.com) to reach out.
Support this Content!
If you like this content, please consider supporting me. You can become a Patron, visit my Amazon wishlist, or buy me a coffee! Any support helps!
Want to get a copy of every new post? Use the form below to sign up for my newsletter.
Archived Comments
For a detailed explanation, see my blog entry here:
http://www.talkingtree.com/...
I''ve had this happen several times as well. It''s particularly annoying!
-Rob