Release Notes › Known Issues › Endpoint Types › General › Modifying Endpoint Directly Causes Failure when Importing Between Endpoint and Provisioning Server.

Modifying Endpoint Directly Causes Failure when Importing Between Endpoint and Provisioning Server.

This section applies to all of the TSS connectors.

When the endpoint is modified directly (not using the Provisioning Server), a failure is returned when importing. This failure is because of inconsistent data between the endpoint and Provisioning Server. Two examples include:

• Someone removed tables from the MSSQL endpoint using native tools which resulted in some users getting resources that no longer exist.

  To resolve the failure, reexplore the endpoint using the Provisioning Server.

• Someone deleted some server roles on the endpoint. The account templates that still had those server roles assigned received extra roles that do not exist on the endpoint any more.

  To resolve this failure, manually remove those "removed" server roles from the account templates.

Restriction on the Endpoint Name for ACF2 ACFESAGE, RACF IRRDBU00, and TSSCFILE Connectors

Symptom:

Attempting to create an endpoint with an endpoint name such as “user test”, “user-test”, and “_usertest” on dumpfile connectors causes endpoint creation to fail with the message: 'Cannot create pool able connection factory'.

Solution:

Space characters are no longer allowed in endpoint names for the ACF2 ACFESAGE, TSSCFILE, or RACF IRRDBU00 connectors. The endpoint name for these connectors also has the following restrictions:

• Must be between 1 and 30 characters in length
• Starts with the alphanumeric characters
• Contains only alphanumeric and/or "_" character only.

Before you upgrade to this version, delete the existing mainframe dumpfile endpoints which are not according to the given restrictions.