Upgraded Windows 12.x latest to Windows 13.0.1 - no software upgrade issues.
Have serveral issues (already inCase # 07906254).
One seems special. When trying to edit certain Jobs we immediately get the error: "Invalid object's ViType. It must be one of VMware's ViTypes.".
Cannot edit that Job anymore.
But we do NOT have any VMware, only Hyper-V.
Since I cannot find this message, anyone seen this issue earlier?
-
dali@iae.nl
- Expert
- Posts: 113
- Liked: 29 times
- Joined: Jan 17, 2022 10:31 am
- Full Name: Da Li
- Contact:
-
PetrM
- Veeam Software
- Posts: 4044
- Liked: 698 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: V13.0.1 - Invalid object's ViType
Hello,
It does not appear to be a known issue. Please continue working with the support team to identify the root cause.
Thanks!
It does not appear to be a known issue. Please continue working with the support team to identify the root cause.
Thanks!
-
dali@iae.nl
- Expert
- Posts: 113
- Liked: 29 times
- Joined: Jan 17, 2022 10:31 am
- Full Name: Da Li
- Contact:
Re: V13.0.1 - Invalid object's ViType
Have created a separate Case #07911740 for this (because the other had several combined issues under it).
Probably seems to be a problem in de Hyper-V machine file vmcx.
Can reproduce it. Now created a new Hyper-V machine, copied over the hard disk. Then no problem anymore.
Uploaded bad and good vmcx files to see if Veeam can understand where and why this goes wrong. This error was also there in V12, so not V13 related.
Probably seems to be a problem in de Hyper-V machine file vmcx.
Can reproduce it. Now created a new Hyper-V machine, copied over the hard disk. Then no problem anymore.
Uploaded bad and good vmcx files to see if Veeam can understand where and why this goes wrong. This error was also there in V12, so not V13 related.
Who is online
Users browsing this forum: Google [Bot] and 4 guests