A specified parameter was not correct.

[daniellynn]

Does anyone know how to get more information out of these errors? I can use the stack trace to track it down to what function caused it, but I can't find any log or event that tells me which parameter was not correct or why. I've run into it a couple of times and I usually have to figure it out by process of elimination, but I've been beating my head against the wall for one of these for hours and I can't figure out what about the call it doesn't like.

Thanks for any help you may be able to provide.

[tos2k]

Hi!

My experience is that this error possibly also comes up in the Virtual Center task list, I am a little unsure here, but if, then you possibly can see more details there.

The main reason for these errors, in my opinion, is poor design of the VI SDK:

It is possible to create objects which need a (very) specific setup before these objects can be used. VMware does in many cases not specify very clearly what exactly a complete setup is.

So three rules following you will basically avoid these errors:

1) For a given object set all its properties to valid values

2) Do 1) for properties for all members of the object (recursive)

3) Know valid values for all properties of a object and its properties members

some samples of configuring more complex VI SDK objects here:

http://communities.vmware.com/message/1015081

http://communities.vmware.com/message/840108

So no, there is no easy way afaik to find out which parameter is wrong. In general, the message may hint you of one or more parameters not or wrong set.

Tos2k