Lutz
Many thanks for your reply, and apologies for not getting
back sooner. As you can imagine we've been pretty busy
trying to get this sorted.
We tried just about everything that we could think of,
including restoring from archive files(which failed),
restoring from backup tapes, which made no difference. We
re-installed all of the SQL Server software, which again
made no difference. We supposed that somewhere, some path
setting had got corrupted, but we could not determine
where or how to update the path settings. All I could
think of was that they were held in the Master or MSDB
databases on SQL so we tried restoring those, again with
no success.
Eventually we noted that it was only the cubes/dimensions
of one 'database' that was affected, and we were able to
re-process these and view them again ok, which led us to
think that 'PTSLITE' was not the answer. I tried to create
a new set of dimensions and a new cube in the corrupt
database and found that this did not work either. Tried it
in another database and it worked ok.
Anyway, we eventually managed to fix the problem in the
simplest of ways....
We right-clicked and copied the whole of the
corrupt 'Production' database.
Right-clicked and pasted on the Server node, and called
it 'Production New'. We then deleted the 'Production'
database and copied it back. We were amazed when this
worked. 2 days down the line and the eventual solution
took about an hour !!
We live and learn, but we're still no wiser as to what
caused it or where the paths are held etc.
Many thanks for your contribution anyway.
Regards
Colin.
Quote:
-----Original Message-----
Colin,
did you install PTSlite on all your olap clients? It
comes with SP3 for MSOLAP. If not, that is probably the
reason why you cannot 'see' the cubes. It installs a new
oledb provider (MSOLAP 8.0).
You are able to see Foodmart2000, because you did not
reprocess the cubes after the update.
Hope this is a good guess.
Lutz
. |