Page Comparison

Problem

Solution

This happens when loading the ‘Target System Name’ Name' into the Assessor-GUI, or running a Basic/ local scan, with ‘not accepted’ information.

To resolve this, you DO NOT need to change the name of the physical Target you would like to asses. If you have built the XML for CLI make sure that the <session id=” ”> fields do not start with one of the below restricted characters. If using the Assessor-GUI the same restrictions apply to the ‘Target System Name’ field.

The' Target System Name' used by the Assessor-GUI are more or less arbitrary names (used for continuity with Assessor-CLI.xml config files.). The <session ID> / Target System Name could be anything as long as it conforms to the restrictions in the next paragraph. It could be Windows-Assessment-123456 or even Toast - it is completely your choice, excepting the following restrictions:

Practical restrictions of an NCName
The practical restrictions of NCName are that it cannot contain several symbol characters like : @ $ % & / + “ ; whitespace characters or different parenthesis. Furthermore, an NCName cannot begin with a number, dot or minus character although they can appear later in an NCName

Resolution

If you are running a local scan via the GUI on a machine that starts with a ‘forbidden’ character:

1. Choose Advanced Scan>

2. Add Remote or Local Target System>

3. Target System Type>

4. Local.

If you’re running a remote GUI scan, you will need to remove the restricted character that starts the name of the Target System Name.

Keywords;

Content by Label