disable the button in the current state

Similar Questions

• vSphere HA is inside in vain. Operation is not allowed in the current state.

  Hello

  I'm testing vSphere HA with two hosts ESXi in my lab. I have a VM on each ESXi host and when I try to open HA by closing the port connection from the switch to one of the hosts, the cluster of vSphere tries to failover of the VM on the host failed to another host, but he is not successful.

  The events under the Cluster gives this warning:

  vSphere HA switched in vain < VM - > < Home > cluster < cluster name>. vSphere will try again if the maximum number of attempts has been exceeded. Reason: The operation is not allowed in the current state.

  Screenshot of the error is attached.

  I tried to restart the service of server vCenter and that did not help. What could be wrong here?

  Thank you.

  Shivani

  Hello adel.

  Do not disable the HA data store. If you have a physical server just power the server by pulling the power plug or just it crash. If you have virtual server vESXi, and then directly 'Power Off' there instead of the stop.

• Unable to connect to the MKS: the operation is not allowed in the current state

  Hi all

  After the upgrade of vmware tools, we have a problem while safeguarding a guest vm with avamar. VM freezes and he said; "Unable to connect to the MKS: the operation is not allowed in the current state.  It can be stopped only by killing the task in the service on the host esx console.

  VMware vCenter Server 5.1 - 5.1.U1b - 1235232

  2013 12-19 T 00: 49:15.146Z | vCPU-1 | W110: MONITOR PANIC: vcpu - 0:NOT_IMPLEMENTED devices/vide/iovmk/videVMK-vmkio.c:1492

  2013 12-19 T 00: 49:15.156Z | vCPU-1 | I120: Core dump with construction build-1065491

  2013 12-19 T 00: 49:15.156Z | vCPU-0 | I120: Exit vcpu-0

  2013 12-19 T 00: 49:15.156Z | vCPU-1 | W110: Writing monitor corefile "/ vmfs/volumes/4ff12f8d-9d4d7a89-9341-e4135bb796b4/TEADEV/vmmcores.gz".

  2013 12-19 T 00: 49:15.202Z | vCPU-1 | I120: Save the anonymous memory

  2013 12-19 T 00: 49:15.209Z | vCPU-1 | W110: Dumping core for vcpu-0

  2013 12-19 T 00: 49:15.209Z | vCPU-1 | I120: CoreDump: dumping core with superuser privileges

  2013 12-19 T 00: 49:15.209Z | vCPU-1 | I120: VMK battery for vcpu 0 is 0 x 412248155000

  2013 12-19 T 00: 49:15.209Z | vCPU-1 | I120: Start monitor coredump

  2013 12-19 T 00: 49:16.454Z | vCPU-1 | I120: End monitor coredump

  2013 12-19 T 00: 49:16.455Z | vCPU-1 | W110: Dumping core for vcpu-1

  2013 12-19 T 00: 49:16.455Z | vCPU-1 | I120: CoreDump: dumping core with superuser privileges

  2013 12-19 T 00: 49:16.455Z | vCPU-1 | I120: VMK battery for vcpu 1 is at 0x4122481d5000

  2013 12-19 T 00: 49:16.455Z | vCPU-1 | I120: Start monitor coredump

  2013 12-19 T 00: 49:17.420Z | vCPU-1 | I120: End monitor coredump

  2013 12-19 T 00: 49:17.421Z | vCPU-1 | W110: Dumping extended monitor data

  2013 12-19 T 00: 49:31.966Z | vCPU-1 | W110: A core file is available in "/ vmfs/volumes/4ff12f8d-9d4d7a89-9341-e4135bb796b4/TEADEV/vmx-zdump.000".

  2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120: Msg_Post: error

  2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120: fatal error [msg.log.error.unrecoverable] VMware ESX: (vcpu-1)

  2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120 + vcpu - 0:NOT_IMPLEMENTED devices/vide/iovmk/videVMK-vmkio.c:1492

  2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120: [msg.panic.haveLog], a log file is available in "/ vmfs/volumes/4ff12f8d-9d4d7a89-9341-e4135bb796b4/TEADEV/vmware.log".

  2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120: [msg.panic.requestSupport.withoutLog] you can ask support.

  2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120: [msg.panic.requestSupport.vmSupport.vmx86]

  2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120 + to collect data to be submitted to the technical support of VMware, run 'vm-support.

  2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120: [msg.panic.response] we will respond on the basis of your entitlement to support.

  We realized that the problem is our url filtering service checkpoint firewall. When we have disabled all begins to work very well.

• Error creating - snapshot operation is not allowed in the current state

  Hi all

  Using Veeam Backup & Recovery 6 software to replicate a LIVE VM (virtual MACHINE, 1). But I can't and I got the following error:

  Error creating - snapshot operation is not allowed in the current state

  The above virtual machine can only be copied when it is STOPPED the VM is running on ESXi 4.0.

  I have a more LIVE VM (virtual MACHINE, 2) on the ESXi Host which I was able to replicate successfully to another ESXi host.

  I contacted the Veeam Support before posting here.

  Things to note about VM 1: I can't take a snapshot manually from the vSphere client. This option is greyed (disabled) on VM1... While its OK on VM2.

  Veeam support told me that since its software uses the snapshot function of ESXi and this feature is disabled, replication cannot continue.

  Thanks for helping me on this.

  Exactly what I thought. When you delte this PCI passtrough your Backup Exec tape will not longer work.
  You will not be able to do replication when you use this passtrough.

  Only solution for replication (which is what I think you want for purposes of disaster) is to install a 3rd VM (or as physical) as "Backup Server" where you install Backup Exec and enable PCI-Passtrough to your tape drive. Then this new virtual machine with Backup Exec backup.

  After that you can delete the passtrough of your SBS and your replication will work.

  Sorry

  Concerning

  Simon

• The current state of the target is down and it displays red arrow down in OEM 12 c. But in fact the database is running

  Hi all

  my instance of database shows down in OEM 12 c but in fact the database is running and status of the listener is unknown. What steps should I take to make the database appear?

  FYI,.

  The error is:

  The current state of the target is down. (I checked events tab in the incident handler here, it is showing error as "inaccessible agent (reason = unable to connect to the agent to https://sunshine.mad:3872/emd/main / [connection refused]).") host is accessible.

  A week before I made switch to digital, the basics of data, is that this is the reason why it shows this error? do we need to change any configuration after switching to the databases on OEM 12 c. at this point time of the database instance shows down and the listener to the top but suddenly the database and listener went wrong.

  Please help me, give your suggestions in this regard.

  Verify that the agent is in place and suggested downloading like Antonio. For the target of the database, the home page, go to the (Oracle database > Configuration target >) Configuration of the analysis page, check the monitoring parameters are correct and do a test connection. You can check the parameters of surveillance for the target of the listener as well.

  Kind regards

  -Loc

• Game-CDDrive operation is not valid due to the current state of the object.

  It's been a while, please remind me how to put the code here? PSVersion 5.0.10105.0 VMWare PowerCLI AutoDeploy component 6.0 build 2358282 VMWare ImageBuilder PowerCLI component 6.0 build 2358282 license of VMware PowerCLI component 6.0 build 2315846 VMware vSphere PowerCLI component 6.0 build 2548068 VMware VDS PowerCLI component 6.0 build 2548068 Cloud of VMware Infrastructure Suite PowerCLI component 6.0 build 2548068 VMware HA PowerCLI component 6.0 build 2510422 VMware PowerCLI component Storage Management 6.0 build 2522368 trying to build a server from the ground using Powercli. Started with:

  $paramVM = @{

  VMHost =   $vmhost

  Version =   "v7"

      Name  =   "CompVM"

  Data store = $datastore

  DiskGB =   50

  DiskStorageFormat = "EagerZeroedThick"

  MemoryGB =   4

  NumCpu =   1

  Location =   $Folder

      CD  =   $true

  ResourcePool = $ResourcePool

  PortGroup = $portGroup

  Notes = "DC of DOM"

  Confirm =   $false

  }

  $paramVM . Location | select *

  New-VM @paramVM

  It seemed to go very well.

  Get-VM svr01mid100 | Start-VM

  Then, something isn't quite right.

  $paramNA = @{

  StartConnected =   $true

  WakeOnLan =   $true

  Connected =   $true

      Type  = « Vmxnet3 »

  Confirm =   $false

  }

  Get-VM chi01osm300 | Get-NetworkAdapter | Set-NetworkAdapter @paramNA

  , I get the error: Set-NetworkAdapter: 29/07/2015-18:44:36 Set-NetworkAdapter operation is not valid due to the current state of the object. Online: 9 char: 43 + Get - VM svr01mid100 | Get-NetworkAdapter | Together-NetworkAdapter @paramNA + ~ ~ ~ + CategoryInfo: NotSpecified: (:)) [game-NetworkAdapter], VimException + FullyQualifiedErrorId: Core_BaseCmdlet_UnknownError, VMware.VimAutomation.ViCore.Cmdlets.Commands.VirtualDevice.SetNetworkAdapter MacAddress: 00:10:56:ss:3f:ab WakeOnLanEnabled: true NetworkName: SameAsAbove Type: Vmxnet3 ParentId: VirtualMachine - vm - 108361 Parent: svr01mid100 Uid: /VIServer = Dom\[email protected]: 443/VirtualMachine = VirtualMachine-vm-108361/NetworkAdapter = 4000 / ConnectionState: logged, NoGuestControl, StartConnected ExtensionData: VMware.Vim.VirtualVmxnet3 Id: VirtualMachine-vm-108361/4000 name: NIC 1 Client: VMware.VimAutomation.ViCore.Impl.V1.VimClient )

  Get-VM svr01mid100 | Get-CDDrive | Select Name,IsoPath

  Name IsoPath - CD/DVD drive 1 C:\ PS > Get - VM svr01mid100 | Get-CDDrive. Game-CDDrive - IsoPath $isoPath - StartConnected $true - confirm: $false Set-CDDrive: 29/07/2015-18:50:39 Set-CDDrive operation is not valid due to the current state of the object. I disconnected and then reconnected my session. I tried to see what was going on in vCenter (which I never do) and I fount it tries to start with the ISO, but giving a frown face and reboot again. I think that he did not like something in the build of the server. Help!

  I don't know that I did it is clear enough. The new VM script seems to work, it creates a new virtual machine.

  But eventually, every setting change that I try to do on the virtual machine, I get an error stating that "the operation is not valid due to the current state of the object."

  It seems to take the configuration but then I noticed he tried to start, but it started getting the error that I put in the screenshot.

  To me, that shows that it is trying to boot from the CD, because it is a Windows error.  Moreover, he just trying to start several times.

  Now, I went back and I think that the error "operation is not valid due to the current state of the object" may have been the fact that the VM tried to boot from the CD over and over, this is what is meant by the current state.

  I noticed just here, the hosts have 4.1 on them, which does not support r2 Server 2012.

  I think we're good.  Thank you!

• "The operation is not allowed in the current state" message when you delete the folder

  I'm test ESXi 5.5 and mounted a datatsore of oriented export NFS in an attempt to redirect my ScratchConfig at this place. I found that I can create a folder in the datasore NFS fine but when I try to delete it, I get a message saying "the operation is not allowed in the current state. This happens on any of the files/sub-sub-sub-folders and only used account's root - I also confirmed that these directory drwxr-xr-x permissions.

  As suggested by KB1003829 which is a bit useful, but not really, I restarted the management on the host agents but it made no difference. Has anyone else seen elsewhere?

  I got this resolved, stumbling on the good guid for the NFS data store. Only after clicking around in WinSCP and realize that the NFS data store guid secondary, shorter - I then tried again to remove the original test directory and it worked.

  On a separate but similar note, then I tried to update my position zero config by applying this same guid with the command "vim - cmd hostsvc/advopt/updated updated ScratchConfig.ConfiguredScratchLocation string vmfs/volumes / [guid] / logs" (followed by a restart of the host) and it worked also.

• ERROR: New-Snapshot (the operation is not valid due to the current state of the object)

  Hello guys!

  I've been googlin everywhere, but impossible to find a solution to my problem. I hope that one of you, qualified people can point me in the right direction :)

  I created a powerCLI script to take a snapshot of our most important servers before we do our weekly maintenance. The idea to run the script as regular powershell script and then have

  1. Add snap-ins powercli and connect to virtualcenter servers
  2. ask the VC servers to virtual machines in a perticular folder
  3. Loop foreach on these servers to create a snapshot with the name $snapshotname

  Currently, I just do it turn on a test folder that I created in vSphere that contains 3 test VMs:

  • Testmagne1 - normal operation
  • Testmagne2 - I renamed the folder for this virtual machine in the data store to generate an error.
  • testmagne3 - normal operation

  Since the servers (not the test servers, but good ones) is the most important servers in our environment, I want to be able to catch exceptions and errors when I run this script. I do this with the Try - Catch - Finally works.

  The strange thing is:

  The release of Powershell/PowerCLI is different from the output in VirtualCenter (!)

  In virtualcenter, the output is as follows

  • Testmagne1 - snapshot is created successfully - as expected
  • Testmagne2 - the snapshot creation fails because it cannot find the files .vmx - as expected
  • Testmagne3 - snapshot is created successfully - as expected

  However, the exit in powercli is slightly different:

  • Testmagne1 - snapshot is created successfully - as expected
  • Testmagne2 - creation of the snapshot fails because it cannot find the files .vmx - as expected
  • Testmagne3 - snapshot fails with the error message: operation is not valid due to the current state of the object - huh?

  
  

  Apparently once the first error is generated all succeeding VMs get error "the operation is not valid due to the current state of the object"

  
  

  I've been pulling trying to figure this problem on my hair, but I'm not getting anywhere

  
  

  Here is some additional information:

  1. the Script (abridged version of it. It generates the same error):

  -STARTUP SCRIPT-

  $ErrorActionPreference = "stop".

  Add-PSSnapin VMware.VimAutomation.Vds, VMware.VimAutomation.Core | Out-Null

  SE connect-VIServer VIRTUALCENTER1, VIRTUALCENTER2 | Out-Null # Sensored VirtualCenter names

  $servers = get-VM-location 'testfolder '.

  $snapshotname = 'Testsnapshot '.

  $verifycreatesnapshot = Read-Host "you are about to create snapshots for $servers. Do you want to continue? o/n.

  If ($verifycreatesnapshot - eq 'y') {}

  Write-Host "snapshots of creation...". »

  {ForEach ($i in $servers)

  Write-Host "instant Creation for $i."

  Try {new-Snapshot - VM $i - name $snapshotname |} Out-Null}

  Catch {$_.exception | select *;} Write-Host "Unable to create the snapshot for $i" ;}

  }

  Write-Host "command finished.

  }

  else {Write-Host "Operation canceled by user"}

  Read-Host "end of the script. Press ENTER to close. "

  ------------------ END SCRIPT -------------------

  2. the PowerCli error messages:

  Error for Testmagne 2 (as expected):

  File: [DATASTORE114] testmagne2/testmagne2.vmx

  DynamicType:

  DynamicPropertyInternal:

  FaultCause:

  FaultMessage:

  ErrorId: Client20_TaskServiceImpl_CheckServerSideTaskUpdates_O

  perationFailed

  ErrorCategory: NotSpecified

  TargetObject:

  RecommendedAction:

  SessionId:

  ConnectionId: /VIServer = SENSORED: 443 /

  Severity: error

  Message: 31/10/2013-10:52:16 New-Snapshot the operat

  ion for the entity 'testmagne2' failed with the follo

  the wing's message: "file [DATASTORE114] testmagne2/testmagn".

  E2.vmx was not found.

  Data: {ParameterValues}

  InnerException: VMware.Vim.VimException: exploitation of the entity

  'testmagne2' failed with the following message: 'thread '.

  testmagne2/testmagne2.vmx e [DATASTORE114] was not crazy

  ND ".

  TargetSite:

  StackTrace:

  HelpLink:

  Source:

  Failed to create the snapshot for testmagne2

  Error for testmagne3:

  Creation of snapshot for testmagne3

  ErrorId: Core_BaseCmdlet_UnknownError

  ErrorCategory: NotSpecified

  TargetObject:

  RecommendedAction: An error occurred when executing command: new-Snapshot. I have check

  f exception for more details.

  SessionId:

  Login ID:

  Severity: error

  Message: 31/10/2013-10:52:17 instant New-capture operation is not

  valid due to the current state of the object.

  Data: {ParameterValues}

  InnerException : System.InvalidOperationException: operation is not valid from

  e to the current state of the object.

  at VMware.VimAutomation.ViCore.Impl.V1.Task.ViCoreTaskCo

  reServiceProviderImpl.BeginTaskCompletionPoll (list 1 taskLi

  St)

  at VMware.VimAutomation.Sdk.Impl.V1.Task.CoreTaskService

  Impl.WaitForTask (IEnumerable 1 taskList, ProgressCallback p

  rogressCallback)

  at VMware.VimAutomation.Sdk.Util10Ps.BaseCmdlet.BaseCmdl

  and. EndProcessingErrorHandled()

  at VMware.VimAutomation.ViCore.Util10Ps.BaseCmdlet.BaseC

  mdlet. EndProcessingErrorHandled()

  TargetSite: Sub ThrowTerminatingError (System.Management.Automation.Err

  orRecord)

  StackTrace: At System.Management.Automation.MshCommandRuntime.ThrowT

  erminatingError (ErrorRecord errorRecord)

  HelpLink:

  Source: System.Management.Automation

  Failed to create the snapshot for testmagne3

  3 PowerCLI version

  PowerCLI Version

  ----------------

  VMware vSphere PowerCLI 5.5 Release 1 build 1295336

  ---------------

  Versions of the snap

  ---------------

  VMWare AutoDeploy PowerCLI component 5.5 build 1262826

  VMWare ImageBuilder PowerCLI component 5.5 build 1262826

  License of VMware PowerCLI component 5.5 build 1265954

  VDS's VMware PowerCLI component 5.5 build 1295334

  VMware vSphere PowerCLI component 5.5 build 1295334

  
  

  4 VirtualCenter version

  VMware vCenter Server Version 5.0.0 Build 913577

  vSphere Client Version 5.0.0 Build 913577

  Hosts: VMware ESXi 5.0.0 Build 914586

  If you need additional information, let me know

  Any help is greatly appreciated

  Thank you!

  -Loincloth

  
  

  
  

  Definition - ErrorAction Stop locally on the cmdlet will not solve the problem. We have found and solved the problem and the fix will be available in the next version. Until then, you can use the $error variable to detect whether the cmdlet was successful or not. You can clear the $error variable before calling the cmdlet and check if it's still empty after the call.

• With Move-VM error: operation is not valid due to the current state of the object.

  I only started shows after update to PowerCLI v5.1.  My vCenter is v5.0.  I saw this when moving virtual machines to a data store in a different data store cluster.  The task submits to vCenter successfully and ends, but the Move-VM errors and returns control to the script or command line that ran.

  $> Move-VM - VM somevm Datastore - somedatastore - confirm: $false
  Move-VM: 13/11/2012-16:07:45 operation Move-VM is not valid due to the current state of the object.
  On line: 1 char: 1
  + Move-VM VM - somevm - data somedatastore store - confirm: $false
  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  + CategoryInfo: NotSpecified: (:)) [Move-VM], VimException)
  + FullyQualifiedErrorId: Core_BaseCmdlet_UnknownError, VMware.VimAutomation.ViCore.Cmdlets.Commands.MoveVM

  I'm puzzled.

  Do you by chance have a PowerShell v2 available somewhere where you can run the same script?

  As much as I know there no official PS still in PowerCLI v3 support, although there are only a few known minor pitfalls.

  While clutching at straws

• Together-NetworkAdapter returning to "operation is not valid due to the current state of the object"

  I'm using fix - up all-NIC in the host servers when a portgroup is renamed.  Demand seems to make the required changes, then crashses.  I don't see any errors in the list recent tasks in vCenter.

  I use the following code:

  Get-VMHost vmware.host | Get - VM | Get-NetworkAdapter | Where {$_.NetworkName - eq "ancien_nom"} |  Together-NetworkAdapter - NetworkName "newname" - confirm: $false
  The error is:
  Together-NetworkAdapter: 17/10/2012 12:16:56 game-card network Operation is not valid due to the current

  State of the object.

  At line: 1 char: 114

  {"+... ancien_nom"} |  Together-NetworkAdapter - NetworkName "newname" - confirm: $false

  +                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: NotSpecified: (:)) [game-NetworkAdapter], VimException)

  + FullyQualifiedErrorId: Core_BaseCmdlet_UnknownError, VMware.VimAutomation.ViCore.Cmdlets.Commands.VirtualDevice.

  SetNetworkAdapter
  It's using PowerCLI 5.1 Release 1 against vCenter 5.0 and 5.0 ESXi.
  Any ideas how or tell you why it's a failure or repair.
  Thank you
  Iain

  No, you should not be a problem.

  Are you by chance using PowerGui?

  There were references to the exact same message when you use an older version of PowerGui and the PowerPack.

  See New - VM error (operation is not valid due to the current state of the object.)

• vmrun start leads to a "error: operation failed because of the current state of the system.

  Hello

  I am running the vmrun like this on the console command.

  / usr/bin/vmrun t CR h https://ourhost/sdk u ouruser Pei ourpwd start ' build001/build001.vmx [datastorename] '.

  I get the error text:

  Error: The operation has failed because of the current state of the system
  

  When I opened the Vsphere client, I see that the operation began, but also with an error: the operation is not allowed in the current state.

  I'm running on VMWare Vsphere Server Version 4.1.0 Build 258902

  How can I make sure via command line that the State of the system is correct. Is there a way to get corrected through an order status?

  When I try to power to the top of the image within the user interface, it works, but I need to know the opposite effect.

  Thank you.

  Hello and welcome to the forums.

  check via the State of the line of command of this virtual machine if necessary, unblock the process using vmsuport x how to show in this http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004340 Ko

• How to disable the current point when validate trigger

  Hi all
  I want to disable the current text point when validate trigger.

  Generally, we rely on WHEN-VALIDATE when the cursor leaves a field. In this case, because the cursor leaves the ground, why are you trying to turn it off at this point? The other time would be during the validation process. In this case, you should be able to disable during the WE-COMMIT or in a VALIDATION KEY.

  I guess if we understood better what you want to accomplish and why you want to do, we could offer something more useful.

• OracleDataReader: Operation is not valid due to the current state of the object

  Hi all
  
  I am new to using libraries and oracle development tools. I have a project in vb 2010 began when I use the oracleDataReader to read data from my db (10g). by using the following code:
  
  Oradb As String = "xxxxxxxxxxx".
  Dim conn As New OracleConnection (oradb)
  Conn. Open()
  
  Dim test (1000) As String
  Dim counter As Integer = 0
  Dim cmd As New OracleCommand
  
  Connection group conn cmd.
  cmd.CommandText = "table FROM SELECT column where otherColumn > 21 June 11 '.
  cmd.CommandType = CommandType.Text
  Var as OracleDataReader dr = cmd. ExecuteReader()
  Dr. Read()
  test (Counter) = Dr. GetString (0)
  While Dr. Read()
  test (Counter) = Dr. GetString (0)
  Counter = counter + 1
  Loop
  
  cmd ExecuteReader().
  cmd.CommandText = "SELECT FROM table where otherColumn > 21 June NewColumn 11'"
  Dr. Read()
  test (Counter) = Dr. GetString (0)
  
  
  How could change the cmd.CommandText to run new queries? As it is the second command dr.read throws the following error: "operation is not valid due to the current state of the object.
  
  I found stating an another OracleDataReader object will allow me to run another query, I guess that there is a better way to "reset" State of the object first, as opposed to the creation of any new object each time I need to reset the command text.
  
  
  Any ideas are greatly appreciated. Do not forget that I am new to coding, so I know the real C could be cleaned.
  
  Thank you

  ...
  cmd.CommandText = ""
  dr = cmd.ExecuteReader()
  dr.Read()
  ... etc ...
  

  It will be useful,
  Greg

• disable the current record...

  How to disable the current record in the table?
  
  My tables 5 records. If my cursor in the first record, I would like to make some calculations and disable it (current record) but other text fields (4 documents) should be the mode.
  
  I used set_item_property it disable all records...
  
  How to do this?
  
  Thank you...
  
  Published by: skud on July 15, 2011 18:36

  Use set_item_instance_property instead of set_item_property and disable insert and update enabled property of all points for example blocks

  If: system.cursor_record = '1' then
  set_item_instance_property ('TEXT_ITEM1', current_record, insert_allowed, property_off);
  set_item_instance_property ('TEXT_ITEM1', current_record, update_allowed, property_off);
  set_item_instance_property ('TEXT_ITEM1', current_record, NAVIGABLE, property_off);
  end if;

• How to get the current state of the son process

  Hello
  
  If I know that the instance id of a child process.
  How can I get the current state of the child (e.g., completed, running, etc.) process in the code "PBL"?
  
  Thank you in advance.

  Hello

  Here's a way to display the status of children sub-process engendered by a process parent process creation activity. In this sense, the process id of the subprocedure is "ChildProcess. The id of the activity of creating processes in the parent process that causes the work item instance in the child process called 'SpawnChildren '. This logic is performed from inside the process parent in an activity downstream process creation activity, called "SpawnChildren".

  Display statements have been added just to see you return values (do) their leash not when going into production.

  display "Children: " + children + "\nKeys: " + children.keys + "\nLength: " + length(children) +
  "\nInstance id of child: [" + children["SpawnChildren"] + "]"
  
  if children["SpawnChildren"] = null or children["SpawnChildren"] = "" then
       display "Child is completed"
  else
  
       bp as BusinessProcess
  
       connectTo bp
                       using url = Fuego.Server.directoryURL,
                           user = "test",
                           password = "test",
                           process = "/ChildProcess"
  
       instance as Fuego.Papi.Instance
       instance = getInstance(bp, instance : children["SpawnChildren"])
       logMessage "run Instance: " + instance.id
                        using severity = DEBUG
  
       display "Status: " + instance.status + "; inside the child process in the activity: " + instance.activityName
  
       disconnectFrom bp
  end
  

  I downloaded the project I used this in to http://www.4shared.com/file/130890113/2d825960/ChildrenOfaParent.html.

  Hope this helps,
  Dan