Known issues specific to ActiveEfficiency Server features
|Tachyon Setup.exe does not populate "Enable Nomad Sync" settings during upgrade||Platform - Tachyon Setup.exe does not populate "Enable Nomad Sync" settings during upgrade|
Enable this option during an upgrade if it was previously enabled.
|Installer does not perform prerequisite check in unattended mode||The unattended installation succeeds even when a prerequisite is not met.|
|ActiveEfficiency version is not updated on Homepage.||When a ActiveEfficiency Server hotfix is applied which has changes specific to stored procedure(s) the new version is not displayed on ActiveEfficiency Server homepage.|
SVCUSER and SVCPASSWORD installer command-line fails during an unattended installation.
|The SVCUSER and SVCPASSWORD command-line parameters fail when you run an unattended installation using these parameters.||Run an unattended installation without using these properties on the command-line. Post-installation, stop the service, change the service user and restart the service.|
|ActiveEfficiency Service runs as Network Service after upgrade.||During an upgrade, the ActiveEfficiency service account is reset to the Network Service account and does not retain user information used for the process.||Manually change the account in the Services interface post upgrade.|
|Prompt to reboot the server during an ActiveEfficiency installation, upgrade or when you uninstall it.||There may be instances where you are prompted to to restart the server in order to complete the installation. In the event that this happens, we recommend you do.|
|The installer fails when installing in an environment where TLS 1.0 has been disabled.||The installer fails when installing in an environment where TLS 1.0 has been disabled.|
In environments where TLS 1.0 has been disabled, use one of the following options
a) interactive installation - check the TLS 1.0 disabled – install using TLS 1.1/1.2 checkbox on the Database Server screen in the installer
b) command-line installation - include ENABLETLS12=1 on the installer command-line.
The ENABLETLS12 installer property is not completely type checked and must only be set to a value of 1 on the installer command line. If it is set to any other value, installation will continue but will fail because of the incorrect value if TLS 1.0 is disabled.
|Installer unable to connect to the database when you run a repair on ActiveEfficiency.|
In environments where TLS 1.0 has been disabled, if you opt to repair ActiveEfficiency by choosing the Repair option from its installer, you will be prompted with this error:
Error 27502: Could not connect to Microsoft SQL Server ... SSL Security error. (18)
This is because the SQL Server connection string used in the original installation is set to SQLOLEDB and cannot be changed to SQLNCLI11.
Option1: Uninstall and re-install ActiveEfficiency Server.
|Content pre-caching on Nomad 6.3 clients fail in an environment where TLS 1.0 has been disabled|
Nomad 6.3 client requires the latest hotfix for pre-caching to work in environments that have TLS 1.0 disabled.
The issue is not with ActiveEfficiency Server and does not affect Nomad 7.0.
|Install the latest accumulated hotfix for NomadBranch 6.3 client.|
|Pre-cached jobs are not listed in the Configuration Manager console using Nomad 6.3 AdminUI Extensions in an environment where TLS 1.0 has been disabled.|
Nomad 6.3 AdminUI Extentions requires the latest hotfix for pre-caching to work in environments that have TLS 1.0 disabled.
The issue is not with ActiveEfficiency Server and does not affect Nomad 7.0.
|Install the latest accumulated hotfix for NomadBranch 6.3 AdminUI Extensions.|
|Content can be registered with greater than 100% in ActiveEfficiency.||Under certain circumstances the Nomad clients may register content with ActiveEfficiency that shows that the client has more than 100% of the content.|
|Nomad Dashboard: Pre-cache download Progress tile not updating correctly.||If the Nomad cache has content that is more than 30 days old which is references in a task sequence, an In-progress or Not Started error is displayed when the task sequence is pre-cached.|
|Nomad Dashboard: ClientHealth expanded view list shows incorrect records when exported to docx.||The Client Health tile content when exported to Word document lists incorrect records.|
|Nomad Dashboard: Dashboard shows 500 Server Error.|
ActiveEfficiency Nomad Sync was not enabled during installation.
ActiveEfficiency does not add NT/Network Authentication User as db_owner to CM database. Due to which dashboard throws server not available error, as it fails to fetch the records from CM Database.
|Nomad Dashboard: Package list does not show up in Task Sequence list in dynamic variable.||This issue seems to have the limitation of SCCM 2012 need a discussion but no major impact.|
|Nomad Dashboard: Pre-cache job doesn't show the list of items in the dropdown.||This issue is intermittent and occurs 4 out of 10 times.|
|Nomad Dashboard: Content Still persists on the list when the disk has been cleaned on client machines.||Nomad cache remains in ActiveEfficiency database even after Cache Cleaning is done on clients.|
|Nomad Dashboard: Caching Matrix tile shows incorrect record even after CacheClean has been done .||Nomad cache remains in ActiveEfficiency database even after Cache Cleaning is done on clients.|
|Nomad Dashboard: Tiles report incorrect information.||The total number of packages displayed may not tally with the number on the site. It also does not give an indication of the devices the information is collected from.|
|Log files fail to capture events after an upgrade.||On occasion, service.log will fail to log events after an upgrade.||Delete the existing log file and restart the 1E ActiveEfficiency Server service.|
|NomadBranch.exe continuously added to firewall exceptions.||Client health adds NomadBranch.exe to the exceptions list every time it runs even though the exception is already in place.|
|Nomad license state fails when the license expires.||The Nomad Branch service stops but ClientHealth.log reports the service is running.|
|When installing/upgrading ActiveEfficiency Server using the command-line and setting the alternative service credentials (SVCUSER and SVCPASSWORD), if these are entered in lower case the values they are set to will appear in plain text in the installer log.|
When installing/upgrading ActiveEfficiency Server via the command-line, using the SVCUSER and SVCPASSWORD properties, you should enter the property labels in upper case to prevent their values from appearing in the installer log. For example, the following sets the service user and password to AcmeUser and MyPassword. Spaces in the password require quotes.
|Upgrading ActiveEfficiency hangs during the database upgrade phase of the install when the existing ActiveEfficiency database is hosted on SQL Server 2012.||When upgrading ActiveEfficiency to version 1.7, or above, the installer occasionally hangs when attempting to access SQL Server 2012. If this occurs restarting SQL Server and then re-running the installation will fix the issue.|
|ActiveEfficiency Synchronization Manager fails to schedule a task if ||If the Windows Task Scheduler already contains a task with the name ||Ensure that there are no tasks in the Task Scheduler with the name ActiveEfficiency, otherwise the directory cannot be created and no further ActiveEfficiency Synchronization Manager tasks may be added.|
|The Scout performance appears to degrade and exceptions appear in the Scout.log file related to sending items to ActiveEfficiency.|
If the Scout execution appears to get progressively slower and on examining the Scout.log file you see errors similar to the following:
During the initial ActiveEfficiency sync, SQL Server will, if necessary, automatically increase the size of the ActiveEfficiency data and log files to accommodate discovered devices as they are scanned. The process of increasing the database size can be quite resource-intensive and may interfere with ActiveEfficiency’s ability to collect and store the data being supplied by the Scout.
Symptoms of this problem include a progressive slowdown in the rate at which devices are added to the database and/or high disk I/O against the database files themselves. In extreme cases this may result in timeouts and potentially the loss of some device information.
To ensure that this scenario does not arise, it is recommended that the data and log files be sized appropriately prior to the first sync. This is a one-time process.
An appropriate initial size for the database files would be around 10GB for the data file and 10GB for the log file, for an organization with 100,000 seats. For other sizes, you can adjust this proportionally. Other than a small amount of potentially wasted disk space there are no negative issues associated with over-sizing the database so you can therefore, if you wish, simply use the above figures in almost all cases.
To resize the database files, use the following steps:
|Installing ActiveEfficiency on a server with UAC enabled may cause installation problems.||When installing ActiveEfficiency onto a server with UAC enabled, run the installer from a command-prompt with elevated permissions. A reboot may be necessary.|
Previous settings do not appear in installer during upgrade.
|Upgrade from certain earlier releases does not show previous settings in the installer dialog. You will need to reset these during installation.|
|Database installation does appear to install correctly on the local host.||Entering |
|Installation fails sporadically with a certificate installation problem.||On rare occasions, installation fails due to a certificate installation problem. A subsequent repeat of the installation will generally succeed.|
|Installation will fail if MSMQ is not present for split installations.||The ActiveEfficiency Server installer does not perform a prerequisite check for MSMQ during a split installation. The installation will subsequently rollback if MSMQ is not actually installed.|
|The ActiveEfficiency server logs reports exceptions related to Nomad 2012.||Log reports an exception when Nomad 2012 fails to retrieve content (this is largely a cosmetic logging issue for a genuine error condition)|
|AppClarity 5.2 installation fails if Windows Authentication has been enabled on the ActiveEfficiency website.||To install AppClarity 5.2 you need to ensure that the authentication for the ActiveEfficiency website is set to anonymous access for the duration of the installation. This may be subsequently set back to Windows Authentication.|
|Certain devices not imported into AppClarity 5.2 from ActiveEfficiency.|
Attempting to import a device into AppClarity 5.2 via the ActiveEfficiency Integrator, where the device lacks a SystemProperties entity in ActiveEfficiency, will log errors in the Integration Host logfile which commence with:
and contain several lines of HTML indicating that an error occurred. The device is not imported but other devices are not affected.
|Customizations to the ActiveEfficiency configuration file are overwritten during upgrade.||If you have made customizations to the ActiveEfficiency configuration file, you will need to retain a copy and re-apply these, where appropriate, following an upgrade.|
|When Nomad agent is re-installed, it creates duplicate entries in ActiveEfficiency database.||If content registration is enabled on Nomad, then on re-installing Nomad all the content gets re-registered on AE, resulting in duplicate database entries.|
|Content download count appears as twice for a machine with two NIC.||Caching metrics tile displays a single content download as downloaded twice on the machine having two NIC|
WAN saving information is visible to unauthorized users on the Nomad Dashboard.
|Users who do not have access to the Nomad Dashboard are able to see WAN saving information.|
|ActiveEfficiency website throws a 404 Page Not Found error.||Server returns 404 error when browsing to ActiveEfficiency using a URL with / appended to the end. For example https://FQDN:4443/Activeefficiency/nomaddashboard/||Specify URL without appending "/". For example|
Know issues specific to the ActiveEfficiency Scout
|Migration mode appears not to work when attempting to test or run a schedule from the ActiveEfficiency Synchronization Manager.|
When attempting to define a schedule using the ActiveEfficiency Synchronization Manager, after Migration mode has been selected during installation, you will see an error in the Scout.log file similar to the following:
The reason for this is that ActiveEfficiency Synchronization Manager does not add the Migration mode option to the Scout command-line. To run the scout in Migration mode you must set the Migration mode option.
To do this manually edit the DailyScheduledTask.xml file (in ProgramData\1E\ActiveEfficiency).
Add the text <Arguments>modes=Migration</Arguments>, as in the following example:
When manually setting a schedule to run the scout outside the Synchronization Manager, you must include the Migration mode option on the scheduled command-line:
|The Test Run button does not work.||The Test Run button will not work if there is no time set for a schedule in the ActiveEfficiency Synchronization Manager.||You must add a time to a schedule in order to perform a test run using the ActiveEfficiency Synchronization Manager.|
|When using multiple data sources some devices may have their device type set to NULL.||Devices retrieved from multiple sources may have their device type set to NULL if a later alternative data source does not supply the type.|
|Data for some devices may not be up to date.||Invalid install\usage data where the date is set far in the future will result in the data for the device being rejected during import.|
|AppV installations may not be completely accurate.||A virtualized installation which is subsequently not found in a later scan does not get deleted from the ActiveEfficiency Server.|
|In certain circumstances the Scout cannot write to the Scout logfile.||If the scout is installed as a user with high privileges and subsequently run with an account that has lesser privileges, it may not be able to write to its logfile due to Windows permissions.||This may be resolved by deleting the logfile.|
|When the scout is run in Migration mode you cannot collect data on AppV installations||By design, Migration mode does not include AppV installations.||You will need to suspend management of AppV applications during the migration process.|