Contribute CS5 Launch Issue … Updated

Lately, Contribute CS5 users have reported that, Contribute hangs or crashes on launch. This is after a recent Adobe Update. An update has been posted to fix this problem, and a KB article is published.

To get the update, follow the steps for the corresponding scenario on your machine

Scenario 1: Contribute CS5 and any CS5 apps with CS Live services ( ex: Dw, Fw, Ps, Ai, ID, Fl, etc) are installed.

  1. Launch the other CS5 app
  2. Sign in to CS Live service. Access CS Live  Login into CS Live Services Wait for couple of minutes.
  3. To verify the update is downloaded, check “ConnectionsHomeOMBackend” folder contains this folder –  “2.5.1.20110506_v2_5_1_120
    • Windows XP – C:\Documents and Settings\Application Data\Adobe\CS5ServiceManager\extensions\ ConnectionsHomeOMBackend
    • Windows 7 OR Vista – C:\users\AppData\Roaming\Adobe\CS5ServiceManager\extensions\ ConnectionsHomeOMBackend
    • Mac OS – Users/Library/Application Support/Adobe/CS5ServiceManager/extensions/ ConnectionsHomeOMBackend
  4. If the folder is still not available try the following :-
    • Sign out of CS Live and Quit the App. CS LIVE
    • Again repeat the above steps 1,2,3.
  5. Launch Contribute CS5

Contribute CS5 should launch as expected since the update is available.

Scenario 2: Only Contribute CS5 is installed [No other Creative Suite 5 applications are installed]

  1. Verify the update is available. Check the  folder “ConnectionsHomeOMBackend”  contains this folder –  “2.5.1.20110506_v2_5_1_120” .
  2. Else remove the ConnectionsHomeOMBackend folder.  [Pre Req – Check in Task Manager / Activity Monitor to ensure that CS5 Service Manager is not running]
    • Windows XP – C:\Documents and Settings\Application Data\Adobe\CS5ServiceManager\extensions\ ConnectionsHomeOMBackend
    • Windows 7 OR Vista – C:\users\AppData\Roaming\Adobe\CS5ServiceManager\extensions\ ConnectionsHomeOMBackend
    • Mac OS – Users/Library/Application Support/Adobe/CS5ServiceManager/extensions/ ConnectionsHomeOMBackend
  3. Launch Contribute CS5

Contribute CS5 should launch as expected since there are no dependency of singing in to CS Live services.

Note – The folder ConnectionsHomeOMBackend will be created only when other CS5 apps are installed and signed on CS Live services. (The folder remains after un-installation of the other app)

 

 

 

var addthis_pub=”shilpar”;
Bookmark and Share    Adobe Contribute  Contribute Publishing Server  Shilpa

 

9 Responses to Contribute CS5 Launch Issue … Updated

  1. I don’t even use CS Live, so this is no help. Nothing worked. I removed Contribute CS5 and have reverted back to Contribute CS4.

  2. Shilpa says:

    I want to know what could be cause. Please check you mail and reply with details to resolve this issue.

  3. Jim Long says:

    I don’t use CS Live either. And I’ve had to delete the ConnectionsHomeOMBackend twice to resolve Contribute crashes.

    • Tara says:

      Same problem, don’t use CS Live either. Jim, you deleted the whole folder called ConnectionsHomeOMBackend and it worked?

  4. Bill Spiegel says:

    Ditto to the above. I don’t have CS Live. Websites are supposed to be updated frequently…this error is costing me money!

  5. Signed out of CS Live, but Contribute CS5 still won’t open. CS4 and CS5.5 open no problem. Really need this to work.

    Using Mac with Snow Leopard. (But don’t think that matters in this case)

  6. Nancy says:

    I go to the task manager and after starting contribute (quickly) I delete the CSManager file and if I catch it quick enough it will work. BIG PAIN but a work around for me.

  7. Shilpa says:

    Issue is fixed, the update is live. Please read the blog for details.

  8. Barbara says:

    I had the last week, always a problem, the CS5 is crashed immediately at startup.
    (to work at the only detour was still able to cut the network connection and off the CS5 start – then you could go back online).

    Thanks Shilpa, I could solve the problem then for one day, then it came up again, unfortunately.

    Have now deleted the folder according instructions “Senario 2” from the service manager and so far it works – hopefully it stays like this …