-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Affects Version/s: Discovery 7.1.0
-
Component/s: Assets Discovery
-
None
-
2
-
Severity 1 - Critical
-
16
Problem
Asset Discovery Collector 7.1.0 service fails to run with error "An item with the same key has already been added."
Environment
Asset Discovery 7.1.0
Steps to Reproduce
- Install Asset Discovery 7.1.0
- Run Collector as a service with a 1-min export interval
Expected Results
The same settings work in Asset Discovery 7.0.5 with the following collector.log, indicating it's checking the import folder every minute:
2/3/2025 1:19:45 AM: [Normal] There no .xml or .zip files in import folder 2/3/2025 1:20:45 AM: [Normal] There no .xml or .zip files in import folder 2/3/2025 1:21:45 AM: [Normal] There no .xml or .zip files in import folder 2/3/2025 1:22:45 AM: [Normal] There no .xml or .zip files in import folder 2/3/2025 1:23:45 AM: [Normal] There no .xml or .zip files in import folder 2/3/2025 1:24:45 AM: [Normal] There no .xml or .zip files in import folder 2/3/2025 1:25:45 AM: [Normal] There no .xml or .zip files in import folder
Actual Results
Instead of checking the import folder, Collector service 7.1.0 prints the following errors every minute:
2/3/2025 1:24:48 AM: [Error] Error occured on startup: 2/3/2025 1:24:48 AM: [Normal] Exceptions: 2/3/2025 1:24:48 AM: [Normal] An item with the same key has already been added. at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at Insight.Discovery.Collector.Program.Start(String[] args)
Collector 7.1.0 can still transfer files after restarting the service, indicating that it can successfully check the import folder during the start (but not afterwards).
