Technical FAQs

Ask a Question

Log Server/Inserter Fails to Start; Gives Corrupt Config Error

Goals and Symptoms

Summary
When a user attempts to start the Log Server/Inserter service, the service fails to start.


Symptoms

When a user attempts to start the Log Server/Log Inserter service, the service fails to start. An error something like the following will appear in the Event Viewer Application Log:

Intercepted message box: (null): Corrupt config file D:\IONEnterprise\config\cfg\logsrv\LOGINSERTER.NEWHOPE\LOGINSERTER.NEWHOPE

An error something like the following will appear in the System Log:

Description Caught: ' IONOBJS LEVEL 1 EXCEPTION: Parse Error ' file logsrv.cpp line 627

The Log Server/Inserter has a Log Acqusition module configured in Input Logs mode, and one of the inputs references a node name that includes a hyphen (dash).

There is no indication of a problem when the Log Server/Inserter is configured, but subsequent restarts of the Log Server/Inserter service will fail as described.

Facts and Changes

Keywords
ION Enterprise

Log Server

Log Inserter

Corrupt

Hyphen

Dash

Causes and Fixes

Cause
The parser that processe the Log Server/Inserter configuration file is unable to parse node names that contain a hyphen (dash).


Resolution

There is no resolution, but there is a workaround.


Workaround

Caution: The steps that follow require direct manipulation of the database. It is adviseable to back up any database that is to be modified in case it is necessary to revert.

Rename the node name that is causing the problem so that it does not include a hyphen. It will also be necessary to rename the node name in the database so that data continuity is not disrupted.

NOTE: The Log Server/Inserter must not be running when the steps below are performed!

ION Enterprise 4.5 and earlier:

1. If the VIP node is the problem, the VIP service must be unregistered, and then registered with the new name. To do this, at a command prompt type:

    • Vip – unregserver – N<VIP.old name > (this will remove the service)

      Vip – Service –N<VIP.<new name> (this will replace it with a new name – the renamed service will have to restarted manually).

2. If the VIP node name is changed, the VIP node will also have to renamed in the database. See Step 4. for instructions on how to do this.
3. If a meter node is the problem, rename it in the Management Console.
4. To rename the node in the database, start ISQL, connect to the database using the LogSchema/autonomy account and type the following SQL command. You will have to fill in old node name and new node name appropriately:
    • UPDATE node SET node = ‘<new node name>’ WHERE node = ‘<old node name>’
5. To restart the Log Server/Inserter, delete the corrupt configuration file (it will be located in the \config\cfg\LOGSRV.<machine name> directory) and then restart the service. You will have to reconfigure the Log Server now that the new node names are in place.

ION Enterprise 5.0 and later:

1. If the VIP node is the problem, the VIP service must be unregistered, and then registered with the new name. To do this, at a command prompt type:

    • Vip – unregserver – N<VIP.old name > (this will remove the service)
2. Vip – Service –N<VIP.<new name> (this will replace it with a new name – the renamed service will have to restarted manually). If the VIP node name is changed, the VIP node will also have to renamed in both ION_Network and ION_Data. See Steps 4. and 5. below for instructions on how to do this.
3. If a meter node is the problem, rename it in the Management Console.
4. Rename the node in ION_Network by executing the following SQL using either the Database Manager SQL Editor or the Enterprise Manager Query Analyzer:
    • UPDATE IAS_Source SET Name = ‘<new node name>’ WHERE Name = ‘<old node name>’
5. Rename the node in ION_Data by executing the following SQL as above:
    • UPDATE Source SET Name = ‘<new node name>’ WHERE Name = ‘<old node name>’
6. To restart the Log Server/Inserter, delete the corrupt configuration file (it will be located in the \config\cfg\LOGSRV.<machine name> directory) and then restart the service. You will have to reconfigure the Log Inserter now that the new node names are in place.




More Information

The VIP suffers from the same problem. Note that if node names are changed to correct this problem in the VIP, the database modifications described above must also be made if the node whose name is changed is providing logged data to the Log Server/Inserter.

Document Change History

Date and Initials Comments
2009-10-27 DRM * Corrected erroneous association to "protection relay PRODUCTS\VIP"
* Re-published to Public security level

Was this helpful?
What can we do to improve the information ?