Posts Tagged ‘Data Warehouse’

So, just the other day I opened the SCSM console to look at the cubes and process as needed, since some new reports needed to be built and Excel spread sheets created by our BI person for business. So, I start to process the cubes and the first cube starts processing without issue. However when I attempt to process the second cube (Change and Activity Management cube). It presented an error stating that "Could not find any resources appropriate for the specified culture or the neutral culture".

I have never seen an error like this before, so it was time to do some investigating.

I started by looking at the Data Warehouse Wunderbar and more specifically the “Data Warehouse Jobs” tab. I noticed that all the Cubes which were giving me said error where missing from the “Data Warehouse Jobs” tab.

I then remembered about a Patch Window that occurred while I was on leave and decided to look further. I was digging through the Event Logs, when I found the following error

Event id: 33410

Source : Deployment


And as you can see from the screenshot, there are plenty of these. Clearly the patching window had interrupted a job. So now with at least something to work with, I started looking around some more and remembered that the MPSyncJOB is responsible for Management Pack Synchronization and upon opening the status of this job, I saw that the Management Packs related to the now problematic cubes were disassociated.

So, from here it was time to check and start putting the pieces of the puzzle together. Upon opening the “Management Pack” section of the “Data Warehouse” Wunderbar, I could see that the deployment of these Management Packs had failed.


So, the next step is to “Restart Deployment”


With mine, nothing happened and I found the following error


Fortunately enough the solution is listed within the error message.

Simple, delete the cube and then re-deploy the Management Pack.

1. Open SQL Management Studio on server hosting the SQL Analysis Services

2. Connect to the server type : Analysis Services


3. Expand Databases, expand DWASDataBase, Expand Cubes


4. Select cube from error and delete the Cube.


The deletion of the cube can take some time. Once Deleted, go back to the Console and “Restart Deployment”


This time you will see an Event log like this.


The Cube is now re-deploying.


You can now process your cubes as normal without any errors

(E-Mail me)


Follow me.

facebook-small322252222 Facebook (Personal)

twitter-small322252222Twitter (Personal & System Center)

scsmlogo25232 Twitter (System Center Focused)




So, my journey with System Centre Service Manager 2012 Beta has begun and so far I have indeed found some funnies.

I will be blogging about them, to make everyone else’s life a little bit easier and in the hope of better product adoption for this product. It is simply put a fantastic product.

Ok, so the first time I ran the upgrade (remember I have a pre-prod environment), so I was able to rollback and did not have to follow Disaster Recovery with the Failure. I will cover the Disaster Recovery steps that I will follow in Production if I have an issue.


So, like I was saying, I ran into a Reporting Services error when upgrading the Data Warehouse. So I rolled back to a previous state as I am using VMS. However, to resolve this particular issue, I ran the upgrade again. However, this time I opened the SQL Reporting Services webpage and allowed the reporting services webpage to load to completion before running the upgrade.

Reporting Services

I suspect due to the limited specs on my virtual environment, the slow opening and hence communications with the Reporting Services caused my first failure. The second attempt was perfect.

I now had SCSM 2012 Beta Data Warehouse.

So, here is a breakdown of what I did.

1. Install Cumulative Update 2 for System Centre Service Manager 2010 SP1

2. Install Windows Server 2008 R2 Service Pack 1

3. Backup Encryption Key

4. Restart Server

5. Check the status of SQL Reporting Services (services.msc)

6. Check the status of Reporting Service (web site). First load of this website was VERY slow.

7. Disabled Data Warehouse Jobs

8. Waited 10 Minutes

9. Run the Upgrade

10. We have successfully upgraded the Data Warehouse Server.

11. The only thing I did differently this time, I left the reporting services website open the whole time of the upgrade process.

With Analysis Services(Cubes), Permissions are controlled differently. Open SQL Management Studio, and ensure that you connect to Analysis Services and NOT Database Engine and then specify the SQL Server and assign permissions as needed so that people can/cannot access Cubes within Service Manager 2012 Console.

More to follow soon on the Management Server.

Follow me

facebook-small32225 twitter-small32225