GUI Version is invalid

[raju devolla]

Hi All,

 

i am getting below error after ugprade to 4.5.

 

GUI version specified in database (4.4.0.23) is invalid. This version of the software can work with DB set for version 4.5.0.36 only. Please contact support.

 

I have tried to update repository after Upgrade, it requested for Admininstrator credentials, When i tried to launch using admin Access got the above error.

 

Please help.

 

Regards, Raju Devolla.

[raju devolla]

it is for SQL Server repository with 2012 version.

[Keith Puzey]

Hi,

 

  Can you confirm that you followed the steps in this Upgrade Guide on page 36 on wards it shows how to remove the rep.xml if present and upgrade the repository, can you let me know exactly in this process where you are seeing the error.

 

Regards

Keith

[Anil Kumar Appukuttan]

Raju,

 

Did you login to Datamaker using administrator credentials or did you run the program in administrator mode? You need to do both together for this to work.

[Somashekhar Morabad]

Me too getting exactly the same error as mentioned below..

         "GUI version specified in database (4.4.0.23) is invalid.
         This version of the software can work with DB set for version 4.5.0.36 only.
         Please contact support."

 

I have run TDM upgrade programs (TDM Version 4.4 to 4.5) as Administrator hence there should not be any issue here.

The only change what I have done is - Upgraded the TDM Portal before upgrading the repository. Not sure if this is causing the issue.

 

Any help is much appreciated.

 

Note:

OS = Win 2012 Server R2

DB = Microsoft SQL Server 2016

[Krushna padhy]

Hi Raju ,

 

Take backup of rep.xml to other location .Then delete rep.xml from GTDatamaker folder .

Then try to login .once you had successful login copyback rep.xml to GTdatamaker folder .

 

Regards,

Krushna

[narma13]

Hi,

 

First Step is to Upgrade Datamaker which upgrades the TDM Repository and then Portal should be upgraded. When you upgrade please follow the steps which is described at our Upgrade Center (CA Test Data Manager ).

 

Please log a ticket to resolve the issue.

 

Thanks and Regards,

Manju

[raju devolla]

Hi ,

 

Also try this below step from repository.

 

update gtrep_system set sys_gui_ver = null

 

 

Regards,

 

Vennlig hilsen

[Ryan McKlveen]

Hello,

It will be a combination of Krushna's response of:

    Take backup of rep.xml to other location .Then delete rep.xml from GTDatamaker folder .

    Then try to login .once you had successful login copyback rep.xml to GTdatamaker folder .

 &

Raju's response of:

    update gtrep_system set sys_gui_ver=null

[Somashekhar Morabad]

Thanks Ryan. Yes, I deleted the rep.xml previously and now after updating gtrep_system, Datamaker is working fine

[Legacy User]

Glad to know we have a workable solution.  However, it leaves a question for me:

 

• Having executed ‘update gtrep_system set sys_gui_ver = null;' so that the UI connects successfully,  what is the ongoing value of gtrep_system.sys_gui_ver ?
• I would suppose that the check of sys_gui_ver is there for a reason - presumably to make sure the UI doesn't ask for or try to write value(s) that are not defined in the current version of the repository?
  • Is there potential for further crashes / instability downstream?

 

Once the UI is able to connect to repo again, should there be a final step to run a repo upgrade, or at least repo maintenance, so that gtrep_system.sys_gui_ver is set correctly again?

 

 

[Somashekhar Morabad]

Hi Adrian,

Thanks for your reply. Ongoing value of gtrep_system.sys_gui_ver is still NULL. In addition, I have performed "Check Repository Tables" process and don't see any issue. However the value of sys_gui_ver still remains NULL.

Not sure about any further repository maintenance/update.

 

After doing all these actions, I still remain with another critical issue - OrientDB Service is not getting started. It ends up with following error. 

 

OrientDB Error

Windows could not start the OrientDB on local computer. For more information, review the System Event log. If this is a non-microsoft service, contact the service vendor, and refer to service-specific error code 1.

 

System Event Log = "The OrientDB service terminated with the following service-specific error:
Incorrect function."

 

Raised a ticket with CA Support and awaiting for the response

[Legacy User]

Thanks - good luck with getting OrientDB started.