2 Replies Latest reply on Apr 13, 2011 11:02 PM by IR-PROGNOSIS

    Unable to Activate RoboHelp 9

    IR-PROGNOSIS

      RoboHelp HTML version 9

      Windows 7

      Word 2007

       

      My PC operating system was recently upgraded from Windows XP to Windows 7, upon reinstalling RoboHelp 9 I am getting the Activation dialog box which fails to activate the product and continues to state 'Please connect to the Internet, then press Continue".  Pressing continue starts the activation process which just returns to the same connection message. Obviously, I am connected to the internet and my Web Browser (IE8) is working fine, I have no other Web browsers are installed. Has anyone any ideas?

       

      Thanks,

       

      Chris

        • 1. Re: Unable to Activate RoboHelp 9
          Peter Grainge Adobe Community Professional

          Are you in a corporate environment? I had a problem with updates where I could not connect even though I had internet access. The cause turned out to be company restrictions and as soon as IT removed those, all was well. I am thinking you have hit a similar problem.

           

          I think it less likely that you would hit the same problem at home.

           

          You are the first person to report this problem so we don't have anything to go on. However you must activate RoboHelp 9 over the internet, that is now the only way. If that fails you will need to contact your local Customer Support team, see the very end of this page. http://kb2.adobe.com/cps/859/cpsid_85930.html

           

          They can put you in touch with a dedicated team for activation issues arising from this new policy. They cannot give you activation codes but they should be able to advise you. If you don't get any joy, post back here.

           


          See www.grainge.org for RoboHelp and Authoring tips

           

          @petergrainge

          • 2. Re: Unable to Activate RoboHelp 9
            IR-PROGNOSIS Level 1

            Thanks for the response Peter, you are spot on. My Internal Systems people have just fixed the problem which was something to do with the proxy server I was attached to.

             

            Cheers,

             

            Chris