It's possibly related to MVC custom routes, but it sounds more like a missing column name.
My next step is either to uninstall and re-install, but analyse the DB from a clean SEOChecker install in a new Umbraco install. However perhaps you're able to steer me more accurately to the root of the problem?
This was a bug in an older version of SEOChecker indeed. If you drop the SEOCheckerPageNotFound table and create again with the following script all should be good,
CREATE TABLE [dbo].[SEOChecker_PageNotFound](
[NotFoundId] [int] IDENTITY(1,1) NOT NULL,
[Url] [nvarchar](255) NOT NULL,
[DocumentID] [int] NOT NULL,
[Ignore] [bit] NOT NULL,
[TimesAccessed] [int] NOT NULL,
[LastTimeAccessed] [datetime] NULL,
[RedirectUrl] [nvarchar](255) NOT NULL,
[Referer] [nvarchar](255) NULL,
[ContentType] [nvarchar](255) NOT NULL,
[Domain] [nvarchar](255) NOT NULL,
[QueryString] [nvarchar](255) NOT NULL,
[WildCard] [bit] NOT NULL,
CONSTRAINT [PK_SEOChecker_PageNotFound] PRIMARY KEY CLUSTERED
(
[NotFoundId] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
SQL error in version 2
We installed v2.0 and upgraded to v2.1. I've now noticed lots of error log entries:
ClientConnectionId:19ee434e-ba05-4cea-92c5-35d9dde794b2 Error Number:207,State:1,Class:16 ```
It's possibly related to MVC custom routes, but it sounds more like a missing column name.
My next step is either to uninstall and re-install, but analyse the DB from a clean SEOChecker install in a new Umbraco install. However perhaps you're able to steer me more accurately to the root of the problem?
Hi David,
This was a bug in an older version of SEOChecker indeed. If you drop the SEOCheckerPageNotFound table and create again with the following script all should be good,
Hope this helps,
Richard
Wonderful. Thanks Richard
is working on a reply...