Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
OpenUtilities
  • Product Communities
OpenUtilities
OpenUtilities Wiki Anatomy of the ect.fid file
    • Sign In
    • +OpenUtilities
    • Access Service Request Manager
    • +Bentley sisHYD Multi Utility
    • Design Features - promis.e Functionality - Promis.e Standard
    • +OpenUtilities sisNET - English
    • +OpenUtilities Substation
    • Promis.e Paths
    • -Promis.e Wiki
      • +CONNECT Edition - Promis.e
      • About Promis.e
      • +Administration Features - Promis.e
      • +APIs_VBA - Promis.e
      • +Automation Features - Promis.e
      • +Component Features - Promis.e
      • +Component Management - Promis.e
      • +CONNECT Services - Promis.e
      • +Data Manager - Promis.e
      • +Database Platform Support - Promis.e
      • +Display - Promis.e
      • +Drawing Management - Promis.e
      • +Engineering Design Considerations - Promis.e
      • Error - Object reference...General
      • +Find_Replace - Promis.e
      • Finding the Tutorial
      • -Installation_Configuration - Promis.e
        • Alert - UI Fail to delete folder
        • Anatomy of the ect.fid file
        • Application Data (per-user configuration) - Promis.e
        • AutoCAD - Previews flicker or are blank
        • Cannot uninstall software
        • Catalog cache - promis.e
        • Clean Installation
        • +Compatibility Chart - Promis.e V8i
        • Create a security certificate for password encryption
        • Creating a deployment image for Silent Install
        • Device.mdb - Promis.e
        • Distribute custom Parts Database Manager layout
        • Distributing the Setup configuration
        • Error - .MDB file in use or locked by another user
        • Error - 1603, installation failed, fatal error
        • Error - Access to the path 'C:\Users\[user name]\AppData\Roaming\Bentley\promis-e V8i(M)' is denied.
        • Error - Can not find a valid AutoCAD, fail to start
        • Error - Can not find a valid MicroStation, fail to start
        • Error - Can't Install or Find AccessDatabaseEnginex64
        • Error - Fail to load plugin
        • Error - Not enough space on drive C:\ to extract this package
        • Error - Object reference, get_IsCommandProtectionOn
        • Error - Project file is corrupt
        • Error - Refresh catalog database error
        • Error - Root element is missing
        • Error - The Microsoft Jet database engine cannot find the input table or query 'Mode'.
        • Error - UI Fail to delete folder
        • Error - Unable to find Multi-Language_UI.mdb although it exists
        • Error at Startup - AutoLoad x64.scr Can't find file
        • Error at startup - The given key was not present in the dictionary (Device.mdb)
        • Error at startup - The type initializer for ECT.ECAD.UI.ShapeManager threw an exception
        • Error at Startup - Unrecognized database format, Device.mdb
        • Error at startup - Void folder Explorer_ExplorerNodeChanged
        • Error Creating New Projects, "UpdateProjectOptionXmlToNewVersion"
        • Error on startup - Cannot modify the design of table BlkInfo
        • Error Opening Project Manager
        • File Open dialog appears at startup
        • How to download the Promis.e software
        • Macro seed file folder - promis.e
        • +Network Installation Guide
        • Program data folder - Promis.e
        • Program folder - Promis.e
        • Promise Data folder
        • Random, distorted, or extra lines appear on every DGN file
        • Select Data Folder appears at startup
        • Specify a Setup Configuration at startup
        • Startup Error: Promis.e not responding
        • Updating and Upgrading Promis.e
        • Why should I upgrade Promis.e?
      • +Interoperability - Promis.e
      • +Licensing - Promis.e
      • +Maintenance Features - Promis.e
      • +Migration - Promis.e
      • +OS Support - Promis.e
      • +Panel Layout - Promis.e
      • +Performance - Promis.e
      • +PowerPlatform Support - Promis.e
      • +Print_Publish Features - Promis.e
      • +ProjectWise Integration - Promis.e
      • Promis.e Help file
      • +Reports_Output Features - Promis.e
      • +Template Management - Promis.e
      • +Text Tools - Promis.e
      • Training FAQs
      • +Wire Numbering - Promis.e
      • +Wiring Features - Promis.e
      • +Project Management - Promis.e
      • Promis.e Title
      • Working from home with Promise.e
    • Replace Family - Find_Replace - Promis.e
    • SQL Server Login

     
     Questions about this article, topic, or product? Click here. 

    Anatomy of the ect.fid file

      Product(s): Promis.e, Bentley Substation
      Version(s): 08.11.13.140
      Environment: N\A
      Area: Installation_Configuration
      Subarea: N\A

    This information is provided as reference. The user does not normally need to deal with the ect.fid file at all.

    Background

    Each project folder contains an ect.fid file. This file is used to correlate the project's folder to the project's data in the SQL project database.

    Contents of the ect.fid file

    167
     (SELECTseries 7)-RELEASE-Microstation
    SQL Server
    (local)\BENTLEYECAD
    MicroStation
    8.1.14
    37d80c36-6236-4ebd-8588-7424c092400a
    MyDatabase
    promise
    4.0

    Line 1 contains the project id value for the project. This value correlates to the id field in the Project table in the project database.

    Line 2 indicates the SELECTseries and platform of the software that last modified the project.

    Line 3 indicates whether the project's data was stored in a SQL Server or Oracle database.

    Line 4 contains the server name hosting the project database. This corresponds to the Server Name field on Setup > Project Database. The format is SERVERNAME\INSTANCENAME. The "(local)" value is a shortcut for the workstation's machine name.

    Line 5 indicates the platform of the software used to create the project. "MicroStation" indicates an integrated platform in later versions.

    Line 6 indicates the Project Database Version, which may give a clue to the version of the software.

    Line 7 contains the unique identifier (GUID) string for the project. This value must match the value in the guid field for the project's record in the Project table for the project to be accessible.

    Line 8 contains the name of the project database that contains the data for the project. This corresponds to the Database or Default Database field on Setup > Project Database. In later versions, the software is able to dynamically switch between project databases, so the project may still be accessible if another database is specified on Setup > Project Database.

    Line 9 indicates the software that created the project ("promise" or "Substation").

    See Also

    The GUID in the project database doesn’t correspond to GUID for this project in the ect.fid

      Original Author: Matt_P
    • promis.e
    • Bentley Substation
    • en
    • Installation_Configuration
    • Project Management
    • Share
    • History
    • More
    • Cancel
    • Matt_P Created by Communities MVP Matt_P
    • When: Fri, Feb 24 2017 6:21 PM
    • Satish Saptasagar Last revision by Bentley Colleague Satish Saptasagar
    • When: Mon, Apr 13 2020 8:24 AM
    • Revisions: 5
    • Comments: 0
    Recommended
    Related
    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies