13.04.2013 Views

Digipass Plug-In for SBR Administrator Reference - Vasco

Digipass Plug-In for SBR Administrator Reference - Vasco

Digipass Plug-In for SBR Administrator Reference - Vasco

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Digipass</strong> <strong>Plug</strong>-<strong>In</strong> <strong>for</strong> <strong>SBR</strong> <strong>Administrator</strong> <strong>Reference</strong> Error and Status Codes<br />

Error<br />

Code<br />

-252 Decryption has failed - an incorrect<br />

Storage Key is specified in the<br />

Encryption Settings<br />

Message Notes<br />

component is there<strong>for</strong>e unable to decrypt the data.<br />

It is necessary to make sure that the encryption settings in all<br />

components are identical. See 4 Sensitive Data Encryption<br />

<strong>for</strong> more in<strong>for</strong>mation.<br />

Some encrypted data has been created or modified using<br />

differently configured encryption settings. This error occurs<br />

when that data is read by a component with configured<br />

encryption settings that use a different Storage Key – the<br />

component is there<strong>for</strong>e unable to decrypt the data.<br />

It is necessary to make sure that the encryption settings in all<br />

components are identical. See 4 Sensitive Data Encryption<br />

<strong>for</strong> more in<strong>for</strong>mation.<br />

-300 A database error occurred General-purpose error on a database operation. This should be<br />

supplemented with more specific details.<br />

-350 The request received was discarded A replication update that was received was found to be<br />

superseded by a later change. <strong>In</strong> this case, the update is<br />

discarded, as it is no longer relevant.<br />

This may occur when creating a record, after a record has been<br />

deleted then re-created.<br />

It may occur when modifying a record, if a later modification<br />

occurred be<strong>for</strong>e replication could apply the first change.<br />

-351 The request received must be retried A replication update that was received could not be applied<br />

immediately. <strong>In</strong> this case, the update is rejected. The retry<br />

mechanism at the source server will re-send the update,<br />

according to its configuration settings.<br />

This may occur if a record does not exist yet, when trying to<br />

apply a modification or deletion.<br />

It may occur after a record has been deleted and re-created,<br />

when a modification of the record is replicated but the<br />

sequence of deletion and re-creation has not been followed in<br />

the correct order.<br />

-352 A replication queue entry had an<br />

invalid hash value<br />

When an entry was read from the replication queue be<strong>for</strong>e<br />

sending, its integrity hash value check failed. This suggests that<br />

the queue entry may have been modified since it was added to<br />

the queue. <strong>In</strong> this case, the queue entry is not trusted and an<br />

error is reported.<br />

-353 The replication queue is full An operation failed because it needed to update the database,<br />

but the update could not be added to the Replication queue. If<br />

the queue is full, no database updates are allowed, to avoid the<br />

databases getting too far out of synchronization.<br />

Check the Replication Status dialog in the Administration MMC<br />

<strong>In</strong>terface and the Replication audit messages to investigate why<br />

the queue has become full. It is necessary to reduce the queue<br />

size in order <strong>for</strong> the system to continue to function.<br />

If this error occurs often, without good reason, consider<br />

increasing the maximum queue size. This can be configured in<br />

the Replication tab of the Authentication Server Configuration<br />

GUI.<br />

-500 The Service was already started When trying to start a Service, the Service was already<br />

running.<br />

-501 The Service was already stopped When trying to stop a Service, the Service was not running.<br />

-10051 File name is blank. No file name was specified.<br />

-10052 Failed to open File. The file could not be opened. The file does not exist or the user<br />

attempting to open the file does not have read permission <strong>for</strong><br />

the file.<br />

© 2006 VASCO Data Security <strong>In</strong>c. 179

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!