Digipass Plug-In for SBR Administrator Reference - Vasco
Digipass Plug-In for SBR Administrator Reference - Vasco
Digipass Plug-In for SBR Administrator Reference - Vasco
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Digipass</strong> <strong>Plug</strong>-<strong>In</strong> <strong>for</strong> <strong>SBR</strong> <strong>Administrator</strong> <strong>Reference</strong> Audit Messages<br />
16 Audit Messages<br />
To set up auditing in the <strong>SBR</strong> <strong>Plug</strong>-<strong>In</strong>, see 11.1.8<br />
16.1 Audit Message Listing<br />
Table 67: Audit Messages List<br />
Message<br />
Code<br />
Auditing.<br />
Description Notes<br />
E000001 A system error has occurred. This message is used whenever there is a general<br />
processing error. It will contain full details of the error.<br />
E001001 The <strong>Digipass</strong> <strong>Plug</strong>-<strong>In</strong> failed to start up. The <strong>Plug</strong>-<strong>In</strong> encountered a fatal error on startup such as an<br />
invalid or missing configuration file.<br />
E001002 The <strong>Digipass</strong> <strong>Plug</strong>-<strong>In</strong> has been <strong>for</strong>ced<br />
into the disabled state.<br />
E001003 The Authentication Server failed to start<br />
up<br />
E002001 The Active Directory AAL3 library failed<br />
to initialize.<br />
E002002 The <strong>Digipass</strong> Authentication library<br />
failed to initialize.<br />
E002004 The RADIUS protocol handler failed to<br />
initialize.<br />
E002006 The Replication library failed to<br />
initialize.<br />
E002007 <strong>In</strong>itialization of a Replication destination<br />
server failed.<br />
E002008 The Authentication Server protocol<br />
handler failed to initialize.<br />
E002009 The VM2 Compatibility protocol handler<br />
failed to initialize.<br />
The <strong>Plug</strong>-<strong>In</strong> has started up, but is in a disabled state in<br />
which it will not process authentication requests. This is<br />
typically due to a license problem (an invalid or missing<br />
License Key in the <strong>Plug</strong>-<strong>In</strong>'s Component record); an invalid<br />
Component Location setting in the configuration file; or a<br />
missing Component record <strong>for</strong> the <strong>Plug</strong>-<strong>In</strong>.<br />
The Authentication Server encountered a fatal error on<br />
startup. This is typically due to an invalid or missing<br />
configuration file or failure to connect to the data store.<br />
The Active Directory 'AAL3' library encountered a fatal<br />
error on initialization, eg. invalid configuration settings in<br />
the configuration file.<br />
The 'Authentication' library encountered a fatal error on<br />
initialization, eg. invalid configuration settings in the<br />
configuration file.<br />
The protocol handler that receives and processes RADIUS<br />
requests did not start up. This may be because of a<br />
missing License Key in the Authentication Server<br />
Component record, or because the License Key in that<br />
Component record does not enable RADIUS support. Look<br />
<strong>for</strong> the line RADIUS=Yes in the License Key details.<br />
A common reason <strong>for</strong> this error, when RADIUS is enabled<br />
in the License Key, is that the RADIUS ports are already in<br />
use by another process on the machine.<br />
Alternatively, the configuration settings may be invalid.<br />
The Replication library encountered a fatal error on<br />
initialization, eg. invalid configuration settings in the<br />
configuration file.<br />
The Replication library found the configuration of a<br />
Destination Server to be invalid. The library will still start<br />
up if its main configuration settings are valid and there is<br />
at least one valid Destination Server. For the invalid<br />
Destination Servers, this audit message is generated.<br />
The protocol handler that receives and processes<br />
administration requests and authentication requests from<br />
the IIS modules failed initialization. This is typically due to<br />
invalid configuration settings or because the API port is<br />
already in use by another process on the machine.<br />
The protocol handler that receives and processes<br />
authentication requests from the VACMAN Middleware<br />
© 2006 VASCO Data Security <strong>In</strong>c. 166