Working with workbench ES2 once in a while a resource / process used building livecycle applications becomes "stuck".
The process can't be checked out anymore, cant delete it. I can make changes to the local version, but changes do not get "noticed" by workbench. Check-in of the specific resource is not possible too..
Only resolution is to Open the File, Save it under a new name. (Icon changes to (to be checked in)). After checking in the resource is usable as normal.
Consequence is that all references to the original(sub)process have to be changed....Also the SOAP endpoint URL changes which requires external applications also to change their code.....
This happens a couple of times (4/5) per week on a fulltime development week.
Any help would be very appreciated... !
Views
Replies
Total Likes
You can try to delete the local copy of your project files manually and try again.
Usually the files will be located under C:\Documents & Settings \ <your pc name>\Workbench ES2\<server name>\<process name>\files
I hope this may help you!
Nith
Views
Replies
Total Likes
Thanks, I tried this, but does unfortunateley not work.
Views
Replies
Total Likes
I "resolved" this by creating a new dns alias and logging onto that new alias instead... =/
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies