Microsoft Dynamics SL (Archived)

Assertion failure parinter.cpp line 90

(0) Share

Report

Posted on by Community Member

When launching DSL I get the following

---------------------------
System Message 10232
---------------------------
Assertion failure!

File: parinter.cpp
Line: 90

Expression: am.pAppNotificationfunc

Hit OK to stop program, and report the error to Microsoft Support,
noting the failed expression, file name and line number.
---------------------------
OK
---------------------------

I've been noticing this issue on several machines. Some get it and you reboot and it goes away. Others get it all the the time. After getting this message MSDynamicsSL.exe is completely hung. I have yet to figure out what the cause or solution is.

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (1)

Community Member on at

Like (0)

Report

Sorry this is Dynamics SL 2015 CU1

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I noticed it when DSL 2015 Cu1 is launched from the startup folder, from a batch file, from a powershell script, from the task scheduler, from a program called tech scheduler, from the gulfstream launcher and when launching Dynamics SL manually. I’ve gotten this on Windows 8, Server 2012 R2, and on Windows 10. When I get this message MSDynamicsSL.exe is completely hung not responding to mouse clicks or other requests to terminate and needs to be killed from the process list. Also Windows Error Reporting (WER) is very active till the MSDynamicsSL.exe is killed off. The WER suggests the problem is in MSDynamics.exe and SWIMAPI.dll. I have not been able to successfully replicate the issue on demand. My current theory is that if you try to launch Dynamics to soon after windows boots you get the assertion in parinter.cpp at line 90.

Does anyone know what Expression am.pAppNotificationfunc is or what it is trying to do at line 90 in parinter.cpp and a solution to this? This is stopping things like Process Manager, Applications Server, and our 3rd party Barcode Gateway from functioning reliability.

Was this reply helpful? Yes No
Laura 460 on at

Like (0)

Report

Rob,

Did you determine the cause of the Assertion error? I have an SL 2011 FP1 client with the same exact error.

Any insight would be helpful.

Thanks,

Laura Vogel

Was this reply helpful? Yes No
Butch Adams 4,763 on at

Like (0)

Report

I have a situation with this error as well. 2011 FP1 with SP2 applied.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

After much angst trying to get around this we finally figured this out. If you attempt to launch a program before the "Parent" is ready you get this. I am guessing ParInter.cpp is short for Parent Interop. So if you launch a module and parent is not running you will get this error. You also get this is parent is not 100% ready. I've gotten this error when launching DSL automatically via a shortcut in Startup and by clicking a favorite as soon as it was displayed right after boot. If you wait for the system to stabilize then you avoid this error.

Was this reply helpful? Yes No
Butch Adams 4,763 on at

Like (0)

Report

Ok! that makes sense in relation to my observations.

I have been trying to run ROI.exe from the command line, and it works fine in three environments, but a fourth one I have tried it consistently fails.

There must be something causing the start up to be slower in that fourth environment.

Thanks for sharing that.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Not sure if this is your issue, but we have seen Windows Defender update CR 3692 cause this issue before.

Resolution

There are 3 options that can allow you to keep the Windows updates turned on and have Dynamics SL functional.

1.Open Windows Defender and go to Tools|Options. Click Real Time protection—deselect the “Use real-time protection” option.

or

2.Deselect the “Scan programs that run on my computer” option

or

3.Click on “Excluded file types” Click Add and type in: *.exe

Was this reply helpful? Yes No
Butch Adams 4,763 on at

Like (0)

Report

This sounds really promising except I am on a 2012 server desktop with not Defender/Anitvirus installed and the DB and SL files all local. The task fails on the workstations in this environment as well, but I don't have remote access to them for testing like I do the server desktop.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Good suggestion for testing but I had completely removed AV for testing and still got this message. I can see where scanning EXEs might cause Dynamics SL to choke while launching. The suggestion that you basically disable end point protection might cause some issues especially where compliance is an issue and I personally could not recommend running without AV for a daily user.

Was this reply helpful? Yes No