Contents x
      SmartIQ2CM Troubleshooting Guide
      • 21 Jun 2022
      • 3 Minutes to read
      • Contributors
      • Print
      • Dark
        Light
      • PDF
      Contents

      SmartIQ2CM Troubleshooting Guide

      • Updated on 21 Jun 2022
      • 3 Minutes to read
      • Contributors
      • Print
      • Dark
        Light
      • PDF
      Article Summary

      OVERVIEW

      The following table below lists some of the common connector issues you may experience along with the possible cause and resolution.

      ERROR DESCRIPTIONPOSSIBLE CAUSE/RESOLUTION
      Send to CM Action failed: Could not load file or assembly 'HP.HPTRIM.SDK, Version=8.X.X.X, Culture=neutral, PublicKeyToken=93ab772ef8ad9a2e' or one of its dependencies. The system cannot find the file specified.This can occur when there is a mismatch between the connector and the version of Content Manager
      Send to CM Action failed: The type initializer for 'HP.HPTRIM.SDK.trimPINVOKE' threw an exception.This can occur when the 32bit Content Manager client is installed and the SmartIQ application pool is not set to Enable 32-Bit Applications.
      Please refer to INSTALLATION GUIDE
      Send to CM Action failed: Unable to connect to Database: Error connecting to the Content Manager dataset 'XX' on Content Manager Workgroup Server 'XXXXXX'. Impersonated logon failed. The account DOMAIN\Account is not trusted to impersonate other Content Manager users.This will mean the account running the SmartIQ application pool is not added to the trusted accounts in Content Manager Enterprise Studio
      Please refer to the ACCOUNT SETTINGS (SMARTIQ APPLICATION POOL) section
      Send to CM Action failed: Unable to connect to Database: Error connecting to the Content Manager dataset 'XX' on Content Manager Workgroup Server 'XXXXXX. The dataset with the ID 'XX' is not available. Possible causes are: it is registered on a different Content Manager Workgroup Server to the one selected, the schema of this dataset is not supported by this Content Manager Workgroup Server, or the network connection between the Content Manager Workgroup Server and the database server has failedThis can be caused by an incorrect Dataset ID being entered into the Connector Settings
      Send to CM Action failed: Unable to connect to Database: Error connecting to the Content Manager dataset 'XX' on Content Manager Workgroup Server 'XXXXXX'. Cannot connect to Content Manager Workgroup Server on 'XXXXXXX'. [RCF: DNS lookup of network address failed, for name "XXXXXX". OS: 11001 - No such host is known.]This can be caused by an incorrect Workgroup Server or Port being entered into the Connector Settings
      Send to CM Action failed: Unable to connect to Database: Database connection failed. The user name or password is incorrect. (0x0000052e).As the error suggests it’s most likely an incorrectly entered username and/or password in the Connector Settings
      Send to CM Action failed: You do not have create record access for this record type.The account specified in the Connector Settings does not have the appropriate permissions in Content Manager
      This specific error message refers to the ‘Can Use’ permissions under the Access Controls of the record type attempting to be made in Content Manager.
      Using an account with Administrator access and Highest Security avoids this issue.
      If you cannot use an Administrator account with Highest Security, you will need to ensure your Content Manager is configured appropriately.
      Send to CM: Unable to attach Action: Default Assignee not setThis error is displayed if “Attach Action” has been included in the “Send to CM” Action, but Attach Action – Default Assignee has not been included. If this is the case, then the document will get created and attached to the record, but the project status will be set to “Failed” and this error message will be shown.
      Send to CM Error: Unable to set Access ControlYou may receive the below error if you set an access control input to include a combination of location URI’s and the value of zero:
      Send To CM Error: Unable to set Access Control: Contribute Contents: Could not find the Location with a unique row identifier of 0. Possible causes are: no Location exists with the identifier supplied; the Location has recently been deleted; access to the specified Location is restricted.
      Send to CM Error: Unable to Create New PartYou may receive the below error if you try to create a new record part, where the part attempting to be created is greater than 999. Content Manager only allows for 999 parts on a record.
      Send To CM Error: Unable to create new part: A maximum of 999 Parts can be created for a record.
      Was this article helpful?
      What's Next