Skip to main content
May 27, 2009
Question

Adobe Connect Enterprise Server service fails at startup

  • May 27, 2009
  • 1 reply
  • 1476 views

New to Adobe forums so please excuse if this is not the correct place for this topic.  I am attempting to migrate database content from a production DB to a test DB and make it accessable by the test server.  I did successfully tranfer all table records using SSIS but overwrote some of the server specific records.  I also copied the "content" folder over to the test server as well.  I went back and manually adjusted the records to reflect the test servers configuration but the service never fully starts and begins to restart repeatedly.  I did restart the DB instance, Adobe and Flash services, and finally restarted the OS with no luck.  The following exception is being generated:        

Exception occurred in startup.
[05-26 08:47:56] brze (c) <status code="too-much-data"/>
[05-26 08:47:56] brze (c) com.macromedia.airspeed.StatusException$TooMuchData: <status code="too-much-data"/>
[05-26 08:47:56] brze (c) at com.macromedia.airspeed.Rows.getRow(Rows.java:57)
[05-26 08:47:56] brze (c) at com.macromedia.airspeed.db.DBStatement.getRow(DBStatement.java:238)
[05-26 08:47:56] brze (c) at com.macromedia.airspeed.dal.DAL.registerHost(DAL.java:270)
[05-26 08:47:56] brze (c) at com.macromedia.airspeed.main.Main.run(Main.java:385)

Would appreciate any pointers before I scrap the DB and go through a restore.  Oh, yes the test server was functioning before I migrated the content.

Thanks

    This topic has been closed for replies.

    1 reply

    Participant
    June 30, 2009

    Make sure you have at least 1 GB of free space.

    July 14, 2009

    Unfortunately, that was one of the first things we verified and increased to 10 gig and then 100 gig with no change.  Ultimately, the error/issue was caused by improper login information (userID and password).  Once this was aligned, the services started without issue.  So, the error message was not meaningful.   Now we have other issues related to content corruption/DB synch but that will require a new thread.

    Thanks for the advice,

    Lee