Troubleshooting - Intergraph Smart Materials - 2.3 - Installation & Upgrade - Hexagon

Intergraph Smart Materials Web API Installation (2.3)

Language
English
Product
Intergraph Smart Materials
Subproduct
Web API
Search by Category
Installation & Upgrade
Version Smart Materials Web API
2.3

This section provides information about the errors that can occur during the web API installation and their respective solutions.

Error 1

While running the config tool , if configure web application failed due to error "HTTPsx.509 certificate's thumbprint is not specified ".

Solution 1

Check if the SSL Certificates are valid or not. If certificate is invalid, follow these steps to resolve the issue:

  1. Check, if https is enabled and correct Https Certificate is displayed as shown:

    Troubleshooting 1

  2. If no certificate is displayed, then navigate to IIS, and select Default Website.

  3. Right click on Default website and select Edit Bindings. Remove the existing https binding.

  4. Load the valid SSL certificate in IIS> Server certificates.

  5. Then re-run the configuration tool and enable Https, and then check if valid certificate is displayed against HttpsCertificate. Provide port number, click Next, and then Finish.

    This automatically adds https binding to the WebSite with the given port number.

Error 2

In Enable Smart API OData Feed Connector in Power BI Desktop, while connecting to Get Data> Integraph Smart API, if you are getting the following error.

Solution 2

In this case, the Base URI is not configured in the webcomic file properly. To resolve this look Configure Smart Materials Web API and repeat the steps again.

Error 3

After enabling API OData feed connector in Power BI Desktop, if you are trying to connect to SAM and getting the following error "Provided redirect URI is not registered for the client".

Solution 3

You need to specify the redirect URL in the registered client in SAM. URL is https://preview.powerbi.com/views/oauthredirect.html.

Error 4

If you are accessing any API, and receiving the following error message.

"Error Code": "12154"

"Message": "ORA-12154: TNS: could not resolve the connect identifier specified".

Solution 4

Please ensure that the TNS details in the web.config file are correct. TNS details includes datasource and connection strings details. Sample path to access web.config file is " C:\Program Files\INTERGRAPH\Smart Materials WebAPI Current\Web\API".

Error 4 solution image

Error 5

While accessing any API, if you receive the following error message.

"Message": "Token validation failed or failed to authorize role(s) using the API authorization filter."

Solution 5

Please ensure that a token value is assigned to access the API.

Token value image

  • Please ensure that the token value is active. If in case the token has expired, try getting a new token, and use that token value to access the API.

Error 6

While accessing any API, if you receive the following error message.

"Message": "Access token is addressed to a different audience".

Solution 6

Please ensure that the token value assigned to access the API does not belong to a different environment.

Error 7

While accessing the API, if you receive the following error.

"Message": "Validating with email, User is not registered in Smart Materials ".

Solution 7

  • You must provide a valid email id which is registered with SAM for the concern SMAT user (User page in SMAT web application and A.20.05 (Users) in classic application).. To know the valid email id, use this link (JSON web token link ) and then decrypt the token value to view the actual registered user and email details. Have a look on the following image to have a better view.

    JSON token

  • If in case, after verifying also if you are receiving same error. Update login option as ā€˜BOTHā€™ or ā€˜SSOā€™ from APEX or through SQL developer. For details refer Map users.

    Map users

Error 8

While accessing any API, if you receive the following error message.

"code": "MAR-51012",

"message": "MAR-51012: You do not have access permission to the project"

Solution 8

  • Please ensure that you are passing correct project, discipline, and language (nls) combination to access the API.

  • Please ensure that the user has required privileges to access the data in Smart Materials application. For reference, see the classic page screenshot where you can view the assigned privilege on user basis.

    Classic user privilege page

Error 9

While accessing any API, if you receive the following error message.

"code": "MAR-51012",

"message": "MAR-51012: You do not have access permission to the project".

Solution 9

  • Please ensure that you are using the correct project, discipline, and language combination.

  • Ensure that the required privileges are assigned to user (for details refer error 6).

  • Ensure that the project used while accessing the API is assigned to the user and the respective box is marked. For reference, view the following screenshot from classic.

    assign project to user

Error 10

While accessing any API, if you receive the following error message.

"code": "MAR-51006",

"message": "MAR-51012: License is not available".

Solution 10

  • This might occur when no WEB API license is available or license got expired. Please assign/load proper license files. Once the license files are assigned, you must get the following description while accessing the Description API.

    Decsription API

    If the error exists even after assigning all the required privileges, then restart the IIS service.

Error 11

While accessing any API, if you receive the following error message.

"InnerError",

"message": "IDX20803: Unable to obtain configuration from: 'System.String'.

Solution 11

Ensure that the issuer url in web.config file is correct. To see the details, navigate to your web.config file in the C drive and look out for the following information.

Issuer url details

Error 12

While accessing any API, if you receive the following error message.

"InnerError",

"message": "The value of the property 'id' cannot be parsed. The error is: Could not find any recognizable digits. (C:\\Program Files\\INTERGRAPH\\Smart Materials WebAPI Current\\Web\\API\\web.config line 133)".

Solution 12

Ensure that the resource id in the web.config file is correct. To see the details, navigate to your web.config file in the C drive and look out for the following information.

Resource id details

Error 13

While accessing any API, if you receive the following error message.

"ErrorCode": ",12154",

"Message": "Unable to connect database".

"ErrorCode": "12154",

"Message": "ORA-12154: TNS: could not resolve the connect identifier specified".

Solution 13

Ensure that the data source name in the web.config file is correct. To see the details, navigate to your web.config file in the C drive and look out for the following information.

Data source details

Error 14

While accessing any API, if you receive the following error message.

"ErrorCode": ",1017",

"Message": "Unable to connect database".

"ErrorCode": "1017",

"Message": "ORA-01017: invalid username/password; logon denied\n".

Solution 14

Ensure that the given password for m_webapi user in the web.config file is correct. To see the details, navigate to your web.config file in the C drive and look out for the following information.

m_web api details

Error 15

While accessing any API, if you receive the following error message.

"Message": "Please provide a valid project".

Solution 15

Ensure that the passed project name is available in the application.

Error 16

While accessing any API, if you receive the following error message.

"Message": "You do not have access permission to the project".

Solution 16

Ensure that you are passing correct project, discipline, and language combination to access the API. Also, you are a user in the given project and have access to view it details.

Error 17

While accessing any API, if you receive the following error message.

"Message": "You do not have required privilege to access the API".

Solution 17

Ensure that you have required privileges to access the features and data.

Common Errors

Errors

Message/Reasons

404 Not Found

  • Queried parameter or ID does not exist in the given project or discipline.

401 Unauthorized

  • Given authorization token or header is not valid.

  • Login user does not have permissions to access the given API.

404 Bad Request

  • When a mandatory parameter is not passed in the body of the API.

  • When a given parameter is not valid. For example: either the parameter is of different data type or length exceeds the allowed limit.

  • When an incorrect URL is provided.