Dhanu is a colleague of mine, so this issue has been resolved for us, but I hope this helps out anyone else having similar issues regarding the installation of Omeka on Solaris 10. Please note that these are solutions that worked for us; they may not provide a solution for your particular environment, but hopefully might point you in the right direction. Sorry it's lengthy, but I wanted to be thorough.
"ImageMagick is not properly configured. Please check your settings and then try again."
Could be that the wrong location is set for your convert. When logged in as admin, go to the "Settings" tab, and make sure that the "Path to Convert" field has the entire path to a working copy of convert. The path MUST include the convert executable.
I know this has been brought up in a few other places in the forums, but it can't hurt to repeat it.
"Something went wrong with image creation. Please notify an administrator."
The first problem we ran into was ImageMagick itself. The version of ImageMagick that ships with Solaris was too old for Omeka. If you run:
Against the default ImageMagick that shipped with Solaris, we got:
Version: @(#)ImageMagick 5.4.7 07/01/02 Q:16 http://www.imagemagick.org
Copyright: Copyright (C) 2002 ImageMagick Studio LLC
The default version shipped with Solaris is REALLY old, so we pointed Omeka to the newer version we installed:
Version: ImageMagick 6.3.8 02/26/08 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2008 ImageMagick Studio LLC
Which seems to work.
Not sure what the minimum version requirement of ImageMagick is, but if you have your convert pointed to the right place, and it's giving this error, try upgrading to a new version.
The dreaded "Blank Screen" after you attempt to upload an image
This was the one that caused us grief. It turns out that when we compiled PHP from source we didn't include exif. It's important to remember to configure PHP with --enable-exif or Omeka will give you a blank screen when you attempt to upload images.
It doesn't trap an error (we had all error messaging turned on, at maximum verbosity, and still not a single error), so it can be really frustrating. I guess most people install PHP from packages, which come compiled with exif, so they don't encounter this.
If this could be added to the installation documents, I think it would help out those of us in a highly customized environment who do compile from source.
"file: illegal option -- b" listed in error logs
We installed the latest gnu version of file, and that fixed this issue. It appears that our version was either too old, or (more likely) Omeka expects the gnu version of file, but the version of file that ships with Solaris simply doesn't support the -b option. Omeka seems to work fine, even though it throws this error to the error log, so it may not be a big issue to you, and you may not even have noticed it. But, I like my error logs to be clean, so I'm including it.