Replacing remote agent error

[James Mitchell]

ErrorMsg: AwE-9999 Internal error (6/9/25 3:54 PM) 
Details: AGENT activeUsage -1

Trying to setup new agent so I can do the bulk change but get this error? Is this a license error?

thanks,

Jim

[James Mitchell]

See this error too:

ErrorMsg: AwE-5126 Agent validation error (6/9/25 4:07 PM) 
Details: AGENT server.domain.edu/xxx.xxx.x.xxx 6021
AGENT server.domain.edu/xxx.xxx.x.xxx 6021

[James Mitchell]

This error too:

ErrorMsg: AwE-5126 Agent validation error (6/9/25 4:07 PM) 
Details: AGENT server.domain.edu/xxx.xxx.x.x 6021
AGENT server.domain.edu/xxx.xxx.x.xxx 6021

[Pat Richards]

what version of ApplicationsManager are you running ?

'AwE-5126 Agent validation error' typically occurs when remote agent processes are started but the agent is set as inactive in the automation engine.

I'm less certain of the 'AGENT activeUsage -1' message, but I think that gets thrown when 2 remote agents are setup with the same IP address

------------------------------
Cheers
Pat
------------------------------

[James Mitchell]

Version 9.5, got the new remote agent to start.  Like you mention might be a sequence thing but now I got that 

ErrorMsg: AwE-9999 Internal error (6/9/25 3:54 PM) 
Details: AGENT activeUsage -1

For a different agent?  I think this might be a licensed agent count exceeded warning?

[Pat Richards]

at v9.5 i'm not aware of any configuration setting that defines the licensed engine &/or agent counts 

prior to v9.3 there used to be a keyfile.ini that limited agent counts, but not anymore

------------------------------
Cheers
Pat
------------------------------

[James Mitchell]

In the RmiServer log there is some sort of wierd counter and if i add the new agent while other agents are RUNNING it throws an error:

RmiServer2506100706.log:07:25:18.924 rfp0: .JobStarter: activeUsage agent APPMANP 3
RmiServer2506100706.log:07:25:20.971 rfp0: .JobStarter: activeUsage agent APPMANP 2
RmiServer2506100706.log:07:25:32.362 rfp0: .JobStarter: activeUsage agent APPMANP 1
RmiServer2506100706.log:07:25:44.971 rfp0: .JobStarter: activeUsage agent APPMANP 0
RmiServer2506100706.log:07:26:01.58 rfp0: .JobStarter: activeUsage agent APPMANP 1
RmiServer2506100706.log:07:26:01.58 rfp0: .JobStarter: activeUsage agent APPMANP 2
RmiServer2506100706.log:07:26:01.78 rfp0: .JobStarter: activeUsage agent PROD 1
RmiServer2506100706.log:07:26:04.364 rfp0: .JobStarter: activeUsage agent APPMANP 1
RmiServer2506100706.log:07:26:05.452 rfp0: .JobStarter: activeUsage agent PROD 0
RmiServer2506100706.log:07:26:05.465 rfp0: .JobStarter: activeUsage agent PROD 1
RmiServer2506100706.log:07:26:12.684 rfp0: .JobStarter: activeUsage agent PROD 0
RmiServer2506100706.log:07:26:14.741 rfp0: .JobStarter: activeUsage agent PROD 1
RmiServer2506100706.log:07:26:22.219 rfp0: .JobStarter: activeUsage agent APPMANP 0
RmiServer2506100706.log:07:27:02.108 rfp0: .JobStarter: activeUsage agent PROD 2
RmiServer2506100706.log:07:27:02.108 rfp0: .JobStarter: activeUsage agent APPMANP 1
RmiServer2506100706.log:07:27:02.109 rfp0: .JobStarter: activeUsage agent APPMANP 2
RmiServer2506100706.log:07:27:05.419 rfp0: .JobStarter: activeUsage agent APPMANP 1
RmiServer2506100706.log:07:27:06.444 rfp0: .JobStarter: activeUsage agent PROD 1
RmiServer2506100706.log:07:27:08.492 rfp0: .JobStarter: activeUsage agent MCSQL-PRD00 -1
RmiServer2506100706.log:07:29:23.211 rfp0: .JobStarter: activeUsage agent APPMANP 0
RmiServer2506100706.log:07:30:01.45 rfp0: .JobStarter: activeUsage agent APPMANP 1
RmiServer2506100706.log:07:30:01.45 rfp0: .JobStarter: activeUsage agent APPMANP 2
RmiServer2506100706.log:07:30:01.47 rfp0: .JobStarter: activeUsage agent APPMANP 3
RmiServer2506100706.log:07:30:01.326 rfp0: .JobStarter: activeUsage agent APPMANP 4
RmiServer2506100706.log:07:30:01.372 rfp0: .JobStarter: activeUsage agent PROD 1
RmiServer2506100706.log:07:30:01.378 rfp0: .JobStarter: activeUsage agent PROD 2
RmiServer2506100706.log:07:30:01.382 rfp0: .JobStarter: activeUsage agent PROCMON-PRD00 1
RmiServer2506100706.log:07:30:02.455 rfp0: .JobStarter: activeUsage agent PROD 3
RmiServer2506100706.log:07:30:02.462 rfp0: .JobStarter: activeUsage agent APPMANP 5
RmiServer2506100706.log:07:30:02.462 rfp0: .JobStarter: activeUsage agent APPMANP 6
RmiServer2506100706.log:07:30:02.462 rfp0: .JobStarter: activeUsage agent APPMANP 7

[Pat Richards]

checking my notes i can see we had a similar message reported after introducing a new agent into the setup

ErrorMsg: AwE-9999 Internal error (08/02/2023, 18:35)

Details: OCIEXORAPR01N02 activeUsage -1

the issue was resolved by restarting the automation engine

------------------------------
Cheers
Pat
------------------------------

[James Mitchell]

Great. Thanks Pat!