cppagent icon indicating copy to clipboard operation
cppagent copied to clipboard

MTconnect agent service not getting start

Open coddddc opened this issue 3 years ago • 5 comments

i am trying to install agent . its installation getting completed but service is not getting created . how to create window service for the same . please help. service created only once after uninstalling is now no service is getting created .Please help

coddddc avatar Aug 23 '22 02:08 coddddc

Did you try from the command line:

agent install

That should create the service.

wsobel avatar Aug 23 '22 04:08 wsobel

i tried it but its not creating service . installation done successful . but on localhost:5000 its not showing anything . in services also no service is created . during first installation service was created successfully.

but after uninstall and again installing service is not getting created .

coddddc avatar Aug 23 '22 14:08 coddddc

This should install the Agent using Windows service controller.

sc.exe create mtconnect-agent binpath= "c:\mtconnect\agent.exe run c:\mtconnect\agent.cfg" DisplayName= "MTConnect Agent" start= auto

And you'll want to change the user that the service starts up to 'Network Service', not 'Local System', both for network access and to reduce the agent privilege on the system. And probably set to 'auto - delayed start'.

MRIIOT avatar Oct 03 '22 13:10 MRIIOT

sometimes you need to explicitly to run the install, 'agent install', as administrator to register it with the Windows Services. It does happen to some of our Windows too.

hulinning2 avatar Oct 03 '22 13:10 hulinning2

Did you run in an administrative console?

(Sent from mobile)

On Aug 23, 2022, at 07:15, coddddc @.***> wrote:

 i tried it but its not creating service . installation done successful . but on localhost:5000 its not showing anything . in services also no service is created . during first installation service was created successfully.

but after uninstall and again installing service is not getting created .

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

wsobel avatar Oct 11 '22 07:10 wsobel

Is this resolved?

wsobel avatar Dec 01 '22 22:12 wsobel

My issue is similar to this. The agent appears to install as a service but fails with a 1067 error. Worked with 1.8.0.3 but later versions than that.

markjmorrison avatar Apr 12 '23 20:04 markjmorrison

Hi Mark, what operating system version are you using? The more specifics will help me isolate the problem.

Also, any log files would be helpful.

Thanks, W

wsobel avatar Apr 12 '23 20:04 wsobel

Thank you for your quick reply.

The issue happens on several computers at work and my personal home computers. Some are running Windows 7 and other Windows 10.

The 1.x agent versions startup fine as services, but none of the 2.x ones startup (usually with a 1067 error). They seem to install fine from what I can tell. The registry information looks OK. I have attached the service log of the error. I will try to find some additional logs that may provide additional information.

Thanks Mark

On Wed, 12 Apr 2023 13:46:49 -0700, William Sobel @.***> wrote:    

Hi Mark, what operating system version are you using? The more specifics will help me isolate the problem.

Also, any log files would be helpful.

Thanks, W

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

markjmorrison avatar Apr 12 '23 22:04 markjmorrison

the event logs would be helpful. also any agent logs that were produced.

wsobel avatar Apr 12 '23 23:04 wsobel

It looks like the agent logs are not updated when the service fails to start, probably because the agent never really runs or does not run long enough to update the log file. Older versions of the agent (1.x) do update the log file when the service starts.

On Wed, 12 Apr 2023 16:31:09 -0700, William Sobel @.***> wrote:    

the event logs would be helpful. also any agent logs that were produced.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

markjmorrison avatar Apr 13 '23 03:04 markjmorrison

I Will close this issue if there is no further discussion.

wsobel avatar Aug 18 '23 07:08 wsobel

I do not have any more information on the problem and have given up. I will continue to use versions 1.x. You can close it out.

Thanks Mark

On Fri, 18 Aug 2023 00:12:42 -0700, William Sobel @.***> wrote:    

I Will close this issue if there is no further discussion.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

markjmorrison avatar Aug 18 '23 14:08 markjmorrison

Are there any company profiles running on your machine? Without more information I can't reproduce the issue.

wsobel avatar Aug 18 '23 14:08 wsobel

This problem was a minor inconvenience for me. I do not intend to pursue it any further. You can close it out.

On Fri, 18 Aug 2023 07:57:31 -0700, William Sobel @.***> wrote:    

Are there any company profiles running on your machine? Without more information I can't reproduce the issue.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

markjmorrison avatar Aug 18 '23 15:08 markjmorrison

Ok, I’ll close it. I would still like to understand the situation so I can avoid it in the future.

wsobel avatar Aug 18 '23 15:08 wsobel

Sorry about that. It happened on every computer I tried, but I could not obtain any useful log information on why.

Mark  

On Fri, 18 Aug 2023 08:48:53 -0700, William Sobel @.***> wrote:     Ok, I’ll close it. I would still like to understand the situation so I can avoid it in the future.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

markjmorrison avatar Aug 18 '23 15:08 markjmorrison

Thanks for trying. I’ll still make another go at reproducing. - W

wsobel avatar Aug 18 '23 15:08 wsobel