Can't Commit Modules - Get Server 500 Error

[lukemilton1]

SugarOS version 4.2.1b
PHP 4.4.4 MySql 4.0.27
Apache/1.3.37 (Unix)
hosted environment

I have been using sugar for some time now. I installed a module for Quotes from C3CRM and then removed it later. Ever since then, I have been unable to install any modules or even do an upgrade. Could not even get into the module or upgrade sections of the admin, it would jsut give me a 500 Server Error (strangely, it would let me get in occasionally, but only after waiting for awhile, the first time it would, then no more.) I overwrote all my files with the most recent version of Sugar OS and I am now able to consistently et into the module and upgrade sections, but I can't successfully install a module. They upload fine, but after attempting to "Committ" it give me the error. Everything else works fine in my installation except I get a 500 error when trying to install any modules.

I have tried everything I can think of (I am not a programmer) Can anyone help? I have also uploaded the latest diagnostic from my site.

Also, when I try to repair the database, I ALWAYS get this, even after I execute it, it still comes up:
/* Table : acl_roles_actions */
/*COLUMNS/*
/*INDEXES/*
/*MISSING INDEX IN DATABASE - idx_aclactions_roles -index ROW/*
ALTER TABLE acl_roles_actions ADD

Thanks,
Luke

[kbrill]

You need to post your apache logs

[lukemilton1]

My web host replies: "we dont provide access to Apache error logs on shared hosting packages for
technical reasons"

Do you have any other suggestions? Does the other information fail to suggest any possible cause?

Your help is appreciated.

Thanks,

Luke

[kbrill]

My web host replies: "we dont provide access to Apache error logs on shared hosting packages for
technical reasons"

Do you have any other suggestions? Does the other information fail to suggest any possible cause?

Your help is appreciated.

Thanks,

Luke

Since the error 500 is comming from apache your only hope is that they will help you. A host that won't show you YOUR apache logs is pretty lazy.

[lukemilton1]

They will not do it... I ahve contacted them directly www.1and1.com and they refuse. Do you have any other suggestions? I'm rather desperate at this point... afraid I am not going to be able to upgrade until this is resolved. Interesting that it didn't start until the C3CRM module, which appears to have modified the database...

Any wild guess would be appreciated at this point.

Thanks

-Luke

[kbrill]

I'm afraid you only have 2 choices, get someone to go in and fix your system or move it to a better system. Without access to the logs it will be very difficult to fix without some programming knowledge.