내 커뮤니티 업적 표시줄을 확대합니다.

Mark Solution

활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.

해결됨

Fail to Process proof in Workfront

Avatar

Level 1

Hello!

My colleagues and I frequently use Workfront to send client proof and proofs to proofreaders. For the last day, we keep getting the same error message when we try to upload a new PDF: 

"The proof failed to process."

Any ideas why this keeps happening? The file size is well within range, its not corrupt and we have plenty of storage space. 

We've tried from separate users, exported a new PDF of the file, reduced the file size, all to no avail. Thanks!

1 채택된 해결책 개

Avatar

정확한 답변 작성자:
Community Advisor

Is it only this particular PDF? Do other PDFs work? I would try printing it from a regular colour printer and see if it prints. Rendering in Proof is akin to printing. If it doesn't print, it probably won't render either.

Try deleting parts of the document; vector graphics, images, sections, etc. to find the culprit as it's probably an element in the PDF that's causing failure.

원본 게시물의 솔루션 보기

6 답변 개

Avatar

정확한 답변 작성자:
Community Advisor

Is it only this particular PDF? Do other PDFs work? I would try printing it from a regular colour printer and see if it prints. Rendering in Proof is akin to printing. If it doesn't print, it probably won't render either.

Try deleting parts of the document; vector graphics, images, sections, etc. to find the culprit as it's probably an element in the PDF that's causing failure.

Avatar

Community Advisor

additionally, secure PDFs (e.g. password protected) will not convert.

Avatar

Community Advisor

Good tip, I didn't think of that.

Avatar

Level 1

yes, thank you! good tip indeed.

Avatar

Level 1

This worked! The culprit was a small illustration that wasn't printing and causing an error on the PDF. It wasn't flagging any major errors and we've used it before without issue. Very strange! Appreciate your help!

Avatar

Community Advisor

Glad it helped. As a follow up, I invite you to mark it as a correct answer so it may help other users with the same issue.