No associated window can be found for process

[Vanessa Keal]

I know this has been asked before but I have just installed an agent and service manager on a Windows server and am seeing the following in the Service Manager log files when trying to start the agent from the Service Manager Dialog on my Automation Engine server:

0200325/122926.531 - U00022019 Client statement: process '699EBDD' should be started.

20200325/122926.531 - U00022031 Client data: User 'U19722367\kealv' of computer 'U19722367'.

20200325/122926.531 - U00022004 Starting process '699EBDD' ...

20200325/122926.531 - U00022005 ... with command line  'D:\Program Files\Automic\ServiceManager\bin\UCYBSMgr.exe'.

20200325/122926.531 - U00022006 ... and start directory  'D:\Program Files\Automic\Agents\windows\bin'.

20200325/122926.531 - U00022007 Process '699EBDD' (ID '11576') successfully started.

20200325/122926.531 - U00022023 No associated window can be found for process '699EBDD'.

20200325/122932.030 - U00022012 Process '699EBDD' (ID '11576') ended.

20200325/122932.030 - U00022022 Process '699EBDD' ended, exit code='0'.

I have searched the Broadcom Knowledgebase and found the following:
https://knowledge.broadcom.com/external/article?articleId=89208&_ga=2.243221707.854271590.1584991034-1559129228.1583254019

Resolution

 The "No associated windows" error with exit code 66 usually has one of these options as a solution:
    
 1. The log files are locked (this happens with Windows operating systems where it will keep a log file locked for some reason). Try deleting the log files in the \Temp directory the Agent (DO NOT restore them from the recycle bin afterwards).  If necessary, add write and modify permissions for the user starting the Agent for the temp directory.
  
 2.  The other option is click the link below and make the changes in the Microsoft Windows registry and in user rights management, as described on the Microsoft site -   http://support.microsoft.com/default.aspx?scid=kb;en-us;184802 .

3. Check the Agent´s ini file if there is an character before the [GLOBAL] section. If so, delete it

4. Check the WP logs for any messages saying something like "Could not find the specified ini file". This might indicate an issue with the name of the ini file. 

I have tried all of the resolutions, except the link to Microsoft which no longer works, and nothing has solved the problem.
I adjusted the user permissions for all folders under Automic on the server where the agent and service manager are installed.
There are no characters in front of the [GLOBAL] section in the agent ini file.
The WP logs make no mention of problems in the specified ini file.

We are running version 12.3.2 for the automation engine and agent.
The agent is installed on Windows Server 2019 Standard.

Does anyone have any other recommendations or suggestions to resolve this problem?

Thanks,
Vanessa

------------------------------
Vanessa Keal
Senior Automation Solution Architect
A&I Solutions
------------------------------

[Michael Pirson]

Hey Vanessa,

From the looks of the log it seems you are trying to start the service manager exe and not the Agent.

20200325/122926.531 - U00022005 ... with command line  'D:\Program Files\Automic\ServiceManager\bin\UCYBSMgr.exe'.

20200325/122926.531 - U00022006 ... and start directory  'D:\Program Files\Automic\Agents\windows\bin'.


I would expect this to read:

U00022005 ... with command line  'D:\Program Files\Automic\Agents\windows\bin\UCXJWX6.exe'
U00022006 ... and start directory  'D:\Program Files\Automic\Agents\windows\bin'.

[Carlos Cardano]

Hello Vanessa,

I think you have just missed the INI file of the agent.
The command should be something like this:

20200325/122926.531 - U00022005 ... with command line ''D:\Program Files\Automic\Agents\windows\bin\ucxjwx6.exe -I<agent ini file>.INI'.

You may want to double check your uc4.smd files for correct settings.

------------------------------
Regards,
Carlos
------------------------------

[kay.koll]

Hi Vanessa,
the error message typically indicates that one of the Microsoft Visual C++ 2010 Redistributable,  2013 Redistributable, 2017 Redistributable Packages are missing on your Windows system.
You find it in the External.Resources folder of the Automic installation set.
Regards
Kay

------------------------------
Sr. Solution Architect
Broadcom
------------------------------

[Frederic BERGERON]

Maybe or maybe not.....

[Frederic BERGERON]

Check that you have the same version of java on the agent side and the server side.

Support took two months to find that.... It was for a Rapid Automation agent but you can still check and test it for free.

[Frank Muffke]

Hi

For a plain WIN agent theres no java needed :-)

cheers, Wolfgang

------------------------------
Support Info:
if you are using one of the latest version of UC4 / AWA / One Automation please get in contact with Support to open a ticket.
Otherwise update/upgrade your system and check if the problem still exists.
------------------------------

[Carsten Schmitz]

Here's that old Microsoft KB article:

https://web.archive.org/web/20120525061608/http://support.microsoft.com/default.aspx?scid=kb;en-us;184802

hth,

[Vanessa Keal]

The problem was in the smd file.  The path to the agent has been corrected and now the agent is being started and stopped correctly from AWI and the Service Manager Dialog.
Thank you all for the responses!
Vanessa

------------------------------
Vanessa Keal
Senior Automation Solution Architect
A&I Solutions
------------------------------