ESdat Forums
»
Forums
»
ESdat
»
Automation Error/Library Not Registered
Rank: Newbie
Groups: Registered
Posts: 5
Thanks: 1 times
|
Some users connecting to SQL Server ESdat database (running 5.1.32) are unable to import or export tables, generating errors such as:
8800 Automation Error
Library Not Registered
Or
15540
Object variable or With block variable not set
Are there any known bugs? This has been cropping up in just the last day or so.
Thanks
Natalie
|
|
|
|
Rank: Administration
Groups: Registered, Administrators Posts: 498 Location: Byron Bay Was thanked: 19 time(s) in 19 post(s)
|
Hi Natalie, If you've not updated ESdat in the last few days then it will be caused by something else updating on your system, most likely a issue introduced in an Office Patch.
We've had a few reports of problems with Excel integration in the last few weeks. There was also a similar "bout" a few years ago. We'd recomend uninstalling any recent Office "patches" and then trying a repair to Excel. We've also seen issues arise where Excel is from a different version of Office to other Office components on the system, in which case a repair, or sometimes a reinstall of Excel is needed to resolve it. Regards,
Warwick
|
1 user thanked Warwick Wood for this useful post.
|
|
|
Rank: Member
Groups: Registered
Posts: 19
Thanks: 1 times
|
Hi, I have similar error when tried importing lab files "Object variable or With block variable not set". We use ESdat server v 3.5.18290, ESdat desktop v 5.1.59.
How can we fix the problem?
Yanti
|
|
|
|
Rank: Administration
Groups: Registered, Administrators Posts: 498 Location: Byron Bay Was thanked: 19 time(s) in 19 post(s)
|
Hello,
We've seen this before and it most likely a issue introduced in an Office Patch. We'd recomend uninstalling any recent Office "patches" and then trying a repair to Excel. If you have a Windows "Restore Point" from before the issue arose that is also worth trying. It can also occur if you've installed applications from different versions of Office on the same PC (eg Microsoft project from Office 2016 with Excel from Office 2013), in which case a repair, or sometimes a reinstall of Excel is needed to resolve it. Warwick
|
|
|
|
Rank: Newbie
Groups: Registered
Posts: 5
Thanks: 1 times
|
Hello,
we are experiencing the same problem when tried importing lab files "Object variable or With block variable not set"
Desktop Version 5.1.61
Server Version 3.9.20268.0
it seems that this is only preventing the XML file from being read and updating the database with the lab report and SDG information. the sample and chemistry files will go in if first the Lab Report and SDG information is committed to the database not by way of the import EDD tool.
I have done as advised above. uninstalled office, reinstalled, uninstalled 115 office updates one by one, etc. the error persists.
what other changes could result in this error? is there firewall exceptions that can be made or other updates on the server that are in conflict with this?
thanks,
|
|
|
|
Rank: Administration
Groups: Registered, Administrators Posts: 327 Was thanked: 29 time(s) in 29 post(s)
|
Hi, Just to confirm, you're importing the EDD via ESdat Desktop. Is this correct? Also, are the files saved separately (i.e. you open the samples.csv file), or are all the files included in a compressed file and you select the zip? Whichever you are doing, can you please try the opposite and let me know what happens? Have you tried importing the file via the Lab Report menu in the Server Web interface? Do the files successfully import this way? There is also an update to ESdat Desktop that you may wish to install. I recommend checking the dowload page on the website periodically here, or you can download it with this link. Finally, can you please try the additional Excel troubleshooting tips provided in this post, and let me know your results? Thanks, Nick
|
|
|
|
Rank: Newbie
Groups: Registered
Posts: 5
Thanks: 1 times
|
Hi Nick,
Yes ESdat Desktop.
I tried both zipped and unzipped files. with the zipped files i get the error "Library Not Registered" before "Object variable or Block with object variable not set"
it will go through in the web version of ESdat with Add New Report. but we will often catch errors from the lab in the chemistry table. having to review and modify the csv, save, zip and import as a zip on the web seems to be added steps for us. we rely on the macros in excel to streamline the import process.
is the new desktop update an update to the whole system? i saw that there was an update to the server and that new fields were added to the database schema. we have just finished jumping through massive hoops getting our labs to comply with the ELDF, we plan to hold off doing this update as we do not require use of the added fields and it will further delay completion of projects.
we are running Windows 10, office 2013 professional. I have tried to: repair excel - same results, uninstall recent patches (115 of them) - same results, uninstall and re-install new office - same results, reapply patches with fresh office - same results.
there was a massive windows office update on circa December 10, 2020. with windows 10 we are unable to block updates and re-starts. i am unsure if updates were also applied elsewhere in our environment that may also be preventing the XML process from executing.
thanks,
|
|
|
|
Rank: Administration
Groups: Registered, Administrators Posts: 327 Was thanked: 29 time(s) in 29 post(s)
|
Hi David, The update to ESdat Desktop is not related to the server update. It will continue to work just fine with the current version of the EDLF. I recommend installing this to see if it resolves the issue. I'm also running Windows 10 and instlled the latest updates recently. Generally speaking it's Office which can cause issues rather than Windows. I'm running the latest version of Office 365, so can't confirm potential issues with Office 2013. Did you try the Excel troubleshooting tips I linked to? These can help identify where the issue is.
If you think that it's related to the xml file, this file isn't actually required when importing via ESdat Desktop. What happens if you delete or move the xml file from the location of the csv files, and then try to import? Thanks, Nick
|
1 user thanked Nick Support for this useful post.
|
|
|
ESdat Forums
»
Forums
»
ESdat
»
Automation Error/Library Not Registered
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.