Skip navigation
Currently Being Moderated

Acrobat 9.0 Shared Review problem

Dec 4, 2008 5:55 AM

Hello,

I upgraded to Acrobat 9.0 professional from 8.0 professional, and can no longer create a shared review. I did a complete uninstall of 8.0 prior to the 9.0 installation. I am running Windows XP Professional w/ Service Pack 3 on a Core2 Quad CPU @ 2.40 GHz using 3.25 GB RAM.

I have never had any issues with the shared review on Acrobat 8.0, but now just prior to completing the setup process for the review, I receive a dialog message stating "Status: Could not save the shared review-enabled PDF file". Options include: Retry (non-productive) and Cancel (which does work). "Cancel" terminates the process.

What leads up to this event is similar to the routine I followed under Acrobat 8.0.

1. Save pdf from FrameMaker.
2. Move pdf to publicly accessible folder on network.
3. Open pdf.
4. Select Comments > Send for Shared Review...
5. Select "Automatically collect comments on my own internal server".
6. Click Next.
7. Select "Network folder" radio button.
8. Click Browse to navigate to pdf location. Status confirms that "Shared folder location is valid".
9. Click Next.
10. Select "Send it automatically using Adobe Acrobat" radio button.
11. Select "As a link within the message".
12. Click Next.
13. Type a name for the server profile (e.g. "Test")
14. Click Next.
15. Click To and add addressee(s).
16. Click Send. "Create Shared Review" dialog box states "Status: Could not save the shared review-enabled PDF file".
17. Click Cancel.

I have searched for this message ("Status: Could not save the shared review-enabled PDF file") and only found a TechNote indicating that "...with Acrobat 9.0 you no longer need to Reader-enable a PDF before you send it for Shared Review; this is done automatically." I'm not doing this, so it appears to be unrelated to my problem.

Does anyone have any suggestions? Sorry for the long post and thanks for any help.

Jeff Skogstad
Technical Publications
Cirrus Design Corporation
 
Replies
  • Currently Being Moderated
    Dec 8, 2008 2:51 AM   in reply to (Jeff_Skogstad)
    Do NOT use the same location for pdf and network folder repository. On step 8 choose some other location other than the pdf location. For instance create a folder at the location where pdf is kept and choose that in step 8.

    BTW, in step 2, you don't need to keep pdf on a 'publicly accessible location on network'. You can keep that on your machine or hard disk. When you decide to send a link to your recipients for the 'review pdf', Acrobat will automatically create it and keep it in the right place i.e. on the network folder you have chosen on step 8.
     
    |
    Mark as:
  • Currently Being Moderated
    Dec 8, 2008 9:58 AM   in reply to (Jeff_Skogstad)
    Jeff, did you tried giving a different network folder in step 8 - other than the pdf location?
    Can you please try keeping the pdf on your machine and choosing the network path of the location in step 8 to be the path where you would have kept the pdf otherwise.

    For you second problem, can you try changing this preference - Open Preferences (ctrl-K), choose 'Documents' and change 'View documents in PDF/A mode' to "Never".
     
    |
    Mark as:
  • Currently Being Moderated
    Dec 10, 2008 8:10 AM   in reply to (Jeff_Skogstad)
    Jeff,

    While trying to participate in the Acrobat 8 review, are you able to see comments added by other reviewers, and when publishing comments
    is any error message seen?
    Some info regarding the state of the review can also be seen on the golden bar at top of the review document.
    Please also open the Review Tracker (Comments Menu > Track Reviews), and see if it shows any error message.

    For the Acrobat 9 creating a shared review case
    Please omit step 2 while initiating a new review and use a new server profile i.e. repeat steps 5-14 instead of using the already created Test
    profile.

    And in case you still have problems we could have a Connect session(connect is a browser plugin which enables desktop sharing) at some convenient time and may be you could walk me through your workflow.
     
    |
    Mark as:
  • Currently Being Moderated
    Feb 4, 2009 2:34 PM   in reply to (Jeff_Skogstad)
    Hello,
    Our users seem to be experiencing the same issues. Our company is in progress of upgrading everyone to Acrobat 9.0.0 Standard from a mix of 8.1->8.1.3 Standard but have run into the problems described above. Users on 9 are no longer able to participate in Shared Reviews created with Acrobat 8.1x Standard, and users on 9.0.0 are unable to create new shared reviews because of the "Status: Could not save the shared review-enabled PDF file" error.

    Desktops are XPsp3, servers are W2k3R2Sp2

    Was a resolution to the above issues found?

    Jason Warmby
    Hathaway Dinwiddie
     
    |
    Mark as:
  • Currently Being Moderated
    Feb 9, 2009 6:27 PM   in reply to (Jeff_Skogstad)
    Think I may have found it, but need someone to confirm.

    Using the Adobe Customization Wizard, we created a custom mst for our msi package.

    go to "Online and Acrobat.com"
    then "Acrobat.com Features"
    then "Disable only initiation of share review and forms:"

    When checked, this checkbox effectively prevents acrobat.com as an
    available option for posting shared reviews, BUT IT SEEMS IT ALSO PREVENTS THE POSTING OF SHARED REVIEWS ON NETWORK SHARES.

    I have a case open with Adobe on this issue but have very low expectations of getting any helpful answers from them.

    1.Can someone confirm what we found is correct?
    2.More importabtly , does anyone have and idea what this checkbox actually does, since we now need to undo its impact. Registry?
    3.If this is correct, will adobe fix its problem and allow us to block sensitive information from being posted on acrobat.com yet still allow us to use network shares for shared reviews?

    Jason Warmby
    Hathaway Dinwiddie
     
    |
    Mark as:
  • Currently Being Moderated
    Apr 2, 2009 8:57 AM   in reply to (Jeff_Skogstad)
    Jason's comment helped solving my problem. I was not able to:
    1. participate in WebDAV shared reviews
    2. create a WebDAV shared review

    I deinstalled my Adobe Acrobat Pro 9 which was initially installed by a customized company MST file. Then I installed it manually without the use of the mst file and by manually entering my license key (which I was lucky to know). Then server based reviews started working.

    There is a good reason for a company to disable server based reviews, particulary on acrobat.com, because of intellectual property protection. But the use of internal servers should be kept possible. I think Adobe need to introduce a distinction between allowed servers and disallowed servers in their setup which can be influenced by company specific mst files then.

    Thanks to all contributors in this forum for helping me indirectly to solve my problem.

    Anonymous Engineer
     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2009 10:30 AM   in reply to (Rolf_Schlagenhaft)

    There is a KB article on how to Disable Access Points to Acrobat.com Services in Windows Network Deployments without disabling shared reviews that might help.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 26, 2010 2:38 PM   in reply to (Jeff_Skogstad)

    I've read through the TechNote on the Acrobat.com/Shared Review issue. Has anyone looked at a way to fix this on a system that's already broken?

    I've been taking some notes on the issue and reaching out to support teams at Adobe and elsewhere. Hopefully I'll have something useful soon.

    http://dark-woods.net/index.php/2010/01/25/error-status-could-not-save -the-shared-review-enabled-pdf-file-in-acrobat-9

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 7, 2010 5:25 AM   in reply to (Jeff_Skogstad)

    Our experience and a solution:

     

    Acrobat 9 Standard - Document Message Bar not shown in shared review

     


    A pdf file is "send for shared review" by Acrobat 8 or 9 on a network folder.
    The file is shared review enabled and is saved at the network folder.

     

    If the file is opened by Acrobat 9 Standard the yellow Document Message Bar (DMB)
    does not show up.

     

    Opening using Acrobat 8 Std/Pro or Acrobat 9 Pro works fine and presents the DMB.

     

    Doing a review without the Document Message Bar is really clumsy, so
    any help is very welcome.

     


    Tested so far:
    ---------------------------------------------------------------------- ---------------
    Registry key has no influence:
    ...\FormsPrefs\bHideDocumentMessageBar
    ---------------------------------------------------------------------- ---------------
    Information from kb-entry is applied:
    http://kb2.adobe.com/cps/508/cpsid_50894.html
    Deleted the 3 Reg-Values:
        [HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Workflows]
        "bEnableAcrobatHS"=dword:00000000\
        [HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Workflows]
        "bEnableWorkflowPart"=dword:00000000
        [HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Workflows]
        "bEnableRTCPart"=dword:00000000

     

    Created this 4 Reg-Values:  
        [HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Workflows]
        "bEnableRTCAuth"=dword:00000000     
        [HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Workflows]
        "bEnableHSLibrary"=dword:00000000         
        [HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Workflows]
        "bEnableShareFile"=dword:00000000          
        [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Acrobat\9.0\FeatureLockDown]
        "bCreateBuzzwordDoc"=dword:00000000
    ---------------------------------------------------------------------- ---------------
    Acrobat 9.3.2. and Acrobat 8.2.1. are used
    ---------------------------------------------------------------------- ---------------


    Additional steps to see the yellow Document Message Bar:
    If this Regvalue is set to 0, it should work:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Acrobat\9.0\FeatureLockDown\cDocumentStatus]
    "bSuppressMessageBar"=dword:00000000

     

    [HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\8.0\AVTracker]
    "bNeedSynchronizer"=dword:00000001

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 3, 2010 4:31 PM   in reply to (Jeff_Skogstad)

    We are getting this on certain machines and not others.  I can't seem to be able to find a rhyme or reason.  We are trying to initiate reviews on a shared internal network location.

     

    A few questions for the forum:

     

    Does Owner rights matter on the share that the review file is to be stored in?  Currently we have Modify rights for all participants and initiators.

    Does it make a difference which updates are installed past 9.0?  Does it make a difference if Pro and Reader are installed?

    Can someone confirm that the Acrobat.com is required to be installed on the machine?  I noticed on the latest installs of reader acrobat.com application is not installed.

     

    I'm posting this now because I haven't seen a clear cut answer to:

     

    Could not save the shared review-enabled PDF file

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 8, 2010 12:24 PM   in reply to ehruska

    Some answers with our internal tests:

     

    1.  Owner rights doesn't seem to matter.

    2.  9.0 and 9.2 professional only on the machine tends to work.  9.3.1 with reader 9.4 on the same machine appears not to work.  9.2 professional and 9.4 reader on the same machine does appear to work.

    3.  From our tests Acrobat.com isn't needed for shared reviews on our own server.

     

    There are still a lot of mysteries why this works sometimes and not other times.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 26, 2011 1:46 PM   in reply to (Jeff_Skogstad)

    I was experiencing this problem over the past two days and I found that in my case the issue was resolved by using a shorter PDF filename.  It seems that the version of SharePoint my organization is using has limits on the length of directory names (and probably file names as well.)  This is an interesting issue when using SharePoint for shared Acrobat reviews since Acrobat takes the existing filename and adds quite a few characters to it when creating the folder where attachments and comments are stored.  Further complicating the matter, I was able to store the plain PDF file on SharePoint with no errors and when Acrobat failed to create the folder for a shared review, the error message produced was not at all helpful in determining the root cause of the problem.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 10, 2011 5:35 AM   in reply to (Jeff_Skogstad)

    We were receiving this same error:

    ""Status: Could not save the shared review-enabled PDF file" on sending the Shared Review to an internal server.  Found out it was just that the user was storing the original file in the same location as the shared reviews so it couldn't copy the Review file and the copy in the same location.  We set up a temporary location on her desktop to store the original file and had no problem after that.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 6, 2012 12:08 PM   in reply to JJ_CUMBY

    Acrobat Pro 9.4, Windows 7 64-bit Enterprise Edition, getting the same error "Status: Could not save the shared review-enabled PDF file".

     

    PDF is stored on my local drive and I'm attempting to upload it to Acrobat.com so there should be no write protection issues. Could it be that Acrobat Pro and Acrobat Reader X are both installed? Is it safe to uninstall Reader?

     

     

    Thanks

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 6, 2012 12:45 PM   in reply to poofyboy

    I found that our issues were related to 1 or multiple of the following 3 issues...

     

    1. custom packaged build had a setting set to not allow comments (the comments bar wouldn't appear)

    2. multiple versions of acrobat/acrobat reader do not work together and can have unforeseen issues

    3. Installing as user with temporary local admin rights then running once as the user while they still have local admin rights seems to clear up any other issues.

     

    Since we have been manually installing and following the above guidelines we have avoided any re-occurrences.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)