Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
  • Welcome
  • Products
  • Support
  • About
  • More
  • Cancel
OpenUtilities
  • Product Communities
  • More
OpenUtilities
OpenUtilities Wiki Error - Invalid object name
    • Sign in
    • +OpenUtilities
    • Access Service Request Manager
    • +Bentley sisHYD Multi Utility
    • Design Features - promis.e Functionality - Promis.e Standard
    • +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
        • Backing Up Promis.e Data Automatically
        • Converting to an SQL Parts Database
        • +Creating and Updating the Project Database
        • Desired SQL server Not Listed in the available Servers List
        • Disable Auto Shrink to avoid performance degradation
        • Error - Could not find SQL Server instance named BENTLEYECAD
        • Error - Could not find stored procedure
        • Error - Database version does not match the application
        • Error - Index was outside the bounds of the array (Microsoft.SqlServer.smo)
        • Error - Invalid database name - on Project Database Utility
        • Error - Invalid object name
        • Error - Login failed for Ecaduser: Reason: The Password of the account Expired
        • Error - No version resource could be located in database
        • Error - OraOLEDB.Oracle provider is not registered
        • Error - T-SQL execution command line utility stopped working
        • Error - The database is for product... you cannot use it
        • Error at Startup - Error 0 No connection could be made because the target machine actively refused it.
        • Error at Startup - Error 40 Could Not Open a Connection
        • Error at startup - The Type initializer for ECT.ECAD.API.SystemSetup threw an exception
        • Error at Startup - Unrecognized database format, catalog.mdb
        • Error deleting project - transaction log full
        • Error messages encountered due to case sensitive collation of SQL Server
        • Error on backup - Invalid database object reference
        • Error on Project Database Utility - Cannot find the file specified
        • Error running SQL scripts - Incorrect syntax
        • Exception thrown when creating a project due to SQL permissions
        • Exception thrown when opening a page, transaction log is full
        • Finding the SQL Data folder
        • Installing SQL Server
        • Minimum SQL user permissions
        • Project Database Version - Promis.e
        • Rebuild indexes in the SQL project database
        • Rules for Regular Identifiers
        • SQL Server FAQ
        • Troubleshooting Project Database Connection Problems
      • +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
      • +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. 

    Error - Invalid object name

      Product(s): Promis.e, Bentley Substation
      Version(s): through 08.11.12.137
      Environment: N/A
      Area: Database Platform Support
      Subarea: N/A

    Error or Warning Message

    An "invalid object name" error message appears when certain operations are performed.  For example, when assigning a part number to a symbol, the following error message is displayed.

    Internal Error
    Error Message: Invalid object name 'DevPartNumberIncludeACK'.
    TargetSite: Boolean CheckConn(System.Data.SqlClient.SqlException)
    DeclaringType: ECT.ECAD.DAL.SqlServerProject
    Attributes: private
    MemberType: Method

    The error messages and affected operations may differ from case to case. Invalid object names specified in error messages have included but are not limited to: DevPartNumberIncludeACK, createProject, ClearSpecifiedParentDevice.

    This problem is usually preceded by an upgrade to the project database schema.

    Explanation

    When the software is upgraded, the schema of the project database often needs to be updated as part of the process.  In order to update Views and Stored Procedures in the database, the update script drops (deletes) and recreates them. Sometimes, the items are dropped but fail to get recreated. When the software tries to use the item, the error message occurs because the item is missing.

    How to Avoid

    1. (Optional) Confirm the object referenced by the error message is an object that gets dropped and recreated by the update script. This can be done by searching the contents of the SQL_UpdateDB.sql file for the object named by the error message. Look for a "DROP" instruction followed by an object type ("VIEW" or "PROCEDURE")  followed by the object name. Then look for another line containing the CREATE instruction and the object type and name.

    2. Execute the SQL_UpdateDB.sql script against the project database (again) using SQL Server Management Studio while using a login with adequate permissions.  There is no harm in running the script more than once.  See Creating and Updating the Project Database for details including the location of the script file.

    If the object referenced in the error message is not one that gets dropped by the script, it could indicate the object was removed by some other means or there is corruption.  Executing the update script may still create such a missing object, but the data in the database may be suspect in this case, depending on what object(s) was missing.

    See Also

    Error - Could not find stored procedure

      Original Author: Matt_P

    P/S: 38821, 500000065467

    • upgrade
    • Database Platform Support
    • promis.e
    • SQL Server
    • error message
    • Bentley Substation
    • Share
    • History
    • More
    • Cancel
    • Matt_P Created by Communities MVP Matt_P
    • When: Mon, Feb 3 2014 6:09 PM
    • Jesse Dringoli Last revision by Bentley Colleague Communities MVP Jesse Dringoli
    • When: Fri, Mar 27 2020 4:51 PM
    • Revisions: 9
    • 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

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