RuntimeError: workspace already in transaction mode

[AddisalemAbera1]

While editing a version via python there was an error with accessing a remote database I was getting values from. This loop had already successfully completed a few thousand times before I had an error accessing the remote database.

I then stopOperation() and then stopEditing(True) and attempted to restart my python script but now I get a runtimeError

RuntimeError: workspace already in transaction mode

I’m the only person who access this version but I have no idea how to get it out of transaction mode?

I tried restarting, disconnecting users (well disconnecting myself), and I tried restarting my computer. Do any of you have any other suggestions that may work?

[JoshuaBixby]

It is helpful if you can include your code, at least the functional parts like the calls to start the define the edit session, start it, stop it, etc....  Also, are you working with cursors within the edit session or Geoprocessing tools? 

[JoshuaBixby]

Although the screenshot may be helpful, seeing the actual Python code you are using is really necessary to comment any further.

[BlakeTerhune]

Posting Code blocks in the new GeoNet