Skip to main content
Participant
November 9, 2020
Answered

PDF file error in Adobe Creative Cloud link

  • November 9, 2020
  • 2 replies
  • 1337 views

Hi everyone,

Would appreciate any help possible. I have a PDF document on Adobe Creative Cloud that was created from Microsoft Word on 365 mac. Instead of displaying the pdf for collaboration as it normally does, I am getting the following error: This XML file does not appear to have any style information associated with it.  Then a bunch of xml code showing in thte browser.

<Error>

<Code>SignatureDoesNotMatch</Code>

Thank you in advance.

-Scott

This topic has been closed for replies.
Correct answer Meenakshi_Negi

Hi Scott!

 

This issue has been resolved now.

Please try to open the PDF again and let us know how it goes.

 

Thanks,

Meenakshi

2 replies

Meenakshi_Negi
Meenakshi_NegiCorrect answer
Legend
November 10, 2020

Hi Scott!

 

This issue has been resolved now.

Please try to open the PDF again and let us know how it goes.

 

Thanks,

Meenakshi

Scott5D98Author
Participant
November 10, 2020

Meenakshi, thank you so much! It's working now. Do you know what caused it by chance?

David__B
Adobe Employee
Adobe Employee
November 9, 2020

Hi Scott,

A few related questions to better understand. 

 

  • If you download the PDF does it open okay?
  • If you upload a different PDF does this one show the collaboration options as expected?
  • If you upload the problem PDF again with a different name does the issue reoccur?


With the results of this comparitive testing that might be helpful for you in terms of knowing what happened. It sounds like the PDF might have gotten corrupted when uploaded.

I'm not sure if this would matter but Adobe also has Document Cloud storage here for Acrobat/PDF types files
https://documentcloud.adobe.com/link/documents/files/


Hope that helps
- Dave

 

Scott5D98Author
Participant
November 9, 2020

Hi and thanks Dave!

PDF downloads fine. It seems now that I've noticed all past previously working links are now suddenly showing that same error. Any suggestions on where to go from here?