Hi everyone,
We did the point update to v15.2.34 last week (we are RAMP/Hosted). Everything looked fine in testing, and as it was "only a service pack update", I didn't really have any qualms about going to Live. Ever since the live update happened, though... users are getting a TON of daily dashboard emails, even if they weren't subbed to them (I have a RIDICULOUS number of them). Support just told me that that's a defect with the upgrade process, that wasn't mentioned ahead of time, and that the onus is on the dashboard owners to check each dash and unsubscribe people. And today, a 3rd party emailed me saying that they were receiving scheduled reports not meant for them. I checked the report schedule, and their email address is not attached to any current schedules. Has anyone else done this service pack update and had it not go smoothly? We've all talked about the many, many issues with v16 update, but I (mistakenly) thought a small service pack update would be smoother...
Does anyone have any feedback on the v15.2.35 service pack? We're looking to update soon and want to know if there are major issues.
We are trying to upgrade from 15.2.28 to 15.2.35 and have run into issues. First analytics and now seats & tickets tables. So, if you aren't already on 15.2.34 then I would go through the service pack instructions for 15.2.34 as well as 15.2.35. We still haven't been able to update yet. It is now in the hands of TessNet. We are self hosted. Good luck and let us all know how it goes.
We upgraded from .34 to .35 last Wednesday, and so far so good. We are hosted. When we originally upgraded to .34 in PROD we had major issues with delivery of Analytics Dashboards, as described elsewhere in this thread. They 'rolled back' just our Analytics to an earlier instance for the last few weeks, so I'm not sure if they did an extra step when doing our latest service pack upgrade, but over the last week, Analytics seems to be behaving. The day we upgraded, some of our custom reports had dismal performance and were sometimes timing out, but that issue seemed to clear itself up the next day.
That's good to hear. I'll keep an ear out, but we are now getting to a point where our next upgrade may simply be to v16.