Smart Connector Maintenance Utility

[Richard_M]

Hi Everyone,

I have a customer using the Maintenance Utility processor to clean up subscriptions but it doesn't appear to be running successfully.

An excerpt of the error is below (and a log snippet attached).

The SQL Express db had filled to 10GB over the past two years. We installed the Maintenance Utility to stop this happening. I cleaned up the db (it came down to 20MB) but the error still occurs.

Does anyone have any ideas why this is happening? The site is running SC v2.4.x

-----------------------

 2023-01-20 16:25:46.5723,Info,Processor,<no principal>,Validation Prompt for Kaba Door Lock EWS Maintenance Utility: MayNotContinue : An error occurred while executing the command definition. See the inner exception for details.
The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information.
at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior)
at System.Data.Entity.Core.Objects.Internal.ObjectQueryExecutionPlan.Execute[TResultType](ObjectContext context, ObjectParameterCollection parameterValues)
at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__5()
at System.Data.Entity.Infrastructure.DbExecutionStrategy.Execute[TResult](Func`1 operation)
at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)
at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__0()
at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Mongoose.Service.Data.MongooseDbContext.Mongoose.Common.Data.IDataSource<Mongoose.Ews.Server.Data.EwsNotification>.Delete(IList`1 items)
at Mongoose.Ews.Server.Data.EwsServerDataAdapter.DeleteNotifications_Internal(EwsSubscription subscription)
at SmartConnector.Utilities.EwsServer.EwsItemManager.DeleteSubscriptionNotifications(IEnumerable`1 subscriptions)
at SmartConnector.Utilities.Maintenance.EwsServerCleanupProcessor.Execute_Subclass()

[ard]

Truncate the tables and update to a 2.5.x version, cleanup is automatic from 2.5 and forward. It will give you problems if you don't truncate the big tables first though.

[MaximeLaudren]

Hey @Richard_M,

Before upgrading to newer version of the smartconnector, always check that your processors are compatible with the new version.

Did you try to restart both the SQL and SC services?

Can you check with SSMS inside the properties of the Smartconnector.service table, what's the size and space available?

Is there still space available on the disk of the machine?

Can you also check what's the stats in the about page:

Max

[Richard_M]

Hi @MaximeLaudren ,

I'm not planning on updating the SC version any time soon. This is the door lock SC site you helped me with a couple of years ago so I'm not going to make any changes unless I absolutely need to.

I have an active support case open at the moment (98710859) but we are still just gathering data.

I'm not sure if I have restarted the SQL service. The SC would have definitely been restarted though.

The database was sitting at about 1.5GB when I looked last week so there is still plenty of drive space. 

I'll check the SC stat's page next time I'm on. Below is a summary of the processor from last week.