Hi folks,
I've taken to scheduling my scheduled reports under the RptServ user that I created to run the report server. This means that I log into the client to set up the reports--which means the application password is subject to expiration.
Am I correct in thinking that gsrbatch.exe doesn't need the application login at all? As in, as long as the SQL user for RptServ matches the login in gsrbatch's ini file, I can change the RptServ user's application password all I want?
Thanks!
Nick,
That's how I understand it, same would apply to other service accounts like the seat server or web api users. They all need SQL but not application-centric credentials.
The api user "might" be the only account that you may ever need to login to Tess with of those three for batch reasons or testing.
Hi Nick,
We do this as well, but simply change ownership of the scheduled report by updating the user_id in gooesoft_request
Michele