Installation Scout Enterprise Management Suite 15.x
Troubleshooting
| Error message / problem | Reason | Solution |
|---|---|---|
| Scout desktop icons are not displayed correctly. | Desktop icons are cached by Windows. This may lead to the fact that after you update Scout, new icons are not displayed correctly. | Delete the Windows icon cache. Please refer to the relevant documentation. |
| File access error while checking HTTP/FTP server (error number = 404) | Possibly caused by missing MIME type entries for the used file extensions s on the web server | In the MIME type settings of the web server, add the file extensions used in eLux containers and assign them to the relevant MIME types. When you install ELIAS 18 or an eLux container on Microsoft Internet Information Server (IIS), the mappings will be performed automatically. |
The following MIME types are required and installed with the container:
| Extension | MIME type |
|---|---|
| .dd | text/plain |
| .epm | text/plain |
| .fpm | text/plain |
| .gz | application/x-gzip |
| .idf | text/plain |
| .ini | text/plain |
| .rdf | text/plain |
| .sig | text/plain |
| .xz | application/x-xz |
The following additional assignments might become necessary:
| Extension | MIME type | Description |
|---|---|---|
| .bin | application/octet-stream | BIOS update via Scout |
| .bup | text/plain | BIOS update via Scout |
| .cab | application/vnd.ms-cab-compressed | UEFI update via Scout |
| .mee | text/plain | Migration of eLux RP 5 devices to eLux RP 6 with whitelist (for current eLux versions done by the container installer). Different images depending on the hardware model (/en-us/unicon-elux-scout/admin_guides/scout/setup/firmware/firmware_macro_hardware.html) |
| .udf | text/plain | UEFI updates in analogy to firmware updates (from Scout 15 2107 and eLux RP 6 2107) |
Troubleshooting for an installation with Microsoft SQL Server
| Error message | Reason | Solution |
|---|---|---|
| Cannot initialize the license database. | When checking the database ID, a problem was identified. A database backup was restored on an SQL Server on which the database does not exist. Note: A unique database ID ensures that a Scout license database cannot be used more than once. | Preventive: Restore a database backup only on the SQL Server on which the database backup was created and the database still exists. In case of error:Contact Unicon™ Support. The Repair database button displays a checksum that can be used by Unicon Support to generate a validation code for repairing the license database. |
Troubleshooting
Copied!
Failed!