VMware Cloud Community
ap_harke_com
Contributor
Contributor

VM error in Scheduled Task after migration

Hello,

we have a problem with our scheduled task. we use them for backing up our servers.

here is the background. we were making a task for shutting down and power on a vm. (these tasks are ~ 4 weeks old). now we install a new esx server. (esx2) we migrate some vms to it. - old server (esx1)

at night, the tasks will start. one vm shutting down. but didn't power on again. here is the error message from the vm when we start the scheduled task for power on the vm. the shutdown task runs without any problems.

we make a new task for startup, the machine start!!!when we want to edit the "old" task the same error message occur.

\----


The request refers to an object that no longer exists or has never existed.

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

\************** Exception Text **************

Vmomi.Fault.ManagedObjectNotFound: The request refers to an object that no longer exists or has never existed

at VirtualInfrastructure.Vmdb.Command.ExecuteHelper()

at VirtualInfrastructure.Vmdb.TransportImpl.RemoteMethod(ManagedObject mo, String opName, Object[] pars)

at Vmomi.Scheduler.ScheduledTask.Run()

at VpxClient.InventoryContextMenus.miRunScheduledTask_Click(Object sender, EventArgs e)

at System.Windows.Forms.MenuItem.OnClick(EventArgs e)

at System.Windows.Forms.MenuItemData.Execute()

at System.Windows.Forms.Command.Invoke()

at System.Windows.Forms.Control.WmCommand(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

at System.Windows.Forms.ContainerControl.WndProc(Message& m)

at System.Windows.Forms.UserControl.WndProc(Message& m)

at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

\************** Loaded Assemblies **************

mscorlib

Assembly Version: 1.0.5000.0

Win32 Version: 1.1.4322.2032

CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll

\----


vpxClient

Assembly Version: 2.0.1.0

Win32 Version: 2.0.1.0

CodeBase: file:///C:/Programme/VMware/VMware%20Virtual%20Infrastructure%20Client%202.0/vpxClient.exe

\----


System.Windows.Forms

Assembly Version: 1.0.5000.0

Win32 Version: 1.1.4322.2032

CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll

\----


VirtualInfrastructure

Assembly Version: 2.0.0.0

Win32 Version: 2.0.0.0

CodeBase: file:///C:/Programme/VMware/VMware%20Virtual%20Infrastructure%20Client%202.0/VirtualInfrastructure.DLL

\----


Interop.VMDBCOMLib

Assembly Version: 10.0.0.0

Win32 Version: 10.0.0.0

CodeBase: file:///C:/Programme/VMware/VMware%20Virtual%20Infrastructure%20Client%202.0/Interop.VMDBCOMLib.DLL

\----


System

Assembly Version: 1.0.5000.0

Win32 Version: 1.1.4322.2032

CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll

\----


VMware.CustomControls

Assembly Version: 2.0.0.0

Win32 Version: 2.0.0.0

CodeBase: file:///C:/Programme/VMware/VMware%20Virtual%20Infrastructure%20Client%202.0/VMware.CustomControls.DLL

\----


System.Drawing

Assembly Version: 1.0.5000.0

Win32 Version: 1.1.4322.2032

CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll

\----


System.Xml

Assembly Version: 1.0.5000.0

Win32 Version: 1.1.4322.2032

CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll

\----


CustomMarshalers

Assembly Version: 1.0.5000.0

Win32 Version: 1.1.4322.573

CodeBase: file:///c:/windows/assembly/gac/custommarshalers/1.0.5000.0__b03f5f7f11d50a3a/custommarshalers.dll

\----


AxInterop.TomSawyer

Assembly Version: 5.5.0.0

Win32 Version: 5.5.0.0

CodeBase: file:///C:/Programme/VMware/VMware%20Virtual%20Infrastructure%20Client%202.0/AxInterop.TomSawyer.DLL

\----


Interop.TomSawyer

Assembly Version: 5.5.0.0

Win32 Version: 5.5.0.0

CodeBase: file:///C:/Programme/VMware/VMware%20Virtual%20Infrastructure%20Client%202.0/Interop.TomSawyer.DLL

\----


Accessibility

Assembly Version: 1.0.5000.0

Win32 Version: 1.1.4322.573

CodeBase: file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll

\----


AxInterop.QuickMksAxLib

Assembly Version: 1.0.0.0

Win32 Version: 1.0.0.0

CodeBase: file:///C:/Programme/VMware/VMware%20Virtual%20Infrastructure%20Client%202.0/AxInterop.QuickMksAxLib.DLL

\----


Interop.QuickMksAxLib

Assembly Version: 1.0.0.0

Win32 Version: 1.0.0.0

CodeBase: file:///C:/Programme/VMware/VMware%20Virtual%20Infrastructure%20Client%202.0/Interop.QuickMksAxLib.DLL

\----


\************** JIT Debugging **************

To enable just in time (JIT) debugging, the config file for this

application or machine (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the machine

rather than being handled by this dialog.

\----


thx for help

esx1 version: 3.0.1 32039

esx2 version: 3.0.1 32039

VIC version :2.0.1 and 2.0.0

0 Kudos
0 Replies