> For the complete documentation index, see [llms.txt](https://docs.videc.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videc.de/june5-3.7/en/fehlerbehebung-und-hilfe/faq.md).

# FAQ

|   |   |
| - | - |

| Reports must be assigned to a printer on the JUNE5 server. To do this, output the affected report in the ACRON Reporter with the "Change Printer" option enabled. In the dialog that follows, you must select a printer (e.g., Microsoft XPS Document Writer). If this measure is not sufficient, it may be necessary to reassign an existing printer to the report form in the Designer. |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

|   |   |
| - | - |

| <p>On the computer where the JUNE5 Server is running, it must be ensured that the ACRON Reporter can display operational data and reports properly. If this does not work, please check the following points in ACRON:</p><ul><li>Are the DBServer and DBEngine services running for the ACRON facility? (See ACRON Admin Tool)</li><li>Is there a valid license for ACRON? (See Reporter / Facilities / Facility Parameters, the ACRON license is displayed here)</li></ul> |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

|   |   |
| - | - |

<table data-header-hidden><thead><tr><th></th></tr></thead><tbody><tr><td><pre><code>-- T-SQL script to clean up a JUNE5 database
-- All historized data is deleted from the _HIST tables
-- SELECT * FROM sys.tables WHERE name like '%HIST%' order by name asc
</code></pre><pre><code>DECLARE @MyValue VARCHAR(MAX);
DECLARE MyCursor CURSOR FOR
SELECT Name FROM sys.tables WHERE name LIKE '%HIST' ORDER BY name ASC;
OPEN MyCursor;
FETCH NEXT FROM MyCursor INTO @MyValue;
WHILE @@FETCH_STATUS = 0
BEGIN
-- Print all _HIST tables
PRINT @MyValue;
-- Use dynamic SQL to execute TRUNCATE TABLEDECLARE @SQL NVARCHAR(MAX);SET @SQL = N'TRUNCATE TABLE ' + QUOTENAME(@MyValue);EXEC sp_executesql @SQL;FETCH NEXT FROM MyCursor INTO @MyValue;
END;
CLOSE MyCursor;
DEALLOCATE MyCursor;
-- Compress database
DBCC SHRINKDATABASE ('JUNE5Portal2022')
</code></pre></td></tr></tbody></table>

|   |   |
| - | - |

| <p>A proven approach for using JUNE5 is to follow these points:</p><p>1. Use HTTPS with a valid official certificate</p><p>2. Disable HTTP</p><p>3. Enable password security rules</p><p>4. Change default passwords, choose a strong password</p><p>5. Enable password security rules</p><p>6. No network shares on JUNE5 relevant directories</p><p>7. Restrict directories using operating system permissions</p><p>8. For internet use, use a JUNE5 installation within a DMZ</p><p>9. Regular backup of JUNE5 configuration</p><p>10. Regularly check log files for errors</p> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

|   |   |
| - | - |

| <p><strong>Error Image:</strong></p><p>When querying larger time ranges, a warning appears.</p><p><strong>Background:</strong></p><p>If multiple data sources are integrated, querying all data sources occurs when creating an event object. This can lead to runtime problems because the request is sent to all data sources, but they respond differently based on runtime. The result can be a limitation of the data or a timeout.<br><br><strong>Example:</strong></p><p>Data Source A (1,000 events per day)<br>Data Source B (10,000 events per day)<br>Data Source C (100,000 events per day)</p><p>The user creates an event object with a time range of 10 days. This "10 days" query is sent to data sources A, B, and C.<br>Based on the abort condition \<EventResultLimit>10000\<EventResultLimit> of the acron connectors, the result for the data sources is as follows:</p><p>Data Source A delivers 10 days (complete data)<br>Data Source B delivers 1 day (incomplete data)<br>Data Source C delivers 2.4 hours (incomplete data)</p><p>The user then sees a difficult to interpret result in the interface, but always with a note that records are missing.</p><p><strong>Remedy:</strong></p><ul><li>Limit the time range to, e.g., 1 minute. If this query runs quickly, the time range can be extended to, e.g., 1 hour or 1 day.</li><li>In the event object properties, limit the query to one data source.</li><li>Set an Item ID filter. The Item ID filter is passed through to the connector. This means data filtering occurs at the connector level.<br></li></ul> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

|   |   |
| - | - |

| In the settings, the option *Cache manual value sizes after each login!* is disabled. This option can be enabled in the settings, which are accessible from the right edge of the screen menu via the *Settings* command. The option is available in the *Offline Manual Value Entry* section. |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

|   |   |
| - | - |

| <p>The C:\ProgramData\VIDEC\JUNE5\Logs\Archives\*.\* files are cleaned up as follows:</p><p>C:\Program Files (x86)\VIDEC\JUNE5\NLog.config</p><p>contains the entry: maxArchiveFiles="100"</p><p>This means no more than 100 files are stored here. The oldest ones are automatically deleted. The value 100 applies to each log process. If 2 acron data processes and one acron report process are used, up to 300 files can be stored in that directory.</p> |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

|   |   |
| - | - |

| <p>1. Stop Configurator & JUNE5 services</p><p>2. Open C:\ProgramData\VIDEC\JUNE5\Configuration\ServerConfiguration.xml with an editor</p><p>3. Edit:</p><p>\<ConnectionString>Data Source=SERVER\JUNE5Portal; Initial Catalog=JUNE5Portal; Integrated Security=True; MultipleActiveResultSets=True;\</ConnectionString></p><p>To</p><p>\<ConnectionString>Data Source=SERVER\JUNE5Portal; Initial Catalog=JUNE5Portal2; Integrated Security=True; MultipleActiveResultSets=True;\</ConnectionString></p><p>4. Restart Configurator & services</p><p>When the JUNE5 service starts, it detects that a "JUNE5Portal2" database is not available in the SQL Server instance "JUNE5Portal" and creates it with all tables and structures. The old "JUNE5Portal" database is not deleted.</p> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

|   |   |
| - | - |

| <p><strong>Error Image:</strong></p><p>After synchronizing with the acron data source, new process parameters are not displayed in JUNE5 under Views.</p><p><strong>Remedy:</strong></p><p>Check whether the "API" checkbox under Provisioning is set for the process parameter in acron. Only process parameters for which this checkbox is set can be adopted by JUNE5.</p> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

|   |   |
| - | - |

| <p><strong>Error Image:</strong></p><p>After restoring the JUNE5 project backup, JUNE5 displays an error message that encryption certificates are not working.</p><p>Please note the option to back up the certificates as well! See section <a href="/pages/gaVT9nAizXb8gkywlM6p">Backup and Recovery of a JUNE5 Project</a>.</p><p><strong>Background:</strong></p><p>With the recovery, the Certificates directory is also recovered (C:\ProgramData\Videc\JUNE5\Certificates)</p><p>The files ca.cer and ca.key are stored here. These two files "do not match" anymore when recovery occurs on a different computer.</p><p>Recreating the certificates in the JUNE5 Configurator also does not work.</p><p><strong>Remedy:</strong></p><p>Delete both files ca.cer and ca.key. If necessary, the certificates must be deleted using mmc.exe and then recreated with the JUNE5 Configurator.</p><p>During recovery, in case of a certificate error, this is indicated by a corresponding warning message!</p> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

|   |   |
| - | - |

| <p><strong>Description:</strong></p><p>If Windows security does not work as desired during initial setup, the following points should be checked:</p><p><strong>Background:</strong></p><p>Domain = PlsAD</p><p>User = Alice</p><p>User Group = JUNE5Users</p><p><strong>1. Domain / User Authentication</strong></p><p>Independent of JUNE5, a domain user can be checked.</p><p>a. Simply create a shortcut for an application (e.g: Notepad.exe) on the desktop.</p><p>b. Hold Ctrl Shift and right-click on the application (Notepad)</p><p>c. Another entry appears: "Run as different user"</p><p>d. Now in the login dialog, enter the user / password specifying the domain (PlsAD\Alice)</p><p>If Notepad.exe can now be started, then successful authentication of "Alice" against the domain "PlsAD" has taken place.</p><p>If Notepad.exe cannot be started and the login dialog appears again, authentication is not possible. Further settings in JUNE5 will not help.</p><p><em>Tip:</em></p><p>If an error message appears in this attempt, authentication has probably occurred, but the permission to start a program is probably missing.</p><p><img src="/files/yGEuX5RxNvfD7o8Yr883" alt="Active Directory - Tip" data-size="original"></p><p><strong>2. Tenant = Domain Name</strong></p><p>The principle of JUNE5 Windows login is that the tenant name is the same as the domain name. If these two names do not match, correct login cannot occur.</p><p>Check the tenant name in the JUNE5 user management. It must be set to "PlsAD".</p><p><strong>3. AD Group Definition</strong></p><p>The principle of JUNE5 Windows login is that a user belongs to a Windows group (e.g., JUNE5Users).</p><p>If the group (JUNE5Users) cannot be defined in JUNE5 and in the AD, no login can occur.</p><p>Check the user group "JUNE5Users" in:</p><p>a. JUNE5 user management</p><p>b. Windows domain</p><p><em>Tip:</em></p><p>GPRESULT /V</p><p>Lists the user groups of a user.</p> |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.videc.de/june5-3.7/en/fehlerbehebung-und-hilfe/faq.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.