Overview
Some operations are limited in time by defining a timeout. Without it, a user may have to wait a long time for a failing operation where an response is missing. A short timeout may break an operation where the processing takes a long time, but no error occurs. Depending on database size, configuration may need to ne changed to allow a longer waiting time.
Web.config
Configuration for AssertServer resides in IIS root folder of the application, normally in this folder. It defines SOAP bindings with timeout for send and receive of SOAP messages.
C:\inetpub\wwwroot\AssertServer
Server.config
Other configuration for the application is found in a different configuration file, normally here. It defines timeout values for publication and validation, for SOAP transactions and for database transactions.
C:\ProgramData\Signifikant\Assert
SOAP interface
Generally one shall check binding elements in AssertServer’s web.config for SOAP interface timeout. But for validation a longer timeout may be defined. Publication is also a long running operation, but it is run as an asynchronous operation, so it has no SOAP timeout.
Publisher
Set PublisherCommandTimeout in server.config to setup a timeout for all database queries during the publication process. The element holds a timeout value as a number of seconds.
Validation
Validate operation, i.e. when issue a Validate on the whole database, uses the PublisherCommandTimeout setting for SOAP send/receive timeout. It will override the binding defined in AssertServer web.config.
Validators database queries uses same parameter, PublisherCommandTimeout, for database accesses.
Also check the log file for duration figures, to get an estimate on what a sufficient timeout may be.
Database queries
When a client running the Manager program requests data from the server, it uses the CommandTimeout value from server.config. The element holds a timeout value as a number of seconds.