Internal documentation only

This page has been marked as draft.

How to Know if you have a Corrupt Workspace

What you’ll need is the Active Console Diagnostic File.

• If processes are running, but gateways do not bind to the listening port (resulting in a “connection refused” error upon connection attempts), and if, beyond the initial startup, there is a lack of normal Gateway activity logged, such as connecting to Netprobes, it is advisable to check the logs. If multiple lines similar to the examples below are observed, it may suggest a corrupt workspace, necessitating a fresh start:

NativeLoggerBridge [ERROR] Directory: severitySet: Received invalid index XXXXX ,type 6
NativeLoggerBridge [ERROR] Directory: severitySet: Received invalid index XXXXX ,type 6
NativeLoggerBridge [ERROR] Directory: severitySet: Received invalid index XXXXX ,type 6
NativeLoggerBridge [ERROR] Directory: severitySet: Received invalid index XXXXX ,type 6
NativeLoggerBridge [ERROR] Directory: severitySet: Received invalid index XXXXX ,type 6

In such cases, starting anew might be the recommended course of action.