GSX2: won't activate PUSHBACK

[crauds]

Capt Sim B727 FSX SP2 YMHB at stand 12 default AFCAD.  After full preflight, fuel load, crew and passenger load, requesting push/departure is acknowledged:  "departure clearance requested" and then nothing.  No action nor further message.  Position is set to pushback: "both" setting.  Pushback truck and all appear as they should prior to pushback but nothing happens.  I kept pushing the request in GSX and one time it came back saying:  "handled by Virgin  Australia" but then again nothing happened.  The option to select departure continues to appear in the menu (CTL-F12) and it is acknowledged each time I select it.  Checked the forum and can't find a similar problem addressed. 

The log file shows:

Error: exception DATA_ERROR in call SetDataOnSimObject param #1 '124294432'
{'Airport': 'YMHB', 'Requested assistance services at': 'Gate 12', 'User Pos': (-42.83759168296309, 147.50651942387458, 7.38178 m, 3.41978 m, 222.9407970498834)}

Is this just a random glitch or is this indicating a wrong setting or problem with the AFCAD.  I have used this AFCAD and position before with GSX1 and never had an issue. 

It seems I have no other choice but to restart FSX and try everything again.  Any ideas as to the cause?

Craig

[crauds]

Reloaded FSX and tried same situation again and this time had no problems.  Not sure what caused the issue the first time.  It might just have been an FSX'ism!
Hopefully it was a one time occurrence.  I had loaded passengers twice on my first attempt.  This is an airport without jetways but in reality doesn't use a bus since aircraft are parked close to terminal.  I discovered that passenger simulation is not available in that case.  So I restarted COUATI after removing "disable bus" setting.  I then requested boarding again and was able to observe simulated passengers (quite impressive!) departing bus and boarding the plane.  Perhaps it was this double request that caused the glitch in GSX2.  But issue is RESOLVED for now.

Craig

[virtuali]

Yes, a double request made shortly after the first one might cause such problems. Simconnect is a client-server communication channel (like a network) and it's shared by all applications, so it's possible sometimes to be affected by internal lag, especially with many installed addons that use Simconnect as well.