topic RE: Database upgrade Failed 6.2.1 -> 6.10.2 in Product Forum

Database upgrade Failed 6.2.1 -> 6.10.2

Eirik.Sandberg — Mon, 30 Aug 2021 14:58:00 GMT

Howdy folks

Having some problems with upgrading the database from version 6.2.1 to 6.10.2

getting this error:

Checked the generated script and the relevant stage seems to be:

exec('INSERT INTO BPADBVersion(dbversion, scriptrundate, scriptname, [description], timezoneoffset) VALUES(''285'', GETUTCDATE(), ''db_upgradeR285.sql'', ''Performance enhancements'', 0); ')

Although im not sure here.

Anybody had similar issues or hav any ideas how to deal with this?

Any help is appreciated:)

Eirik Sandberg

------------------------------
Eirik Ferdinand Sandberg
Associate
Differ Strategy Consulting
Europe/Oslo
------------------------------

RE: Database upgrade Failed 6.2.1 -> 6.10.2

steven.boggs — Mon, 30 Aug 2021 17:23:00 GMT

Hi Eirik,

This looks to potentially require a bit more investigation than we could perform in a Community post, but we'd be happy to help troubleshoot this with you via a Support ticket. I would recommend you create a new ticket with the above details and the exception information/screenshot, along with the required info outlined in our KB, "What information should I provide when reporting Database errors?".

------------------------------
Steve Boggs
Senior Software Support Engineer
Blue Prism
Austin, TX
------------------------------

RE: Database upgrade Failed 6.2.1 -> 6.10.2

JerinJose — Tue, 31 Aug 2021 07:49:00 GMT

Hi Eirik,

usually this kind of issue comes when you are trying to upgrade to a latest version skipping versions in between. though 6.2.1 is not listed among invalid upgrade paths while updating to 6.10.2. you can try upgrading databse to 6.4 before upgrading to 6.10.2

------------------------------
Jerin Jose
Technical Product Owner
EY
Asia/Kolkata
*"If you find this post helpful mark it as best answer, .*
------------------------------

RE: Database upgrade Failed 6.2.1 -> 6.10.2

Eirik.Sandberg — Thu, 23 Sep 2021 09:00:00 GMT

Our problem was that our insatlled version of supervisor had not been properly uninstalled at the server and had left a trigger in one of the tables. Disabled the tigger and i worked fine:)

------------------------------
Eirik Ferdinand Sandberg
Associate
Differ Strategy Consulting
Europe/Oslo
------------------------------

RE: Database upgrade Failed 6.2.1 -> 6.10.2

PritamPoojari — Thu, 23 Sep 2021 13:27:00 GMT

Hi Eirik

Is that RPA Supervisor product which added triggers to BP database?

Regards
Pritam

------------------------------
Pritam Poojari
Solution Architect
Capgemini
Europe/London
------------------------------