Nicola Taylor Posted August 9, 2021 Posted August 9, 2021 Has anyone encountered this error message when trying to open pdf documents? It's happening in both Designer and Publisher and I have no idea what to do. Everything is updated to the latest version but I just cannot get this file to open. I've attached the file itself just in case that's any help - it's a dieline. Thanks for any advice you can give! Nicola fefco 427_310x235x50.pdf Quote
walt.farrell Posted August 9, 2021 Posted August 9, 2021 That PDF is broken. If you Open it with Acrobat Reader it silently "fixes" the problems and opens it, and then prompts you to Save the document when you Close it. If you Open it in PDF-XChange Editor you get this error message, which at least explains the issue: Affinity is unable to handle this kind of error in a PDF file, and just tells you it can't parse it. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
David in Яuislip Posted August 9, 2021 Posted August 9, 2021 (edited) It opens ok in Chrome so I printed it to pdf and that opens ok in AP and APub edit: AAArgghhh, beaten by @walt.farrell....again fefco 427_310x235x50CHROME.pdf Edited August 9, 2021 by David in Яuislip walt.farrell 1 Quote Microsoft Windows 11 Home, Intel i7-1360P 2.20 GHz, 32 GB RAM, 1TB SSD, Intel Iris Xe Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10
walt.farrell Posted August 9, 2021 Posted August 9, 2021 8 minutes ago, David in Яuislip said: AAArgghhh, beaten by But you provided a version of the PDF that may work for the OP (depending on what had to be deleted to "fix" it in the applications that do so). David in Яuislip 1 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
David in Яuislip Posted August 9, 2021 Posted August 9, 2021 3 minutes ago, walt.farrell said: depending on what had to be deleted to "fix" it in the applications that do so Indeed, I guess we'll never know what's missing. I must admit that Chrome is my first port of call for fixing files that Affinity can't parse, it's especially good for svg's walt.farrell 1 Quote Microsoft Windows 11 Home, Intel i7-1360P 2.20 GHz, 32 GB RAM, 1TB SSD, Intel Iris Xe Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10
Nicola Taylor Posted August 10, 2021 Author Posted August 10, 2021 Thank you so much @walt.farrell and @David in Яuislip - it never occurred to me that it could be the file that was dodgy! Managed to get a copy in .ai format and that solved the issue. Thanks again, Nicola walt.farrell 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.