How to manually Install/Configure ProControl on Windows NT/2000?

« Go Back


EnvironmentProgress 8.X
Progress 9.X
Windows NT 32 Intel/Windows 2000
Question/Problem Description
How to manually Install/Configure ProControl on Windows NT/2000?
ProControl manual install
Procontrol manual configuration
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
NOTE1: The preferred method is to reinstall Progress using "custom" rather than "quick", but the method below can be used if a reinstall is not an option. If this method does fail, you should perform a reinstallation of Progress with use of the custom option.

NOTE2: If reinstallation is desired and it happens that the file C:\winnt\system32\Proctrl.cpl isn't deleted during the uninstall process it's because it was in use (locked) by the Windows operating system. To get around this problem stop the ProService and configure it to a "manual" startup. Then shutdown and restart the Windows server machine. Upon re-start of Windows server machine the Proctrl.cpl is now longer in use, thus you can remove Progress correctly.

NOTE3: Progress recommends that you back up your Registry before you make changes to it because a modification to the Registry might make your OS unusable.

Start a Proenv session (that sets the paths and variables required for, in this example, Progress Version 8.3D.

If Proenv is not an option, you must make sure that the environment is correct for the version of Progress that you are using.

If you run Proctrl.exe (that should be located in the %DLC%\BIN directory), you might receive the following error:

Cannot read registry.

This is correct, because this key should not exist because ProControl was not installed.

If you get the error, follow these steps to create this Key and one other:

1) Use Regedit or create the keys manually with the reg.exe command if you have the Windows NT Resource Kit installed.

Create the following keys with Regedit:



Or, if you use reg.exe, create the keys with:


REG ADD HKLM\SOFTWARE\PSC\ProService\8.3D\Environment\DLC

2) Run ProCtrl.exe once more.

You get the following message:

DLC is not defined correctly!

3) Click OK.

You get the following error:

Cannot read the Registry Key Environment.

4) Click OK.

The environment dialog is displayed.

5) Enter DLC in the variable fill-in.

6) Enter the drive and path to the DLC directory in the Value fill-in.

7) Click SET.

8) Click APPLY.

This should display the DLC setting in the environment.

9) Click OK.

The ProControl main window should show. This does not make ProControl usable. Because the ProControl was not installed, it is probable that the ProService is not installed either.

You must install ProService with the following command:

prosrvc /install

(prosrvc.exe should exist in the %DLC%\BIN directory). ProService is installed within the NT Services with the default settings it would have had in a normal installation.

The ProControl icon is not placed in the Progress Group in the start menu. The
installation procedure does this. You can manually place an icon in the Progress group or, you can access ProControl through the Control Panel or create a shortcut to proctrl.exe.
Last Modified Date9/13/2015 10:24 AM

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Was this article helpful?


Your feedback is appreciated.

Please tell us how we can make this article more useful.

Characters Remaining: 255