For those migrating soon, what’s your migration date?
We are T-minus 17 days – Sunday October 7
Gonna start working on my migration-day procedure sheet!!
Dave Vivino
Cleveland Orchestra
We also have a support ticket open about SSRS reports not emailing when scheduled.
Nancy Sheleheda
412-456-1387
sheleheda@trustarts.org
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of John Brandt Sent: Tuesday, December 11, 2012 5:06 PM To: Sheleheda, Nancy Subject: RE: [Tessitura Next Generation Forum] What's your Migration Date?
Yes we have the same support ticket open. Scheduled and e-mailed reports.
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Chris Jensen Sent: Tuesday, December 11, 2012 1:48 PM To: John Brandt Subject: RE: [Tessitura Next Generation Forum] What's your Migration Date?
Beth Hawryluk: We were working with several of the TN Support staff before we finally found that GPs were the root of the issue.
Beth Hawryluk:
We were working with several of the TN Support staff before we finally found that GPs were the root of the issue.
We have a stubbornly open support ticket about SSRS reports as well, specifically scheduled & e-mailed ones. Your mention of group policies is intriguing. Do you recall which GPs were at the root of the issue for you?
Thanks.
From: Beth Hawryluk <bounce-bethhawryluk7830@tessituranetwork.com> Sent: 12/11/2012 2:17:08 PM
Hmmm. Interesting problem! Were you ever able to schedule the SSRS reports or is this new since your V11 upgrade?
There's a forum thread here that might be of use to you:
http://www.tessituranetwork.com/Community/forums/t/8059.aspx
We were working with several of the TN Support staff before we finally found that GPs were the root of the issue. Unfortunately, that was as far as they could help. It's up to us to figure it out from here. :)
If that forum thread isn't helpful I'd suggest opening a help ticket. Good luck!!
You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!
______________________________________________________________________ This email has been scanned by the Symantec Email Security service. For more information please visit: http://www.symanteccloud.com ______________________________________________________________________
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 downto permissions on the folder that temporarily stores the files prior toemailing.1) we had to move to using a snapshot folder on the app services machine (whichis also our Report Server) instead of on our SQL database machine2) we shared the snapshot folder (particularly to the user running SQL services andthe Report Server)3) we gave full read/write permissions to the 'IIS AppPool\Tessitura_Svcs'application poolIt was #3 that was really the sticking point - if we kept the snapshot folder on the SQLdatabase server, adding the app services *machine* rights were not enough to makethis work. It seems we specifically needed the *app pool* rights, and theonly way to do that was to have the folder on the same server as the appservices. Not sure if that is the intended setup, but at least we have itworking again. On pg 12 of the Report Setup/Admin document, it is not veryclear as to the best location of the folder, nor does it specify the apppool permissions we found to work in our situation.Our patch upgrade to 11.0.4 last week seems to have also cleared up a fewother 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.
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 SQLdatabase server, adding the app services *machine* rights were not enough to makethis work. It seems we specifically needed the *app pool* rights, and theonly way to do that was to have the folder on the same server as the appservices.
[...] if we kept the snapshot folder on the SQLdatabase server, adding the app services *machine* rights were not enough to makethis work. It seems we specifically needed the *app pool* rights, and theonly way to do that was to have the folder on the same server as the appservices.
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....