Hi,
First of all:
Our application has been written in C# and VB.NET Framework 1.0. We use SQL
Server and Analysis Services 2000.(SP3 and ASP3 respectively)

In our application, we have a service that repeatedly performs many cube -
related operations using DSO. These operations are like creating / deleting
partitions, processing them etc.

Just recently, I saw an error in the logs that occured while processing a
dimension in the cube (Note : Service was running fine for about 6 days):
System.Runtime.InteropServices.COMException (0x800A000E): Out of string
space
at DSO._Dimension.Process(ProcessTypes Options)

Thereafter some other cube operations (creating/deleting partitions/getting
partition count etc) also gave the same error.

Also, after about 1 hour of getting the first exception, I am also getting
System.OutofmemoryException although about 2GB of memory is available for
Analysis Services.

Exception text from logs :
Error Message = System.OutOfMemoryException: Out of memory
at DSO.ServerClass.Connect(String ServerName)

Seems to be a problem with using DSO (which uses COM-interop) with managed
applications.
These exceptions are affecting our application in a big way.
Is there any solution any one has to offer?
It would be of great help.

Thanks in advance,
Srikanth

Is your code multithreaded? If it is, change it to multiple processes
and use an OS mutex around any edits. I was experiencing a similar
error when I tried parallel processing using parallel threads. It
works much better now with parallel processes.

Hi,
Thanks for the reply, Scott !
But, my code is not multithreaded. I have a single thread that does all the
operations.

Thanks,
Srikanth

"scott_gunn (AT) email (DOT) com" wrote:

Because COM uses reference counting you need to make sure you are
clearing object references. In particular are you sure that every time
you call .Connect on the DSO.Server object that there is a matching
..CloseServer?

Similarly, if you call .Lock on an object you should make sure that
there is a matching .Unlock. In .Net you can implement this pattern a
lot easier than in VB6, by using a try..finally block.

I suspect the memory issue will be referring to your tool/service rather
than to Analysis Services.

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