Error: "Build Failed: The directory is not empty"
-
- Propellus Maximus
- Posts: 1571
- Joined: Fri Jan 11, 2008 1:30 pm
- Location: Horsham, Pennsylvania
Error: "Build Failed: The directory is not empty"
What should I do if I encounter the error "Build Failed: The directory is not empty" when trying to build my PDF output?
Craig
Lost in Disturbia
Lost in Disturbia
Re: Error: "Build Failed: The directory is not empty"
I usually encounter this error when I've been manually opening a file in my Output folder. For some reason, this seems to sometimes stop Flare from auto-clearing the output folder, even if I have since closed the file. I just close anything relevant that I have open, delete the contents of that target's Output folder, and run the build again.
Not sure if you're having the same issue though.
Not sure if you're having the same issue though.
-Dan, Propellerhead-in-training
-
- Propeller Head
- Posts: 23
- Joined: Tue May 03, 2016 12:04 pm
- Location: Simi Valley, CA
Re: Error: "Build Failed: The directory is not empty"
I've been getting this error a lot today but I've found that if I close Flare and then reopen it the problem goes away.
Brian
Brian
Flare ( ) v12, Windows 10
-
- Senior Propellus Maximus
- Posts: 3669
- Joined: Thu Feb 02, 2006 9:57 am
- Location: Pittsford, NY
Re: Error: "Build Failed: The directory is not empty"
Instead of restarting Flare, maybe just clean the project (which deletes everything in the Output folder) and then try to build the PDF. So that's Project > Clean Project.
Nita
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
-
- Propeller Head
- Posts: 23
- Joined: Tue May 03, 2016 12:04 pm
- Location: Simi Valley, CA
Re: Error: "Build Failed: The directory is not empty"
Hmmm. I'm starting to think it's a Flare 12 issue because it only happened a handful of times with Flare 11 but on Flare 12 it's a daily occurrence for me. Also, it only happens on my print outputs and never the online ones.
Brian
Brian
Flare ( ) v12, Windows 10
Re: Error: "Build Failed: The directory is not empty"
I've found that if you have the app "AdobeCollabSynch.exe" running in Taskmaster, that this is the reason for the error. It keeps a copy of the document built and displayed in Acrobat, so that it isn't really deleted. I couldn't find a way to properly delete it and since I heavily use Creative Cloud apps for work, I decided to simply rename the file by taking one character out. Now, I can find it and use it if it is ever necessary and since I did this the error hasn't returned.
Hope this helps a future Flare traveler.
Hope this helps a future Flare traveler.
Keith S.
“Most of us find our own voices only after we’ve sounded like a lot of other people.” –Neil Gaiman
“Most of us find our own voices only after we’ve sounded like a lot of other people.” –Neil Gaiman
-
- Propeller Head
- Posts: 62
- Joined: Mon Jan 04, 2016 7:39 am
- Location: York, North Yorkshire, England
Re: Error: "Build Failed: The directory is not empty"
I get this happening a fair bit. I just start the build again and it runs ok. It usually happens when I have been viewing an output then closed it and clicked Rebuild Target.
Re: Error: "Build Failed: The directory is not empty"
Hi folks
We are running Flare 2017 and are seeing this bug a lot. I found that if I use Windows to delete the Output folder entirely, it fixes the problem, albeit temporarily. I have tried the Clean Project command too, but it cannot delete everything for some reason. It appears that the same files that Clean Project fails to delete are those blocking the build, which makes sense. MadCap should fix this bug.
We are running Flare 2017 and are seeing this bug a lot. I found that if I use Windows to delete the Output folder entirely, it fixes the problem, albeit temporarily. I have tried the Clean Project command too, but it cannot delete everything for some reason. It appears that the same files that Clean Project fails to delete are those blocking the build, which makes sense. MadCap should fix this bug.
Re: Error: "Build Failed: The directory is not empty"
I turned off AdobeCC Auto sync and it helped with this issue quite a bit. For some reason though, stopping the sync capability to AdobeCC only works for a bit, then it turns itself back on again, possibly through Acrobat. One person in this thread mentioned that it wasn't a Madcap issue but an Adobe one and they were absolutely right. The issue stems from Adobe not releasing the file completely after editing is complete. I have added a link below to a screenshot of the Adobe CC screen where the option is located.bwait wrote:Hi folks
We are running Flare 2017 and are seeing this bug a lot. I found that if I use Windows to delete the Output folder entirely, it fixes the problem, albeit temporarily. I have tried the Clean Project command too, but it cannot delete everything for some reason. It appears that the same files that Clean Project fails to delete are those blocking the build, which makes sense. MadCap should fix this bug.
https://drive.google.com/a/colossalarts ... sp=sharing
You do not have the required permissions to view the files attached to this post.
Keith S.
“Most of us find our own voices only after we’ve sounded like a lot of other people.” –Neil Gaiman
“Most of us find our own voices only after we’ve sounded like a lot of other people.” –Neil Gaiman
Re: Error: "Build Failed: The directory is not empty"
Thanks for posting this fix--this worked to solve the issue for me.
netwrk219 wrote:I turned off AdobeCC Auto sync and it helped with this issue quite a bit. For some reason though, stopping the sync capability to AdobeCC only works for a bit, then it turns itself back on again, possibly through Acrobat. One person in this thread mentioned that it wasn't a Madcap issue but an Adobe one and they were absolutely right. The issue stems from Adobe not releasing the file completely after editing is complete. I have added a link below to a screenshot of the Adobe CC screen where the option is located.bwait wrote:Hi folks
We are running Flare 2017 and are seeing this bug a lot. I found that if I use Windows to delete the Output folder entirely, it fixes the problem, albeit temporarily. I have tried the Clean Project command too, but it cannot delete everything for some reason. It appears that the same files that Clean Project fails to delete are those blocking the build, which makes sense. MadCap should fix this bug.
https://drive.google.com/a/colossalarts ... sp=sharing
-
- Propeller Head
- Posts: 13
- Joined: Tue May 22, 2018 3:01 am
Re: Error: "Build Failed: The directory is not empty"
Ending this task also worked for me. Thanks for sharing!netwrk219 wrote:I've found that if you have the app "AdobeCollabSynch.exe" running in Taskmaster, that this is the reason for the error. It keeps a copy of the document built and displayed in Acrobat, so that it isn't really deleted.
Re: Error: "Build Failed: The directory is not empty"
Yes, thanks netwrk219. Just had this same issue and killing that exe solved the problem!
Re: Error: "Build Failed: The directory is not empty"
I keep getting this message when I try to build a book. The error points to a directory that doesn't exist. I have tried every suggestion in this thread, and still the build fails. How do I get around this?
You do not have the required permissions to view the files attached to this post.
-
- Senior Propellus Maximus
- Posts: 3669
- Joined: Thu Feb 02, 2006 9:57 am
- Location: Pittsford, NY
Re: Error: "Build Failed: The directory is not empty"
Is that path specified as the Output Folder in your target? That might be the issue. If that folder is specified in the target, Flare's going to look for it, and if it doesn't exist, the build will fail.
Nita
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
Re: Error: "Build Failed: The directory is not empty"
When I select the target, then select Open Output Folder, this is the path. C:\Users\garyschx\OneDrive - Intel Corporation\MCF-Unite\Output\garyschx\Deployment-Guide-Enterprise
Re: Error: "Build Failed: The directory is not empty"
For some reason, I am unable to delete the Output folder. Anyone know why that might be?bwait wrote:Hi folks
We are running Flare 2017 and are seeing this bug a lot. I found that if I use Windows to delete the Output folder entirely, it fixes the problem, albeit temporarily. I have tried the Clean Project command too, but it cannot delete everything for some reason. It appears that the same files that Clean Project fails to delete are those blocking the build, which makes sense. MadCap should fix this bug.
Also, it should be noted that a coworker was able to publish the book that failed for me, so all sorts of mystery surround this issue.
-
- Senior Propellus Maximus
- Posts: 2634
- Joined: Wed Apr 14, 2010 8:01 am
- Location: Surrey, UK
Re: Error: "Build Failed: The directory is not empty"
Check that Acrobat isn't "holding onto" your generated PDF. I've sometimes even had to close Outlook to release the output! (Yes, I know, it's weird.)
Started as a newbie with Flare 6.1, now using Flare 2023.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Re: Error: "Build Failed: The directory is not empty"
Here's a twist to the whole situation. I was able to delete the project output folder. However, there is something in the Temporary folder that I can't delete, and I wonder if this is what's preventing me from building the book. Is this a possibility?
You do not have the required permissions to view the files attached to this post.
-
- Senior Propellus Maximus
- Posts: 3669
- Joined: Thu Feb 02, 2006 9:57 am
- Location: Pittsford, NY
Re: Error: "Build Failed: The directory is not empty"
I take it that you store your Flare project in OneDrive. MadCap recommends not storing Flare projects on network drives or in cloud spaces, such as OneDrive, Google Drive. I suspect that the issue you are encountering has to do with OneDrive rather than with Flare. With Flare closed, can you go out to OneDrive in the cloud and manually delete the Temporary folder? Then give OneDrive a little while to sync up with your computer. Thereafter, try to open the project again and see if you can build.
Per the Flare documentation:
Per the Flare documentation:
https://help.madcapsoftware.com/flare20 ... ojects.htmWhere to Store Projects
When you create new Flare projects, the default location is the Documents\Projects folder. However, you can choose any location you want. See Creating a Project.
It is recommended that you always store your project locally, rather than on a network. Of course, there may be times when you need to place a copy of your project on a network (e.g., to use source control, or to make a copy available to a co-worker). But performance and speed should be significantly better if you work on a local copy of the project rather than working on it from a remote server. Working on a remote copy of a Flare project is also not an ideal solution for team authoring, because there is not a good solution for resolving file conflicts between writers.
Nita
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
Re: Error: "Build Failed: The directory is not empty"
I appreciate your response. You're correct. My files are on OneDrive. I closed everything and tried to delete the Temporary folder with no success.
-
- Senior Propellus Maximus
- Posts: 3669
- Joined: Thu Feb 02, 2006 9:57 am
- Location: Pittsford, NY
Re: Error: "Build Failed: The directory is not empty"
Try something, then. Open up your OneDrive tray app and tell it to pause syncing. THen see if you can build in Flare.
The first thing that Flare does when you instrust it to build is to delete whatever was in the Output folder from the last prior build. I think because your project is in a OneDrive folder, the deletion of the Temporary folder doesn't really take place immediately bc OneDrive needs to sync your local drive with the cloud. That takes a bit of time. So Flare gets stuck.
But if you temporarily pause OneDrive's syncing, then you should be able to build. At least, this is my guess.
The best practice really is not to put a Flare project in a OneDrive, Box, Dropbox, etc., folder. That platform's syncing will bite you.
If you have the project in OneDrive so that you can co-author it with other Flare users, then you really should be using dedicated source control such as Git or SVN.
The first thing that Flare does when you instrust it to build is to delete whatever was in the Output folder from the last prior build. I think because your project is in a OneDrive folder, the deletion of the Temporary folder doesn't really take place immediately bc OneDrive needs to sync your local drive with the cloud. That takes a bit of time. So Flare gets stuck.
But if you temporarily pause OneDrive's syncing, then you should be able to build. At least, this is my guess.
The best practice really is not to put a Flare project in a OneDrive, Box, Dropbox, etc., folder. That platform's syncing will bite you.
If you have the project in OneDrive so that you can co-author it with other Flare users, then you really should be using dedicated source control such as Git or SVN.
Nita
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
Re: Error: "Build Failed: The directory is not empty"
I'll give this a try. Also, after your previous post, I moved the files locally and that allowed me to build the books that were being blocked.Nita Beck wrote:Try something, then. Open up your OneDrive tray app and tell it to pause syncing. THen see if you can build in Flare.
The first thing that Flare does when you instrust it to build is to delete whatever was in the Output folder from the last prior build. I think because your project is in a OneDrive folder, the deletion of the Temporary folder doesn't really take place immediately bc OneDrive needs to sync your local drive with the cloud. That takes a bit of time. So Flare gets stuck.
But if you temporarily pause OneDrive's syncing, then you should be able to build. At least, this is my guess.
The best practice really is not to put a Flare project in a OneDrive, Box, Dropbox, etc., folder. That platform's syncing will bite you.
If you have the project in OneDrive so that you can co-author it with other Flare users, then you really should be using dedicated source control such as Git or SVN.