Yes!  It uses the DSN's in the Administrative tools folder (that's "Data Sources (ODBC)").  I suggest you look at the old server's Data Sources, and get ready to create a new Data Source on the new server.

Don't forget that on 64bit OS's that "Data Sources (ODBC)" bit is 64bit, but Domino uses the 32bit ODBC so you have to run odbcad32.exe in the \Windows\SysWOW64 directory if it's 64bit Windows.  Happy happy joy joy.

Assuming you have the correct ODBC Data Source Administrator running, we want the system DSN's...  Click on the System DSN tab.  If you see stuff about Excel, and Access, you're in the wrong place.

To Create a new System DSN, press the "Add..." button.  Or, push the "Configure..." button.

You will be presented with a (long) list of possible drivers.  Scroll all the way to the bottom, and choose "SQL Server", then press "Finish".

Now the next few windows relate to setting up the DSN connection to the SQL server... First up is the Name of the System DSN.  I think, from your code, yours will be called "OLEDB" or "sqloledb". Then press the "Next >" button.

Now we need to log into the SQL server.  We need to change the authentication from Windows NT to SQL Server authentication,  Then we enter the username  and the password.  Press the "Next >' button.

Now we specify the SQL database we're connecting to.  Press the "Next >' button.

Finally, press the "Finish" button.  (We don't change anything on this screen.)

Although, you can test what you've written in the next screen by pressing the "Test Data Source...", otherwise press OK.

Regards

Tim

Hi,

Thanks for your advice, especially the warning about the 32 bt / 64 bit oddities. I thought I was in the right area, and your answer confirmed that for me. The thing is, I already checked the Data Sources in System DSN on the old server; there are 2 listed but none of them relate to this sql database. I don't understand how the agent is managing to succeed if there is no sign of the Data Source on the agent server. 

Any ideas?

Thanks :-)