VMware Communities: The operation is not allowed in the ...

VMware

Up to Discussions in vSphere Web Services SDK

Sample Code
Tech Exchange

vSphere Web Services SDK:

This Question is Not Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)

2 Replies Last post: Nov 10, 2009 1:12 AM by johndemic

The operation is not allowed in the current state posted: Nov 5, 2009 6:44 AM

johndemic

13 posts since
Mar 23, 2009

Hey All,

I'm executing the following SOAP request to determine the amount of tasks running on VirtualCenter:

<CreateCollectorForTasks xmlns="urn:vim2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<_this type="TaskManager">TaskManager</_this>
<filter>
<state>running</state>
</filter>
</CreateCollectorForTasks>

This works well, but under some circumstances (which appear load related) I occasionally get a response as follows:

"The operation is not allowed in the current state"

I've previously only seen this error when performing invalid operations on a VM, like trying to stop an already stopped server.

Does anyone have any ideas?

Thanls,
-jd

Re: The operation is not allowed in the current state

1. Nov 10, 2009 12:15 AM

in response to: johndemic

AngelaS

43 posts since
Sep 28, 2009

Hi,

Can you please elaborate more on "This works well, but under some circumstances which appear load related..."?

Are you performing any other tasks on the server parallely apart from retrieving the current running tasks?

Re: The operation is not allowed in the current state

2. Nov 10, 2009 1:12 AM

in response to: AngelaS

johndemic

13 posts since
Mar 23, 2009

Hey Angela,

The concurrent tasks are either clone or power on/off operations. So you understand my use case, I'm attempting to throttle requests to virtual center when there are more then X of these operations going on a the same time. My strategy is to use the CollectorForTasks to determine if its ok to issue a clone or power on/off operation. For instance, if the CollectorForTasks says there are more then 10 tasks currently running then I will wait for a certain period of time and try again, hoping that virtual center isn't as busy.

This approach is obviously flawed if the concurrent activity impacts task collection as well...

Any insight would be very much appreciated,
-jd

Go to original post