I created a Notes DB to pull info from a MS Access DB and did all my testing locally first. I created a system DSN and pointed it to my MS Access DB which is out on a server. Everything works fine like that. I then moved my Notes DB to the server and created the same system DSN (on the server) to the same MS Access DB. I cannot connect when I run my script now. Is is neccessary to have a system DSN on the local machine as well as on the server?
Currently my script is running through a button for testing, but will eventually run as a scheduled agent. Does this make a difference?
Thanks for the help
Subject: System DSN on Server Only
Edward, you will probably get more help if you post this in the Enterprise Integration forum.
It doesn’t matter where the Notes database is located, it matters where the code is executing. If you click a button in a Notes client to run the code, the local Notes client is doing all the data access. In this scenario you would still need an ODBC DSN on the Notes client computer to connect to the Access database. You do not need an ODBC DSN on the Domino server at all until the agent is running from the server.
HTH,
Charles
Subject: RE: System DSN on Server Only
I created an agent and told it to run at a certain time. I also created a system dsn on the server that points to my access DB. However, the agent is not running. I do have access to run agents on the server, but it does not do anything. When I run the agent myself and have a dsn on my local machine pointing to the access DB, it works.
However, what I want is for this agent to run automatically without user interferance.
Subject: RE: System DSN on Server Only
You maybe running into a Windows permission issue if the MDB is on a different server then your Domino server and is using a mapped drive/share to access the database.
The restriction comes from the fact that Domino is operating as a service AND is allowed to interact with the console user.
Two ways to test this…
#1 - Copy the MDB to the Domino server and redirect the DSN to point at the local database. Run your agent and if all is well, procede to test #2. If this still fails, then you have some other problem.
#2 - Remove the Domino services right to interact with the console/desktop. Run your agent…if it works you definately have a permission issue…if not, then it is still some other issue.
This used to be an issue and may have been resolved, but I am not certain.