We are having problems with Analysis Server crashes (unrelated to my earlier
message) whereby the server will crash if a dimension (or cube) is locked
for editing and the cube processing kicks off:

Exception Type: System.Runtime.InteropServices.COMException
ErrorCode: -2147221468
Message: User EXDBGCC\Administrator on computer exdbgcc has locked 'Wrap
Up'.
Description: Dimension 'Wrap Up' has been locked for writing by Dimension
Editor.
TargetSite: Void Process(Microsoft.SQLServer.DSO80.ProcessTypes)
HelpLink: NULL
Source: DSO

Is followed by:
Unexpected fatal error occurred. Attempting to restart server.

Is there a fix for this issue. If not, can I work around it?

Regards,
James Snape

Hello Jim,

I would appreciate your patience, while I am having OLAP experts to look
into this issue. I will keep you posted as soon as I have an update for you.

Thanks for using MSDN Managed Newsgroup.

Vikrant Dalwale

Microsoft SQL Server Support Professional


Microsoft highly recommends to all of our customers that they visit the
http://www.microsoft.com/protect site and perform the three straightforward
steps listed to improve your computer’s security.
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
..phx.gbl

Jim,

Thanks for your questions.

I can reproduce the ErrorCode: -2147221468 by the following steps:

1. Open Analysis Manager, Open the dimension editor windows against the
dimension "Product"

2. Open VB studio (6.0), make sure refrence the DSO object, and run the
following programming copied from
http://msdn.microsoft.com/library/de...us/olapdmpr/pr
dimensioni_7f03.asp:

Dim dsoServer As New DSO.Server
Dim dsoDB As DSO.MDStore
Dim dsoDim As DSO.Dimension

' Connect to local Analysis server.
dsoServer.Connect "LocalHost"

' Open FoodMart 2000 database.
Set dsoDB = dsoServer.MDStores("FoodMart 2000")

' Open the Product dimension.
Set dsoDim = dsoDB.Dimensions("Product")

' Lock the dimension for processing.
dsoDim.LockObject olapLockProcess, "Locked for processing."

' Completely reprocess the dimension.
dsoDim.Process processFull

' Once complete, unlock the dimension.
dsoDim.UnlockObject

' Clean up.
Set dsoDim = Nothing
Set dsoDB = Nothing
dsoServer.CloseServer
Set dsoServer = Nothing

I get the following error:
Run-time error '-2147221468 (80040024)':

User <user name> on computer <computer name> has locked '<Dimension name>'
Description: Dimension editor has locked dimension 'Product' for writing


This is expected behavior.
Before processing dimension "Product", Analysis Service needs read
dimension definition from the repository database. Since dimension editor
window for the "Product" dimension is still open, which prevents anybody
accessing the dimension definition to cause the above error.

But my server does not crash. Can you give me steps to crash the crash the
server?

Thanks!

Jean Zhang

Hi Jean,

Thanks for your response. I'm not sure exactly what will crash the server as
I have difficulty reproducing it in the office (we are currently seeing the
behaviour on a customer site).

Some differences from your sample are as follows:
1. I don't call lock object - an oversight on my part, I will see if it
makes a difference
2. I am cloning and merging partitions
3. I am also processing virtual cubes
4. The processing code is C# not VB

Regards,
James Snape


"Jean Zhang [MS]" <jeanzha (AT) microsoft (DOT) com> wrote

Hi Jim,

Yes, Calling lock object during processing OLAP objects is very important.

Please take following steps to setup the utility to collect the user dump
once the problem occurs again:

1. copy the file dbghelp.dll from SQL Server folder ?:\Program
Files\Microsoft SQL Server\MSSQL\Binn. Make sure the file version is
6.1.3.0, or later into AS folder ?:\Program Files\Microsoft Analysis
Services\Bin.

2. create these registry settings in the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\CurrentVersion Registry
key:

- SQLDUMPERDIR: This registry entry is a STRING. It has the path for
where the dump files are created.

example: SQLDUMPERDIR = C:\dumpfolder

- SQLDUMPERFLAGS: This registry entry is a DWORD. The hexadecimal value
is a bit-mask of the following values:

SQLDUMPERFLAGS = 3F4 (as a hexadecimal value)

Once your AS server crashes, please provide us user dump and application
event log.

Thanks!

Jean