Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 4 of 4 total |
Error #401 module extmoduleabc does not exist in the configuration EDBConfig |
Wed, Nov 17 2010 7:26 PM | Permanent Link |
George | Just upgraded the server from 2.03 Build 21 to 2.04 Build 4, with Delphi 7
When I tried calling my external modules, I got the following. ElevateDB Error #401 The module extmoduleABC does not exist in the configuration EDBConfig I recompiled my external module and placed the new dll copy and rerun the server, but still I get above error. I tried searching support threads for the past hour about this, but can't find related issues yet. The external module is located in the directory as specified in Configuration -> File Folder. I just actually replaced my old (2.03) edbsrvr with the new edbsrvr (2.04b4). What is wrong with my setup? Thanks, G Patena |
Wed, Nov 17 2010 8:01 PM | Permanent Link |
Terry Swiers | ?G,
> The external module is located in the directory as specified in > Configuration -> File Folder. 2.03 and older automatically registered the external modules, but starting with 2.04 you have to manage the external module registration yourself. So check the configuration.modules table to see if the module is registered when starting your application or after making the connection to the server. If the module isn't present, use the CREATE MODULE statement to register it with the server and you should be good to go. -- --------------------------------------- Terry Swiers Millennium Software, Inc. http://www.1000years.com --------------------------------------- |
Thu, Nov 18 2010 12:09 PM | Permanent Link |
George | > ?G,
> >> The external module is located in the directory as specified in >> Configuration -> File Folder. > > 2.03 and older automatically registered the external modules, but starting > with 2.04 you have to manage the external module registration yourself. > So .... ah progress, but it is well worth it to give more time to edb developers for more goodies and cool features in upcoming builds .... > check the configuration.modules table to see if the module is registered > when starting your application or after making the connection to the > server. If the module isn't present, use the CREATE MODULE statement to > register it with the server and you should be good to go. > Terry Swiers Thanks, Terry ... that was quick and easy. I hope I don't need to do that the next time I migrate a DBISAM4 table using the external migrator-- but it is ok now that I know the solution. Thanks, George Patena Rancho Cordova, California |
Thu, Nov 18 2010 5:04 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | George,
<< Thanks, Terry ... that was quick and easy. I hope I don't need to do that the next time I migrate a DBISAM4 table using the external migrator-- but it is ok now that I know the solution. >> No, once an external module is registered with CREATE MODULE, it will stay registered in the configuration file until you unregister it (DROP MODULE). The whole process of module registration was done to eliminate any issues with EDB trying to load DLLs in the configuration path that weren't EDB external modules, which also improves the startup performance for sessions. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Monday, May 6, 2024 at 03:23 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |