cannot edit code in SDK

[Former Member]

Hello

My colleague created a small project that I have to update. However, I cannot edit the project, getting following error time after time

I'm pretty positive that the user ***QBY who reportedly locked required objects is not logged in at this time. Possibly he has to do something on his end before I can have a change/write access to his code?

Thanks

[astrid_burghart · Accepted solution]

Hi Max,

you colleague didn't checked in the Object.

He can see that on the small tickle before the Object Symbol like here:

You should see an other small symbol before the Object.

To check in, the user who checked it out has to right click on the Object and choose "Check In Content".

If you have the latest Status of the coding in the Studio, you can go to the session Administrator and kick your colleague. This should check in the files.

Be aware that the latest implementation might get lost. Please do this only in the case you have the latest Status in you Studio.

Best regards,

Astrid

[Former Member · Accepted solution]

Hello

I logged on as the author of these objects and they apper to be checked in:

However, I still get the same "Failed to lock / already locked" message as shown in my opening message above when trying to change the object. 

[Former Member · Accepted solution]

Hello

I logged on as the author of these objects and they apper to be checked in:

However, I still get the same "Failed to lock / already locked" message as shown in my opening message above when trying to change the object. 

[astrid_burghart · Accepted solution]

HI Max,

as you can see there is a small symbol before the Object. This means it is checked out by someone else.

Check the Session Administration who is logged in (you have to refresh it to the all logged in users).

If you think the implementation is on the correct level, you can just kick the user.

It happened to me that my Studio froze and I had to stop it with the Task Manager of Windows.

After that the Object was logged by my user. So I had to kick myself via Session Administation.

Best regards,

Astrid

[Former Member · Accepted solution]

It can be a cache error. Delete the cache from folder C:\Users\<youruser>\Documents\CopernicusIsolatedShell\Projects\

[HorstSchaude · Accepted solution]

Hello Alessandro,

Mostly this is a backend lock and so Astrid's suggestion will work.

Bye,

  Horst