OLAP bulding not wokoring in clean install environment

[Sander]

Hi,

I have 1 your experience in installing ProjectServer 2007 with all the
problems ever heard of with the OLAP cube building service.
However, this week I encoutered one really ***** problem which i just can't
solve. so please help if anyone does know what the following error is. It is
a clean install, nothing changes in settings. Just 1 resource in the system
(the install account). the cube is created, but processing fails. Also
manually processing gives an error (OLE DB error: OLE DB or ODBC error:
Operation canceled; HY008.)

project server error message:
Failed to build the OLAP cubes. Error: Analysis Services session failed with
the following error: Failed to process the Analysis Services database
TEST2007 on the ocean01 server. Error: Errors in the back-end database access
module. OLE DB was unable to convert a value to the data type requested for
column 0. Errors in the OLAP storage engine: An error occurred while
processing the 'Resource Timephased' partition of the 'Resource Timephased'
measure group for the 'Resource Timephased' cube from the TEST2007 database.
Internal error: The operation terminated unsuccessfully.

OLAP error data (from manual process command):
Errors in the back-end database access module. OLE DB was unable to convert
a value to the data type requested for column 0. Errors in the OLAP storage
engine: An error occurred while processing the 'Resource Timephased'
partition of the 'Resource Timephased' measure group for the 'Resource
Timephased' cube from the TEST2007 database.

 

[Sander]

extra info: i'm using sql2005 with sp2

 

[Gordon]

Hi Sander,

This is really insufficient information, but here are my questions.

1. Did you successfully build the OLAP cube when you installed PS2007?
2. Is your SQL Server in a singel instance or clustered?
3. Do you have any special charcacters in your measures/dimensions like &%
etc?

 

[Sander]

Hi gordon,

Thanks for a reply. The Cube did build, but could not be processed. After
some fiddling around with regional settings on the sql server (no cluster),
that is: set them to UK and back to US, it seemed to solve the problem.
Really frustrating as I tried first just to swap the decimal and the
thousands separator.
But it is working now..

Sander