Ideally, we would run a utility on the client. As the problem is intermittent, I am hoping that there is something we can do from the client side. The vendor indicates that latency is an issue. If this is not possible, because an existing database shares the same name, the database must be restored to another SQL Server instance for access using its original name. We have an application that is intermittently losing connection to the database from the client. Rename the database to its original name using the sp_renamedb stored procedure or use the command ALTER DATABASE MODIFY NAME. When the name of a database has been changed using a stored procedure or a database is restored to a name different from the original, the database cannot be be accessed via ArcSDE or ArcGIS clients. The name of the original database is hard-coded in database objects. Unfortunately, it is not possible to rename an ArcSDE geodatabase once it has been created. The cause of such an error may be linked to restoring a database in SQL Server Enterprise Manager/Management Studio under a different name than the original backup or datafile. Microsoft OLE DB Provider for SQL Server: There is already an object named 'dbtune' in the database.Ĭonnecting via Application server service within ArcCatalog:ĪrcSDE 10.0 for SQL Server Build 1343 Thu Feb 17 11:45:42 2011 Unable to verify the existence of the DBTUNE table, error = -62. DBMS error code: 2714".ĪrcSDE 9.3 SQL Server Build 508 Thu Mar 3 18:55: "An error was encountered while running ArcSDE Post Installation Operation Failed, Unable to start iomgr. Learn more after switching to SOLR in Sitecore 8. The following error message appears after the service has been created and an attempt to start the service has been made: Connect and share knowledge within a single location that is structured and easy to search. Performing direct connect from ArcCatalog:įailed to connect to database. In the above examples, several errors could occur if the original name of the database is not used: connecting via an application server connection performing a direct connect to a restored database If an existing ArcSDE for SQL Server geodatabase is restored to a new or existing server and the original name of the database is not retained from when the ArcSDE Post-Installation was run initially, issues can be encountered when trying to connect to the geodatabase through ArcGIS.Ī few examples of when errors may be encountered when accessing geodatabases restored in this manner are: Error: An error is received when trying to access a SQL Server ArcSDE geodatabase that has been restored with a new name Error Message