Script deployed as a Windows service do not work when built with PowerShell Studio 2019+

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 2 years and 3 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
User avatar
abarker5
Posts: 3
Last visit: Mon Sep 18, 2023 8:13 am

Script deployed as a Windows service do not work when built with PowerShell Studio 2019+

Post by abarker5 »

To help you better we need some information from you.

*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***

Product, version and build: PowerShell Studio 2019, 2020, 2021
Operating system: Windows 7, Windows 2008, Windows 2008R2
PowerShell version(s):2.0 and newer

*** Please add details and screenshots as needed below. ***
I have a PowerShell script that is built as a Windows service with PowerShell Studio. The compiled service executable stopped working on Windows 7 and Windows 2008 R2 after upgrading from PowerShell Studio 2018 to 2019, 2020, and 2021. I have to still use 2018 to compile the service. I need it to work in new versions of PowerShell Studio.
User avatar
Alexander Riedel
Posts: 8479
Last visit: Thu Mar 28, 2024 9:29 am
Answers: 19
Been upvoted: 37 times

Re: Script deployed as a Windows service do not work when built with PowerShell Studio 2019+

Post by Alexander Riedel »

Windows 7 (and Windows Server 2008) support has ended a while ago. Even the extended support for Windows 7 has ended in January 2020.
The current system requirements for our products are always listed on the product page. In the case of PowerShell Studio 2021 they are currently:
Windows Server 2016 / 2019 or Windows 10, 64-bit versions supported
400MB free disk space
2GB RAM
.NET Framework 4.8
.Net 5 for PowerShell 7
Visual Studio 2015-2019 Runtime

If supported platforms or runtime versions are no longer supported, it is usually listed in the corresponding release logs.
These can be found here: https://www.sapien.com/software/version_history

Having pointed all of that out, it is impossible to determine why your packaged executable is no longer working with the information provided.
At the very least you would need to supply your exact configuration, which runtimes are installed and, most importantly, what exactly "not working" entails.
There is a wide range of "not working", from a service executable not even registering as a service, to the service not starting, crashing, or the embedded script not doing what it is supposed to be doing.
At a minimum the corresponding Windows event log entries should be included to provide information.
Alexander Riedel
SAPIEN Technologies, Inc.
This topic is 2 years and 3 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.