We're running Optigold 3.3.4, with Profdata PDM Plugins on Windows 2000 Pro. Today, our "Auto Server Restore From Hold" script stopped working. Our server events use SQL to connect to our radius database, which uses mysql. We receive an error stating that the: URL or datasource are invalid: [Microsoft][ODBC Driver Manager] Data Source name not found and no default driver specified SQLException: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified I've verified the ODBC data source exists and can connect to the SQL server using myODBC for Windows. I've checked the Server Events and they have not changed. In fact, the "Auto Restore" event is identical to the "Place on Hold" event, and "Place on Hold" works without error. I tried reinstalling the PDM plugins, no change. I reinstalled JAVA, no change. I uninstalled the last set of Windows Updates to see if they were affecting it, no change. Anybody have any suggestions? Thanks, dhardison
Oh, yeah. They've worked for several years. This morning is the first I've seen it happen. And it happens on multiple workstations.
I'm not really sure to be honest, I haven't looked at the PDM plug-in in about 5 or 6 years. Can you attach a screenshot of the error (the one you posted above) by chance?
We haven't installed anything on the server. It's dedicated to running Filemaker Server, so it doesn't really require anything else. Actually, nothing has been installed on the server, the radius/sql server, or the workstations in quite a while.
I didn't really think it was Optigold itself. I'm trying to isolate the error. We usually see the box with just "Reporting enabled" when the events go through correctly. I figured it might have to do with one of the plugins, esp. PDM. What's odd is that the other events do not produce the error message, and it's not confined to one machine.
I can't manage to get it to log anything more. Under Control Panel -> ODBC Data Sources -> Configure there is an option to trace the sql, but it doesn't produce anything different from the error Window I posted.