Announcement

Collapse
No announcement yet.

Persistant Error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Paprika
    replied
    It worked, thanks guys!

    Leave a comment:


  • Paprika
    replied
    Thank you! I will be doing that tommorow, I just had to post a message warning users today to back up any important PMs they can access..

    Leave a comment:


  • Steve Machol
    replied
    First backup your database. Then delete those three tables and run these three queries to recreate them for 3.0.3:

    CREATE TABLE pm (
    pmid INT UNSIGNED NOT NULL AUTO_INCREMENT,
    pmtextid INT UNSIGNED NOT NULL DEFAULT '0',
    userid INT UNSIGNED NOT NULL DEFAULT '0',
    folderid SMALLINT NOT NULL DEFAULT '0',
    messageread SMALLINT UNSIGNED NOT NULL DEFAULT '0',
    PRIMARY KEY (pmid),
    KEY pmtextid (pmtextid),
    KEY userid (userid),
    KEY folderid (folderid)
    );

    CREATE TABLE pmreceipt (
    pmid INT UNSIGNED NOT NULL DEFAULT '0',
    userid INT UNSIGNED NOT NULL DEFAULT '0',
    touserid INT UNSIGNED NOT NULL DEFAULT '0',
    tousername VARCHAR(50) NOT NULL DEFAULT '',
    title VARCHAR(250) NOT NULL DEFAULT '',
    sendtime INT UNSIGNED NOT NULL DEFAULT '0',
    readtime INT UNSIGNED NOT NULL DEFAULT '0',
    denied SMALLINT UNSIGNED NOT NULL DEFAULT '0',
    PRIMARY KEY (pmid),
    KEY userid (userid),
    KEY touserid (touserid)
    );

    CREATE TABLE pmtext (
    pmtextid INT UNSIGNED NOT NULL AUTO_INCREMENT,
    fromuserid INT UNSIGNED NOT NULL DEFAULT '0',
    fromusername VARCHAR(50) NOT NULL DEFAULT '',
    title VARCHAR(250) NOT NULL DEFAULT '',
    message MEDIUMTEXT NOT NULL,
    touserarray MEDIUMTEXT NOT NULL,
    iconid SMALLINT UNSIGNED NOT NULL DEFAULT '0',
    dateline INT UNSIGNED NOT NULL DEFAULT '0',
    showsignature SMALLINT UNSIGNED NOT NULL DEFAULT '0',
    allowsmilie SMALLINT UNSIGNED NOT NULL DEFAULT '1',
    PRIMARY KEY (pmtextid),
    KEY fromuserid (fromuserid)
    );

    Then run these queries to reset the pm totals:

    UPDATE user SET pmtotal='0';

    UPDATE user SET pmunread='0';

    Leave a comment:


  • Paprika
    replied
    Loose all the PMs? thats not a big deal, tho important to the users they can't send them at all atm really anyway so.. yeah hit me up with that. Thanks.

    BTW could a crappy server cause this to happen? B/c Mine sucks and I am moving from it asap then I am going to turn around and stab it... then run it over.

    Leave a comment:


  • Steve Machol
    replied
    If this is still the case:

    After having looked at the last 30 rows of the table i believe the next auto-index number for pmid would be 4278220987
    ...then you have a serious problem. That needs to be fixced first. The only sure fire way to do this would be to delete and recreate these table:

    pm
    pmreceipt
    pmtext

    Of course this means that you will loose all your PMs. If you want to try this let me know and I'll find the queries.

    Leave a comment:


  • Paprika
    replied
    Well I just ran the tests, even rechecked the table dispite the fact I did not get any errors, straight OKs. *sigh*

    Though I understand the importance of having up-to-date software, spending the money at this very moment will not help me if it wont' fix this problem.

    Leave a comment:


  • George L
    replied
    PHP should be updated to 4.3.11 for bug fixes and MySQL 4.0.24 is recommended as it's at least 3x times faster than 3.23.x

    for now try repairing the pmreceipt table by typing this in ssh telnet as root user

    1. check database tables

    mysqlcheck -s -u mysqlusername -p vbforumdbname

    ignore session and cp session table messages but copy and paste any other error messages you get or take note of those

    2. repair dataabase

    mysqlcheck -r -q -u mysqlusername -p vbforumdbname


    3. recheck database tables

    mysqlcheck -s -u mysqlusername -p vbforumdbname

    if you want to do one table at a time then add tablename(s) to end of commandline

    i.e.

    mysqlcheck -s -u mysqlusername -p vbforumdbname tablename1 tablename2 tablename3

    mysqlcheck -r -q -u mysqlusername -p vbforumdbname tablename1 tablename2 tablename3

    I strongly recommend you renew your members area access to update to Vb 3.0.7 as prior versions have security bugs which can compromise your forums.

    Leave a comment:


  • Paprika
    replied
    Help please??

    Leave a comment:


  • Paprika
    replied
    Well though I have an owned license which was donated to my site, my member's area access has expired and the latest version I can download is 3.0.3. I was betting to keep using this version just as many sites in the past have keept using vbulletin 2x after 3x was released. Right now I do not have the funds avalible in my paypal account to make the purchase. But I still need this fixed. As I said earlier it cannot be the files for I have tried using a fresh installation with the same database and gotten the same error.

    I'm thinking it's the server atm. I am running PHP 4.3.8 & MySQL 3.23.58.
    I am also currently looking for new host so as soon as I get that together I can say weither or not the problem is just my current host.

    Leave a comment:


  • George L
    replied
    tried vB 3.0.7 ? what PHP and MySQL versions you're using ?

    Leave a comment:


  • Paprika
    replied
    After having looked at the last 30 rows of the table i believe the next auto-index number for pmid would be 4278220987

    Leave a comment:


  • Steve Machol
    replied
    Yes, look at the table in phpMyAdmin and note the next auto-index number.

    Leave a comment:


  • Paprika
    replied
    Exactly how do I do that?

    Using phpMyAdmin?

    Leave a comment:


  • Steve Machol
    replied
    The problem is the negative number for the pmid:

    -16746330

    vB would not have created this since this should be a unsigned fieeld by default.

    Check the next auto-index number for the pm table. What does it show?

    Leave a comment:


  • Paprika
    replied
    Well I know it's not the files, which I didn't really suspect in the first place. I created a clean installation of the forum in a seperate directory and using the exsisting database. Then I tested the PM ability and got the same error!


    Code:
    Database error in vBulletin 3.0.3:
    
    Invalid SQL: INSERT INTO pmreceipt
    	(pmid, userid, touserid, tousername, title, sendtime)
    VALUES
    	(-16746330, 1, 499, 'Obinice', 'testing', 1114803096)
    mysql error: Duplicate entry '0' for key 1
    
    mysql error number: 1062
    
    Date: Friday 29th of April 2005 03:31:36 PM
    Script: http://www.teen-moods.net/forums2/private.php
    Referer: http://www.teen-moods.net/forums2/private.php?do=newpm&u=499
    Username: Paprika
    IP Address: xx.xx.xxx.xxx

    Leave a comment:

widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...
X