Failed to create change tracking time stamp for virtual disk file

[g.natsoulis]

The case number is 06005294

Hello,

I have a cluster with 3 nodes and after some upgrades and reboots done in the operating systems of those notes I have a problem with the time stamp in two VM's
I have tried resetting the CBT but nothing changed.
The logs show the following.

[05.04.2023 21:34:41.902] <20> Error [RPC] Element not found.
[05.04.2023 21:34:41.902] <20> Error [RPC] Failed to obtain location of file 'I:\VM-PDM\Virtual Hard Disks\PDM_Data.vhdx'.
[05.04.2023 21:34:41.902] <20> Error [RPC] --tr:Error code: 0x80070490
[05.04.2023 21:34:41.902] <20> Error [RPC] --tr:Failed to add file 'I:\VM-PDM\Virtual Hard Disks\PDM_Data.vhdx' to the list of CTP tracked items. VM: 'VM-PDM'. VmID: '{73a6780a-31ea-470a-9aba-c113c6dda6af}'.

I've searched all over the forum but haven't found a solution yet.
Can anyone help?

[PetrM]

Hello,

It's not a support forum, we cannot effectively troubleshoot technical issues over the forum posts. Please continue working with your support engineer to find out the root cause.

Thanks!

[g.natsoulis]

Hi Petrv,

I am just asking the community for suggestions on my problem. Maybe some fellow here had the same problem in the past and can help.

[PetrM]

I understand it but keep in mind that someone else's suggestion that was helpful in one case might even worsen the situation in your case and make troubleshooting even more complicated. The error code 0x80070490 means that the file is corrupted or was not found. If the file is corrupted, there are many possible reasons, most probably related to the storage and I really doubt that this is something that can be easily fixed.

Thanks!

[g.natsoulis]

After upgrading the VM to version 9 the CBT works perfectly!

[PetrM]

I must admit that in this specific case the resolution time is much shorter than I expected Glad to hear that the issue is sorted out and many thanks for sharing the solution with us.

Thanks!

[g.natsoulis]

It was quickly resolved because it was easy to see that those Vms that had the problem were the only VMs that were on v5.

[ctihelpdesk]

Hi g.natsoulis,

I'm having the same issue. can you please clarify what you mean by "upgrading the VM to version 9"

what exactly did you upgrade and how?

[PetrM]

Hello and Welcome to Veeam R&D Forums!

I guess it's about upgrading a virtual machine version but before doing anything please open a support case and provide a support case ID as requested when you make a post about a technical issue. All posts about technical issues without case ID will be eventually deleted by the forum moderator.
UPD 11/23/2023: the link for upgrading a virtual machine version

Thanks!

[g.natsoulis]

Hi g.natsoulis,

I'm having the same issue. can you please clarify what you mean by "upgrading the VM to version 9"

what exactly did you upgrade and how?

Hello ctihelpdesk,

You can find the exact procedure here https://learn.microsoft.com/en-us/windo ... ows-server

[ctihelpdesk]

You are awesome. That worked. I submitted a ticket to Veeam and they provided me with this https://www.veeam.com/kb1934 .

However, none of the steps listed in that article fixed the issue. Veeam should definitely include your fix on their KB article.

Thanks again for your help

[g.natsoulis]

That's great news ctihelpdesk,
I'm very happy that I could help you.
Merry Christmas, my friend.