Hi every body,
I’m using visual paradigm 15.0 professional edition.
Some times when i try to open a project that is shared between a team this error occurred:
“Action aborted since the chosen file is currently in use”
Why is this for ?
Thanks in advance
Hi every body,
When you open a project, the project file will be locked. If you open this project again with another VP instance, you’ll get this message.
But this error will show even when i close the project and reopen it also after closing VP client and reopening it.
Usually i solve this problem by deleting project files from my Hard Disk and checkout it again from server.
I guess the problem is on well closing project i mean the project does not close properly and VP thinks its open yet while i close it before.
How can i find the source of this problem ? I mean the source that made the project stay open after i close it .
Does project logs can help me find the cause of this problem ?
I can take a look on the log file, you can send it to firstname.lastname@example.org and include the link to this post in the Email.
And I’d like to get more details:
- Visual Paradigm version
- Have reference projects or referenced by other project?
- Is teamwork project?
I will keep in touch with you with the email.
Thank you so much,
So what was the final solution?
Same issue here. This message is extremely annoying esp. taking into consideration the fact that I have quite a big chunk of work in progress and cannot save it. What should I do?
Please help !
Unfortunately i’m busy this days and couldn’t contact support team yet.
As KIT.SO said before, send your log file to the specified email address because this problem may be related only to your special case . I will send my own log soon and share the results here.
Even so; I am wondering how you guys are trying to open your projects? I assuming using the standard dialogs, so “open project” (control-o), select either VP Online or Local file system and open the project from there?
I’m suffering from the same problem, and was wondering if you have found the solution
Did you opened the project with another instance of VP?
Can you provide the steps or project configuration (e.g. project reference) to reproduce the problem?
Is the problem still persist after system restart?