While porting SSIS package from Dev environment to UAT environment, the SSAS connection / task goes bad. When I open the package on the UAT server, I get the following error: The 'Actual' cube was not found in the 'Company' database on the '' server. I do not have Actual cube the cube name is Budget and I am using server name as localhost. When I open the Cube Processing task i do not see the partition I used for processing, instead I see a blank. Any Ideas, why this happens?

Hi Manish, Could you please check the connection for the SQL Server Integration Services(SSIS) package in teh UAT server? The issue might be caused by the package connect to a unexpected server, as incorrect connection. Thanks, Jin ChenJin Chen - MSFT

Hi Manish, The problem could also be with localhost server name. Do you have UAT analysis server, as you are trying to execute the SSIS package from UAT environment it refers to UAT server.

Since I need to move the pacakge around environments, I am using localhost. So the connection should not fail. Its the cube information which goes away not the server information. Is I am missing something?

yes it is UAT analysis server, but it is not a named instance. It only erases cube information rather than server name.

Also it just struck me, u need to have the cube created in new environment to process it. As ur SSIS package is trying to process the cube in UAT but it will not create the cube in UAT. So create a cube in UAT and then try executing the SSIS package in UAT.