Hi MVP's

an interesting bug in AS2K:

when creating a linked cube off another server, I get the following error
from all client browsers including the analysis manager browser:

"Unable to process one or moe Commands.

Unspecified error"

The linked cube processes perfectly and the original cube works fine too (it
can be seen and opened normally from anywhere).

I have deleted and rebuilt the original and linked cubes, dimensions and
catalogs several times - without any luck. I have also removed any security
on the system. Strangely enough it does not happen consistently - as I have
other examples of where the linked cubes work just fine on the same set of
servers.

Any ideas? Is this a known bug? Is there something in the repository that is
screwed up?

Thanks
Avi

Ps: running both servers in Win2000 Server, with AS2K 3a.

Hi Avi,

I worked on a bug that looks like this, the symptoms where these.

Create a linked cube on a source cube that has a virtual dimension If the
destination database (where the linked cube is) has a dimension same as the
dimension on which the virtual dimension is based on it fails otherwise it
works.

In other words:
Create an empty database
Create a linked cube that points to HR cube fo foodmart 2000,
linked cube processing fails Now in the linked cube database create an
employees dimension,
the processing works ok.

Let me know if this is happening in your situation we fixed this bug I can
send you the build if you like.

HTH,
Bas

"This posting is provided "AS IS" with no warranties, and confers no
rights."

Hi Bas

Thanks for your reply.

Problem is that neither the source nor destination databases has virtual
dimensions. In fact, the destination DB is completely empty.

Here is my sccenario:

Server A
=========
-2 Standard Cubes + 1 Distinct Count cube (all hidden) fused into 1
Virtual Cube (visible)
-All shared dimensions, none virtual, none parent-child
-The virtual cube has numerous member calcs and cell calcs. no actions
or named sets (yet).
-repository in SQL Server 2K

Server B
========
-An empty database of the same name
-1 datasource to Server A
-1 linked cube to the virtual cube on A
-repository in SQL Server 2K

At first I thought it was the distinct count cube - but I have
successully linked to a virtual cube with a distinct measure. Then I
thought it was the different calc's... but they do not seem to impact
the outcome. Then, I thought it was maybe using a DB of the same name -
but I have successfully linked with 2 DB's of the same name.

So I am out of ideas. I can only think its something in the repository
or under the covers.

Any further ideas?

thanks
Avi

PS: I have noticed yet another bug related to linked cubes:

If I restore a DB with a linked cube, whose source does not exist
anymore - the server will lock up during any "deletion process". This
means that if I try to delete any database on that server, AS2K locks up
and the service needs to be restarted. In the end , I have found that
the only way to address the problem is to delete the dead-linked cubes.
Not a big bug, but one that stumped me for months!!!



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!