-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot get PSService to run on Windows Server 2019 #29
Comments
I just tried it on a Windows Server 2019, and it works fine. |
Hi,
Thanks for your response.
I am administrator on the server and domain admin on the network.
The same piece of code works on a 2012 R2 Server (6.3.9600) but not on a Server 2019 Standard (10.0.17763).
I get this message when starting it.
***@***.***D73130.C7BDB990]
Rick Foster
Data Manager
520-225-6309
Tucson Unified School District
From: JFLarvoire ***@***.***>
Sent: Friday, April 9, 2021 3:43 AM
To: JFLarvoire/SysToolsLib ***@***.***>
Cc: Foster, Rick (TS) ***@***.***>; Author ***@***.***>
Subject: Re: [JFLarvoire/SysToolsLib] Cannot get PSService to run on Windows Server 2019 (#29)
I just tried it on a Windows Server 2019, and it works fine.
Are you sure you have sufficient rights on that machine, like the "Log on as a service" right?
See the detailed help for more information about that.
-
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJFLarvoire%2FSysToolsLib%2Fissues%2F29%23issuecomment-816594313&data=04%7C01%7CRichard.Foster2%40tusd1.org%7Ca86ddfd1d682475afbe908d8fb444a80%7Cbc7050e04bcc48099245ea8b65084865%7C0%7C0%7C637535618030967530%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=D%2BZdWD%2Btntmv91FH1qrYn0YqG1coVDLgOLNhkTnb8wA%3D&reserved=0>, or unsubscribe<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEUI77OAT5GPTSSDKDGIOLDTH3K4PANCNFSM42POJBKA&data=04%7C01%7CRichard.Foster2%40tusd1.org%7Ca86ddfd1d682475afbe908d8fb444a80%7Cbc7050e04bcc48099245ea8b65084865%7C0%7C0%7C637535618030967530%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=AjnsLoi4RQrBhfDCaKcG6vJ3ue47QuFuKG2dvrfWXis%3D&reserved=0>.
|
Thanks for the reply, I see the issue is some setting on Server 2019 that protects the Windows\system32 directory. For some reason, I can only see the created executable while in the PowerShell. If I look in DOS or Explorer it does not exists. I changed the install directory to C:\temp and it installed and would start and run however it seems that Services and System32 have some type of symbiotic relationship as the status command comes back with "it says it started, but it is not running" (not those exact words).
So, I was wrong it does work on Server 2019, I am working with a consultant to see why our Server is setup like this.
Thank you for the tool, I have it installed on quite a few programs, saves converting to C#.
Rick Foster
Data Manager
520-225-6309
Tucson Unified School District
From: JFLarvoire ***@***.***>
Sent: Friday, April 9, 2021 3:43 AM
To: JFLarvoire/SysToolsLib ***@***.***>
Cc: Foster, Rick (TS) ***@***.***>; Author ***@***.***>
Subject: Re: [JFLarvoire/SysToolsLib] Cannot get PSService to run on Windows Server 2019 (#29)
I just tried it on a Windows Server 2019, and it works fine.
Are you sure you have sufficient rights on that machine, like the "Log on as a service" right?
See the detailed help for more information about that.
-
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJFLarvoire%2FSysToolsLib%2Fissues%2F29%23issuecomment-816594313&data=04%7C01%7CRichard.Foster2%40tusd1.org%7Ca86ddfd1d682475afbe908d8fb444a80%7Cbc7050e04bcc48099245ea8b65084865%7C0%7C0%7C637535618030967530%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=D%2BZdWD%2Btntmv91FH1qrYn0YqG1coVDLgOLNhkTnb8wA%3D&reserved=0>, or unsubscribe<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEUI77OAT5GPTSSDKDGIOLDTH3K4PANCNFSM42POJBKA&data=04%7C01%7CRichard.Foster2%40tusd1.org%7Ca86ddfd1d682475afbe908d8fb444a80%7Cbc7050e04bcc48099245ea8b65084865%7C0%7C0%7C637535618030967530%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=AjnsLoi4RQrBhfDCaKcG6vJ3ue47QuFuKG2dvrfWXis%3D&reserved=0>.
|
Hi,
Update I figured out the issue with the "symbiotic relationship", it was a spawned instance that was left running when I removed the service to re-install and it caused the started but not running message.
The issue I found is that outside of PowerShell the CSharp executable cannot be seen (so it appears it was not created) but it is created and can only be seen from inside of PowerShell (see 2nd insert). All of the those print screens are the same user (administrator) at the same time.
The issue is that in our Server 2019 install, somehow an Application Package authority (1st insert) was set up and it does something unusual and keeps the exe from being seen outside of PowerShell thus the Service will not start and gives a 575 application error (3rd insert).
I thought you might want to put in a blurb for those creating on Server 2019 that uses the Application Package Authority, they may have issues.
I solved by using an install directory other than System32 and it works fine.
***@***.***D73696.A4570680]
***@***.***D73696.A4570680]
***@***.***D73696.A4570680]
Rick Foster
Data Manager
520-225-6309
Tucson Unified School District
From: Foster, Rick (TS)
Sent: Wednesday, April 21, 2021 8:39 AM
To: JFLarvoire/SysToolsLib ***@***.***>; JFLarvoire/SysToolsLib ***@***.***>
Cc: Author ***@***.***>
Subject: RE: [JFLarvoire/SysToolsLib] Cannot get PSService to run on Windows Server 2019 (#29)
Thanks for the reply, I see the issue is some setting on Server 2019 that protects the Windows\system32 directory. For some reason, I can only see the created executable while in the PowerShell. If I look in DOS or Explorer it does not exists. I changed the install directory to C:\temp and it installed and would start and run however it seems that Services and System32 have some type of symbiotic relationship as the status command comes back with "it says it started, but it is not running" (not those exact words).
So, I was wrong it does work on Server 2019, I am working with a consultant to see why our Server is setup like this.
Thank you for the tool, I have it installed on quite a few programs, saves converting to C#.
Rick Foster
Data Manager
520-225-6309
Tucson Unified School District
From: JFLarvoire ***@***.******@***.***>>
Sent: Friday, April 9, 2021 3:43 AM
To: JFLarvoire/SysToolsLib ***@***.******@***.***>>
Cc: Foster, Rick (TS) ***@***.******@***.***>>; Author ***@***.******@***.***>>
Subject: Re: [JFLarvoire/SysToolsLib] Cannot get PSService to run on Windows Server 2019 (#29)
I just tried it on a Windows Server 2019, and it works fine.
Are you sure you have sufficient rights on that machine, like the "Log on as a service" right?
See the detailed help for more information about that.
-
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJFLarvoire%2FSysToolsLib%2Fissues%2F29%23issuecomment-816594313&data=04%7C01%7CRichard.Foster2%40tusd1.org%7Ca86ddfd1d682475afbe908d8fb444a80%7Cbc7050e04bcc48099245ea8b65084865%7C0%7C0%7C637535618030967530%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=D%2BZdWD%2Btntmv91FH1qrYn0YqG1coVDLgOLNhkTnb8wA%3D&reserved=0>, or unsubscribe<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEUI77OAT5GPTSSDKDGIOLDTH3K4PANCNFSM42POJBKA&data=04%7C01%7CRichard.Foster2%40tusd1.org%7Ca86ddfd1d682475afbe908d8fb444a80%7Cbc7050e04bcc48099245ea8b65084865%7C0%7C0%7C637535618030967530%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=AjnsLoi4RQrBhfDCaKcG6vJ3ue47QuFuKG2dvrfWXis%3D&reserved=0>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It works fine on 2012 but has issues starting on 2019, I am guessing it is in the structures for reading the registry, but it is over my head...
Testing.exe OnStart() // Failed to start C:\Windows\System32\Testing.ps1. {Application Error}
The application was unable to start correctly (0x%lx). Click OK to close the application
The text was updated successfully, but these errors were encountered: