August 10, 2015 at 4:43 am
Hello there. I've got a very annoying issue that I cannot seem to get to the bottom of. I deployed a new version of a SSAS cube a couple of weeks back. Due to connectivity restrictions, the method of deployment consist of
1. Deploying the cube to a local server
2. Backing up that cube
3. Restoring the cube to the target server
4. Repointing to the correct datasource
5. Full refresh
I have used this approach several times over the past couple of years and it's never had any issues up until now.
Some users are complaining that reports that they have created prior to the deployment now no longer are displaying new data. They do not receive any errors, the pivot tables are definitely refreshing as I can see them hitting the database, but they do not pull out the new data.
If the same report is recreated from scratch, it behaves as you would expect displaying the new data without any problems.
I've tried several things.
1. All type of SSAS processing of the cube. Full
2. Data clear, then full again.
3. Reprocessing all dimensions
4. repointing the pivot tables to new SSAS connections.
This really does have me stumped.
Any suggestions, would be greatly received.
August 13, 2015 at 11:34 am
Hi Paul,
When you browse the cube in BIDS, do you see the new data?
Also, I realize the users aren't receiving any errors, but I was also wondering if any of their rights have recently changed?
August 19, 2015 at 3:59 am
Yes, the "new" data is viewable in BIDS, in SSAS and when you create a new connection to the SSAS database via Excel. It is only some older reports that have an existing connection are not pulling any new data, even when the connection is replaced with a new one.
No permissions have changed. The permissions in the cube itself are very simple. Everyone connects using the same account. That account has read only access to all objects.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply