July 23, 2018 at 2:03 pm
I updated our test environment with SQL 2016 SP2 CU1 from RTM. One of my developers is now reporting an issue with his IS package which refreshes data of a cube in a Tabular instance of AS. His dev box is at SP1 CU4 and the package still works. It seems this is due to updating to SP2, but there are warnings out there about pulling back SP2 so I would rather find a fix than completely break the box.
Looking at the execution report I see the package succeeded and there are no errors, but the cube data is not being updated.
My developer can run the query manually from Management Studio and the cube data is updated.
I attempted to install SP2 CU2 as I hoped it would contain a fix for the issue, but this did not resolve the problem.
I've seen the other threads with the assembly error, although it seems similar, but we are not receiving those errors.
Any assistance would be greatly appreciated.
July 23, 2018 at 2:19 pm
csmotter - Monday, July 23, 2018 2:03 PMI updated our test environment with SQL 2016 SP2 CU1 from RTM. One of my developers is now reporting an issue with his IS package which refreshes data of a cube in a Tabular instance of AS. His dev box is at SP1 CU4 and the package still works. It seems this is due to updating to SP2, but there are warnings out there about pulling back SP2 so I would rather find a fix than completely break the box.
Looking at the execution report I see the package succeeded and there are no errors, but the cube data is not being updated.
My developer can run the query manually from Management Studio and the cube data is updated.
I attempted to install SP2 CU2 as I hoped it would contain a fix for the issue, but this did not resolve the problem.
I've seen the other threads with the assembly error, although it seems similar, but we are not receiving those errors.
Any assistance would be greatly appreciated.
Are there any warning messages in the log which might be relevant?
July 24, 2018 at 11:25 am
No warnings. I am working with my developer a bit and he's working on recreating the packages. He believes he is having some success but I won't know until he's done.
It seems almost like a version issue with the packages which were created on 2016 SP1.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply