DCSIMG
Error Processing a Cube: Key cannot be null. Parameter name: key - Ella Maschiach's BI Blog

Ella Maschiach's BI Blog

BI, Olap Technologies, Tools, System Analysis and Design

News

About Ella Maschiach

Business Inteligence

Error Processing a Cube: Key cannot be null. Parameter name: key

I recently opened a new project in SSAS 2008 R2. After finishing developing the cube, I deployed and processed it on the server. I got a really weird error message that meant, unfortunately enough, nothing to me:

"Key cannot be null. Parameter name: key"

So what's a girl to do? Well actually, I remember that every so often when I was developing a cube, I would have a problem with the data connection. The default I had defined for me when I opened a new connection was .Net Provider\SqlClient Data Provider.

And somehow the default definition would always create an error in the process of the cube...
So I decided to try that first. Changing the data connection to Native OLE DB\SQL Server Native Client 10.0.

Deploying and processing it worked. I love me a good short fix! :)

Update July 14th, 2011:
Another member in my team found this solution applicable to his problem. He had a connection string that was defined as: Native OLE DB\Microsoft OLE DB Provider for SQL Server. What he got was a process that gave him all the labels for all his members as "???" (question marks). That's even though right clicking the table in the DSV and chosing Explore data showed the Hebrew correctly. Locale Identifier was already set to 1037. I wondered if it was a matter of collation... no, it was redefining the data connection to Native OLE DB\SQL Server Native Client 10.0. I'm hoping for better error messages. One day...

Comments

No Comments

Leave a Comment

(required) 

(required) 

(optional)

(required) 


Enter the numbers above: