Alwaysup

"sanity check"Click the ... button to browse to the Netcam Watcher program folder, locate the file NCWPING.BAT.Click the ... button to browse to the Netcam Watcher program folder, locate the file NCWPING.BAT and click OK. Use an interval of one minute or 30 seconds.Click over to the Startup tab and check the Ensure that the Windows Networking components have started box.This informs AlwaysUp that Netcam Watcher needs the TCP/IP networking stack to operate.Click the Save button. In a couple of seconds, an application called Netcam Watcher Pro will show up in the AlwaysUp window.It is not yet running though.To start Netcam Watcher, choose Application > Start "Netcam Watcher Pro".On Windows 7, 2008 or Vista (or when connecting via RDP), you will have to choose Application > Start "Netcam Watcher Pro" in this Session to show Netcam Watcher's windows and tray icons.(More on this in the AlwaysUp FAQ.)That's it! Next time your computer boots, Netcam Watcher will start up immediately, before anyone logs on.We encourage you to edit Netcam Watcher in AlwaysUp and check out the many other settings that may be appropriate for your environment.Netcam Watcher Professional not working properly as a Windows Service?From AlwaysUp, select Application > Report Activity > Today... to bring up a HTML report detailing the interaction between AlwaysUp and your application.The AlwaysUp Event Log Messages page explains the more obscure messages.Consult the AlwaysUp FAQ or theNetcam Watcher Professional FAQfor answers to commonly asked questions and troubleshooting tipsContact the friendly and helpful folks at Beausoft, the

AlwaysUp, developed by Core Technologies Consulting LLC, is a robust and versatile software solution designed to ensure that your critical applications and services run continuously without interruptions. Tailored for both personal and enterprise use, AlwaysUp transforms your regular Windows applications into Windows Services, thereby enhancing their reliability and uptime. One of the standout features of AlwaysUp is its ability to automatically restart applications that have crashed or hung. This proactive approach minimizes downtime and ensures that your essential programs are always operational, even in the face of unexpected failures. The software achieves this by monitoring the health of applications and services, and it can be configured to send notifications via email when issues arise, keeping administrators informed in real-time. AlwaysUp is highly customizable, offering a user-friendly interface that allows you to set up and manage services with ease. Its intuitive design makes it accessible to users of varying technical expertise, while its advanced options cater to the needs of IT professionals seeking granular control over application behavior. You can specify startup parameters, set priority levels, and even define custom scripts to execute at various stages of the application lifecycle. Compatibility is another strong suit of AlwaysUp. It supports a wide range of applications, from simple executables to complex server-based programs, and is compatible with all modern versions of Windows. This flexibility ensures that it can be seamlessly integrated into diverse IT environments, providing a reliable solution for businesses of all sizes. Security is a top priority for Core Technologies Consulting LLC, and AlwaysUp reflects this commitment by running applications in the background as Windows Services, which can operate without the need for a logged-in user. This not only enhances security by reducing the risk of unauthorized access but also conserves system resources, as services can run independently of user sessions. In addition to its core functionalities, AlwaysUp offers a comprehensive set of features such as detailed logging, which provides insights into application performance and helps in diagnosing issues. The software also supports clustering, allowing for high availability setups that further bolster application resilience. Overall, AlwaysUp stands out as an essential

The arguments passed to PlexIn our step-by-step tutorial, we recommend running Plex Media Server.exe with the -nointeractive flag. This tells Plex that it should not create a tray icon because we cannot access it when PMS is running in the background (in Session 0).However, when the flag is specified, Plex doesn’t create a main window either. And without a main window, AlwaysUp cannot send Plex the “default” signal to close.Without the flag, AlwaysUp is able to close Plex smoothly — sans error messages.To remove the nointeractive flag, edit your PMS entry in AlwaysUp and clear the Arguments field:There is only one (minor) downside to this solution. Without the flag, Plex will print a warning to its log file every few seconds. This won’t be a problem — unless you are a techie digging into the Plex internals — but it deserves to be mentioned.Solution #2: Stop Plex with taskkillThe second alternative is to plug in a separate program to close PMS. Several folks on the Plex forums recommend using the Windows taskkill command.To configure AlwaysUp to shut down Plex with taskkill:Create a batch file with this line:taskkill /t /f /im “Plex Media Server.exe”As you can see from the taskkill documentation, this command will terminate PMS and all its child processes.Start AlwaysUp and edit your Plex Media Server entrySwitch to the Extras tab.Enter the full path to the batch file you created in step 1 in the Use this special command to stop the application field. And you might as well give taskkill up to 30 seconds to do its work by completing the field below that:Save your settingsWith this solution in place, the next time you stop PMS from AlwaysUp:AlwaysUp will run the batch fileThe batch file will run taskkilltaskkill will close all the PMS processesAlwaysUp will see that PMS has closed and will set the state of the Plex Media Server entry to “Stopped”.No error messages!You may also like...

I’ve download the trial version of AlwaysUp and installed it on a Server 2016 standard machine. I’ve created a Windows service for Plex Media Server and all is working well except for shutting the service down (or restarting).Every time I restart or shut down the service I’m getting this error:The application has failed to stop gracefully and may be forcibly terminated. The following processes may be terminated: Plex Media Server.exe, PlexScriptHost.exe, conhost.exe, PlexScriptHost.exe, conhost.exe, Plex Tuner Service.exe, conhost.exeCan you please let me know what’s wrong?— PanjaHi Panja. We can fix this 🙂But first, a brief explanation of what is going on…Plex Media Server (PMS) launches several processesWhen you start PMS (either normally on your desktop or as a service from AlwaysUp), the main executable (Plex Media Server.exe) spawns a family of processes. Those processes work together, invisibly in the background, to share your files with hungry devices.You can see the “tree” of up to 8 processes with Microsoft’s Process Explorer:Exiting PMS from the tray icon closes all the processesWhen Plex is running normally on your desktop, you close it by selecting “Exit” from the tray icon menu. The main process receives the signal and quietly closes the other 7 processes. You never witness the behind-the-scenes coordination.AlwaysUp tries several methods to exit PMS and close all its processesWhen you are running Plex Media Server as a background service, there is no tray icon. You must rely on AlwaysUp to shut down PMS and its family of processes.AlwaysUp tries up to four methods to close the media server properly. The error message you see is reported because the first two methods are unsuccessful and AlwaysUp must move on to the last two, more “aggressive” tactics.However, looking at the logs, the third stop-method works for Plex. The server isn’t actually being “forcibly terminated”. So though annoying, you can safely ignore the error — it is a false alarm.But who likes to see a useless error message, right? Here are a couple of ways to eliminate it entirely. Choose one or the other; no need to do both:Solution #1: Remove the “nointeractive” flag from