PSExec on Vista VM : Initialization of tree component failed

[Buildboy]

Hi All,
I am trying to start the build file remotly on a Windows Vista Enterprise VM running on the VMWare server 1.4 and encountring the following error.
Also Running VB Pro 6.6 on the VM, host executing the command is running VB Pro 6.3
Any help is greatly appreciated :)

from the event viewer:

Log Name: Application
Source: Visual Build Professional
Date: 10/25/2007 4:53:43 PM
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: VISTA_ENT_QA
Description:
Initialization of tree component failed.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Visual Build Professional" />
<EventID Qualifiers="49152">1</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2007-10-25T22:53:43.000Z" />
<EventRecordID>453</EventRecordID>
<Channel>Application</Channel>
<Computer>VISTA_ENT_QA</Computer>
<Security />
</System>
<EventData>
<Data>Initialization of tree component failed.</Data>
</EventData>
</Event>

[kinook]

Please send the details requested at http://www.kinook.com/Forum/showthread.php?threadid=3044. Thanks.

[Buildboy]

Hi,
I have sent out the information per your request to the support email address
Thank you :)

[kinook]

We were able to reproduce this problem on Windows Vista running as a guest inside VMWare or Virtual PC. VBP is acting as if it does not have full interactive access to the desktop in order to initialize and display its GUI. The problem is not specific to VBP -- any GUI application is affected (for instance, try psexec -i \\xyz write [or notepad, regedit, calc, etc.]). Apparently a bug or limitation in Windows and/or psExec is resulting in this behavior. The problem may only occur when Vista is running in non-Aero Glass mode -- see http://forum.sysinternals.com/forum_posts.asp?TID=12560.

A couple of workarounds:

1) Running it in the system account (check the 'Run in System account' checkbox on the Remote tab of the VisBuildPro Project or Run Program actions, or use the -s psExec flag if calling directly) does work in our tests

2) Running the console app (VisBuildCmd.exe) instead of the GUI app (VisBuildPro.exe) also works (console apps don't need interactive desktop access).