Skip to main content
Participating Frequently
November 9, 2022
Answered

Unable to post comment in cloud-based review

  • November 9, 2022
  • 3 replies
  • 15500 views

My team is creating PDFs in Acrobat Pro 2022.003.20263. We recently began using "Share this with others" to conduct browser-based reviews. (We used to do shared reviews on a SharePoint server.)

 

When a reviewer is logged in as a guest and tries to post a comment, he gets the message "We were unable to post your comment, please try again." (Screenshot attached) This happens intermittently, and on only one review document so far. But I'm anxious to fix it. In at least one case, the reviewer was locked out and could not reenter the review.

 

Does anyone know what might be causing this? Is there a way to prevent it? A workaround?

 

Thanks.

This topic has been closed for replies.
Correct answer Amal.

Hi @Larry Kunz 

 

Hope you are doing well and sorry to hear that.

 

A similar issue was reported earlier today, which is now resolved. Please try to sign out, reboot the computer and sign in back to start the review process again and see if that works for you.

 

Let us know if you still experience the issue and need more help.

 

Regards

Amal

3 replies

Participant
September 19, 2023

Our company is also experiencing issues with commenting on review links. I created three files last week that contain comments all the way up to 9/17. Then all of a sudden, we can no longer post comments. I am worried about the lack of response here. Any update Adobe?

Participant
September 19, 2023

My organization is experiencing the exact same commenting issue. I have logged out of Creative Cloud, rebooted, logged back in, and tried two browsers (Chrome and Safari) on Mac and PC. Please help resolve this issue, Adobe. 

LDSchneider
Known Participant
September 19, 2023

Same results on my end, Windows only [minus Mac and Safari]! Still not working at all. Missed a deadline, and my team is now angy about that product ship delay (delay = -$$$) as well as frustrated at my promise of "easy, collaborative PDF reviews".

LDSchneider
Known Participant
September 18, 2023

I and one reviewer tried the various suggestions and workarounds above. Still no luck for either of us!

Help us, Adobe Support, you're our only hope!

Participant
September 18, 2023

I tried the same suggestions and am also having the same issue with posting comments in the document. Does Adobe have a workaround? 

Participating Frequently
September 21, 2023

Hi Pietari! No, I didn't catch that entire point from your original post. Thank you so much for revising the procedure! I hope that it works for some people!!

However, I tried that (revised) process and several variations of it. Unfortunately, nothing I tried fixed the problem.

Also, yesterday at 1:23 PM CT I shared a brand new document (after restarting yesterday). After restarting this morning, after shutting down last night, I now see two versions of the same document in my "Shared" tab--one reviewer made comments at about 9:30 AM CT, and the comments only appear in "FileName(1).pdf", not the original "FileName.pdf". Is it going to create a new version of the PDF each time someone comments? (Hopefully not!) Off to test that some more now... Thanks all for your help! I think this is on Adobe to fix, though. I've been doing this for years, never had problems like this...


That sounds horrible 😅.

We are now experiencing the original "unable to post comments" problem again... and now have been sharing the documents once more. Hope it gets more stable very soon!

Amal.
Community Manager
Amal.Community ManagerCorrect answer
Community Manager
November 9, 2022

Hi @Larry Kunz 

 

Hope you are doing well and sorry to hear that.

 

A similar issue was reported earlier today, which is now resolved. Please try to sign out, reboot the computer and sign in back to start the review process again and see if that works for you.

 

Let us know if you still experience the issue and need more help.

 

Regards

Amal

Participating Frequently
November 17, 2022

Thank you, Amal. No one has experienced the problem since I shared your response with the team. So I think it is now resolved.