The ILST is failing to complete

After running the ILST, it fails to perform any actions within the digital workplace. 

Whenever the ILST is run it creates a log file in the same location as the ILST executable. This log file contains all the actions that the ILST is performing, and will indicate any errors that it encounters. Match these error messages with those below to identify the needed troubleshooting steps.

The ILST is unable to connect to the Active Directory via an LDAP Connection.

Identify this error by the following logging message:

Error during Sync occurred: The LDAP server is unavailable.

To resolve this issue:

• Verify that the <Host> in the <Connection> section of the config files is correct.
• Verify that you can connect to and query your AD from the location of the ILST using an LDAP browser. If you cannot, there is likely a firewall or security setting that is preventing connections.

The <Connection> has not been configured correctly

Identify this error by the following logging message:

Error during Sync occurred: The object does not exist.

To resolve this issue:

• Verify that the <BaseDN> exists.
• Verify that the <BaseDN> does not contain any encoded characters.
• Verify that the <Username> is not a full distinguished name of a form like: "cn=username,ou=users,dc=community,dc=com".
• Verify that the  <Username> and <BaseDN> match a user in the AD and that user has permission to query other users. 

The ILST cannot authenticate with the provided user

Identify this error by the following logging message:

Error during Sync occurred: The supplied credential is invalid

To resolve this issue:

• Verify that the <Username><Password> combination in the <Connection> section of the config are valid AD credentials. 
• Verify that the <Username> <Password> combination in the <CommunityApi> section of the config are valid Igloo administrator credentials.
• Verify that the <Domain> in the <CommunityApi> corresponds to the correct digital workplace domain.

Note: When checking passwords, it can be helpful to re-enter and encrypt them again.

A provided password has incorrect formatting

Identify this error by the following logging message:

Error during Sync occurred: Index was outside the bounds of the array.

To resolve this issue:

• Verify that passwords do not contain any XML special characters (<, >, &, ', "). 
• Re-enter passwords as plain text in both the <Connection> and <CommunityAPI> sections of the config file. Then encrypt them once.

A <connectionId> tag may be missing or misspelled

Identify this error by the following logging message:

Error during Sync occurred: Object reference not set to an instance of an object.

To resolve this issue:

• Verify that all <UserAccout> and <Group> sections have a <connectionId> value. This value should match the Id of the <Connections> block that they are associated with. The default for this value is <ConnectionId>1</ConnectionId> .

The page size of queries to the AD is too large

Identify this error by the following logging message:

Error during Sync occurred: The size limit was exceeded

To resolve this issue:

• Lower the <PageSize> in the <Connection> section of the ILST config. The default value is 1000, try lowering this to 500.

A digital workplace group GUID is not valid

Identify this error by the following logging message:

Unhandled Exception: Unhandled Exception: System.InvalidOperationException: There is an error in XML document (1, 418). ---> System.FormatException: Unrecognized Guid format.

To resolve this issue:

• Verify that all <IglooGroup> or <GroupID> fields have a GUID in them that matches an existing group GUID in your digital workplace. 

A required value is missing in the config file.

Identify this error by the following logging message:

Unhandled Exception: System.InvalidOperationException: There is an error in XML document (1, 36). ---> System.FormatException: Input string was not in a correct format.

To resolve this issue:

• Verify that all fields in the config file have values.
• Verify that all fields have both a beginning and end tag (ex. <BaseDN></BaseDN>).

The ILST config file has an XML formatting error

Identify this error by the following logging message:

Unhandled Exception: System.Xml.XmlException

To resolve this issue:

• Validate the XML of the config file using an XML checker, or by comparing to a clean config file. These can be used to catch common XML issues:
  • A missing or extra XML <tag>
  • A missing or extra "<" or ">" symbol
  • A tag that has been <!--commented--> out

Duplicate <Attribute>

Identify this error by the following logging message:

Error: [An item with the same key has already been added.]

To resolve this issue:

• Verify that an <Attribute> value does not duplicate another <Attribute> value. Remove the duplicate value.