APPCRASH SO/IM/MF

Posted By w855173w over 9 years ago

2 weeks ago we upgraded to Sage 2013 October MRU and Citrix 7.5 (2008 r2). We run DC Warehouse so we are unable to upgrade any further at this time. Some users have been experiencing an intermittent generic APPCRASH.. So far it seems to occur in SO sozdj101.exe, MF mfzdb001.exe and IM (rarely).. mfzdb001.exe has been customized and the other two have not. We are unable to recreate the error and can go a full day without hearing about it. Sometimes all of the user has to do is enter the WO# or SO# and hit tab then BOOM. This crash has occurred outside of the virtual Citrix environment which eliminates any server related memory leaks & hot fixes.

I have updated permissions in the registry for the state of the art key, folder permissions for the Sage install, recreated user profiles, MAS500 profiles, replaced the workstation/thin client..

I can't seem to find any info on this.. Anyone have any other ideas I could try?

Parents

0 w855173w over 9 years ago

Just a quick update: we were able to recreate the error in the Work Order Maintenance screen so it made things a bit easier to troubleshoot. I have tried the following with no results: .NET 4.0, 4.5.1 and 4.5.2 update, DEP disabled and UAC disabled.

The very last thing I tried was changing the compatibility mode on the module exe itself to windows xp sp3.. I was not able to recreate the error! Since we have multiple modules that are affected I am testing compatibility mode on businessdesktoploader.exe fingers crossed that this works! So much for 2013 being compatible with windows 7 or server 2008 r2!!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 JohnHanrahan over 9 years ago in reply to w855173w

Nice job on the troubleshooting.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 w855173w over 9 years ago in reply to JohnHanrahan

Thank you! I have a bad feeling about running the loader in compatibility mode and might have to do just the affected modules individually :/

so far they are MCZMB001.exe sozdj101.exe sozda101.exe mfzdb001.exe* mfzda001.exe mfzrv001.exe imzqk001.exe Imzmt001.exe pozda001.exe Apzdj001.exe

Monitoring the logs today...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 w855173w over 9 years ago in reply to w855173w

Compatibility mode on desktoplauncher caused “Unable to create MAPI Session or log on to specified Mailbox” with e-invoicing.. So back to compatibility on individual exe's and case opened with Sage :/
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ralph. over 9 years ago in reply to w855173w

What operating system was your Sage 500 client software running on just prior to this upgrade?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Ralph. over 9 years ago in reply to w855173w

What operating system was your Sage 500 client software running on just prior to this upgrade?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 w855173w over 9 years ago in reply to Ralph.

It was on server 2003 and windows 7 pro.. I was able to recreate the WO error on our Sage re-sellers machine which tells me this is a Sage issue and not specific to our environment. Since setting the WO compatibility mode we have not seen an error for WO maintenance on server 2008 r2 or windows 7 pro.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Sage 500

APPCRASH SO/IM/MF

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING