'Input String was not in a correct format'

Applies To: SecurityEXPERT

This .NET message usually occurs when opening a scan report, and is most likely caused by a security point issue where something expected is missing.

Currently, finding the offending security point requires eliminating security points from the policy definition and re-scanning/re-opening the scan report in a trial and error fashion, until locating the offending security point.

On XP Pro for example, it was found the security point below caused the error above.

Once the security point is identified, the underlying problem must be identified, in this case two missing DWORD values expected, but not present on a target machine.

Shown below, the two DWORDS "ntlmminclientsec" and "ntlmminserversec" were not present in the highlighted key and needed to be manually created. This allows opening the scan report.