Virtualization Station Errors After Update

[Fuzzy John]

A few days ago my Virtualization Station was updated from v3.6.27 to v3.6.33.
After this update when I log into Virtualization Station using the Microsoft Edge browser I receive an email that states:

[Error][Virtualization Station] Notification from your device: My-NAS
NAS Name: My-NAS
Severity: Error
Date/Time: 2022/08/13 10:34:56
App Name: Virtualization Station
Category: System
Message: [Virtualization Station] Failed to install Virtualization Station. Error message: John

This email comes from QTS 5.0.0.2055.
However I do not see any issues with Virtualization Station as it runs.
Note that I get this message only when I access Virtualization Station directly (http://192.168.1.11:8080/qvs/). If I start Virtualization Station from the QTS (http://192.168.1.11:8080/cgi-bin/) Dashboard I do not get this error and email.

Also, after creating a snapshot of a VM, when I start that VM I get another email that states:

[Error][Virtualization Station] Notification from your device: My-NAS
NAS Name: My-NAS
Severity: Error
Date/Time: 2022/08/13 10:36:02
App Name: Virtualization Station
Category: Virtual Machines
Message: [Virtualization Station] Failed to carry out incoming migration of VM "Name of snapshot" from "Name of VM". Error message: There is insufficient system memory to migrate the VM.

Note that I also get this error and email when I use Virtualization Station inside the QTS.

I never got these emails before the update to v3.6.33.
TS-451+
Version 5.0.0.2055
RAM 8GB
RAM Usage 25%

[netbix]

I have same error !
Any snapshot, manual and automatic with this error

[NUT65]

I got the error "Failed to install Virtualization Station. Error message: Downgrading Virtualization Station to an earlier version is not supported. " on any backup task that ran on my VMs.

All VMs are running fine, the backups are created, I only have to still test if I can restore and have a working VM...

VS 3.6.33

TVS-471
i7-4790T CPU
16GB RAM

[cacakaka]

I have the same error after updated from v3.6.27 to v3.6.33.
"[Virtualization Station] Failed to carry out incoming migration of VM "Name of snapshot" from "Name of VM". Error message: There is insufficient system memory to migrate the VM."

[dolbyman]

time for a ticket I'd say

[klaus.singer]

After updating the Virtualization Station my VM does not start anymore.
Windows blue screen: "your computer was unable to start - Startup Repair is checking your system for problems..."
This applies also for all my snapshots!!!

Currently a system repair check is running for 4 hours - and this is still ongoing.

Is there a way to install the previous version of the Virtualization Station?

[bokr71]

My VMs work fine, but I get emailed the error every night saying:

Message: [Virtualization Station] Failed to carry out incoming migration of VM "VM SS Schedule" from "Windows 10". Error message: There is insufficient system memory to migrate the VM.

This started when Virtualization Station was updated a few days ago.

[stefp77]

Same problem here!

After updating Virtualization Station I get this error every time I take a snapshot:

App Name: Virtualization Station
Category: Virtual Machines
Message: [Virtualization Station] Failed to carry out incoming migration of VM "Name of snapshot" from "Name of VM". Error message: There is insufficient system memory to migrate the VM.

[dolbyman]

Hope everyone opened tickets..as repeatedly posting the same error here, will do nothing

[EDIflyer]

Identical issue here too, definitely seems to be a bug.

[rolandrat]

I logged a call as had the downgrade error whenever a VM backup ran - They have started a remote session today - no news yet.

[rolandrat]

3.6.34 release, looks like to fix this.

[ptimmons]

I logged a call as had the downgrade error whenever a VM backup ran - They have started a remote session today - no news yet.

Release 3.6.34 solved this error message too.

[serendrewpity]

Same Problem. Same Fix. v3.6.34 fixed the error message.

Thank you to all the different people who posted they have the same issue.

It let me know that, running chkdsk, reclaim, rebooting and memory optimization wasn't going to fix my issue because the issue was not on my end, but a larger issue with Virtualization Station that affected everyone with a particular configuration.

Keep posting here... it DOES do something.

[dolbyman]

Keep posting here... it DOES do something.

No, only opening tickets will catch QNAPs attention..posting here will not do that.

You are mixing up cause and effect