we've stumbled upon an odd behavior at one of our customers:

During a C# program accessing the GroupWise Object Store through the
Groupwise Object API, we trigger the Garbagabe collection with the


If we do not do that, our program runs into the following exception
after a time:

"System.AccessViolationException: Attempted to read or write protected
memory. This is often an indication that other memory is corrupt.
at System.RuntimeType.ForwardCallToInvokeMember(Strin g memberName,
BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData&
at GroupwareTypeLibrary.DIGWAccount6.get_AllFolders()
com.vivex.update.groupware.GroupWise.GroupWiseInte rfaces.OAPIGroupWise.GetMessages(DateTime
modified, GroupWiseRetrievalSettings settings) in
E:\Projekte\update.groupware for GroupWise\update.groupware for
groupwise\GroupWise.cs:Zeile 2805.
com.vivex.update.groupware.GroupWise.Synchronizer. SyncMessages(User
user, GroupWiseRetrievalSettings settings, DateTime lastRetentionDate,
DateTime nextRetentionDate, DateTime lastSyncDate, DateTime
nextSyncDate) in E:\Projekte\update.groupware for
GroupWise\update.groupware for groupwise\Synchronizer.cs:Zeile 584.

Now at our customer's, this instruction does not return. This occurs on
differing machines, all running DotNet 2.0.50727, which we also run on
our test environment, where this behavior is unheard of.

Has anyone else ever encountered a similar problem?

Thanks for the help.

Best regards, Martin Schmidt.