web

You’re offline. This is a read only version of the page.

News and Announcements icon

Dynamics 365 CommunityForums Microsoft Dynamics SL (Archived) Assertion failure

Microsoft Dynamics SL (Archived)

Assertion failure

(0) Share

Report

Report

Posted on by Community Member

The error comes up randomly. Tried c:\Windows\SysWOW64\regsvr32.exe C:\Windows\SysWOW64\msigrid.ocx that doesn't help.

also tried removed customization as well. (delete FROM [Sys].[dbo].[CustomVBA] where ScreenId ='xd10000')

Any input is helpful, thanks.

*This post is locked for comments

I have the same question (0)

All responses Img

All responses (3)

Answers Img

Answers (1)

Verified answer

Community Member on at

Like (0)

Report

In the past we have seen this assertion failure being called if there is a custom trigger that has the following line:

Set Nocount Off

If you run the following script it will show you all of the triggers on the database. You will need to review the triggers and make sure none of them contain the Set NoCount Off line.

Select * from sysobjects where xtype ='tr'

Then to review each trigger whose name begins with X (by convention a customized trigger should have a name starting with x) using this command:

sp_helptext xtriggername

Here is an example of how you would modify the trigger to Set NoCount On.

Example of how to set this to ON:

alter TRIGGER TrnsfrDocStatusUpdate ON TrnsfrDoc

FOR INSERT, UPDATE

AS

Set NOCOUNT ON

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks! It works like magic (I guess it is a SDK requirement.)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Apparently we changed how we interact with SQL in SL 2011 that causes this needing setting change.

Was this reply helpful? Yes No

Helpful resources

Quick Links

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans