Any directions on how to upgrade to the new 2.18 version from a previous version??

It is possible that one of the other modules is closing the database, saw that issue prior when I was closing my database.

The apache@localhost does seem strange, if that is not the user name you are using for your database access.  I do not use that anywhere in my code. 

Not sure what else I can say about it, if you would like to PM me the links, I could possibly take a look at it as time permits.  May be a little bit though.

Hi,
I also noticed some modules fail (serverstat and LGSL) when using the treasury mod.
Using Joomla 1.5.4
The LGSL was reporting denied acess apache@localhost (password no) which was strange.

A quick fix was to move the modules about.

Seems the treasurey doesn't like to si on the same menu segment as other modules.

Using treasury 2.18

Please upgrade to 2.18

OK --- Let's try this again.  I have updated the version to 2.18, please upgrade (May have to do it manually this time only) and try the unbrand check once more. 

I replied directly form e-amil, btu  I did upgrade and did click the "Check Unbranding" again. No changes on my end.

I just attempted to install the Treasury v2.16 component with Joomla v1.5.4 in legacy mode. The first errors received  were related to  the default  DB configuration. It would be helpful if the end user was instruction to enter the correct information somewhere during or before the installation of the component. But after updating the required fields,  I still continue to receive the following mysql errors (3 to be specific). I elected to create a separate database to avoid possible corruption of my main CMS database. Could this have something to do with my receiving the following error?

Warning: mysql_close(): supplied argument is not a valid MySQL-Link resource in /home/user/public_html/components/com_mh2treasury/mh2treasury.class.php on line 835

Since this file is encrypted, there is nothing more that I am able to do without further assistance from you. I notice that there was only one other post regarding this specific error but the response was nondescript. Can you please provide a solution?

No problem, that 500 error is typically because your web host is taking a proactive step to hardening their box.  I have had to deal with it on a few occasions, that is the reason I am familiar with it, for the typical end user they are always left in the dark.

Glad it is working!

its works! thanks a lot! 

chmodded the files to 755. i am looking into why all the files are being set to 777

One of two things is happening based on the fact that your host is running phpsuexec or suexec.
(1) The directory/file is set to 777 when it needs to be max 755 (most likely)
(2) Your user account does not own the directory/files

Try setting the directories and files within to be 755 and try it again.