Problem with the dll (version 1.2) of an Extended Stored Procedure with SQL Serv

Question

Post reply

Problem with the dll (version 1.2) of an Extended Stored Procedure with SQL Serv

SKEITA

Valued Member

Points: 62
More actions
January 20, 2025 at 3:33 pm

#4519276

SQL Server 2022 16.0.4165.4
Windows Server 2022 Datacenter 21H2 20348.2849
Our Extended Stored Procedure works 95% but it occasionally generates overflow errors (BEX64) in the Windows event log.
In the Event Viewer we have an Information Event 1001 from Windows Error Reporting (Event name BEX64 and SQLException64). What's strange is that this indicates that there was an error with version 1.1, a previous version of our dll and with version 16.0.4125.3 of SQL Server 2022.
We tried uninstalling Extended Stored Procedure and SQL Server updates up to version before 16.0.4125.3 but the error remains the same.
Same by deactivating our antivirus or installing our dll in the C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\Binn directory.
When we set up a new server with version 1.2 of our dll, there is no problem.
I have more than 100 servers so this is not a feasible solution.
We are looking to add logs to our dll but also to migrate to CLR.
On the other hand, it is absolutely necessary to understand why in the Event Viewer the error information is false.
Do you have any ideas or suggestions?
January 31, 2025 at 8:29 am

This was removed by the editor as SPAM
February 6, 2025 at 7:31 am

This was removed by the editor as SPAM

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Site Owners SSC Guru Points: 80323 More actions · Answer 1

Thanks for posting your issue and hopefully someone will answer soon.

This is an automated bump to increase visibility of your question.

Jeff Moden SSC Guru Points: 1004495 More actions · Answer 2

I don't have any help to offer because I don't build CLRs on our systems and so have zero experience there.

As a bit of a sidebar, though, what does your CLR actually do?

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

EdVassie SSC Guru Points: 60489 More actions · Answer 3

If SQL reports an error, even if you think it is a false positive, you have a problem you need to deal with.

IMHO if you know that a new version of your DLL does not report an error then the simplest way forward is to upgrade all servers to the new version.

Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara