Forums

I know this has been rased before but I get this error when installing:

JInstaller::install: SQL Error. DB function failed with error number 2006
MySQL server has gone away SQL=DELETE FROM `jos_components` WHERE `option` = 'com_chronocontact';
SQL =
DELETE FROM `jos_components` WHERE `option` = 'com_chronocontact';Component Install: SQL Error. DB function failed with error number 2006
MySQL server has gone away SQL=DELETE FROM `jos_components` WHERE `option` = 'com_chronocontact';
SQL =
DELETE FROM `jos_components` WHERE `option` = 'com_chronocontact';Error Loading ModulesMySQL server has gone away SQL=SELECT id, title, module, position, content, showtitle, control, params FROM jos_modules AS m LEFT JOIN jos_modules_menu AS mm ON mm.moduleid = m.id WHERE m.published = 1 AND m.access <= 2 AND m.client_id = 1 ORDER BY position, ordering

Is ther any new solution for this problem?

Hi paulmin,

DB Connection errors seem most often to be a sign of an over-loaded server. The best advice is to get a new ISP or choose a quieter time of day to do the installation. That said the installation isn't very DB intensive :-(

Bob

Hi paulmin,
This could also be the result of a very low timeout setting of the MySQL server, especially with the rather large size of the ChronoForms package. You could try manually uploading the installation files to your webserver,and install from there, which should buy you a little time as the files are already uploaded.
That said, as Bob mentioned, this is a good (or rather bad?) sign that the SQL server is not scaled for the load it suffers...

/Fredrik

Thanks for the replies. Here is an interesting development:

I have an old non-Joomla site for my business on a server. A few months back I decided I want a better website and installed a Shape5 template on the server live, but not public. After working on it for some time I drifted away without finishing it. Then about a months ago I found a new better template from Shape5, that I installed on the same server in yet another folder. That's the one I am serious about finishing and need to use ChronoForms on. I used supplied site shapers for both and everything has been working fine up until this problem with Chronoforms.

I have tried the manual installation and preloading the files and it did not make a difference. Last night in desperation I thought I'd try to install CF onto the first site. And -wadda ya know- it installed first go no probs. The only real problem is that it is on a wrong site. They are on the same server so it wouldn't be a server issue.

Now, I compared all the settings for both sites in their Global Config and they are identical. Only difference I can see is that the former site is using Joomla 1.5.7 and the one with problem is 1.5.9

I am not a web developer, but I have been mucking about with computers since the DOS 2.1 and this really bugs me. Here is my question: are there settings in MySQL or in other places I can look at and compare? Where do I look?

Hi paulmin,

The template shouldn't make a difference (if in doubt switch to JA Purity to test); and I don't recall any Joomla changes between those versions that would affect the installation.

Do both sites access the same database? If so it's even odder.

Have you tried a manual installation as Fredrik suggested?

Bob

Hi paulmin,
There's a good information-page on the error message from the MySQL-crew here: http://dev.mysql.com/doc/refman/5.0/en/gone-away.html
I don't have any ideas at the moment why one would work flawlessly while the other critically fails, especially as they're runing on the same server.. Are they also using the same database credentials and database?

/Fredrik

I installed the new site into a new database so they are each on different one. That's probably the problem, that there is something in the database causing this. But I haven't got a foggiest idea of how to find what is it. Would anybody know? Or is it a case of re-installing the site again and starting from the scratch? :mrgreen:

BTW Bob: I tried the manual install with the same result.
Thanks Fredrik for the link about the error message. I didn't find any solution in there yet.