Automic Workload Automation

  • Private Community
Back to discussions
Expand all | Collapse all

Anyone run into this issue before?

  • 1.  Anyone run into this issue before?

    Posted May 20, 2015 10:29 AM
    Hi All,

    After installing the service manager and windows agent to a group of servers, I went to start the agent manually and it wouldn't start up. I checked the log for it and it's saying

    "20150520/095751.601 - U0022007 Process 'WINDOWS' (ID '4940') successfully started.
    20150520/095751.679 - U0022023 No associated window can be found for process 'WINDOWS'.
    20150520/095751.679 - U0022012 Process 'WINDOWS' (ID '4940') ended.
    20150520/095751.679 - U0022022 Process 'WINDOWS' ended, exit code='66'."

    for reference, "WINDOWS" is what I'm naming my agent. It starts the process off fine but then has some sort of issue I've never seen before (the No associate window can be found..." error and then closes the process.

    So I've copied the files exactly from another server which is working (making sure to tweak the config file for the windows agent), all the directory paths are good and I've tried uninstalling the service manager, rebooting the server and re-installing the service manager/agent hasn't helped at all.

    It seems like it's a windows error, but I've never seen it before, wondering if anyone here has?



  • 2.  Anyone run into this issue before?

    Posted May 20, 2015 11:25 AM
    Hi Bertie,

    I have run into this several times. Yes, it's a Windows error and you can search on their kbase for that.

    Other option is to delete all files from the temp directory from the agent and smgr and restart the service. It normally works for me.



  • 3.  Anyone run into this issue before?

    Posted May 20, 2015 12:29 PM

    I don't know if this experience is related, but it might be if you are re-using any agent names.

    I recently upgraded some Windows2003 servers to Windows2012 servers, and I discovered that in order for the new windows agent to work, I had to go into client 0000 and delete the HOST entry for that agent in order to force it to refresh itself with the correct type of windows agent information.



  • 4.  Anyone run into this issue before?

    Posted May 20, 2015 04:10 PM
    Hi Simone,

    I have actually completely removed the entire UC4 directory for both the Service Manager and the Windows Agent and then removed all trace of UC4 from the server and re-installed it completely but it still gives me that same error which doesn't make sense, it's essentially a blank slate for the server but it's getting the same issue. Unless there are temp files somewhere else that are causing this issue? but it should just be in bin/../temp, right?

    Hi Pete,

    For many of these servers, they don't exist in the client at all, yet, since they've never had UC4 on them before so I'm not sure these are related, but thank you anyway!


  • 5.  Anyone run into this issue before?

    Posted May 20, 2015 04:40 PM
    So now it's saying this:
    20150520/163905.352 - U0022004 Starting process 'WINDOWS' ...
    20150520/163905.352 - U0022005 ... with command line  'D:\uc4\ServiceManager\bin\..\..\Agents\windows\bin\UCXJWI3.EXE'.
    20150520/163905.352 - U0022006 ... and start directory  'D:\uc4\ServiceManager\bin\..\..\Agents\windows\bin'.
    20150520/163905.352 - U0022007 Process 'WINDOWS' (ID '6104') successfully started.
    20150520/163905.617 -          Window: Hnd=00380078, Title='UC4 Agent [FP015.WIN]'
    20150520/163907.929 - U0022012 Process 'WINDOWS' (ID '6104') ended.
    20150520/163907.929 - U0022022 Process 'WINDOWS' ended, exit code='0'.



  • 6.  Anyone run into this issue before?

    Posted May 21, 2015 10:26 AM
    I figured it out!

    It was actually a combination of the original install being corrupted (didn't bring in all the shared DLLs it was meant to) and what petwir was saying, so I got it to work!

    Thanks everyone!


  • 7.  Anyone run into this issue before?

    Posted Jan 04, 2017 03:07 PM
    Not meaning to necro this thread, but I experienced this issue as well.

    I found that if you are trying to start the agent with Log On As designated as any user other than Local System, the error will occur if the designated user does not have permissions for the Automic install directory.

    This would be the case if you installed to C:\


    Hope that helps!


  • 8.  Anyone run into this issue before?

    Posted Jan 18, 2018 07:05 AM
    Thread necroing FTW  :)

    I had the same problem. In my case, it was simply an already running Windows agent process that had lost it's attachment to smgr. Killed it with task manager, agent restarts fine.


  • 9.  Re: Anyone run into this issue before?

    Posted Nov 20, 2018 10:30 AM

    Hi, I've got the same error when trying to start the process via service manager, but using a different user than the local admin and this other user had only read access.

    Giving modify permission to the whole installation structure was enough to solve.

    Cheers.



  • 10.  Re: Anyone run into this issue before?

    Broadcom Employee
    Posted Dec 28, 2018 07:59 PM

    There can always be an underlying problem. The easiest way is to start the Windows agent through command line and maybe then we'll get  a meaningful error message that is not passed through to the parent process (Service Manager).



  • 11.  RE: Re: Anyone run into this issue before?

    Posted Jul 21, 2020 11:14 AM
    Hi,

    I have the same problem but I try to start it from the services manager, I have configured a server-proxy and the log I get when I execute it is the following


    -------------------------------------------------------------------------------------------------------------------
    20200721/100316.004 - U00022012 Process 'UC4 SERVER-PROXY' (ID '2504') ended.
    20200721/100316.004 - U00022022 Process 'UC4 SERVER-PROXY' ended, exit code='1'.
    20200721/100458.815 - U00022019 Client statement: process 'UC4 SERVER-PROXY' should be started.
    20200721/100458.815 - U00022031 Client data: User 'DEVOPS\johnny.castro' of computer 'SRVRA55EXEC'.
    20200721/100458.815 - U00022004 Starting process 'UC4 SERVER-PROXY' ...
    20200721/100458.815 - U00022005 ... with command line 'java -cp proxy.jar com.uc4.proxy.Server -keyStore="C:\Automic\Proxy\bin\keystore.jks" -keyStorePwd=--1073E169C0ABA5642F -servicePort=4321 C:\Automic\ServiceManager\bin\..\..\Proxy\bin\proxy.jar'.
    20200721/100458.815 - U00022006 ... and start directory 'C:\Automic\ServiceManager\bin\..\..\Proxy\bin'.
    20200721/100458.816 - U00022007 Process 'UC4 SERVER-PROXY' (ID '4356') successfully started.
    20200721/100518.818 - U00022023 No associated window can be found for process 'UC4 SERVER-PROXY'.
    20200721/100518.818 - U00022012 Process 'UC4 SERVER-PROXY' (ID '4356') ended.
    20200721/100518.818 - U00022022 Process 'UC4 SERVER-PROXY' ended, exit code='1'.
    -----------------------------------------------------------------------------------------------------------------------------

    Running it from the CMD console does not generate any errors and the agent proxy client conected correctly, 

    I've searched several forums on this same problem

    https://knowledge.broadcom.com/external/article/89267/u0022023-no-associated-window-can-be-fou.html
    https://community.broadcom.com/communities/community-home/digestviewer/viewthread?MID=784200

    Right here, but none of that works.


    Could you please help me? thanks


    ------------------------------
    Software Architecture, Computer Engineer
    N.A
    ------------------------------

    Original Message


  • 12.  RE: Re: Anyone run into this issue before?

    Posted Jul 31, 2021 06:57 AM
    Hi
    Realize its over a year since your post but still.....
    I had the same problem when I tried to restart service manager:
    More of a workaround than a fix, but seems to work.

    20210728/141740.100 - U00022004 Starting process 'UC4 JCP' ...
    20210728/141740.100 - U00022005 ... with command line 'java -Xrs -Xmx2G -jar ucsrvjp.jar -Ic:\Automic\ServiceManager\bin\..\..\AutomationEngine\bin\ucsrv.ini -svc%port% -rest'.
    20210728/141740.100 - U00022006 ... and start directory 'c:\Automic\ServiceManager\bin\..\..\AutomationEngine\bin'.
    20210728/141740.108 - U00022007 Process 'UC4 JCP' (ID '8692') successfully started.
    20210728/141800.114 - U00022023 No associated window can be found for process 'UC4 JCP'.
    20210728/141801.320 - U00022012 Process 'UC4 JCP' (ID '8692') ended.
    20210728/141801.320 - U00022022 Process 'UC4 JCP' ended, exit code='1'.

    This article came up when I Googled "U00022023 No associated window can be found for process 'UC4 JCP'"
    https://knowledge.broadcom.com/external/article/112156/u00022023-no-associated-window-can-be-fo.html

    Which talks about java binary paths.

    When I checked I had java processes hanging around after I had shut everything down.

    C:\windows\system32>tasklist /fi "imagename eq java.exe"

    Image Name PID Session Name Session# Mem Usage
    ========================= ======== ================ =========== ============
    java.exe 6612 Services 0 230,432 K
    java.exe 6988 Services 0 375,296 K
    java.exe 3208 Services 0 89,560 K
    java.exe 1864 Services 0 183,880 K

    I killed these off, and then was able to restart everything without problem.

    C:\windows\system32>taskkill /F /pid 6988 etc




    Original Message