You are currently reviewing an older revision of this page.
When opening SELECTseries 3 version of a Haestad Methods product (or earlier), one of the following error messages is generated:
Haestad.Domain.DaoInterop.DAOException: COM error not documented
at Haestad.Domain.DaoInterop.InteropLibrary.ThrowCOMException(_com_error* e)at Haestad.Domain.DaoInterop.DaoDatabase.CreateDatabase(String fileName, CultureInfo locale)at Haestad.Domain.LibraryObjects.JetAppSettings.OpenRegistryDatabase(String fileName)at Haestad.Domain.LibraryObjects.EngineeringLibraryService.OpenImpl()at Haestad.Domain.LibraryObjects.EngineeringLibraryService.EngineeringLibraryTypeNames(HmiProductBeta product)
This is sometimes followed by the following message:Database format not recognized. It could not be opened.
When opening the program:
System.TypeInitializationException: The type initializer for 'Haestad.Domain.LibraryObjects.EngineeringLibraryService' threw an exception.
Haestad.Domain.DaoInterop.DAOException (0x80040154): COMerror not documented at Haestad.Domain.DaoInterop.InteropLibrary.ThrowCOMException(_com_error* e) at Haestad.Domain.DaoInterop.DaoDatabase.CreateDatabase(String fileName, CultureInfo locale) at Haestad.Domain.LibraryObjects.JetAppSettings.OpenRegistryDatabase(String fileName) at Haestad.Domain.LibraryObjects.JetAppSettings..ctor(String filename) at Haestad.Domain.LibraryObjects.EngineeringLibraryService.OpenImpl() at Haestad.Domain.LibraryObjects.EngineeringLibraryService..cctor()
When closing the program:
Haestad.Domain.DaoInterop.DAOException (0x80004005): COMerror not documented at Haestad.Domain.DaoInterop.InteropLibrary.ThrowCOMException(_com_error* e) at Haestad.Domain.DaoInterop.DaoDatabase.CreateDatabase(String fileName, CultureInfo locale) at Haestad.Domain.LibraryObjects.JetAppSettings.OpenRegistryDatabase(String fileName) at Haestad.Domain.LibraryObjects.JetAppSettings..ctor(String filename) at Haestad.Domain.LibraryObjects.EngineeringLibraryService.OpenImpl() at Haestad.Domain.LibraryObjects.EngineeringLibraryService..cctor()
When opening a file:
at Haestad.Domain.LibraryObjects.EngineeringLibraryService.set_ProjectWiseManager(ProjectWiseManager value) at Haestad.Framework.Application.ProjectManagerBase.get_ProjectWiseManager() at Haestad.Framework.Application.ProjectManagerBase.get_IsProjectWiseAvailable() at Haestad.Framework.Application.HaestadParentFormModel.get_IsProjectWiseAvailable() at Haestad.Drawing.Control.Application.GraphicalParentFormUIModelBase.Initialize() at Haestad.Drawing.Control.Forms.GraphicalDrawingParentForm.DoLazyInitialization(Boolean lazyInitialize) at Haestad.Drawing.Control.Forms.GraphicalDrawingParentForm.FileNew() at Haestad.Montana.Forms.MontanaXMParentForm.FileNew() at Haestad.Framework.Windows.Forms.Forms.WelcomeForm.buttonCreateNewProject_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
This error may occur if the 64-bit version of the Haestad product has been installed along with a conflicting version of Microsoft Office. When installing the software on a 64-bit operating system, the program should detect the presence of the 32-bit version of Microsoft Office and force the software to install as a 32-bit application. The reason for is a Microsoft Office component called Access Database Engine. The 32-bit version of Microsoft Office will have the 32-bit version of the Access Database Engine.
On rare occasions, the 32-bit version of the Access Database Engine is not properly identified. When this occurs, the 64-bit version of the product is installed and used in the Desktop shortcut. Since the 64-bit version will conflict with the 32-bit version of the Access Database Engine, the error message is generated.
This is a rare issue that will only occur the the SELECTseries 3 versions of the Haestad products and only on a 64-bit operating system with 32-bit Microsoft Office installed.
Note that this problem will no longer occur, as of the SELECTseries 4 versions of WaterCAD, WaterGEMS and HAMMER (or later). The reason is because a SQLite database is now used instead of an Access Database, eliminating the dependency on the Access Database Engine for opening a file. This also applies to the SELECTseries 4 release of StormCAD, SewerCAD, SewerGEMS and CivilStorm.
The error could be occurring because of unregistered DAO. See this article for steps to register the DAO360.dll file.
The SELECTseries 4 and later versions of the Water products and the Storm and Sewer products will not have this issue. Upgrading to the latest version of the software will eliminate this error completely and provide you with all of the latest updates and tools the programs have to offer. You can find the steps to upgrade to the latest version here.
If you cannot upgrade, the next best workaround is as follows:
Another variation of the above is described below:
If 32-bit version of the Haestad product could not open from the program files directory, try reinstalling it. If you must use the 64-bit version of your Haestad product (such as for integrating with the 64-bit version of AutoCAD), then this workaround will not work.
How do I download the Water and Storm-Sewer hydraulics and hydrology products?
How to register DAO360.dll or a dll file
How to Delete Engineering Libraries