A
Anderson Imes (Mary Kay, Inc.)
I am using the WorkflowCompiler to compile xoml workflows at runtime into DLL
files. This has been working great, but lately after upgrading to .NET 3.5
(it seems - possibly this is unrelated) sporradically I get the following
error:
System.AccessViolationException: Attempted to read or write protected
memory. This is often an indication that other memory is corrupt. at
System.Workflow.ComponentModel.Compiler.WorkflowCompilerInternal.Compile(WorkflowCompilerParameters
parameters, String[] allFiles) at
System.Workflow.ComponentModel.Compiler.WorkflowCompiler.Compile(WorkflowCompilerParameters
parameters, String[] files) at
MaryKay.CRM.BusinessLayer.WorkflowUtil.CompileWorkflowXoml(String xoml) in
C:\Projects\FrontOffice\SAM-CRM\Current\Service
Interface\MaryKay.CRM.Services\WorkflowUtil.cs:line 127
This is inconsistent and nearly impossible to debug (since it appears to
happen inside the .NET Framework). We've rebooted the server, done other
things and nothing seems to consistently resolve the issue - it just comes
and goes.
If I don't hear back from anyone on the newsgroups, I'll open an incident
with Microsoft.
Thanks in advance for your help.
files. This has been working great, but lately after upgrading to .NET 3.5
(it seems - possibly this is unrelated) sporradically I get the following
error:
System.AccessViolationException: Attempted to read or write protected
memory. This is often an indication that other memory is corrupt. at
System.Workflow.ComponentModel.Compiler.WorkflowCompilerInternal.Compile(WorkflowCompilerParameters
parameters, String[] allFiles) at
System.Workflow.ComponentModel.Compiler.WorkflowCompiler.Compile(WorkflowCompilerParameters
parameters, String[] files) at
MaryKay.CRM.BusinessLayer.WorkflowUtil.CompileWorkflowXoml(String xoml) in
C:\Projects\FrontOffice\SAM-CRM\Current\Service
Interface\MaryKay.CRM.Services\WorkflowUtil.cs:line 127
This is inconsistent and nearly impossible to debug (since it appears to
happen inside the .NET Framework). We've rebooted the server, done other
things and nothing seems to consistently resolve the issue - it just comes
and goes.
If I don't hear back from anyone on the newsgroups, I'll open an incident
with Microsoft.
Thanks in advance for your help.