Unable to complete OLAP Breakout

[Jeff Cecil]

I'm trying to extend timephased data using the SDK. I have the OLAPBreakout
test program running and the initialize connection works. My OLAP
administrator IS the local administrator account (only because this is a a
test server) so the trace should be able to write. However when I click the
OLAP Breakout 1 or 2 button I get

"Error! Unable to complete OLAP Breakout 1. Unhandled Error: "ActiveX
component can't create object"

I can't figure out what is causing the error. Any ideas?

 

[Guest]

Hello Jeff,

I ran into this error when I mistakenly tried to delete and then recreate a
table
in the database rather than deleting the records in the database. It turns out
that while you can indeed delete a table, the context you are running in will
not let you create a new one.

If this isn't related to the problem you are seeing, set a few break points and
tell us where the error is occurring.

Did this resolve you problem?

Bob Segrest, PMP
Microsoft Project Blackbelt

 

[Jeff Cecil]

No, I didn't touch the database other than to run the SQL updates via the
batch files that come with the SDK. Also, I am not running this from an IDE.
I'm running the exe that came with the SDK. We don't have VB6 or MSDN and
really have no way to use the code samples.

 

[Jeff Cecil]

Oh yeah, I forgot..................thanks for replying!! I always appreciate
the efforts when people try and help.

 

[Guest]

Hi Jeff,

There are a couple more things you need to do... For example,
you will need to register the MSPOLAPBREAKOUT library.

I wrote a white paper to address this in some detail. While it uses the
earned value extension as a base, the structure and process is the
same. It might help get you started on the right path and can be found
at

http://bsege.com/white_papers.htm

Bob Segrest, PMP
Microsoft Project Blackbelt

 

[Jeff Cecil]

I had actually already read your white paper from another post. It also
assumes we have VB6. We do not. I have been informed we can get it from
MSDN, but we are not MSDN subscribers. Why is a feature of project server
that should be a default set to this absolutely rediculous process to access?