1.16 Troubleshooting
-2005
PROPHANDLING_NO_
MODIFY_SIZE_RIGHTS
-2006
PROPHANDLING
_INCOMPATIBLE_
COMPONENTS
-2008
PROPHANDLING
_UNSUPPORTED_
PARAMETER
-2009
PROPHANDLING_SIZE_
MISMATCH
-2010
PROPHANDLING_
IMPLEMENTATION_
MISSING
-2011
PROPHANDLING
_ACCESSTOKEN_
CREATION_FAILED
MATRIX VISION GmbH
The caller can't modify the
size of this component.
The two involved compo-
nents are not compatible.
One or more of the speci-
fied parameters are not sup-
ported by the function.
Different sized value buffers
have been passed.
A feature that is not imple-
mented so far has been re-
quested.
An
access
token
object
couldn't be created.
It has been tried to mod-
ify the size of this list or
the number of values stored
by a property, but the caller
doesn't have the required
right to do this.
This er-
ror will also be reported if
the user tried to increase the
number of values handled by
a property above the maxi-
mum number of values it can
handle. Therefore before re-
sizing a property check if
the new size might exceeds
this maximum value by call-
ing the appropriate function.
[-2005]
An operation requiring two
compatible components has
been called with two compo-
nents, which are not compat-
ible.
[-2006]
This error might also be gen-
erated if a certain feature is
not available on the current
platform.
[-2008]
While trying to read value
pairs the caller passed two
different sized value buffers
to a function while one is too
small to hold all the informa-
tion.
[-2009]
The caller requested a fea-
ture, that hasn't been im-
plemented so far. This er-
ror code is only provided for
compatibility and will be set
in very rare cases only.
[-2010]
This can either happen, be-
cause the caller has not the
rights required to create an
access token or because the
system runs very low on
memory.
DeprecatedThis
error code currently is not
used anywhere within this
framework. It might be re-
moved in a future version.
[-2011]
93
Need help?
Do you have a question about the MATRIX VISION mvBlueNAOS and is the answer not in the manual?