Results 1 to 5 of 5

Thread: Major Problem After Upgrade To 4.5.1b

  1. #1
    Deland01 is offline Sugar Community Member
    Join Date
    Sep 2006
    Posts
    66

    Default Major Problem After Upgrade To 4.5.1b

    I upgraded to 4.5.1b from 4.5.0h yesterday & everything went fine. I took a backup of the site and also made a backup of the SQL tables with MyPHP Admin.



    I've been doing some testing today and cleared the tables with the data in that I’ve been testing. I then re-instated the following tables:



    accounts_cstm
    accounts_opportunities
    acl_actions
    acl_roles
    acl_roles_actions
    acl_roles_users
    bugs
    bugs_audit
    calls
    calls_contacts
    calls_cstm
    calls_users
    campaigns
    campaigns_audit
    campaign_log
    campaign_trkrs
    cases
    cases_audit
    cases_bugs
    config
    contacts
    contacts_audit
    contacts_bugs
    contacts_cases
    contacts_users
    currencies
    custom_fields
    dashboards
    documents
    document_revisions
    emailman
    emails
    emails_accounts
    emails_bugs
    emails_cases
    emails_contacts
    emails_leads
    emails_opportunities
    emails_projects
    emails_project_tasks
    emails_prospects
    emails_tasks
    emails_users
    email_marketing
    email_marketing_prospect_lists
    email_templates
    feeds
    fields_meta_data
    files
    iframes
    import_maps
    inbound_email
    inbound_email_autoreply
    leads
    leads_audit
    leads_cstm
    linked_documents
    meetings
    meetings_contacts
    meetings_users
    notes
    opportunities
    opportunities_audit
    opportunities_contacts
    opportunities_cstm
    project
    project_relation
    project_task
    project_task_audit
    prospects
    prospect_lists
    prospect_lists_prospects
    prospect_list_campaigns
    relationships
    releases
    roles
    roles_modules
    roles_users
    saved_search
    schedulers
    schedulers_times
    tasks
    tracker
    upgrade_history
    users
    users_feeds
    users_last_import
    users_signatures
    user_preferences
    vcals
    versions


    I then tried to log into Sugar & now all i get is a blank white page with the following:



    "Sugar CRM 4.5.1b Files May Only Be Used With A Sugar CRM 4.5.1 Database."



    I didn’t backup the SQL database after the upgrade as I didn’t realise it would be upgraded.



    Can anyone help?





    Is there a way I can upgrade the SQL database to a 4.5.1b without sugar?
    Sugar Version - 4.5.0h
    Sugar Edition - SugarSuite
    OS - Win 2003 Server Std
    PHP Version - 5.2.0
    Database - MySQL Server 5
    Web Server - Apache 2.0.59

  2. #2
    Deland01 is offline Sugar Community Member
    Join Date
    Sep 2006
    Posts
    66

    Default Re: Major Problem After Upgrade To 4.5.1b

    Considering my blunder in not taking an SQL backup of all the tables after the upgrade I'm now thinking about setting sugar up again from scratch as I've had so many issues with it.



    My question is would I be able to import my existing tables into a new Sugar database after I’ve set a new sugar up with the same customisations as the old one?
    Sugar Version - 4.5.0h
    Sugar Edition - SugarSuite
    OS - Win 2003 Server Std
    PHP Version - 5.2.0
    Database - MySQL Server 5
    Web Server - Apache 2.0.59

  3. #3
    johncereus is offline Junior Member
    Join Date
    Dec 2006
    Posts
    2

    Default Re: Major Problem After Upgrade To 4.5.1b

    You should look into Jitterbit. It is an intergration server that will allow you to transfer info from almost any format to any format. I have used it for a migration from Salesforce to Sugar and it went awsome.

  4. #4
    jmaxwell is offline Sugar Community Member
    Join Date
    Jul 2005
    Posts
    51

    Default Re: Major Problem After Upgrade To 4.5.1b

    check your database, look in the config table, at the field where the version number is stored. That's what causing the error most likely, a mismatch between what sugar thinks the version is and what you have in the databse. Change it so they are the same (code base and DB field) and that error will go away.

    (database sugar.config, field where category = info, name = sugar_version value = 4.5.0 or whatever)

    it is possible to update the codebase and then migrate the database to the new version, either via the included update scripts in sugar's updater packages, or by running the scripts separately (the mysql schema changes) and then updating this and a few other fields as needed so sugar thinks the DB was migrated too.

    HTH

    -Ed

  5. #5
    Deland02 is offline Sugar Community Member
    Join Date
    Sep 2006
    Posts
    35

    Default Re: Major Problem After Upgrade To 4.5.1b

    Thanks both for that, I found a way round it in the end. I've got backups of Sugar & SQL everyday since I can remember.

    I restored the site (sugar) and then loaded an SQL restore with the same date & time. It took sugar back to 10 minutes before I upgraded it.
    OS = Win 2003 Server Std Edtn
    Webserver = Apache 2.0.59
    Sugar Version = 4.5.0h
    MySQL = 5.0.27
    PHP = 5.1.6

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Upgrade process review - 2.0 to 4.0
    By kimvette in forum General Discussion
    Replies: 2
    Last Post: 2007-05-22, 06:18 PM
  2. Warning: Please upgrade 4.5.1b
    By SugarBuddy in forum Installation and Upgrade Help
    Replies: 6
    Last Post: 2007-03-29, 11:58 AM
  3. Upgrade 4.5.0h to 4.5.1b errors
    By Deuce in forum Installation and Upgrade Help
    Replies: 12
    Last Post: 2007-03-27, 12:16 AM
  4. Replies: 1
    Last Post: 2006-08-11, 09:39 AM
  5. Replies: 1
    Last Post: 2006-01-11, 03:24 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •