I apologize in advance if I’m not giving critical information, but I’m hampered by the fact that I have no Administrator knowledge (Dev and Adm are strictly separated here), so have no idea what server issues, if any, might be involved here.
The agent involved worked without incident on R5 for years. It stopped the moment the server was upgraded to R6(.5.3, I think). Our working model here is that the devs do all the work on one server, DEV, and then the Admins create copys on another server, MODEL, and control the refreshes. Wholly inefficient until I found some code here that used an API to do server to server refreshes in a scheduled agent, that got around the problem of us Devs not being authorized to refresh Model databases as long as the agent was signed with an Admin ID. With the new Agent security, I’m sure it’s not that simple anymore, but frankly, I’m lost. I can’t get the agent to run on schedule anymore, I have no idea what needs to be done on the Admin end, and since the Admins generally wait for me to tell them what to do, I’m at a standstill.
On R5, the Model databases accepted the refresh simply because the agent was signed with an Admin ID with full administrative access. On R6, 1) the agent won’t run at all and 2) if run manually by Admin, it returns the error that the database (the one on Model that we’re trying to refresh) isn’t open yet.
So is there something that I can tweak in the agent or something I can tell Admin to tweak that would allow a scheduled agent to open the database in R6 the same way it opened in R5 when the agent was signed by an Admin ID??? Otherwise, we’ll be forced to go back to waiting 1-4 hours for a simple refresh request to be executed, and sometimes it doesn’t come until the next day…