Have about 50 cubes which all process fine except one
which returns the following error:

"Error -2147221421 Internal Error:Could Not Update Query
Log"

I've checked BOL, the knowledge base and this newsgroup
but can't find any mention of this error. A google search
turned up one link which referred to disk space however
that is not the problem in this case as disk space is
excellent.

Can anyone give any pointers?

TIA.
Kristen

Hi Kristen,

Thanks for your post. According to your description, I understand you have
about 50 cubes which all process fine except one which returns the
following error:
"Error -2147221421 Internal Error: Could Not Update Query Log"

If I have misunderstood, please feel free to let me know.

Before we go any further, I would like to collect more information from you:

1. What is the version of Analyzer Services (Service Pack)?
2. If you only process the problematic cube, does the same problem occur?

Please make sure you meet the following requirements on your side.
1. The user has "FULL CONTROL" permission on both msmdqlog.mdb and
msmdqlog.ldb files (under <x>:\program files\microsoft analysis
services\bin)

2. Allowing local "OLAP Administrators" group to have FULL CONTROL on
folder <x>:\program files\microsoft analysis services\bin and
MSOLAPRepository$ (the share of the bin folder) and both msmdqlog.mdb and
msmdqlog.ldb files will resolve the issue.

3. The read-only attribute of the query log file is not enabled.
According to the error message, this occurs mostly due to a problem
updating msmdqlog.mdb in the bin directory of the product. This Jet file
might be corrupted or there is no disk space.

In this situation, you can try the following suggestions to see if they are
able to solve this problem.

1. Check for the space of the db/dbfile/hard disk (msmdqlog.mdb)

2. Try to compact the file in Access In Access 2002, please perform the
following steps.
In the menu, Tools-> Database Utilities-> Compact and repair database¡*

3. Turn off the query sampling in the options dialog on the server.
Right-click the problematic server-> Properties-> Logging tab -> clean up
the check box of the log queries sent to server option.

Thanks for using MSDN newsgroup.

Regards,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Thanks so much for your speedy reply.

Sorry - I just realised I was a unclear. It's the dimension thats the
problem not the cube.

Analysis Services Version 8.0.534

The dimension is processed by a DTS package which contains all 8
dimensions for that particular cube. The package is scheduled to run
nightly as an Agent job. This job fails whether run in the usual manner
(overnight with the other 50-odd dimension/cubes) or when run by itself.
That said, if I open the DTS package and execute the step for just the
one dimension which seems to be the problem, it is processed fine.

Security settings have not changed prior to this problem occuring and I
would expect that if it was a perms issue then, the other dimensions and
cubes would experience the same problem but it is always the same single
dimension affected. There is no OLAP Administrators local group and
the Users local group has Read & Execute, Read and List Folder Contents
access only.

The Query Log file is not Read Only.

Disk space is fine - the drive which has the mdf files has 112Gb free,
the c drive (where AS is installed) has 10Gb free and the drive which
contains the log files has 25Gb free. So disk space isn't the problem.

The mdb file is quite large I guess (1.5Gb) but the ldb is 7Mb so it's
quite small because we don't have logging turned on. Unfortunately
Access isn't installed on that server so I will need to see if I can get
our NT guys to arrange that and give the compact & repair a go.

Query Logging is not turned on. The checkbox on the logging tab is
unchecked so unless there's some other way it can be turned on, it's not
enabled.


*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Hi Kristen,

Thanks for your feedback. According to your description, I understand that
the error "Error -2147221421 Internal Error: Could Not Update Query Log"
occurred when you processed the dimensions in the DTS package. If I have
misunderstood, please feel free to let me know.

I would like you to provide more information so that I can narrow down this
issue.

1. What is the version of SQL Server (Service Pack)?
For more information regarding verifying the version of SQL Server, please
refer to the following article:
321185 HOW TO: Identify Your SQL Server Service Pack Version and Edition
http://support.microsoft.com/?id=321185


2. Please perform the following steps to provide all the error information
in the job history.
Right-Click the problem job->Click View Job History

3. Why do you think the error is induced by the specified dimension? Can
you please describe it in detail?

4. Do you have Analysis Manager (Analysis Services client tool) on your
side? If so, does the same error occur when you process the problematic
dimension using Analysis Manager?

Also, please let me know the result of the compact & repair for
msmdqlog.mdb.

I am looking forward to hearing from you soon.
Regards,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

oops sorry I misread - SQL is SP2.

Job History gives scant detail - "The job failed. The Job was invoked
by User CSR\KHodges. The last step to run was step 1 (Cell Process
Bricks,Pavers&Hebel Dimensions(PNL/FE/CF)))." On receiving that
notification from the job, I tried running it using Analysis Manager
(AM) and that is when I was able to see the Error 2147221421 message.
It seemed to take an extremely long time to read the rows in the
partition and before (if I recall correctly) it began the aggregations,
the error was shown.

I believe it to be one specific dimension because when I look at the
other dimensions in that cube they have all processed fine. And if I
process those other dimensions in AM there are no errors.

Will get onto that compact & repair asap - getting our NT guys to do
anything is always a struggle!!!

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

I think I may have found the cause. The source table the dimension
looks at was empty. Will see overnight if that fixed the problem.

cheers,

Kristen Hodges

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Hi Kristen,

Thanks for your feedback and good information. Please feel free to post in
the group if the same problem still occurs. I will continue to work with
you.

Thanks for using MSDN newsgroup.

Best wishes,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Yep that sorted the problem out.

Thanks for all your help Michael!

cheers,

Kristen Hodges

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!