Adobe Community: Message List - AAM crashes in one user, works in the other...

Re: AAM crashes in one user, works in the other...

forums_noreply@adobe.com — Wed, 27 Mar 2013 15:35:14 GMT

Excellent Peter! You might want to try removing Muse using the uninstaller in Applications/Utilities/Adobe Installers.

If that doesn't work I might also recommend posting regarding the Muse specific issues you are experiencing to the Help with using Adobe Muse forum at http://forums.adobe.com/community/muse/help_with_using_adobe_muse.

Re: AAM crashes in one user, works in the other...

forums_noreply@adobe.com — Wed, 27 Mar 2013 01:09:42 GMT

Bull's Eye, Jeff !

Have a drink on me, you can charge it to my account at Adobe ;-)

The AAM lets me sign in again, CCC is syncing, and Muse sings.

AAM still complaints about not installing Muse because of a beta,

but I bet this will be over by the next update...

Re: AAM crashes in one user, works in the other...

forums_noreply@adobe.com — Tue, 26 Mar 2013 23:43:45 GMT

Peter the account specific folder you are looking for is located in Users/<Username>/Library/Application Support/Adobe/OOBE. In specific I believe the discussion was to remove the opm.db file.

You are certainly welcome to try this as it seems to assist many Muse users who are facing installation or problems in general with Adobe Muse. It also is something which is user account specific so it may allow your current user account to begin functioning properly again.

You can access the hidden User Library by holding down the option key in the Finder and going to your Go Menu.

Re: AAM crashes in one user, works in the other...

forums_noreply@adobe.com — Tue, 26 Mar 2013 23:01:08 GMT

Oops, I almost forgot: I do need to mention that I have two CC accounts; one for 'normal' activities, and one for testing official Adobe pre-release versions. But I've been working with that double sign-in for a while now, with no serious issues.

AAM crashes in one user, works in the other...

forums_noreply@adobe.com — Tue, 26 Mar 2013 22:56:11 GMT

I have a ton of CS applications installed on my Mac, and switch between several users, depending on my activity (researching, presenting, teaching). Until last week, everything went fine: all CS6 applications ran under CC, even CCC seemed up to date and all apps reported nicely in my AAM (apart from those AIR-based apps). Until Muse prompted me to update, which I did. AAM downloaded Muse, installed it, and I opened it. Muse prompted me to supply more CC account details, but as I did that, it said there was an unexpeted error (I-200). I tried again, but in vain - the same message. I didn't have time to look into the problem immediately, so I left it for a while.

A few days a casual system restart passed by, and I noticed more CC problems: CCC didn't sign in anymore, and AAM crashed, as soon as I was prompted to sign in. I hoped that after removing the previous version of Muse, things might change for the better, but it didn't. AAM still went on crashing and Muse kept throwing that error. I tried replacing AAM with a manually and freshly downloaded and installed version. But still, exactly the same trouble.

Strangely enough, on another user (on the same Mac), AAM, CCC and Muse run just fine ! I was even able to install the Muse update, with some difficulties though, but I don't think these were directly related to the above problem. AAM reported a "beta version present", which is just not true. So I manually ran the Muse installer, with no problem. Still, AAM is not satisfied and keeps telling me it can't install Muse, due to that resident beta version. Whatever...

Well, a couple of weeks ago, someone at a different forum advised users to delete a certain AAM prefs storage folder from the User Library. And it helped in some cases and circumstances ! I wonder if I could give that a try, but I've forgotten the name of that folder and can't retrieve the forum post anymore.

Any clues, advice, or solution ?