+2
Under review

operation is not valid due to the current state of the object keeps popping up

CFBDAVE 3 years ago updated 2 years ago 4

I keep getting this popup on certain clients.  It pops back up if I close the window, sometimes quick enough where I cannot even navigate to another client quick enough to stop the popup.  Server is self hosted and i run monthly maintenance to purge chat.

Version is 6.5.16479.6613

ConnectWise Control Version:
19.5
Server Affected:
Host Client Affected:
Guest Client Affected:

We are also having this problem.

I still get this quite often w/ no real explanation.  It will only occur for certain customer sessions and only when I access certain tabs.  RIght now I have a customer who does this when I go into chat.  It says I have a current chat and the red start is there indicating but I just get the above error.  There has to be a solution to this problem where is connectwise/screen connect support?

This was the response and explanation I received.


The underlying issue occurs if a connection is deleted before an unacknowledged sessionconnectionevent is acknowledged. So if your end user sends you a message, but that event gets deleted without being viewed, this error will occur.


Unfortunately this is still a known issue, though it does not look like our bug report has updated just yet on that item: https://control.product.connectwise.com/communities/6/topics/1701-operation-is-not-valid-due-to-the-current-state-of-the-object-keeps-popping-up


It looks like this item has a potential fix set for 6.8, but is still currently in QA so a bit too far out to make any assumptions. In your shoes, I may recommend following that bug report, as well as our output stream (http://controlforum.connectwise.com/yaf_topics9_Output-Stream.aspx) to see any status changes related to it.

Who can delete this without being viewed and how exactly?  We have maintenance triggers but it would  delete chats over 30 days old and we don't miss chats for 30 days.  I'm on  6.7x still (latest) so let's hope 6.8 fixes that.  I'll look into that link.

Dave