10 Replies Latest reply on Jul 27, 2010 10:15 AM by Peter Grainge

    RH 6 - publish fail

    ELALIB

      One of our authors is having issues publishing a project that they have published before with no problems.  Here is the error message they received:

       

      Publishing has been cancelled.

      Connection failed.  Please check the connection and post again.

      Native Error:Not Found.

       

      I asked them to get a fresh copy from source control and try to publish that and they got another error:

      On the Confirm File Replace:

      Unhandled exception has occurred in a component in your application.  If you click Continue, the application will ignore this error and attempt to continue.

      Attempted to read or write protected memory.  This is often an indication that other memory is corrupt.

       

      Any ideas as to what is happening with this project?

       

      Any help is appreciated.

       

      Thanks.

        • 1. Re: RH 6 - publish fail
          RoboColum(n) Level 5

          I think you'll need to narrow down the possibilities here. Does this happen on other source controlled projects? If so, does it happen with other users? If not, does it happen if checked out to a different PC but the same user?

           


            The RoboColum(n)   @robocolumn   Colum McAndrew
          • 2. Re: RH 6 - publish fail
            MergeThis Level 4

            We experience this same issue from time to time, but only to one of the two servers we publish to. I suspect that: 1) the server is old; 2) the server is overworked; and 3) atmospheric pressure and other environmental issues cause the buildup of network sewer gases.

             

            Publishing several hours later usually works fine, and you might go days or weeks before it happens again.

             

            The temporary workaround is to manually copy the entire generated output folder from your machine to the server(s).

             

             

            Good luck,

            Leon

             

            EDIT: Source control shouldn't have any bearing on this issue, since you're not dealing with source files: they're generated output files being synced to a server.

            • 3. Re: RH 6 - publish fail
              ELALIB Level 1

              It is not happening to other projects.  It is happening to other users.

              The last successful publish of this project was a couple of days ago.

              • 4. Re: RH 6 - publish fail
                ELALIB Level 1

                We will try to rebuild the project from the hhp file and see how that goes.

                • 5. Re: RH 6 - publish fail
                  MergeThis Level 4

                  Why? There is no problem that needs to be addressed, here.

                   

                  The project's source files are being generated properly; therefore no "rebuilding" is needed. It's simply the transfer of properly generated output files to the server that is a concern, and I addressed the likely causes and efficient workaround in my first response.

                   

                  Do not waste any time on this, simply use the workaround when needed.

                   

                   

                  Good luck,

                  Leon

                  • 6. Re: RH 6 - publish fail
                    ELALIB Level 1

                    Because the error message when retrieving from source control about the corrupt memory.  It looks like something went awry with this project.

                    • 7. Re: RH 6 - publish fail
                      MergeThis Level 4

                      Rereading your initial post seems to indicate that you have two separate issues, both of which are probably due to how your networks are being maintained, such as server issues for where your source control database is located. Although your post title reads "publish fail," that seems like the least of your problems.

                       

                      • Are you all working the projects on your local machines (good practice, preferably off the C:\ drive, not My Documents), not on the server (bad practice)?
                      • Check to see if these project files are in source control (they should not be): .cpd, .hhp, .ldb, and .pss.
                      • Check that all users have the proper paths established to their local machines.
                      • Check with your Admin folks about the memory issue.

                       

                       

                      Good luck,

                      Leon

                      • 8. Re: RH 6 - publish fail
                        ELALIB Level 1

                        We've done everything by the book.

                         

                        Author's work off their C drive.  They have admin access to it.

                        None of the "RoboHelp" files are in source control.

                        All the paths are correct.

                         

                        For some reason the project got corrupted.  We deleted the .cpd and .xpj files and rebuilt the project from the hhp file and that seemed to do the trick.

                        • 9. Re: RH 6 - publish fail
                          MergeThis Level 4

                          Glad you worked it out.

                           

                           

                          Good luck,

                          Leon

                           

                           

                          By the way, don't forget to mark your last reply as the Answer (helps other folks who come to this post at a later date).

                          • 10. Re: RH 6 - publish fail
                            Peter Grainge Adobe Community Professional (Moderator)

                            You would have been better to try deleting just the CPD first. See Opening Projects on my site.

                             


                            See www.grainge.org for RoboHelp and Authoring tips

                             

                            @petergrainge