An item with the same key has already been added

[udotrautmann]

Bug description

New-AsBuiltReport : An item with the same key has already been added.
At line:1 char:1

• New-AsBuiltReport -Report VMware.vSphere -Target "xc-vca-01.sysc-chem ...

•   + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-AsBuiltReport
  
  

Command-line input

New-AsBuiltReport -Report VMware.vSphere -Target "" -Username "administrator@vsphere.local" -Password "password" -Format TEXT,Html,Word -OutputFolderPath "C:\Doku\VMware" -Timestamp -AsBuiltConfigFilePath "C:\Doku\AsBuiltReport.json" -Verbose

Steps to reproduce

any time trying to create a new report with the cli above I getting this error at the end of the runtime and there is no report created

Expected behaviour

successful create report

Screenshots

No response

Operating System

Windows Server 2025 Standard
PowerShellVersion 5.1.26100.3624

PowerShell Version

Name Value

---

PSVersion 5.1.26100.3624
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.26100.3624
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

PowerShell Modules

Name Version

---

AsBuiltReport.Core 1.4.3
AsBuiltReport.VMware.vSphere 1.3.4.1
PScribo 0.11.1

Additional Context

No response

Before submitting

• I have read and followed the bug reporting guidelines.
• I have read the documentation, and referred to the known issues before submitting this bug report.
• I have checked for previously opened & closed issues before submitting this bug report.

[tpcarman]

Hi,

Would you mind narrowing down the issue by trying the following;

• Generate a report with a single format at a time (Word, HTML, or Text)
• Modify the repost JSON configuration file and disable all reporting sections. Gradually increase the InfoLevel for each section until you encounter the error.

Finally, please share the verbose output to assist identifying where the issue may lie.

Thanks.

[udotrautmann]

The error is getting only for the report format Text. All other reports are running successfully with the standard InfoLevel settings.

[tpcarman]

Can you further isolate the issue? What is the verbose output prior to the error occurring? Can you determine which section of the report it is happening?

[udotrautmann]

It is coming at the end of the script... at the moment where the document should be created. But the creation of the document will not be happened.

AUSFÜHRLICH: [ 08:13:51:102 ] [ Document ] - Processing section 'xc-vca-01.sysc-chemnitz.de' completed.
AUSFÜHRLICH: [ 08:13:51:282 ] [ Document ] - Document 'VMware vSphere As Built Report - 2025-05-06_08.07.44' processing completed.
AUSFÜHRLICH: [ 08:13:51:297 ] [ Document ] - Total processing time '5,80' minutes.
WARNUNG: The 'DrsMode' property of Cluster type is deprecated. Use the 'DrsAutomationLevel' property instead.
New-AsBuiltReport : Ein Element mit dem gleichen Schlüssel wurde bereits hinzugefügt.
In Zeile:1 Zeichen:1

• New-AsBuiltReport -Report VMware.vSphere -Target "xc-vca-01.sysc-chem ...

•   + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-AsBuiltReport
  

[aledr]

Hi.

Same issue here with the Text format.
How can I help to diagnose?

[tpcarman]

VERBOSE: [ 15:21:18:667 ] [ Document ] - Connecting to vCenter Server 'labvcsa.lab.local'.
VERBOSE: [ 15:21:19:216 ] [ Document ] - Checking vCenter user privileges.
VERBOSE: [ 15:21:19:277 ] [ Document ] - Creating VM lookup hashtable.
VERBOSE: [ 15:21:19:864 ] [ Document ] - Creating VMHost lookup hashtable.
VERBOSE: [ 15:21:19:944 ] [ Document ] - Creating Datastore lookup hashtable.
VERBOSE: [ 15:21:19:985 ] [ Document ] - Creating VDPortGroup lookup hashtable.
VERBOSE: [ 15:21:20:010 ] [ Document ] - Creating EVC lookup hashtable.
VERBOSE: [ 15:21:20:144 ] [ Document ] - Checking for VMware Update Manager Server.
VERBOSE: [ 15:21:20:145 ] [ Document ] - Checking for VxRail Manager Server.
VERBOSE: [ 15:21:20:145 ] [ Document ] - Checking for VMware Site Recovery Manager Server.
VERBOSE: [ 15:21:20:145 ] [ Document ] - Checking for VMware NSX-T Manager Server.
VERBOSE: [ 15:21:20:146 ] [ Document ] - Collecting tag information.
VERBOSE: [ 15:21:20:443 ] [ Document ] - Collecting labvcsa.lab.local advanced settings.
VERBOSE: [ 15:21:20:495 ] [ Document ] - Processing section 'labvcsa.lab.local' started.
VERBOSE: [ 15:21:20:496 ] [ Document ] - vCenter InfoLevel set to 0.
VERBOSE: [ 15:21:20:497 ] [ Document ] - Cluster InfoLevel set to 1.
VERBOSE: [ 15:21:20:530 ] [ Document ] - Collecting Cluster information.
VERBOSE: [ 15:21:20:530 ] [ Document ] - Processing section 'Clusters' started.
VERBOSE: [ 15:21:20:531 ] [ Document ] - Processing paragraph 'The following sections detail the co[..]'.
VERBOSE: [ 15:21:20:531 ] [ Document ] - Processing blank line.
VERBOSE: [ 15:21:20:652 ] [ Document ] - Processing table 'Cluster Summary - labvcsa.lab.local'.
VERBOSE: [ 15:21:20:654 ] [ Document ] - Processing section 'Clusters' completed.
VERBOSE: [ 15:21:20:654 ] [ Document ] - ResourcePool InfoLevel set to 0.
VERBOSE: [ 15:21:20:654 ] [ Document ] - VMHost InfoLevel set to 0.
VERBOSE: [ 15:21:20:654 ] [ Document ] - Network InfoLevel set to 0.
VERBOSE: [ 15:21:20:655 ] [ Document ] - vSAN InfoLevel set to 0.
VERBOSE: [ 15:21:20:655 ] [ Document ] - Datastore InfoLevel set to 0.
VERBOSE: [ 15:21:20:655 ] [ Document ] - DSCluster InfoLevel set to 0.
VERBOSE: [ 15:21:20:655 ] [ Document ] - VM InfoLevel set to 0.
VERBOSE: [ 15:21:20:655 ] [ Document ] - VUM InfoLevel set to 0.
VERBOSE: [ 15:21:20:656 ] [ Document ] - Processing section 'labvcsa.lab.local' completed.
VERBOSE: [ 15:21:20:657 ] [ Document ] - Document 'Sample VMware vSphere As Built Report' processing completed.
VERBOSE: [ 15:21:20:657 ] [ Document ] - Total processing time '5.22' seconds.
New-AsBuiltReport: An item with the same key has already been added. Key: LinkedView

I have identified that this issue occurs when the following sections are configured with an InfoLevel to >=1

"InfoLevel": {
"Cluster": 1,
"ResourcePool": 1,
"VMHost": 1,
"Network": 1
}

I'll need to examine the PScribo repository to identify any potential issues with PScribo's text output plugin