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
Apparently we changed how we interact with SQL in SL 2011 that causes this needing setting change.
Thanks! It works like magic (I guess it is a SDK requirement.)
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
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (