What's your Migration Date?

I am realizing reading through several posts that this seems similar to a problem we wrestled with for a few months post-conversion to v11. We opened a ticket, but eventually resolved it on our own. Infomaker reports were scheduled and ran just fine. SSRS Reports were scheduled, and would "run", but not get "saved" to the folder for emailing, so it appeared as though they didn't run at all. A bevy of errors in the Tessitura Report Server Application Log pointed us in the right direction. Here is a brief description of what we discovered:

----------

We did indeed finally get a working solution, and it came down
to permissions on the folder that temporarily stores the files prior to
emailing.

1) we had to move to using a snapshot folder on the app services machine (which
is also our Report Server) instead of on our SQL database machine
2) we shared the snapshot folder (particularly to the user running SQL services and
the Report Server)
3) we gave full read/write permissions to the 'IIS AppPool\Tessitura_Svcs'
application pool

It was #3 that was really the sticking point - if we kept the snapshot folder on the SQL
database server, adding the app services *machine* rights were not enough to make
this work. It seems we specifically needed the *app pool* rights, and the
only way to do that was to have the folder on the same server as the app
services. Not sure if that is the intended setup, but at least we have it
working again. On pg 12 of the Report Setup/Admin document, it is not very
clear as to the best location of the folder, nor does it specify the app
pool permissions we found to work in our situation.

Our patch upgrade to 11.0.4 last week seems to have also cleared up a few
other small issues as well.

----------

Unknown said:

SSRS Reports were scheduled, and would "run", but not get "saved" to the folder for emailing, so it appeared as though they didn't run at all.

An almost exact description of our situation, i.e. "error creating snapshot" in the Report Server log, the snapshot actually gets created in Report Manager and can be seen and opened there, but nothing is e-mailed. We've gone around and around with permissions settings on the EMAIL REPORT PATH, but our support ticket remains open (since September).

Unknown said:

[...] if we kept the snapshot folder on the SQL
database server, adding the app services *machine* rights were not enough to make
this work. It seems we specifically needed the *app pool* rights, and the
only way to do that was to have the folder on the same server as the app
services.

I'd love to give this a try immediately, but moving our SSRS server to our Services server would not be trivial.

I wonder if the snapshot folder (same as the SSRS_SNAPPATH from t_defaults, yes?) needs to live on the same server as the rest of SSRS? Hmm....

Unknown said:

SSRS Reports were scheduled, and would "run", but not get "saved" to the folder for emailing, so it appeared as though they didn't run at all.

An almost exact description of our situation, i.e. "error creating snapshot" in the Report Server log, the snapshot actually gets created in Report Manager and can be seen and opened there, but nothing is e-mailed. We've gone around and around with permissions settings on the EMAIL REPORT PATH, but our support ticket remains open (since September).

Unknown said:

[...] if we kept the snapshot folder on the SQL
database server, adding the app services *machine* rights were not enough to make
this work. It seems we specifically needed the *app pool* rights, and the
only way to do that was to have the folder on the same server as the app
services.

I'd love to give this a try immediately, but moving our SSRS server to our Services server would not be trivial.

I wonder if the snapshot folder (same as the SSRS_SNAPPATH from t_defaults, yes?) needs to live on the same server as the rest of SSRS? Hmm....