I checked the permissions of the folder, rebuilt disk permissions and they
seem to be OK, PS is working OK. 10.6.4 + graphics update, 18GB ram, quad-core
any thoughts would be appreciated.
Don't understand the messages but it seems script related to me. In your
list of solutions I did not find resetting the preferences.
Quit Bridge and restart it with option key pressed. Then choose reset
On seconds thoughts, it might also a good idea to first do this also for
Photoshop itself, holding down shift + option + cmd key and choose to delete
preferences. Set them again to your wishes, restart PS if you have made
changes that need a restart before being applied (memory and scratch)
Then reset Bridge prefs as described above and try again.
Can I reinstall Bridge without reinstalling the entire suite?
Sadly you can't uninstall and Bridge itself as it did in CS4 but you don't
need to reinstall the whole suite. I tried it once with just uninstall PS
and the reinstall PS again, that worked fine.
Be sure to back up your workspaces, actions and presets, 3th party plug in
and filters etc for PS before uninstall.
See also this KB article:
is the error that is being report correct?
dropdown.onChange not a function?
Here is where it ends for me, I have less to none knowledge about scripting
Maybe Paul Rigott will hop in or you might take your change in reinstall PS
and bridge (about 10 minutes work)
Also try first to delete the plist file for both PS and Bridge. Quit both
apps and look for those files in the user library preferences folder. Try
again if that helped.
I created the mediagallery folder within the Users/library/Application Support/Adobe/Bridge CS5/Adobe Output Module/MediaGallery
I get the following error when starting Bridge in the Output module ( Essentials etc. is not effected)
first the type error:
and then the script error
so far I've repaired the permissions and ACL's via the SL dvd, reinstall the suite. It seems that I've missed something, because I'm back in the same place.
first, thanks for you time.
>I wonder if you have tried creating another user account and trying from that?
I haven't yet, but it's between that or a new install. I'm a bit busy with projects so I can avoid the output module for awhile but I'm concerned that this may be a symptom of another problem, so I still looking to fix it.
If I create a new user, will the Adobe suite require a new license, or does it pull up the existing suite serial as it does now?
I'm surprised to see that Bridge doesn't have an uninstaller, or a separate installer. I tried to just uninstall PS and reinstall hoping that it would install Bridge but it didn't.
I wonder if the permissions problems with the CS5 install are not quite fixed.
Is there any process where I could move my existing account files to this new
Should have thought of the new user option...
A solution for that will be an Archive and install for your current system.
Use the original install disk for your OS and start up from this disk. In
the options choose for archive and install. This creates a new user library
and makes a copy of the old one.
You can download the combo update from the Apple Download site for the
latest OS version and be back in business within the hour. (assuming that
you already have a back up of all your important files and settings because
you need that for security just in the very rare case of failure with this
We are having the exact issues here, and logged in as a different user, which didn't fix our problem. We also tried resetting PS and Bridge preferences, and creating the Adobe Output Module/MediaGallery folder, but to no avail.
Does anyone have any other ideas for a work-around?
which of the errors above are you experiencing? I found that I had 2 different problems so the fix was 2 very different things.
I was able fix the first set of errors by reinstalling the CS Suite after using the "cleaner tool". I had reinstalled the Suite without the "cleaner tool" and it didn't resolve the problem.
Here's the follow up thread of what I did with the remaining errors:
The remaining problems/errors that I received are because of a Windows computer being mounted on my desktop. It's a very repeatable problem and I ran into it today. Fortunately I only need to unmount that Windows 7 folder ( btw if I mount a Windows XP folder on my desktop I don't get the error).
It was really a pain to uncover the problem, but the good news is that 12.0.1 looks like a good version. So there is a positive end result. Unless Adobe is secretly working on the network problem I assume that I will just live with having to mount/unmount the network folder when needed. BTW, I am not accessing the folder with the suite, I am not working on any images via the network, just having it mounted causes the error.
edit- make sure that you follow the instructions to uninstall using the Adobe uninstaller, then run the CS Cleaner.
I just had a thought are you using Dr Browns Services 2.0.4 script? Not that this is the problem but a way to confirm which problem it may be.
The second part of my problem (Windows 7 folder on desktop) with AOM also effected the 1-2-3 script. The problem with the script is that it won't write or read the xml file so folder settings and previous setup is not saved and needs to be reset each time. But again, when I unmount the Windows 7 computer the script works fine. So Bridge AOM and Brown's script, 2 unrelated things effected by the same problem. It may just be my network setup and not the Win7 computer or the Mac OS, but something is wrong.
So to sum-up:
1. Bridge CS5 is throwing the same error messages on startup, and when using the Output module to save to the local harddrive, as posted by <JM> at the start of this thread.
2. The errors are fixed by unmounting any Windows-security enabled CIFS shares, in our case, from a Netapp.
3. UNIX-security enabled CIFS shares from the same Netapp do not cause any errors.
Like <JM> we were not trying to access any of the network shares, and were trying to save to /Users/ouruser/Documents/, which are on the local harddrive.
I appreciate you following up with your situation. I almost assumed that there was a quirk with my setup. I was fortunate to have the login within the User startup items so when the new User account worked it pointed to a limited set of possibilities. But it was definitely a surprise to see how a seemingly unrelated thing would kick out an error in Bridge.
Adobe - any thoughts on this error? is this a known problem?