Only experienced a 117 fortunatly. We tied it down to our front end
(Proclarity) some users were slicing 2 named sets (time dimension). I'm quite
sure there are many other situations that cause a 117, but here's a start and
a ray of hope that the problem lies with the client server interaction and
not the server itself.
"Ofri" wrote:
Quote:
Hello
When processing my olap database (AnalysisService 2000, SP 3a) I get error
117 or 132 and the service will be restarted bevor ending processing. What
can I do?
Thanks. |