CounterSoft Community Server

Welcome to CounterSoft Community Server Sign in | Join | Help
Home Forums

Upgrade from V2.0.3 to v2.2.7

Last post 11-19-2008, 8:58 PM by SaarCohen. 21 replies.
Page 2 of 2 (22 items)   < Previous 1 2
Sort Posts:
  •  11-18-2008, 8:51 PM

    Re: Upgrade from V2.0.3 to v2.2.7

    From the errors I see, it seems that you are trying to upgrade a 2.0.x database directly to 3.0.4, which can not be done!

    You need to run the upgrdae scripts first:

    • Upgrade_v2-1.sql (this script should drop the procedure 'gemini_issuelinktypes'
    • Upgrade_v2-2.sql

    After these have run, run the upgrdae to 3.0 scripts.

  •  11-18-2008, 8:53 PM

    Re: Upgrade from V2.0.3 to v2.2.7

    can i call you to get help from this, i am getting more and more weird errors

    well, let me try to use the 2 version script first and we'll see.  I think i messed up  because of skipping 2 version scripts
  •  11-18-2008, 9:04 PM

    Re: Upgrade from V2.0.3 to v2.2.7

    Now, i deleted the existing db, restored the v2.0.3 db again to sql2005 server

    I know the steps now:

    1) Run Upgrade-v2-1.sql
    2) Run Upgrade-v2-2.sql
    3) Run Create_Tables.sql
    4) Run Create_Views.sql
    5) Run Create_Procs.sql
    6) Run Upgrade-v3-0-step1.sql
    7) Run Upgrade-v3-0-step2.sql
  •  11-18-2008, 9:31 PM

    Re: Upgrade from V2.0.3 to v2.2.7

    I'm getting this error from executing the upgrade-v3-0-step1.sql

    (53 row(s) affected)
    Msg 208, Level 16, State 1, Line 16
    Invalid object name 'geminiappsettings'.


    Do we have such thing as geminiappsettings?
  •  11-18-2008, 9:35 PM

    Re: Upgrade from V2.0.3 to v2.2.7

    Yes, this gets created when running the 2.1 script!

    Make sure that you are using the same user to execute all scripts.

  •  11-19-2008, 3:51 PM

    Re: Upgrade from V2.0.3 to v2.2.7 --> 3.0.x

    I'm seeing this error with executing the Upgrade-v3-0-step1.sql  The original issues table doesn't have issuetypeid column

    The DELETE statement conflicted with the REFERENCE constraint "gemini_issues_issuetypeid_fk". The conflict occurred in database "Gemini", table "dbo.gemini_issues", column 'issuetypeid'.


  •  11-19-2008, 8:58 PM

    Re: Upgrade from V2.0.3 to v2.2.7 --> 3.0.x

    You have some issues with type id that does not exist in the issuetypes table. Suggest you find these and update them to use a valid type before running the script.
Page 2 of 2 (22 items)   < Previous 1 2
View as RSS news feed in XML