Hi all,
I'm using AS 2000, sp4

I have been trying (unsuccessfully) to clear the error
"Provider cannot be found. It may not be properly installed"
"Unable to browse the cube 'xxx'. Unspecified error"
"Unspecified Error"

I have reviewed the 10 K.B. entries when searching the KB for
'analysis services unspecified error'

I have msolap80.dll version 8.00.323.03
and verified that this is the version loaded by scanning the system info.

I'm running Win 2000, SP4, build 2195.

I can create, edit and process cubes on the localhost.

I cannot browse cubes on the localhost, or cubes on a Win2003 server.

Any help troubleshooting this would be most appreciated.

Thanks,
Steve

That version of msolap80.dll does not look correct for SP4 - it should be
8.0.2039.0, I think. Try installing SP4 again, and make sure it is the
Analysis Services service pack rather than the SQL Server service pack (they
are separate).

Good luck

--
Dean Adam
Magenic Technologies


"Steve Gundersen" wrote:

When you unpack the service pack, there is a subfolder called PTS. This
contains the client side provider files. You need to run PTSFull or
PTSLite on your client machines.

The difference between the Full and Lite versions is that the Full
version also contains a copy of MDAC.

--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell

Thanks Dean,
I was beginning to think my system was totally hosed. Based on your
suggestion, I reinstalled the AS SP4 and then the cube browsing began to work
(at last). Very strange that there are so many different versions of the
driver. The one I had that was not working, came from the Office XP detect
and repair process, which one of the KB threads implied would fix this.
And Darren too.
--
Cheers,
Steve


"Dean Adam" wrote:

Office XP rings a bell, I think there is a KB article to the effect that
the Office XP install does not correctly detect later versions of the
msolap provider and may overwrite them with an earlier version. To fix
this on a machine with AS you need to re-install the latest SP. To fix
this on a client PC, running either PTSFull or PTSLite (from the
relevant SP) is sufficient.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <D781110A-5369-4574-85D5-1BF99503B7AB (AT) microsoft (DOT) com>,
SteveGundersen (AT) discussions (DOT) microsoft.com says...