Hello,

We are running Analysis Services for SQL Server 2000 (Enterprise
Edition), SP 3a, on a Windows Server 2003 box, and are having a few
nagging issues. First, we are able to build cubes just fine, but after
the cube is built, we get the following error:

Error(-2147221421): Internal error (Could not update the query log.);
Time:10/31/2005 6:16:43 PM

Secondly, when we attempt to use the usage-based optimization wizard,
we get this error:

Usage-Based Optimization Wizard: Unable to initialize the connection
to the query log database.

Details:

Error Number:-2147467259
Error Description: Could not use ''; file already in use.
Error Source: Microsoft JET Database Engine

Third, the primary user of Analysis Services is sometimes presented
only the list view of details about cubes, even though he has specified
the HTML view. This means he cannot see metadata, which he needs to
see.

The user running the Analysis Manager is connecting to the server via
Remote Desktop Connection, and his rights on the server are limited.
He has been added to the local OLAP Administrators group, and obviously
has the right to logon to the server, but otherwise, he has been
granted no other rights explicitly. Are these problems symptomatic of
a lack of privilege on the server? Is there a combination of rights
that he needs to be granted that would allow him to work with no
problems, or must he be made an administrator on the server?

Thanks for your help,

Scott Ashby
DBA
Swedish Match North America
scott.ashby (AT) smna (DOT) com

Error(-2147221421) - Is you log in SQL server or msmdrep.mdb?

I assume msmdrep.mdb because you are getting
Error Number:-2147467259

A solution for both is to migrate the repository to SQL Server.

Sorry about the third question.

Hope this helps.

You should not need to migrate to a SQL repository if you don't want to
(although it is not a bad idea). It sounds like path to the query log
database is not set correctly. This path is stored in registry at the
following location.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\CurrentVersion


It is store twice, once for local connections and once for remote
connections

QueryLogConnectionString
=========================
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program Files\Microsoft
Analysis Services\Bin\msmdqlog.mdb

RemoteQueryLogConnectionString
==============================
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\<< MACHINE_NAME >>
\MsOLAPRepository$\msmdqlog.mdb

Note that the remote one refers to a hidden share on the AS server
rather than to a local path.

This should fix your first two problems. I have intermittently seen your
third issue, but do not know of a definitive fix. It may be permissions
related, usually I will install Analysis Manager on someone's
workstation if they need to access it regularly.


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

In article <C5B0927D-3459-4948-9E11-E35F59A505E1 (AT) microsoft (DOT) com>,
HWUK (AT) discussions (DOT) microsoft.com says...