Maintain Database Indices job error 404

Daniel Sandberg

Vote:

I get the following error when running the MaintainDatabaseIndicesJob. Does 404 have something to do with Http 404?

Job EPiServer.Business.Commerce.ScheduledJobs.MaintainDatabaseIndicesJob failed for the job 'Maintain Database Indexes' with jobId ='17fe1abe-9592-47d5-b140-3e37f285f55c' 
System.Data.SqlClient.SqlException (0x80131904): Incorrect syntax near '404'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at EPiServer.Business.Commerce.ScheduledJobs.MaintainDatabaseIndicesJob.RebuildIndexesInCmsDB()
   at EPiServer.Business.Commerce.ScheduledJobs.MaintainDatabaseIndicesJob.Execute()
   at EPiServer.Scheduler.Internal.DefaultScheduledJobExecutor.<Execute>d__31.MoveNext()
ClientConnectionId:9dfc4325-b237-47f0-b8aa-455483c1ddc8
Error Number:102,State:1,Class:15

#249772

Mar 09, 2021 13:22

Quan Mai

Vote:

Not really, I think you are running on an old version, and you have the https://github.com/Geta/404handler (formerly BVN Network 404 ) installed. The bug was fixed on EPiServer.Commerce 13.3.1

#249773

Mar 09, 2021 13:46

- Mar 09, 2021 15:14

I am running version 12.12. What is the bug?

- Mar 09, 2021 15:34

COM-9475

- Mar 09, 2021 15:51

basically the 404handler creates some tables with unusual name, like 404.something. 13.3.1 handles that better

- Mar 10, 2021 7:40

Aha. I see. But we are not ready to upgrade just yet, is there a temporary workaround? Actually the job runs in our test environments, but doesn't work in production.

- Mar 10, 2021 8:28

You can theoretically run the script manually, or create a job with that script. Reach out to Support so they can help with