Monday, February 20, 2012

PTS sp4 causes Distinct Count error

I have Analyisis Sevices service pack 3a. Office xp has been installed on the client machines and the server, which has installed PTS service pack 4. This has resulted in one of the calculated members showing as #1NF in Proclarity. It works perfectly well from client machines still running with PTS service pack 3. The calculated member in question uses a distinct count which is now always returning 0.

Does anyone have any suggestions? Thanks.

If the cube where it happens is a virtual cube - then it is a known regression in SP4 w.r.t. DistinctCount MDX function. There is a hotfix avaialable - please contact product support in order to obtain it.|||

Hello,

Yes it is a virtual cube. Is the hotfix for Analysis services sp4? The server is still on Analysis services sp3a but PTS got upgraded when office xp was installed.

Thanks for your help.

|||Yes, the hotfix is on top of SP4 and should be applied to PTS.

No comments:

Post a Comment