Progress Errors

[Samj]

WINNT Terminal Server - 8.3D

Hello,


We have a crew out at a customer site installing a new system. They tell me they are receiving this event viewer error when the system is rebooted but, I see that the messages were written into the log file the last time the server was shut down.
('HSI' is the database name)

Is anyone familiar with this error mesage?

TIA

Sam Johnson
Professional Data Systems, Inc.
samj@pdsi.com

09:50:54 BROKER 0: 'CTRL_SHUTDOWN_EVENT' console event received. (5406)
09:50:54 BROKER 0: Registry error 1717: Could not register 'HSI' events with the Event Viewer. (5179)
09:50:54 BROKER 0: Begin ABNORMAL shutdown code 2 (2249)
09:50:56 BROKER 0: Registry error 1717: Could not register 'HSI' events with the Event Viewer. (5179)
09:50:56 BROKER 0: Multi-user session end. (334)
09:51:01 SHUT 1: Database killed by root on CON: (2250)
09:51:01 SHUT 1: Registry error 1717: Could not register 'HSI' events with the Event Viewer. (5179)
09:51:01 SHUT 1: Error opening file d:\protrac\db\hsi.lk, errno = 2. (4029)
09:51:01 SHUT 1: Registry error 1717: Could not register 'HSI' events with the Event Viewer. (5179)
09:51:16 SERVER : Multi-user session end. (334)
09:51:16 SERVER : Registry error 1717: Could not register 'HSI' events with the Event Viewer. (5179)

Mon Jun 25 12:07:06 2001
12:07:06 BROKER 0: Multi-user session begin. (333)
12:07:06 BROKER 0: ** The last session was abnormally terminated. (852)
12:07:06 BROKER 0: ** Any incomplete transactions are being backed out. (459)
12:07:07 BROKER 0: ** Database recovery complete. Rerun all active transactions. (36)

 

[Samj]

Ok, like Roseanna Dana used to say...'nevermind'... I found the answer to my question in the progress.com knowledgebase:

Kbase Id: 17917
Title: CTRL_SHUTDOWN_EVENT Explained

You should avoid a Windows shutdown or restart with a database
running. The database needs to run through normal crash recovery, so
it might take up more time to start once the system is up and running.

SOLUTION:

It is possible to shut down the database(s) before a Windows NT
shutdown command is issued. Here are two ways to accomplish it:

- Create a batch file called SHUTDOWN(dbname).bat that contains
the following:

%DLC%\BIN\PCCMD.exe DATABASES STOP database-
name-from-proctrl

This must be done for all the databases that are defined in
ProControl.

- Issue a NET command:

NET STOP <ProService name>
(example; NET STOP "Proservice for 8.2C"

Thanks anyway,

Sam