+2
Has anyone else experienced issues on 5.6 where the timer step just does not pass?
In my case, even if the timer should halt for just 3-5 seconds, it never resumes.
Restarting the K2 Service (1-2 times) normally resolves this, but it is becoming an annoying hassle.
+8
Hello
SELECT a.[ID]
,a.[ProcInstID]
,P.Folio
,P.Originator
,a.[ItemID]
,a.[Type]
,a.[Date]
,a.[ServerID]
,a.[Status]
FROM [K2].[Server].[Async] a
left join [Server].[ProcInst] p on a.ProcInstID = P.[ID]
where a.[Date] < getdate()
order by a.[Date]
+2
Hello
SELECT a.[ID]
,a.[ProcInstID]
,P.Folio
,P.Originator
,a.[ItemID]
,a.[Type]
,a.[Date]
,a.[ServerID]
,a.[Status]
FROM [K2].[Server].[Async] a
left join [Server].[ProcInst] p on a.ProcInstID = P.[ID]
where a.[Date] < getdate()
order by a.[Date]
Hi Deon.
Yes, there is one.
Although, I don’t see an workflow linked to it.
+8
I would delete that one - it’s in the past - and see if that solves your problem.
+2
I would delete that one - it’s in the past - and see if that solves your problem.
Tnx Deon
Will give it a go.
Just to confirm, I don’t need to delete any other possible dependencies linked to that ProcInstID, do I?
+8
That Process Instance ID should at least be in the [ServerLog].[ProcInst] unless it was deleted with the delete history check flagged as true. I would leave it for now but it is an inconsistency for sure that it’s not in [Server].[ProcInst], but please make 100% sure you only delete thet 1 instance in the Async table, i.e. copy the ID and say delete from [K2].[Server].[Async] where ID = 2640492
+2
That Process Instance ID should at least be in the [ServerLog].[ProcInst] unless it was deleted with the delete history check flagged as true. I would leave it for now but it is an inconsistency for sure that it’s not in [Server].[ProcInst], but please make 100% sure you only delete thet 1 instance in the Async table, i.e. copy the ID and say delete from [K2].[Server].[Async] where ID = 2640492
Tnx Deon
I checked the workflow linked to the service instance, and it was one I created to specifically test Timer Events, so deleting the row from Async does not have direct consequences.
The record is still on the ServerLog.ProcInst table
I will keep in touch should the issue appear again.
Kind regards
+20
Hi
Did Deon’s reply resolve your question?
+2
Hi
Did Deon’s reply resolve your question?
Hi Milla
I can’t say for sure at this point in time. The issue happens spontaneously, so we have to keep an eye on the service to see if the issue occurs again.
I will respond promptly as soon as the issue shows itself.
Tnx
+20
Thank you
+2
Thank you
Hi Milla
It safe the to assume that
It’s been two weeks, and we haven’t picked up the issue since.
We also installed Fix pack 36 recently, so I don’t know if that also may have contributed to the resolution in some capacity.
Regards
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.