Start the Database Interference Detection Service - Intergraph Smart 3D - 2019 - Help

Intergraph Smart 3D Point Cloud

English (United States)
Intergraph Smart 3D
Point Cloud
Search by Category
Smart 3D Version
12.1 (2019)

Prior to starting the Database Interference Detection Service, you must configure its properties. For more information, see Configure Interference Service properties.

  1. Log on with Administrative privileges to the computer on which the Project Management and Database Interference Detection Service options are installed.

  2. Open the Control Panel, and then double-click Administrative Tools.

  3. In the Administrative Tools window, double-click Services.

  4. Open Properties:

    Right-click Intergraph Smart 3D Interference Detection Service, and then click Properties.

    Right-click Intergraph Smart 3D Interference Detection Service 64-bit, and then click Properties.

    The 64-bit Intergraph Smart 3D Interference Detection Service does not process point clouds. Use Reference 3D if you are running 64-bit IFC, or you can switch to a 32-bit IFC server to process Point Clouds.

  5. On the Log On tab, select the This account option, and then type the user name that has Administrative privileges.

    This version of the software does not support the Local System account option.

  6. In the Password and Confirm password boxes, type the password for the user account.

  7. On the Recovery tab, set the First failure, Second failure, and Subsequent failures options to Restart the Service.

  8. Set Restart service after to a minimum of 6 minutes.

  9. On the General tab, verify that the Startup type is set to Automatic.

  10. In the Service status section, click Start.

  11. Click OK.

  • The interference checking service does not consume a license when it starts. It consumes a license only while processing the model. For more information, see Checking Interferences.

  • Errors that are encountered during startup of the Database Interference Detection service are logged to the Event Viewer Application Log with the source name IFCNTSvc. The service can automatically recover from these situations:

    • network interruptions

    • lost database connection

    • the interference checking process runs out of memory

    • the interference checking process or service is terminated for any reason

  • Do not run the 32-bit and 64-bit interference detection services simultaneously on a computer. IFC must only run as a single instance for the entire model.

  • While working in a global workshare environment, you can only run and monitor IFC status from the host location.