Unimplemented command 'setting'

Content Authoring
1

(imported topic written by SystemAdmin)

hi,

i want to write a custom setting on my BESClient

setting “HDDDrivelockState” = “{now}” on “{now}” for client

I get following error:

STATUS: Running action…

Command failed (Unimplemented command ‘setting’.) setting “HDDDrivelockState” = “{now}” on “{now}” for client

  • Result —

Evaluation failed!

Earlier this always works fine.

Where is the problem now??

Please for help.

Andi

2

(imported comment written by Lee Wei)

Some ActionScript commands cannot be run from the Fixlet Debugger.

Just run it from an actual Fixlet and it will work correctly.

3

(imported comment written by SystemAdmin)

I test it again and i get this error:

Fixlet Action:

setting “HDDDrivelockState”="{now}" on “{now}” for client

Message Console:

Failed setting “HDDDrivelockState”="{now}" on “{now}” for client

Logfile on Client:

Command failed (Error writing setting to registry) setting “HDDDrivelockState”=“Mon, 17 Sep 2012 07:48:49 +0200” on “Mon, 17 Sep 2012 07:48:49 +0200” for client (fixlet 48795)

Thanks Andi

4

(imported comment written by SystemAdmin)

hi Lee Wei.

do you have an idea, why I get these error?

Thanks Andi

5

(imported comment written by Lee Wei)

Looks like spaces before and after the equal sign “=” causes problems.

Here is an export of a Task that works for me.

If this does not work for you, at least we know that it is environmental rather than the code.

Lee Wei

6

(imported comment written by SystemAdmin)

hi,

i test your fixlet, but I get the same error.

Andi

7

(imported comment written by Lee Wei)

Looks like the problem is not with the ActionScript statement, but something with the endpoint.

You should probably try this on different endpoints. Maybe call tech support to help verify the environment in terms of component versions etc.