Error "The uploaded PDF is password protected or corrupted and cannot be opened" from Magcloud

[packetgrrl]

I now get this error even with a pdf that I made a couple of weeks ago that I have printed with MagCloud.  All the password protection and encryption is turned off on export.  I am a mac and I am running Affinity publisher 2.5.5 on MacOS 14.7

All of the encryption and password stuff is disabled on export.

 

Thanks

 

 

 

[Hangman]

Hi @packetgrrl and welcome to the forums,

Can you upload the PDF file so we can take a look?

[packetgrrl]

It's huge.. Sure let me try.  This is a pdf I have already uploaded and successfully printed and now it's giving me that error.  It's the exact file I uploaded already and printed.  I have not regenerated it or anything.  The pdf is huge though so I am not sure if it will upload here.  It's like all of a sudden even ones I have already printed give me this error.  Definitely all the new ones I try to generate.  I finally got escalated to some tech support guy named Jake who "fixed" the pdf I desperately need to print.  I am not sure what he did.  He said, "How I fixed it was by saving this PDF as a postscript file, and then I place that file in Adobe Distiller and used the MagCloud settings to format it. Those export settings can be found by downloading one of the templates for InDesign from Magcloud. In that template is a a joboptions file that you can load into Adobe distiller. "

What I don't understand is why does this file that I have already uploaded and printed with magcloud now give me that error?  What is going on? 

Thanks!

----Cathy

Aunt Sally250 250.pdf

[kenmcd]

1 hour ago, packetgrrl said:

---Cathy

Aunt Sally250 250.pdf 251.33 MB · 8 downloads

Does not appear to be anything wrong with the PDF.
Opened it in multiple PDF editors.
Ran it through a PDF repair tool - and it reported no issues.

My guess is the PDF is damaged during the upload process.

Maybe a temporary connection issue. (try different connection or computer)
Or maybe their PDF ingester is having issues.
 

That convert-to-PostScript round-trip thing is an old way to fix some broken PDFs.
But there does not appear to be anything wrong with the PDF.

[packetgrrl]

Well there is something wrong since I can no longer generate a pdf with Affinity and upload it to magcloud and make a book.  I sent one that I really needed to print to a friend who also has a magcloud account and he also got the same error.    I have no idea what to do here.  I am unable to make a pdf (any pdf) with Affinity publisher and upload it successfully to magcloud.

 

[kenmcd]

2 hours ago, packetgrrl said:

Those export settings can be found by downloading one of the templates for InDesign from Magcloud.

Can you share those recommended export settings?
Maybe that is the issue.

There are others here who know far more about issues involving PDF export settings.
So they can take a look at the recommended settings and provide some guidance.

[packetgrrl]

It's not the issue.  I have figured it out.  Their site says this

"You can upload a PDF up to 300MB in size if you have the Adobe Flash Player or Microsoft Silverlight installed. Without one of these plug-ins installed in your browser, the maximum file size you can upload is 200MB."

Both of these options are well past end of life. So although I have Adobe Flash Player it is recommended that I uninstall it.  So I generated the pdf at a lower resolution of 240 and it generated a file < 200mb and it uploaded just fine to magcloud.  It's a strange error for the file being too big.   I have a note off to the tech support guy to see about this.  I don't know why that book that I posted here worked a couple of weeks ago and doesn't now.   It's so weird but it is bigger than 200mb.

 

[packetgrrl]

An update on this.. The tech support guy "fixed" something on their end and now I can upload up to a 500mb pdf and the ones that were failing now work.  This problem was entirely on their end and the tech support person's name  who fixed it is "Jake".   He asked me where I read about the file size limitations and I gave him a link to their own documentation.  Fun times!  Anyway it's all working now as it should and it was not an Affinity problem.