v13 upgrade sql error

[tm67]

Hello
#07821030
My upgrade to v13 failed with an error
"Error details: The index 'Test_INDX_ObjectEntity_CollectorIdEntityKeyHash' is dependent on column 'CollectorId'"

In a remote session with support, we tried to manually execute the upgrade script. There was an error regarding a sql stored procedure that could not be found.
The SP that was referenced in the script is "rsrp_Backup_Common_ResovleOIJ" (in the v13 iso -> Addins -> SQLScript -> VeeamONE.sql)
In my MSSQL database, the SP is called "rsrp_Backup_Common_ResolveOIJ"
I think there is a spelling mistake in the SQL script.
I just downloaded the ISO again and also the typo is there. I do not have access to another VeeamOne v12 database at the moment but I think this typo can/will affect v13 upgrades.
I am actually not sure if my upgrade failed because of this (support is analyzing now), but I thought I'd share this one here.

Timo

[jorgedlcruz]

Hello Timo,
Thank you very much for such detailed post, we are investigating internally in RnD, we will keep you updated via ticket, and here as well for everyone else.

Thank you again

[sandsturm]

We wanted to upgrade our vONE v12 installation as well and struggled with the exact same error. Unfortunately, we had to rollback vONE database and server to the backup we have conducted prior to the upgrade. The recovery went fine and we're waiting for a clean vONE v13 iso release.
just a sidequestion: How can such a typo be in a production release of a software? For me, that is completely unbelievable and I just ask how you software quality assurance processes work.

This forum post is from 12. Sept and therefore almost one month old, but the iso file, which is downloadable has this typo still in it. Please remove this iso from your website as fast as possible, otherwise you will have a lot of customers with the same upgrade horror....

thx,
sandsturm

[jorgedlcruz]

Hello,
We are investigating from where this table come from, if with any update or hotfix. This problem could not be seen or reproduced on our extensive QA testing, so it is important to understand why that table was there.

At the time of when tm67 reported the issue, we had only that single report among a few hundreds successful installs, so we reviewed and provided with this SQL query that needs to be executed before upgrading verified by RnD:

Code: Select all

SELECT 
    i.name AS IndexName,
    i.type_desc AS IndexType,
    c.name AS ColumnName
FROM 
    sys.indexes i
INNER JOIN 
    sys.index_columns ic ON i.object_id = ic.object_id AND i.index_id = ic.index_id
INNER JOIN 
    sys.columns c ON ic.object_id = c.object_id AND ic.column_id = c.column_id
INNER JOIN 
    sys.tables t ON i.object_id = t.object_id
WHERE 
    t.name = 'ObjectEntity'
    AND c.name = 'CollectorId';

Then the upgrade was successful for that customer (although he had some other .NET problems after for what I can see, but now is all working)

My recommendation, even with this query here, will be:

• Always have a backup as you did, great job!
• Try this query with support on a Webex
• Try the upgrade

I will return with some more insights about the source of the issue, and next steps, which surely will be add this query before upgrade.

Thank you

[tm67]

Hi
I can confirm v13 is up and running in my environment.
We had a few issues during the upgrade, as Jorge mentioned. But I think we need to clarify that those were separate issues.

First, the error about "Test_INDX_ObjectEntity_CollectorIdEntityKeyHash"
We fixed this by running the above sql query provided by support.

Seccond, the "rsrp_Backup_Common_ResovleOIJ".
I am actually not sure if this interrupted my upgrade or if it did not matter. However, I think it is a spelling mistake, and it would be good to get fixed in a new ISO or completely removed if not used. I think Jorge mentioned that they will check internally.

And third, we had some .NET issues due to old .NET installations that were still on the server.

And one other issue we had was the database version.
As mentioned here post554578.html#p554578

Maybe this helps with your case.
Timo