Changes
/* Diagnosis */
==== {{UBIK}} Content Service ====
{| class="wikitable sortable"
|-
! Test !! Type !! Description
|-
| rowspan="3" width="200" | Try to find the service end point|| Error || The service cannot be reached: Possible reason is an error in the web.config, which cannot be parsed. An other reason can be a faulty configuration of the service in IIS.
|-
| Warning || The service end point provides a non-secure connection ("http://"). A connection without transport security should only be used for testing or in internal networks in a trusted enviroment only. This is generally not recommended for a productive environment.
|-
| Warning || The service endpoint provides a secure connection ("https://") but has issues with the certificate provided: e.g. expired validity, non-trusted root authority etc. This means, a connection to the service will still be possible but it is not recommended to use in a productive environment.
|-
| Fetch a token || Error || The session management service is not configured to testing mode or does not have a valid test login configured in the {{UBIK}} database
|-
| Verify token || Error || The fetched token is not recognized as a valid token to be used with the content service. A possible reason is that the session management has a different database connection configured.
|-
| Verify if token gets invalid || Warning || The fetched token is always valid. The reason can be that the setting "TokenRestrictive" is switched off which is not recommended for productive use.
|}
==== {{UBIK}} Push Service ====
| Warning || see the section in the Session Management tests
|-
| Check database connection Add push data || Error || Database cannot be reachedAdding push data failed. Possible The reason can could be a faulty database connection string or the used database server cannot be reached or is blocked by miscofigured service access point for the network configurationpush service.
|-
| Upload a file Fetch push data || Error || The configured target file system in the database settings is not set correctly to a folder allowing to write No push datareceived. The If this error occurs even if adding the push data worked, the reason can could be that the user running cached push data has been lost because the {{UBIK}} web service does not have read/write access had to be restarted or persisting the data in the configured target folderbackground failed.
|-
| Download a file || Error || The uploaded file (uploaded in the previous test) cannot be downloaded. Possible reasons could be a timeout which is set too restrictive to download the Reset push data in time.|-| Write logs || Error || The log cannot be written. Possible reason is that the configured log folders do not exist or the user running the web service has no read/write access to the logging folder.|-| Check rights structure || Error || At least one see description of the configured target directories used to store data possible error(e.g. uploaded photoss) does not have the required read/write rights. See the details if there are issues with one of the configured foldersdescribed for "Fetch push data".
|}
== See also ==
