Generate DOC specification file error

Drew shared this problem 6 years ago
Solved

When I attempt to generate a sprcifications document I am presented with an error...


"The destination file C:Usersdrew_westDesktopTestTest.coc is already opened by another application or you do not have write access to it."

Comments (10)

photo
1

And I presume you don't have that document opened right? Could you send the file 'logs.log' located in c:Documents and settings[your user name]Justinmind4.4.1 to jim.support at justinmind.com please?

photo
1

I'm having the same problem ...

photo
1

We're checking the log file you sent to us.

photo
1

Thanks Victor. Wer'e eager to use the documentation function for an active project and appreciate your assistance. Please let me know how I can help troubleshoot.

photo
1

We're working on the Karen's case and it seems she has been able to generate the document, but we're still looking for the source of the error. So far we have detected the following cases where the generation fails:


- Either you have the document opened or you try to write in a folder where you don't have write permissions


- You select some templates and these templates have links to screens that are using another template which is not selected.


We recommend to close MS Word before generating the document.

photo
1

Karen found a bug. When you have templates with links to screens that use other templates which you didn't selected, then the generation shows an error. So the obvious workaround is to select at least, all the templates, and then select the screens you want to have in your document.


Drew, I hope that helps you as well. If that's not your case tell us and we will try to find what could be going on.

photo
1

OK. I closed all programs except JIM and selected ALL when launching the document generator. This time it stopped responding when the process flow was visible. It did create a 0 byte Word document ...

photo
1

Tried it again - this time selecting ADD ALL. It took some time, but worked.

photo
1

Ok, then it's the same error than Karen's. We will try to fix it for the next release (February the 22nd )

photo
1

Fixed in version 5.0