EvotecIT/Testimo

Error when running invoke-testimo

dkervin opened this issue · 23 comments

When I run this command I receive the following error:
Start-Testing : Cannot process argument transformation on parameter 'ExtendedValue'. Cannot convert value to type System.String.
At C:\Program Files\WindowsPowerShell\Modules\Testimo\0.0.48\Testimo.psm1:4939 char:13

  • $null = Start-Testing -Scope 'Forest' -ForestInformation $ForestD ...
    
  •         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : InvalidData: (:) [Start-Testing], ParameterBindingArgumentTransformationException
    • FullyQualifiedErrorId : ParameterArgumentTransformationError,Start-Testing

Thoughts?

Which version?

What did you run to execute it?

Simly ran invoke-testimo with no parameters.

Any specific test it failed on?

As noted in my first message, it errors on line 4939 of testimo.psm1 when it tries to run the start-testing command.

Ye, I was more interested which Testimo test failed

image

In this case it seems it failed on Time Synchronization. I'll fix it today - I've been reworking Testimo in last few versions and broke it in the process. sorry for that

Mine is a bit different;
Cannot process argument transformation on parameter 'ExtendedValue'. Cannot convert value to type System.String.

Same issue?

Should be, i'll fix both

Great, thank you!

New version is released. Please update and try again. Please be aware that running Invoke-Testimo without picking tests you need will work but HTML report will be very slow when switching tabs or scrolling. I've to resolve this issue, but for now it is what it is. This is because each tab has lots of tables that are refreshed on tabs switch.

I've got the same issue on 0.0.49, at a different point

Invoke-Testimo
[i][Testimo] Version [Informative] [Current/Latest: 0.0.49 at 01/25/2021 16:16:52]
[i][Testimo] Using configuration defaults [Informative] [No configuration provided by user]
...
Aging primary DNS Zone [Informative]
Start-Testing : Cannot process argument transformation on parameter 'ExtendedValue'. Cannot convert value to type System.String.
At C:\Program Files\WindowsPowerShell\Modules\Testimo\0.0.49\Testimo.psm1:5102 char:17
+ ...             Start-Testing -Scope 'Domain' -Domain $Domain -DomainInfo ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Start-Testing], ParameterBindingArgumentTransformationException
    + FullyQualifiedErrorId : ParameterArgumentTransformationError,Start-Testing

If you run it like that? Does it work?

invoke-testimo -Sources DomainDnsZonesAging -ShowReport

OK, I think i found the reason. If the cmdlet would give more than 1 error it would fail because it expected one string output when it was given an array of strings. Please update and test again.

You need to provide more data - just line numbers is not enough. Which test, what error message

Did you do

Install-Module Testimo -Force
Import-Module Testimo -Force

image

The line number is very unlikely to give error.

invoke-testimo -Sources DomainDnsZonesAging -ShowReport
[i][Testimo] Version [Informative] [Current: 0.0.49, Published: 0.0.50 at 01/25/2021 18:04:54. Update?]
[i][Testimo] Using configuration defaults [Informative] [No configuration provided by user]
[i][Forest] Forest [Informative]

   [i][ad.XXXXXX.com] Domain ad.XXXXXX.com [Informative]
      [i][ad.XXXXXX.com] Aging primary DNS Zone [Informative]
Start-Testing : Cannot process argument transformation on parameter 'ExtendedValue'. Cannot convert value to type System.String.
At C:\Program Files\WindowsPowerShell\Modules\Testimo\0.0.49\Testimo.psm1:5102 char:17
+ ...             Start-Testing -Scope 'Domain' -Domain $Domain -DomainInfo ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Start-Testing], ParameterBindingArgumentTransformationException
    + FullyQualifiedErrorId : ParameterArgumentTransformationError,Start-Testing
invoke-testimo -Sources DomainDnsZonesAging -ShowReport
[i][Testimo] Version [Informative] [Current/Latest: 0.0.50 at 01/25/2021 18:04:54]
[i][Testimo] Using configuration defaults [Informative] [No configuration provided by user]
[i][Forest] Forest [Informative]

   [i][ad.XXXXXX.com] Domain ad.XXXXXX.com [Informative]
      [i][ad.XXXXXX.com] Aging primary DNS Zone [Informative]
         [t][ad.XXXXXX.com] Aging primary DNS Zone [Fail] [Failed to get the zone information for ad.XXXXXX.com on server dc00.ad.XXXXXX.com.; Failed to get the zone information for ad.XXXXXX.com on server dc01.ad.XXXXXX.com.]
         [t][ad.XXXXXX.com] Zone DNS aging should be identical on all DCs [Fail] [Input data not provided. Failing test.]
      [i][ad.XXXXXX.com] Aging primary DNS Zone [Time to execute tests: 0 days, 0 hours, 0 minutes, 5 seconds, 271 milliseconds][Tests Total: 2, Passed: 0, Failed: 2, Skipped: 0]
   [i][ad.XXXXXX.com] Domain ad.XXXXXX.com [Time to execute tests: 0 days, 0 hours, 0 minutes, 5 seconds, 578 milliseconds][Tests Total: 2, Passed: 0, Failed: 2, Skipped: 0]
[i][Forest] Forest [Time to execute tests: 0 days, 0 hours, 0 minutes, 5 seconds, 671 milliseconds][Tests Total: 2, Passed: 0, Failed: 2, Skipped: 0]

So that bit seems to be fixed, thanks!

Cool! Thank you.

I'm having this error message when I run Invoke-Testimo. Not sure why. Is there anything I'm doing wrong ? Is Testimo supposed to be run ONLY on domain controllers ?

[i][Testimo] Version [Informative] [Current: 0.0.72]
[i][Testimo] Using configuration defaults [Informative] [No configuration provided by user]
Get-WinADForestDetails : Cannot index into a null array.
At C:\Program Files\WindowsPowerShell\Modules\Testimo\0.0.72\Testimo.psm1:6298 char:22

  • ... stDetails = Get-WinADForestDetails -WarningVariable ForestWarning -Wa ...
  •             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : InvalidOperation: (:) [Get-WinADForestDetails], RuntimeException
    • FullyQualifiedErrorId : NullArray,Get-WinADForestDetails

image

I would suggest opening a new issue. You can run it on Windows 10 without any issue. Most likely something is different on your domain that makes it unique, and something that I don't expected to find.

Please check: Get-ADForest, Get-ADDomain - does that work properly?