SUPPORT Q&A - Curious Error

daniel.broomall - Friday, May 4, 2007 2:03 PM:

I am a new member to the Innovator family and I've run across a curious error.  While setting up a development instance of Innovator, I've run across an error with editing an Identity I created:

Update failed: the Identity is not locked by you.

The problem with this error is that I am currently the only one working in the system.  On top of that, the record doesn't show as locked within the view display.  Has anyone seen anything like this along the way?  Any guidance you can provide would be greatly appreciated.

Thanks

RobMcAveney - Monday, May 7, 2007 1:55 PM:

Hi Dan, and welcome.  The error you are seeing results from a synchronization problem between the client and server.  In other words, the server is reporting that your item is locked, but for some reason the client doesn't have the same information.  This error does not usually pop up in normal usage, but there are a couple of ways it can happen:

1. The same login user opened multiple login sessions and modified the same items
2. A connectivity or timeout problem resulted in the server completing an operation without the client being notified

Either way, you should be able to clear the error by simply closing all client sessions and restarting.

Hope that helps -

Rob 

daniel.broomall - Tuesday, May 8, 2007 5:13 PM:

Rob

Thanks for your quick response.  I did close out the client sessions and that worked.  It's nice to know the cause for future reference.

Again, I appreciate your help.

fgosselin - Friday, April 11, 2008 2:59 PM:

Hello,

 Hope you can help me as well. We are starting to have this error more and more often now. Users lock items, make a few changes and when attempting to save, they have this same error message.  The item is still displayed as 'locked' on the client side. No concurrent session exist for those users at that time.

Usually by cancelling the changes, refresh the item, locking the item once again, will work after a few tries.

Any solution to make sure that the client and server are synchronized on the item status?

 Thanks 

Bill - Friday, April 18, 2008 7:33 PM:

Are there any methods that could be unlocking these items on the server?

A good indicator is the context of the problem.  If it is only happening for Documents, then there could be a method that is unlocking the items when another action is performed.

Is this happening for one ItemType or many?

-Bill

fgosselin - Tuesday, April 22, 2008 12:16 PM:

There is no method I can see that might unlock this item. No events are triggered at that point. The item is simply locked for editing.

This seems to be happening on a single ItemType so far.

 
Thanks for following up.

Bill - Tuesday, April 22, 2008 12:35 PM:

Is it a standard ItemType like Part or a custom ItemType?  (Just want a baseline if I have one.)

Thanks,

Bill

fgosselin - Tuesday, April 22, 2008 1:38 PM: