tag:blogger.com,1999:blog-6575283218005807475.post4426735655208572113..comments2023-12-14T05:50:47.097-08:00Comments on More to life...: Problems starting the OPMN Essbase windows service after changing the Log On accountJohn Goodwinhttp://www.blogger.com/profile/03663642245534297566noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6575283218005807475.post-63484632216657463582013-03-21T09:27:29.326-07:002013-03-21T09:27:29.326-07:00Ran into this same issue last weekend and came to ...Ran into this same issue last weekend and came to the same resolution.<br /><br />Oddly enough, our environment had previously been up and running smoothly for a month or so and this issue reared its ugly head during a reboot of the services. Go figure...<br />JonHarveyhttps://www.blogger.com/profile/02507557474894855262noreply@blogger.comtag:blogger.com,1999:blog-6575283218005807475.post-86684102915816323812013-03-13T13:35:19.662-07:002013-03-13T13:35:19.662-07:00It's very likely that this error, like the sim...It's very likely that this error, like the similar one you get on the weblogic wallet, is due to a mismatch between Fusion libraries and Hyperion-EPM ones. Fusion installers on Windows *require* UAC to be enabled in order to correctly assess security on wallet files and modify it accordingly; the EPM installer enforces the exact opposite policy, in order to accommodate legacy components. As a result, wallets get screwed. This will not change until they eradicate those legacy components (hfm? fdm? who knows), I can only hope they stop adding new wallets until then.toyghttps://www.blogger.com/profile/04499664589774142384noreply@blogger.com