[solved] PVSS00data errors on startup (and Panel Topology ruined)

[EER]

Nevermind, the problem was a missing WinCC OA patch...


[strike]Hello,

I encounter some annoying problems during the project-startup which seem to ruin the topology and thus the complete user interface.

Here is some info about the system:
- Windows server Enterprise (2007) + SP2
- WinCC OA 3.10 + SP2
- AquaPackage310


The errors I encouter look like this (this is a small snippet, the same type of error repeats it self for a lot of data-points):

Code: Select all

*** skipping 43888 bytes from PVSS_II.log ***
rgUlicoten.Alarms.Personeel_te_lang_aanwezig:_alert_hdl.._value (Type: 0 Sys: 0 Dp: 16972 El: 3428 : _alert_hdl.._value)
PVSS00data   (0), 2016.03.01 16:59:34.619, IMPL, SEVERE,     50, Default branch called, StAHVariableUtils, loadVariable, unbekannter Typ
PVSS00data   (0), 2016.03.01 16:59:34.619, SYS,  SEVERE,     69, Database error, AlertCacheItem, loadText, Code :0
rgUlicoten.Alarms.Personeel_te_lang_aanwezig:_alert_hdl.._value (Type: 0 Sys: 0 Dp: 16972 El: 3428 : _alert_hdl.._value)
PVSS00data   (0), 2016.03.01 16:59:34.620, IMPL, SEVERE,     50, Default branch called, StAHVariableUtils, loadVariable, unbekannter Typ
PVSS00data   (0), 2016.03.01 16:59:34.620, SYS,  SEVERE,     69, Database error, AlertCacheItem, loadText, Code :0
rgUlicoten.Alarms.Niet_paraat:_alert_hdl.._value (Type: 0 Sys: 0 Dp: 16972 El: 3429 : _alert_hdl.._value)
PVSS00data   (0), 2016.03.01 16:59:34.620, IMPL, SEVERE,     50, Default branch called, StAHVariableUtils, loadVariable, unbekannter Typ
PVSS00data   (0), 2016.03.01 16:59:34.620, SYS,  SEVERE,     69, Database error, AlertCacheItem, loadText, Code :0
rgUlicoten.Alarms.Niet_paraat:_alert_hdl.._value (Type: 0 Sys: 0 Dp: 16972 El: 3429 : _alert_hdl.._value)
PVSS00data   (0), 2016.03.01 16:59:34.622, IMPL, SEVERE,     50, Default branch called, StAHVariableUtils, loadVariable, unbekannter Typ
PVSS00data   (0), 2016.03.01 16:59:34.622, SYS,  SEVERE,     69, Database error, AlertCacheItem, loadText, Code :0
rgUlicoten.PT1.Alarms.StilstandMeting:_alert_hdl.._value (Type: 0 Sys: 0 Dp: 16972 El: 3751 : _alert_hdl.._value)
PVSS00data   (0), 2016.03.01 16:59:34.622, IMPL, SEVERE,     50, Default branch called, StAHVariableUtils, loadVariable, unbekannter Typ
PVSS00data   (0), 2016.03.01 16:59:34.622, SYS,  SEVERE,     69, Database error, AlertCacheItem, loadText, Code :0
rgUlicoten.PT1.Alarms.StilstandMeting:_alert_hdl.._value (Type: 0 Sys: 0 Dp: 16972 El: 3751 : _alert_hdl.._value)
*** skipping 302577 bytes from PVSS_II.log ***

Once all managers are running there the user interface does not show the correct graphics. Also, no panels are to be found in the "panel topology"-panel. Inserting a child node does not respond and throws the error:

Code: Select all

PVSS00ui     (12), 2016.03.01 17:12:26.404, CTRL, SEVERE,    176, Uncaught exception in thread started at main: 
PVSS00ui     (12), 2016.03.01 17:12:26.404, CTRL, SEVERE,     79, Index out of range, 
    Module: _PanelTopology_
    Panel: C:\\Data\\Projecten\\WBD\\BOAWBD\\panels\\para\\PanelTopology\\PT_main.pnl []
    Object: 53 named: "cmdAddChild" of type: PUSH_BUTTON
    Script: Clicked
    In panel scope library: para\\PanelTopology\\PT_main.pnl []
    Line: 256, , 1
Stacktrace:
     1: addNode(int addMode = 1) at :256
     2: cmdAddChild() at :318
     3: main() at [Module: _PanelTopology_ Panel: para\\PanelTopology\\PT_main.pnl Object: cmdAddChild Script: Clicked]:3

Contrary to what I expected, the internal data-type "_PanelTopology" does contain two data-points ("_PanelTopology" and "System1_PanelTopology") which do contain information refering to the panels which should be in the topology:



Does anyone have any experience with such errors? What steps can I take to resolve it?

So far i have tried the following steps (without success):
- starting the database manager with "repair on" and "repair alerts" arguments
- reinstalling WinCC OA
- running the project on different PC (Windows 7)
- running "PVSStoolRepairDb.exe chkvfs" from the project root folder (still running, gives no feedback and it is unclear how long it will take.)

I hope someone can help.[/i][/strike][/color]

[EER]

Patch P037 fixed it.