Skip to main content
C
Cristi_XP
Participating Frequently
September 9, 2013
Question

Installing adobe connect pro 9

  • September 9, 2013
  • 2 replies
  • 2167 views

Hello,

I am trying to install Adobe Connect pro 9 on a windows 2008 r2 server.However , after the installation is complete, the platform doesn`t work.

When I try to connect to localhost:8510 the page doesn`t load at all.

Any ideea what seems to be the problem ? What to check on my installation ?

These are the 2 errors from the log

com.adobe.connectpro.install.action.server.DBProcessAction

Error and

com.adobe.connectpro.install.action.server.InstallerDeployAction

                          Status: ERROR

                          Additional Notes: ERROR -     class com.adobe.connectpro.install.action.server.InstallerDeployAction.install() Unexpected Fatal Error:

    This topic has been closed for replies.

    2 replies

    D
    dobergerator
    Participant
    September 23, 2014

    I had a similar problem with a standalone server and external SQL local at the same LAN.

    Fixed with giving sysadmin rights on SQL Server to the user.

    Jorma_at_Knox
    Jorma_at_Knox
    Legend
    September 9, 2013

    Sounds like it didn't install properly. I would un-install and then reinstall it and see if works correctly the second time.

    This error, com.adobe.connectpro.install.action.server.DBProcessAction, looks to be a DB communication issue. Did you have any errors when tying the Connect server to your DB?

    If needed you can always reach out to Support to have them look at the issue and help identify that problem.

    C
    Cristi_XPAuthor
    Participating Frequently
    September 9, 2013

    Hello,

    Thanks for your reply.If I install the connect pro with the sql server on the same server, then it works.The issue appears to be with the connection to the database.

    Have you any ideea why ?  I have tried installing and uninstalling it 10 times till now ,but only when I am using the same server for the DB works.

    Jorma_at_Knox
    Jorma_at_Knox
    Legend
    September 9, 2013

    It could be a variety of things (port communication issue, un/pw issue, not having an SA account for initial access, some setting on the DB side that Connect doesn't like/can't use, etc.).

    Without being a part of the deployment I'm only guessing. I've seen all those issue come up at one point or another with installations, so you may want to start there, but having Support look at the logs and errors may give them a quick idea as to what is wrong.

    If you go to the Configuration tool on the server, and go to the Database Settings page. If you put in the information for your external DB, does it throw any errors?

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices