Enterprise Workflow .Net Client Crashes on Startup

From Support

If you have a question or seek clarification, please call Technical Support.

Problem:

Enterprise Workflow .Net Client Crashes on Startup

User is running into an issue where the Enterprise Workflow .Net Client is crashing on some Windows XP machines when it starts up, but it works fine on others.

The following message is shown right away on startup: The error text in the message box is: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

When the user clicks OK on the message box, all settings are missing.

Then another message box may appear with a Red X on it and the following message: Unhandled exception has occurred in your application.

In the error message box is a list of Exception text that says something similar to: System.Configuration.SettingsPropertyNotFoundException.

From what we can tell something is causing the user settings properties file to get corrupted.

This may have something to do with the .Net 2.0 SP1 Framework Update, but we're not sure yet.

Solution:

It appears that something within the .Net 2.0 settings mechanism is causing settings file corruption of some sort after an application is recompiled and updated on a PC.

The Enterprise Workflow .Net client holds its property settings in the following directory for each user:

C:\Documents and Settings\<windowsusername>\Local Settings\Application Data\RJS_Software_Systems_Inc\WorkflowDotNetClient.exe_Url_203ostrzhxvjprkdu4h2ek0bz5scqpn5

Note: the directory name may not be exactly the same for each user, but it starts with: WorkflowDotNetClient.exe_Url

Note: Where we specified <windowsusername>, substitute the appropriate Windows user name info.

The quick way to browse the appropriate folder is to type Start/Run and enter the following where <windowsusername> is the current user: C:\Documents and Settings\<windowsusername>\Local Settings\Application Data\RJS_Software_Systems_Inc

After locating the WorkflowDotNetClient.exe_Url directories (there may be one or more), simply delete the directories and all info within the WorkflowDotNetClient.exe_Url directory.

Then try re-starting the Enterprise Workflow client, re-enter settings and see if it works as expected.

If not, please let us know.