Hello,
For our customers system we have two different servers where the specific services are running.
Specifically, it deals with the problem that a service on server A, which has activated the TaskScheduler and is only responsible for the job queue, has an error in combination with a service on server B, which is only responsible for web services for the web store.
This is a snippet from the server responsing with the errors:
It’s important to know, that both Services on both Server have most of their interaction with SalesHeader and SalesLine.
We’ve already invested lots of time with analyzing SQL Server Management Studio and therefore we also introduced some deadlock monitoring.
This is one of the resutls that is corresponding to the above error message:
unknown
(@0 nvarchar(20),@1 nvarchar(10),@2 nvarchar(10))SELECT "99000850"."timestamp","99000850"."Item No_","99000850"."Variant Code","99000850"."Location Code","99000850"."Latest Date","99000850"."Inactive","99000850"."Action Msg_ Response Planning","99000850"."Net Change Planning","99000850"."$systemId","99000850"."$systemCreatedAt","99000850"."$systemCreatedBy","99000850"."$systemModifiedAt","99000850"."$systemModifiedBy" FROM "biohof".dbo."Example$Planning Assignment$437dbf0e-84ff-417a-965d-ed2bb9650972" "99000850" WITH(UPDLOCK) WHERE ("99000850"."Item No_"=@0 AND "99000850"."Variant Code"=@1 AND "99000850"."Location Code"=[@2)]
unknown
(@0 nvarchar(20),@1 nvarchar(10),@2 nvarchar(10))SELECT "99000850"."timestamp","99000850"."Item No_","99000850"."Variant Code","99000850"."Location Code","99000850"."Latest Date","99000850"."Inactive","99000850"."Action Msg_ Response Planning","99000850"."Net Change Planning","99000850"."$systemId","99000850"."$systemCreatedAt","99000850"."$systemCreatedBy","99000850"."$systemModifiedAt","99000850"."$systemModifiedBy" FROM "biohof".dbo."Example $Planning Assignment$437dbf0e-84ff-417a-965d-ed2bb9650972" "99000850" WITH(UPDLOCK) WHERE ("99000850"."Item No_"=@0 AND "99000850"."Variant Code"=@1 AND "99000850"."Location Code"=@2
How can we avoid this error message? Why does it always interact with the Planning Assignment table? Is there any way to stop this?
thx 