Daniel Halse
Jun 8, 2023
(3 votes)

Prevent SQL error on CMS 12 minor version update

If using an early version of CMS 12, like 12.0, you will get an SQL error after upgrading to newer patch versions.
The fix for this is minor locally using SQL:

CREATE PROCEDURE dbo.netSoftLinksGetBroken

This will create the missing stored procedure and allow it to proceed.
But as this is a pain when dealing with DXP environments there is a better way to fix this before deployment:
  1. Go to reports in the CMS
  2. Run the broken links report
  3. If this fails then you may need to get Optimizely support involved
  4. If this succeeds then the stored procedure above has been created correctly and used
  5. Optionally download the DB from PAAS portal and verify that the dbo.netSoftLinksGetBroken stored procedure is present
This has been raised before:
The bug for which was closed without being fixed:
Bug - CMS-26818 (optimizely.com)
I suspect the issue is mainly visible on new sites / databases only so will more commonly be seen in early development.
Jun 08, 2023


Ethan Schofer
Ethan Schofer Jun 9, 2023 06:02 PM

Daniel - what I have been seeing with this error is that these Stored PRocedures get created, but with the wrong SQL schema. I have to manually update the Schema myself, which is a problem on DXP environments.

Please login to comment.
Latest blogs
Performance optimization – the hardcore series – part 2

Earlier we started a new series about performance optimization, here Performance optimization – the hardcore series – part 1 – Quan Mai’s blog...

Quan Mai | Oct 4, 2023 | Syndicated blog

Our first steps into local AI

After a consumer of tools like ChatGPT and CoPilot, we as developers like to dive deeper into it. How does it work? Where to start? Can I create my...

Chuhukon | Oct 4, 2023 | Syndicated blog

Update on .NET 8 support

With .NET 8 now in release candidate stage I want to share an update about our current thinking about .NET 8 support in Optimizely CMS and Customiz...

Magnus Rahl | Oct 3, 2023

Adding Block Specific JavaScript and CSS to the body and head of the page

A common requirement for CMS implementations includes the ability to embed third party content into a website as if it formed part of the website...

Mark Stott | Oct 3, 2023