topic 0kb PDF File after publishing to Dropbox folder in Documentation

0kb PDF File after publishing to Dropbox folder

furtonb — Fri, 19 May 2023 13:45:17 GMT

Hi,

Publishing PDF goes wrong for some reason with certain files, it creates a 0kb PDF file in the destination folder. I've seen this thread, but my problem is not like that, but I could be wrong:
https://archicad-talk.graphisoft.com/viewtopic.php?f=11&t=71386&p=319531&hilit=empty+pdf#p319531

I would publish to a Dropbox folder - could that be the problem? After creating this PDF it's stuck on syncing.
It's this specific PDF right now, when I publish another batch this could export well and another might go wrong. Any ideas where to start troubleshooting?

I've tried publishing to my desktop, it seems to work there.

What do you think, is this ARCHICAD or Dropbox (or Windows) related?

I'm having an admin user on my own machine, Win10 Pro 64bit, AC22 b5009.
This is a project on a remote BIMcloud, but I had this problem before with local files (also stored in Dropbox).

Some context: I only have this problem with ARCHICAD right now, I'm publishing "raw" PDFs that I compose with renderings and text in another application. Exporting the "final" PDFs from there sync well and I don't have these issues.

Any help would be appreciated!

Re: 0kb PDF File after publishing to Dropbox folder

Barry Kelly — Wed, 16 Dec 2020 01:15:27 GMT

furtonb wrote:
I would publish to a Dropbox folder - could that be the problem? After creating this PDF it's stuck on syncing.
It's this specific PDF right now, when I publish another batch this could export well and another might go wrong. Any ideas where to start troubleshooting?

I've tried publishing to my desktop, it seems to work there.

What do you think, is this ARCHICAD or Dropbox (or Windows) related?

Basically I would recommend not saving files to or publishing files (PDF or DWG) to a cloud share folder directly.
These processes take time to complete and quite possibly the share is trying to sync them before they are finalised.

As you said yourself, publishing to your desktop worked fine.

I would do that and then drag and drop into your share folder.

Barry.

Re: 0kb PDF File after publishing to Dropbox folder

furtonb — Wed, 16 Dec 2020 02:43:49 GMT

Thanks, Barry.

Weird, I've been doing this for ages, and never had this problem before.
This syncing process takes seconds, this pdf is a few MBs big (cca. 4.1 MB), and the rest are kilobytes.

The funny thing: it does this when there is a completely new file in a completely new folder with completely new names (to prevent if something stuck while indexing). I wait for Dropbox to finish syncing, publish the said new files, and a random one (at least I couldn't figure out why) won't be written. The file is created, but it's 0 kb. Dropbox runs through the rest of the folder but is stuck syncing the one.

The AC publishing window tells me the PDF was written with a size x.

Copying files:
Could work for now, but I wish to avoid this in the long run.

Re: 0kb PDF File after publishing to Dropbox folder

LucaP — Wed, 16 Dec 2020 08:12:31 GMT

Hi,

Take a look in following topic, it seems to be a similar issue.

https://archicad-talk.graphisoft.com/viewtopic.php?f=11&t=68959

Perhaps it may help you.

Re: 0kb PDF File after publishing to Dropbox folder

furtonb — Wed, 16 Dec 2020 18:01:35 GMT

Hi Łukasz,

Thanks, I didn't read it before.
Yes, my issue is similar - I went with Barry's suggestion for now and I publish to the desktop, then copy the files, which works so far.

I will try to create the FastLogger files, as Minh described in the other thread, later.
I don't have particularly long paths, though - this publisher went to a path which was 36 characters long + file name string length - imagine "details.pdf", "floorplan.pdf", nothing fancy in this case* (Windows limit is 256, I've run into issues in the past, I try to use as short, but not cryptic names as possible).

I don't publish to a server neither.

*There are path length problems on Windows when the client requests file naming in their own system, and the file itself is ~150 characters long, but this thread is nothing like that case.