I have upgraded a serverbox from Windows 2003 server to Windows 2008 server. I am running Domino 7.0.3 on that serverIn a Notes application I have an Lotus Script agent which has to write records into a SQL database on a SQL server, which is running on another machine (Windows 2003 server).
On the Windows 2008 server where Domino is running I created a ODBC (system DSN) datasource to communicate with the SQL database.
When I test the ODBC Datasource the connection it is succesfull.
The agent is scheduled to run on the server. with runtime security level 3.
On Windows 2003 with Domino 7.03 everything went fine.
Now the agent cannot create the ODBC connection
Dim con As New ODBCConnection 'Make ODBC Connection
If Not con.ConnectTo("prices","user","password") Then <- line 42
Print "Could not connect to prijslijsten"
Exit Sub
End If
I let things writing to a Notes Agent log and this says:
An Error LS:DO- ODBC could not complete the requested operation.( 720) has occurred on line 42 in ExportAgent
When I run the agent not scheduled but On Event, Agent Menu Selection from the Notes database, the agent is running fine. In that case the ODBC connection on my developer machine is used (Windows XP).
I am afraid that this has to do with the way Domino as service is running on Windows 2008 server.
It is about an Notes application which exports data to a financial application, running on a MS SQL server. The export is coded in a Lotus Script agent which runs scheduled on the Domino server. The SQL server runs on an other machine. It worked fine but after we replaced the machine which Lotus Domino from 2003 server to 2008 server, the agent did not run anymore. That is: it started but gave errors when connecting to SQL. So no data was exported to the financial application. That is very urgent for our organisation.
I never use the term URGENT, this was the first time because I paniced and had to solve the problem ASAP (here in the Netherlands we say: When should it be solved? Answer: yesterday).
On my notes 7.0.3 server (Windows 2003) my ODBC agent has been running fine for years. We are now testing for the R8 upgrade on Windows 2008, same error connecting to the Datasource.
Sounds like creating a User DSN is a quick fix, but not a great long term solution.