Issues with service pack update

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...

Parents
  • We just upgraded to v15.2.34 and I wanted everyone to know a different headache, just so you are aware of some necessary work that will need to be completed post upgrade.  For all of our dashboards, wherever there is a multiselect filter in use (whether on dashboard level or widget level) those have all reverted to having every option selected.  I own all of our major dashboards that get emailed out to leadership and the rest of the staff, so I'm going to have to go through and check every one of them.  

  • 15.2.35 it is!  (until I hear a story about that one...maybe we'll just sit on it until v16)

  • maybe we'll just sit on it until v16

    And of course v16 will have no Analytics bugs. :-)

  • Looks like we should keep this string open to keep track of what is happening with these service pack releases.

    We aren't planning on installing any service packs until early July - unless .35 hasn't been released. We passed on .34 because we have custom cubes and we were told that we could run into issues with them when .34 was installed into PROD (since there is no way to test them in TEST). 

    What we really need is a TRUE test environment (and true DEV and STAGING environments), so we can test all changes before introducing them to PROD. 

    I'm with you Gawain, might just wait until v16, though I have concerns about moving to it right now too. I'm sure by the time were ready to move, we will have worked through all of our concerns and will have a solid plan based on everyone else's experiences.

Reply
  • Looks like we should keep this string open to keep track of what is happening with these service pack releases.

    We aren't planning on installing any service packs until early July - unless .35 hasn't been released. We passed on .34 because we have custom cubes and we were told that we could run into issues with them when .34 was installed into PROD (since there is no way to test them in TEST). 

    What we really need is a TRUE test environment (and true DEV and STAGING environments), so we can test all changes before introducing them to PROD. 

    I'm with you Gawain, might just wait until v16, though I have concerns about moving to it right now too. I'm sure by the time were ready to move, we will have worked through all of our concerns and will have a solid plan based on everyone else's experiences.

Children