You get an Error Message - Intergraph Smart Materials - Version 10.2 - Installation & Upgrade - Hexagon

Following messages might show up to the user:

• MAR-05001 License service was not specified

  This is only be displayed to first time user when opening the application. In classic, after this message, the user gets into the Smart Materials Classic A.60.81 License screen or the Smart Materials Web License page to enter the license service address.

• MAR-05005 The maximum number of concurrent users has exceeded

  This message can show up during logon, if none of the requested module seats can be retrieved because the license pool doesn’t have these seats available anymore.

  It will also be shown when external sessions call "select login", but no payable seat can be pulled for them.

• MAR-05012 Maximum users exceeded for module #1 (module-related license count)

  This is the standard message that expresses that a certain license module has no seats available in the pool. The same message can also mean that the requested license tag is not in the pool at all.

• MAR-05013 Your license for module #1 expired #2 day(s) ago (module-related license outdated)

  From ISL, you will not get information about the elapsed days (#2). Alert will show up "n" instead of a number.

• MAR-10155 No license is available for project #1 to access #2

  This is an exception that is thrown during the project quotas check, if the limits are reached. Go to Smart Materials Classic A.30.04 License Modules/Menus screen or to the License Modules section of the Roles and Menus page in Smart Materials Web and check the project quotas for all license module your screen is assigned to. The check is not done against ISL.

• MAR-05020 Reservation or Return of a license for #1 failed: #2 (internal problem)

  This message indicates some unexpected problem. #1 contains the license tag, #2 contains the message.

  Here are some error cases that might occur during request and return of seats:

  • MAR-05020 is also raised if an unexpected HTTP status code is returned like FAILURE HTTP-500 : Internal Server Error.

    If an internal server error occurs, it might help to restart the application pool which hosts the license webservice. If the error persists, it is an indication that the installation of the license webservice is broken. Dlls could be missing or path is incorrect or IUSR user and IIS_IUSRS user have insufficient privileges on the folders. Consider to reinstall the license webservice from the setup.

    To test if it is a general issue with IIS, you can check if the homepage of the IIS is properly displaying on a browser.

  • TNS:Operation timed out: This is derived from Oracle error ORA-12535. Typically it indicates, that the IP addresss of hostname you have used for license service URL could be retrieved, but the server itself could not be reached. This can happen if the server running the license service is down.

  • Transfer timeout: This timeout can happen once connection to license webservice was established, but ISL client did not respond to license webservice in a timely fashion. The DBA setting LICENSE_CALL_TIMEOUT can be used to specify the timeout in seconds of DB waiting for license webservice to return. Default is 120. It does not make sense to enter values greater than 120 because anyway internally there is a timeout happening close to one minute. Plus, waiting several minutes will block resources. Also, do not set a value lower than 60 to get the license before the internal timeout happens. If you see "transfer timeout" errors frequently, you might want to restart the license webservice, because with this kind of timeout orphaned licenses pile up in the ISL client. See also Webservice Maintenance.

  • Connect failed because target host or object does not exist: This is derived from Oracle error ORA-12545. This message is issued if the host address cannot be resolved from the database server machine. For example, it may happen if you specify the following as license service URL:

    nonExistingHost/SmartMaterialsLicenseWebservice2020/SmartLicensingService/service/home

    It is not found in the network.

  • ORA-29259: end-of-input reached: means that the database started to read the response from the license webservice but it was interrupted unexpectedly because the server does not return more chunks of data. This error can hide other network issues. Check if the license webservice is up and running as described in chapter .

  • ORA-29264 : unknown or unsupported URL scheme: can occur when the license web service URL was prefixed with the scheme and the scheme is in uppercase like "HTTP://...". According to specification this is not supported. You can omit the scheme in your definition or use lowercase.

  • MAR-05020 can also forward errors from ISL. In this case, the message is containing the ISL-status code with a trailing question mark (?), followed by a descriptive text.

  Examples:

• MAR-05022: License service returns an invalid response.

  The URL configured for license service is incorrect. While the request returns HTTP 200 which means "successful", the response data is unusable for licensing. This may happen if you specified a valid URL of a web page (for example, inside Google, Microsoft, Oracle, and so forth) for your license webservice, which of course returns content but not a license response. Correct the license service URL to point to the proper location. The standard URL has the following format:
  <servername><.domain if required>/SMatLicenseWebservice10.1/SmartLicensingService/Service/home

• MAR-05023: Database is not allowed to contact license service

  The server name used for license service was not found in the access control list of the DB. This message encapsulates "ORA-24247: network access denied by access control list (ACL)" The message comes if the access control list was not maintained properly. Following needs to be done. If no ACL is existing:

  DBMS_NETWORK_ACL_ADMIN.create_acl (

  acl => 'LicenseWebservice.xml',

  description => 'Access control list for the License Webservice',

  principal => 'M_SYS',

  is_grant => TRUE,

  privilege => 'connect',

  start_date => NULL,

  end_date => NULL);

  If the ACL is existing, entries to this list can be made as following:

  DBMS_NETWORK_ACL_ADMIN.assign_acl (

  acl => 'LicenseWebservice.xml',

  host => <application-server name (with domain if required)>,

  lower_port => NULL,

  upper_port => NULL);

  See also Make the Webservice available to the Database.

• MAR-05024: License service received invalid request

  The URL may be correct, but the data sent to license service cannot be used. Contact the support.

• MAR-05027: License service is not found on this server

  The URL configured for license service is incorrect. Though the server name might be correct, the path cannot be found. So, the response status is HTTP 404.

  Http 404 is the same return code you might get in a browser if you misspell the address of an internet page. The license service URL can be maintained in the third tab of Smart Materials Classic A.60.81 License screen or on the License page in Smart Materials Web. Maybe a typo is in the value.

  This may happen if you specified a valid servername for your license webservice, but the succeeding virtual path is not existing. Correct the license service URL to point to the proper location. The standard URL has the following format:
  <servername><.domain if required>/SMatLicenseWebservice10.1/SmartLicensingService/Service/home

• MAR-05028: License service is ill formatted

  The format of the URL does not meet minumum requirements. In this case it means, the URL must end with 'Service /home'.

  Correct the license service URL to point to the proper location. The standard URL has the following format:
  <servername><.domain if required>/SMatLicenseWebservice10.1/SmartLicensingService/Service/home

• MAR-05030: License service not available

  The license service does not respond. It runs into a timeout. This typically has to do with the current state of the IIS, the IIS webpage or the application pool which contain the license service. Open the IIS server manager and make sure that all relevant units are up and running.