Services
Contents
What is a Windows Service?
Possibly the biggest new feature of DLS IV is the service-based architecture.
On Microsoft Windows operating systems, a Windows service is a long-running executable that performs specific functions and which is designed not to require user intervention. Windows services can be configured to start when the operating system is booted and run in the background as long as Windows is running, or they can be started manually when required.
There are many advantages to this architecture:
- DLS IV does not rely on the current user's permissions
- Allows effective integration with SQL Server Express
- Allows operations to continue in the background AFTER the application has been closed
DLS IV Services
The following are services which DLS IV uses and requires to run:
MCPH
The Multi-Comm Port Handler is the service component that handles the comm port assignment of each job. This service allows Comm Port Sharing, without requiring any extra user intervention.
Thanks to the MCPH, it's a one-time setup per connection type in the Modem Manager.
DLS Authentication Service
The Authentication service is DLS IV's padlock. This service ensures that your database will never fall into the wrong hands. The Security Stamp and Hardware Key are both processed by the authentication service on every login attempt.
DLS Communication Service
The Communication service is the workhorse that performs all communication jobs. This service receives each communication job, converts to panel-friendly commands, and executes your upload/download. Having the communication service allows you to submit many jobs in queue, close down the DLS IV application and walk away. The Communication service executes the jobs silently in the background, storing detailed information about each job in the database for your later review.
DLS Application Service
The Application service is DLS IV's engine. This service is at the core of every operation in DLS IV. It controls all traffic to-and-from the database, it builds up each communication job and checks the job's status as it's processed,
Managing Services
Service based architecture is becoming more and more mainstream, but is still relatively new to many PC users. DLS IV Services are set to launch "Automatically" on startup. This means that DLS IV, regardless of the permissions of the current PC user, will launch as a fully-functioning application every time Windows starts.
This startup routine, though robust, is not perfect. You may find that your PC has difficulty starting some services from time to time. Here are a couple of quick tips to help you manage your services:
DLS IV Launch
If any DLS IV service is not in a working state when the DLS IV application is launched, DLS IV will automatically try to start the services for you. This function will execute successfully for admin level users.
Start Menu - Restart All Services
Use DLS IV's built-in Service startup utility. Browse to DLS IV in your Start Menu, select Utilities and "Restart All DLS IV Services". This will automatically shutdown all DLS IV services and restart them in the desired order.
If you experience trouble stopping a service, it may be because that service is currently busy trying to startup. It is recommended to allow approx 2 mins to let the service gracefully complete the startup routine before shutting it down. Try the "Restart All DLS IV Services" utility again in a couple of minutes.
Services Manager
Access the Windows Services Manager by:
- Right-click "My Computer"
- Click "Manage"
- Browse to "Service and Applications" and then "Services"
You'll see a comprehensive list of all the service based applications installed on the PC, and each service's current state.
From here you can see the state of all DLS IV services, and correct any issues. Remember, when starting the DLS Services, start them in this order:
- Authentication Service
- Application Service
- Communications Service
- MCPH Service
Rebooting Your PC
Rebooting your PC is an excellent way to get back to a safe starting point. Rebooting your PC will close any conflicting applications and will allot the proper resources to the DLS IV services on startup. It also allows each service to restart with the designed System privileges.
Troubles with Services
IF you continue to have difficulty with Services, please review the following items.
Startup Time
Each DLS IV service is in the "Windows Service Manager's" startup queue. When your PC boots up, it must work through the entire list of services set to startup automatically. This process can take a few moments.
The DLS IV services must be started before running DLS IV. It is suggested that the PC is completely booted before running DLS IV.
During this startup, it is strongly recommended that you do not attempt to STOP any DLS IV services.
Dependancies
There are as few service dependencies in DLS IV as possible. For example: The Windows TCP/IP service must be running to allow the DLS IV components to properly initialize. Please ensure that the following Services are set to "Automatic" startup and are fully started when attempting to run DLS IV:
- Remote Access Connection Manager (RasMan)
- Windows Management Instrumentation
- SQL Server (Express)
If any of these services are not started, you may experience difficulty operating DLS IV.
One of the Services has NEVER started
If only one of your DLS IV services has NEVER started, it is likely that there was a problem during installation. This type of issue can be avoided by ensuring that the PC is not busy during the installation process.
As with the installation of most applications, is is recommend that you close all open programs, ensure that anti-virus is not actively scanning, and reduce the workload of the PC so that the installation process can run smoothly.
Uninstall DLS IV and re-install to correct this issue.
