Closed (fixed)
Project:
e-Commerce
Version:
5.x-3.4
Component:
installation
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
15 Feb 2007 at 18:13 UTC
Updated:
24 Nov 2008 at 02:25 UTC
When trying to enable the e-commerce modules, I get the following error:
_ec_mail_modref() SERIOUS ERROR! Your system is not functioning properly. Consult your system administrator and DO NOT, repeat DO NOT, modify any mail settings.
Update to reference counts failed
Comments
Comment #1
simeBETA2 has had heaps of bug fixes, please try again with dev version.
http://drupal.org/node/115490
Comment #2
sime*Assuming* that your specific case is now fixed by changes since Beta2, I am going to hi-jack this ticket. Above error occurs when adding a reminder to a schedule.
I fixed up a lot of the fapi of ec_recurring, but got stuck with ec_mail_selection_form() missing the fourth parameter:
Anyway, turns out that mid is empty in ec_mail_modref(). I couldn't work out the fix.
Comment #3
sammys commentedThe issue has been fixed in both 4.7 and 5.0 releases of EC 3.0.
--
Sammy Spets
Synerger
http://synerger.com
Comment #4
kevinwalsh commentedHmm, i'm having the same problem with EC 3.0 beta 3 on 5.1
-kevin
Comment #5
simeKevin
This error can happen in many places in ec, please describe steps to reproduce. Feel free to open a new ticket, or mark this ticket as open when you supply the info.
Thanks
Comment #6
kevinwalsh commentedthanks sime
I first tried enabling all core ecommerce modules simultaneously. Got the error above, so i manually turned all the EC modules off in phpmyadmin, dropped all the ec tables, and reinstalled the modules.
I also then deleted the one cck product type that i had created that had product enabled from my 4.7 install.
I then tried enabling the four modules that seem to be the core of the core, based on their requirements--store, product api, mail subsystem, and anon purchasing. Same deal. Going into phpmyadmin, i noticed that the status store module was still 0. So i disabled them and then tried one by one, first the product api, then anon purchasing, then mail subsystem. Upon enabling store.module i got the error again.
My bug-finding methodology is probably not very good, let me know if i can do something that would produce more info. i could try disabling, dropping the tables, deleting the files and starting over again.
oh yeah, i'm using this morning's (Feb 18) build.
-kevin
Comment #7
WisTex commentedI updated to E-Commerce 5.x-3.0-Beta3 and I still get the following error when attempting to enable the e-commerce module:
_ec_mail_modref() SERIOUS ERROR! Your system is not functioning properly. Consult your system administrator and DO NOT, repeat DO NOT, modify any mail settings.
Update to reference counts failed
Comment #8
sammys commentedThank you for submitting the extra information Kevin and also to WisTex for revisiting the issue. I can't reproduce the problem on my configuration (PHP 4.3/PostgreSQL). I've added a backtrace and list of installed modules to the error message output in _ec_mail_modref(). This will be available in beta 4.
If you still experience this bug with beta 4 please also post the version of the file displayed on the line starting with $Id at the top of the four modules in question.
--
Sammy Spets
Synerger
http://synerger.com
Comment #9
simeSeems I can replicate this currently by installing all the core modules. FYI, I was working with an existing site. I deleted all the ec_ tables, and all the ec records from the system table and all the ec_ variables:
Comment #10
simeSo, installs OK if I leave out shipping and subproductapi (seems to be shipping install triggers too early). This is fine if people follow the install instructions in the handbook.
.s
Comment #11
simeAnother tidbit. I have been uninstalling ecommerce by deleting all tables and lines out of the system table. In 4.7v3 I was getting the error. Then I tried deleting all variables out of the variable table as well. Seemed to work.
So, this could be happening to others too, if installation has failed in the past and they try to re-install.
Comment #12
kevinwalsh commentedquick clarification... where do i delete the ec_variables?
Comment #13
kevinwalsh commentedsame error. I:
- deactivated the modules
- dropped teh ec_tables
- deleted the ecommerce rows from the system table
- installed beta4
- followed the handbook installation guide (installing the product api, anon purchasing and mail subsystem).
same error! i'm wondering if there's another ecommerce reference somewhere in my database that i need to drop or delete.
Comment #14
sime@kevinwalsh
To delete the variables, just go into the "variable" table and delete all the variables beginning with ec_, there are a couple others related to ecommerce that don't begin with ec_, but it shouldn't matter if you miss those.
Comment #15
sammys commentedI'm still unable to reproduce on both 4.7 and 5.0.
Comment #16
simesammys: should variable table setting be implicated here? or is it a red herring?
Comment #17
jdsaward commentedI just had the same problem with an install of 5.x-3.0 on a 5.1 site. The site had tables and variables left over from an older version of ecommerce.
I still got the error when I cleaned up the tables and the system records.
The problem disappeared when I cleared all the ec_ variable records as in #14.
John
Comment #18
sammys commentedCould two of you please give me EXACT steps, winblowz/linux, PHP version, DB flavour/version, webserver type/version and all other details required to reproduce from installation of default Drupal core. This is obviously a rare case that doesn't exist on my platform so I need as much information as I can get to solve it.
E.g...
Linux
PHP 4.3
Apache 1.3
PostgreSQL 7.4
From Drupal Core install:
* Enabled token, foo
* Configured foo with blah blah blah
* Enabled ec_mail
...
In the above the separate lines of Enabled means you clicked the button to install the selected modules.
Cheers,
--
Sammy Spets
Synerger
http://synerger.com
Comment #19
WisTex commentedSammys, Here is what I think caused the problem in my case.
From what I recall, this is how to reproduce the error:
1. Install Beta version of E-Commerce Module and it fails when you don't activate all the modules as required at the same time. This crashes the entire site.
2. Go into database and delete all e-commerce related tables you can find, but forget to delete the e-commerce variables. Site usable again, but e-commerce not enabled.
3. Reinstall the e-commerce module, preferably non-beta version.
4. Attempt to reactivate e-commerce module, except make sure all modules are activated this time.
5. Site crashed with _ec_mail_modref() SERIOUS ERROR!.
5a. Repeat steps 2 thru 5 until you find out you have to do step 6 below. ;)
Resolution:
6. Delete variables for e-commerce in the variables table.
7. Press refresh a couple times on the error screen. It will complain the tables are already there but everything seems to work fine now.
Platform information:
Operating system Linux
Kernel version 2.6.9-42.0.3.ELsmp
Machine Type i686
Apache version 1.3.34 (Unix)
PERL version 5.8.7
PHP version 4.4.1
MySQL version 4.1.21-standard
cPanel Build 10.9.0-RELEASE 118
Theme cPanel X v2.6.0
cPanel Pro 1.0 (RC36)
Hope this helps.
Comment #20
simeThis happened to me again today. Same thing, uninstalled ec. I agree it's the remaining variables.
Comment #21
druvision commentedIt happened to me today with Drupal 5 and EC3.0.
I agree it's the upgrade from old versions (4.6, in my case).
The only way to get read of it was by
(1) Deleteing all EC tables.
(2) Deleting EC information from the system table.
delete from system where filename like '%ecommerce%' and type ='module';(3) Deleting all EC variables from the variables table, including those not prefixed by EC.
delete from variable where name like 'ec_%' or name like 'payment_%' or ...;(4) Reinstall by the instructions as set in the Ecommerce handbook
Comment #22
p_palmer commentedthanks levavie for comment #23, worked a treat for me when i borked into this, no bug report, just that this solution worked.
a note, you may experience some left over table errors but if you double check the variables table with a second delete, then all should be ok when you then refresh the module page. This cleanup works for me under D5.2 and EC 5.x-3.2-rc2patch1 EC 5.x-4.0-dev.
Comment #23
p_palmer commentedbah, i meant comment #21, sorry
Comment #24
rdsmith commentedI recently installed the 5.x-4.0-alpha1.
I then rolled back to version 5.x.3.0 b/c I wanted to have the authorize.net payment module and the shipping API on my ecommerce install.
I tried the steps as below...to uninstall 5.x-4.0-alpha1.
(pre) I un-enabled the module
(pre2) I used Drupal GUI to drop all tables from the database
(1) Deleting all EC tables. manually
(2) Deleting EC information from the system table.
delete from system where filename like '%ecommerce%' and type ='module';
(3) Deleting all EC variables from the variables table, including those not prefixed by EC.
delete from variable where name like 'ec_%' or name like 'payment_%' or ...;
(4) Reinstall by the instructions as set in the Ecommerce handbook
This sort of worked,
I enabled the store module (which enables the core the ecommerce module)
I then enabled the Address module
I then enabled the Authorize.Net module
I then enabled the Generic Product then the Parcel Product Product types
I then enabled the Invoice module
Then I finally enabled the Ship Calc and Shipping API modules
I get the monstrous error stated all through this post (starting with _ec_mail_modref() SERIOUS ERROR! ) but then I refresh the page
Now when I view http://www.mysite/admin/build/modules. I see that the Shipcalc module is enabled and the Shipping API module is greyed in so you can't check it , but then it appears to be working....
I think that the 5.x-4.0-alpha1 module is inserting more into the MySQL database than meets the eye.
Any suggestions?
Comment #25
goose2000 commentedHi, getting this error too; upon a fresh install (no past e-commerce installed). I'm using:
IIS 5.0
PHP 5.1
MySQL 5.0
Drupal 5.2
I was using module: ecommerce-5.x-4.x-dev.tar.gz as of today 9/20/07
I have tried to install with all core bits checked off and get the error.
I have tried with just the Store part checked, same problem.
Between test installs, I completely delete my database. Then restore a known good database
setup and try again.
Comment #26
goose2000 commented@rdsmith - yes I have now gone through your steps too, enormous page of error, back to admin page I get this:
I refresh the page and it goes away. Check the watchdog and I now see this entry (although I have done nothing):
ec_mail 09/20/2007 - 1:11pm Mail added: Default customer invoice janderso edit
Seems like the refresh triggered this?
Comment #27
GravitySpec commentedI'm getting this same error with a fresh install of Drupal 5.2.
My setup:
WinXP running: Apache/2.2.4 | PHP/5.2.4 | MySQL 5.0.45
My Steps:
1. Fresh install of Drupal 5.2.
2. Added Token to /sites/all/modules
3. Enabled Token, saved changes
4. Added e-Commerce-5.x-4.x-dev to /sites/all/modules
5. Enabled Store, saved changes
6. Get error "_ec_mail_modref() SERIOUS ERROR!..."
If I navigate back to my admin page I get the same message as goose2000.
In modules Cart, Anonymous purchasing, Customer, eC Mail, eC Receipting, and Product API are shown as enabled but Store is Grayed out and shown as Disabled.
I hope this helps.
Comment #28
Osangar commentedDrupal 5.2
PHP 5.0.3
Postgres 8.2.3
Apache 2.0.55
Windows XP
Fresh installation of Drupal into Postgres db.
Install CCK modules first.
Installed Imagecache, Thickbox, Taxonomy Menu, and Token (required by Store).
Go to install Store (depends on Token, already installed) and I get this mass error.
I now look at Store and it is greyed out, but the checkbox is not checked. Can not edit.
Comment #29
brmassa commentedGuys,
fixed on eC4
regards,
massa
Comment #30
syngistic commentedI have Drupal 5.3 , PHP 5 and Mysql 4.1.2 and am still getting this error.
" I _ec_mail_modref() SERIOUS ERROR! Your system is not functioning properly. Consult your system administrator and DO NOT, repeat DO NOT, modify any mail settings."
I also get a couple thousand lines of error messages after that. What can I do to figure this out?
Comment #31
rdsmith commentedHere's how I resolved my error (describes my transition from Ecommerce 5.x-4.0-alpha1 to Ecommerce 5.x-3.3 to Ecommerce 5.x-3.4 to Ecommerce 5.x-4.0-alpha6) I have Drupal 5.3
I deleted the Ecommerce 5.x-4.0-alpha1 module on mysite.com.
I deleted all ec_ tables.
I deleted all ec_ information from the system table.
delete from system where filename like '%ecommerce%' and type ='module';
I deleted all EC variables from the variables table, including those not prefixed by EC.
delete from variable where name like 'ec_%' or name like 'payment_%' or ...;
I copied in the files for Ecommerce 5.x-4.0-alpha6.
I ran update.php.
I enabled the Ecommerce 5.x-4.0-alpha6 module.
I deleted all ec_ information from the system table.
delete from system where filename like '%ecommerce%' and type ='module';
I deleted all EC variables from the variables table, including those not prefixed by EC.
delete from variable where name like 'ec_%' or name like 'payment_%' or ...;
I ran update.php.
I uninstalled the module through the admin part of the site.
I ran update.php.
I installed Ecommerce 5.x-4.0-alpha6 again.
And now there’s no module error ..
“ _ec_mail_modref() SERIOUS ERROR! Your system is not functioning properly. Consult your system administrator and DO NOT, repeat DO NOT, modify any mail settings.”
When I activate the shipping module..
The parts of the module I activated are (the e-Commerce Core ..by clicking on 'Store' it installed all of this, e-Commerce Customer Interface : Address, e-Commerce Payment Methods : Authorize.Net, e-Commerce Product Types : File Product, and e-Commerce Uncategorized : 'eC Recurring' and 'Shipping'
I went through this tedious process first to preserve all the data b/c I had installed the module on a site that was live dynamic with data flowing in and out continuously therefore I could not just revert back the database to an earlier state without losing a lot of data.
Hope This helps someone,
Robert D. Smith
Comment #32
marie70 commentedRobert
Thank you for posting, after a very frustrating couple of weeks my searching turned up your post and using the directions (specifically #21) above was able to go successfully get rid of my alpha version and install Ecommerce 5.x-3.4. I'm staying with that one because I need taxes and shipping, which don't work on 5.x-4.0
Comment #33
Phillip Mc commentedsame problem here guys. Anyone got a patch for this?
using ecommerce 5.x-3.4 (Is that the stable version?)
Phil
Comment #34
Phillip Mc commentedI had the same problem with ecommerce 5.x-3.4 as others did on here. I tried the instructions outlined in comment #21, but, I still got the dreaded
_ec_mail_modref() SERIOUS ERROR!message when trying to re-install the ecommerce suite.Through pure guesswork, I found a solution to the problems I was having by uninstalling the token.module and deleting references to it in the SYSTEM table in the database...ran update.php after that and then re-installed the token.module before enabling the store.module (which installs all the base modules) for ecommerce 5.x-3.4 suite without any error messages.
I'm not sure if it was uninstalling the token.module and deleting it from the system table, or if I forgot to run the update.php (you can run update.php from the admin/modules page) when trying to do this earlier, but, it worked and I thought I would share this on here.
(Changing the version for this thread to be for version 5.x-3.4 - apparently the problem has been fixed in 5.x-4.x and the 5.x-3.4 version is considered the stable version, so people who are having this problem might miss this issue).
Comment #35
Nikkol commentedI am getting this same error on a new install of 3.4 ... I have been using the token module, so I didn't want to uninstall it. Has there been any resolution to this?
Comment #36
Nikkol commentedI must have missed some of the ec_* variables when I first tried manually uninstalling. After following recommendations above to remove the tables, ecommerce entries in the system table, and ec_* entries in the variable table, installation went without a hitch.
Comment #37
ms2011 commentedLike Nikkol, I was trying to do a manual uninstall since the module currently has no hook_uninstall() function. Here's what worked for me:
Comment #38
decibel.places commentedRE:
#37
mikesmullin
This is a good starting point, but it will cause SQL errors if the tables do not exist - also I had an ec_invoice and ec_tax table that were not on the list - this code will not trip errors, using DROP TABLE IF EXISTS
AND - I had big problems with products still in the node table - they did not appear on the content admin, I only discovered them when I uninstalled e-Commerce and installed Ubercart - they need to be deleted on uninstall too
[EDIT - I have corrected an errant single quote that appeared instead of a semi-colon]
Comment #39
theorichel commentedI am having the same error omn Drupal 5.11 EC 5x-3x dev of nov 17 2008 when I try to change a setting on the store page.
Comment #40
davea commentedTheo,
This bug thread is so long- can you be specific about the error?
Thanks,
DaveA
Comment #41
theorichel commentedI had that error when I tried to change anything on the store-settings in ecommerce. I then removed Ecommerce according to the instructions in nr 38, reinstalled it and then the problem was gone.
Thanks
Comment #42
davea commentedadded numerous uninstalls to ec- also added code to prevent ec_modref error from mis-firing.
DaveA