Posts Tagged ‘Cubes’

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

image

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.

SNAGHTML53c4c56

So, the next step is to “Restart Deployment”

SNAGHTML54834f0[4]

With mine, nothing happened and I found the following error

image

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

image

3. Expand Databases, expand DWASDataBase, Expand Cubes

image

4. Select cube from error and delete the Cube.

image

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

SNAGHTML552e490

This time you will see an Event log like this.

image

The Cube is now re-deploying.

image

You can now process your cubes as normal without any errors

(E-Mail me)

image_thumb_thumb_thumb_thumb_thumb

Follow me.

facebook-small322252222 Facebook (Personal)

twitter-small322252222Twitter (Personal & System Center)

scsmlogo25232 Twitter (System Center Focused)

MCC11_Logo_Horizontal_2-color_thumb_

Advertisements

So, You are now ready to take the plunge and upgrade to SCSM 2012 RTM as it now “publically” available.

There is great documentation, obviously, on TECHNET. I have however found out a few other things which will helpfully make your transition a little easier. I have found that the following can cause some complications and how to “mitigate” these if you will.

Service Manager 2010

Connectors – Please make sure that your connectors are NOT running while you do the upgrade, the upgrade will work, however your connectors will run and attempt to catch up with itself. This will in turn, create additional load on the SQL Service on your Management Server, which will in turn affect overall performance and will slow down workflows in particular.

Fix : Simply ensure that your connectors are NOT running.

Service Manager 2012 PRE-RTM

Connectors – Please make sure that your connectors are NOT running while you do the upgrade, the upgrade will work, however your connectors will run and attempt to catch up with itself. This will in turn, create additional load on the SQL Service on your Management Server, which will in turn affect overall performance and will slow down workflows in particular.

Fix : Simply ensure that your connectors are NOT running.

Cubes – If you are upgrading from a PRE-RTM Version to RTM, please note that I am sure that is not supported by Microsoft unless you were a TAP customer. So, this would be more for a lab environment. If your cubes are running, please allow them to process and ensure that they are in a processed and preferably NOT a “Partial Processed” state. Please also check the status of these job as per the TECHNET article and ensure that get-scdwjob returns all jobs in a “Not Started” state.

Fix : Ensure all cubes are in a processed state and NOT “Running” or “Partial Processed”

As for System Centre Service Manager 2012, the connectors are greatly improved in SCSM 2012, while your SCSM 2010 Connectors will work, you will see that there is a difference in the Connectors as seen below.

ConnectorsSCSM2012

The old connectors “Active Directory” are migrated from SCSM 2010 to SCSM 2012. However, the new type “ADConnector” are more robust and more streamlined. I would recommend Creating the new type for all your existing connectors, disabling the existing and running only the new connectors. Once you are happy with the results and that new objects are being created and tested this for some time, then remove the older connectors.

If I can think of anything more, I will post this in future.

Follow me

facebook-small32225222222 twitter-small32225222222

MCC11_Logo_Horizontal_2-color_thumb_[1]