Practical Programs

[Pawel]

If you want to install any custom services, you need to install the default services first. At the least, these "default" services need to be "created" but can be left in the "uninstalled" state, and only after can custom services be added.

Any "lockups" or freezes at the "starting" stage are most likely due to conflicts in either "Port" or misconfiguration of the ServiceName.

The first five Dv Services listed in the Dv Service Manager must be:

Dv AdminSvc
Dv WebServer
Dv RegistrationSvc
Dv AppConnectSvc
Dv DocumentImportSvc

This is a requirement of both the Dv Service Manager and the Dv Admin Service - which checks that services are running periodically, and restarts the individual services if necessary.

The default services cannot have custom service names. If the order and service names are not as described, you can "reset" the settings by right-clicking in the Services list, and selecting "Reset" (last menu option). Note that this will remove any services listed, and will re-install the default services into the Windows registry.

Services which require a valid database connection are:
Dv Web Server - will check always require its own .INI file (DvWebServer.ini or custom), if no DB is configured will raise error.

The Web server DB configuration is written by the "Tools -> Web Publish" menu, via the Dv Service Manager -> Database Configuration right-click menu, or via the Dv Database Configuration utility

Dv AppConnect Service - will check its own .INI file first (DvAppConnectServer.ini or custom), if no DB is configured, will use REDIRECT.PPD from the Desktop client

Dv DocumentImport Service - will check its own .INI file first (DvDIServer.ini or custom), if no DB is configured, will use REDIRECT.PPD from the Desktop client

The AppConnect and DocumentImport server DB configurations are written by the Dv Service Manager -> Database Configuration right-click menu, or via the Dv Database Configuration utility

The Dv Admin Service and Dv Registration Service do not require access to the database.

For custom service instances, the SERVICE_NAME listed in the Windows Service console, and the Services list in the Dv Service Manager, must match the SERVICE_NAME entered in the custom .INI file: