I am encoutering an issue no one at my company is able to figure out.

Data imports successfully and when I export water levels ESdat hangs and when I click on the screen the following appears:​​​​​​

*see First message

I have to right click and close the program from the taskbar and then receive this message

*see Second message

I click okay and then receive this

*see Third message

I press cancel and receive the next message:

*see Forth message

ESdat still works for water chemistry exports but not for water levels. Any ideas as to what's going on with my ESdat?

Forth Message.PNG (10kb) downloaded 1 time(s). Forth Message.PNG (10kb) downloaded 1 time(s). Forth Message.PNG (10kb) downloaded 1 time(s). 3. 2nd error message after ending task.jpg (2,105kb) downloaded 1 time(s). 4. Message after right click closing ESDAT on taskbar.jpg (1,748kb) downloaded 0 time(s). 1. Error after attempting to export data.jpg (2,637kb) downloaded 0 time(s). 2. End task in task manager, Error 35400 automation error.jpg (2,598kb) downloaded 0 time(s).odd, images were showing in my preview for the post, I will try to upload these again with this replay.

In regards to excel running in the background, I have confirmed that it is running when I start the export process.

I have also restarted the PC that ESdat is running on as well as updating the office suite running on the machine. The error is still appearing after all of these measures.

This is affecting all of the data that has been uploaded into ESdat (water levels, chemistry, etc). We do not have any issue with uploading data into the software, this only problem we are having is the export of this data either in tabulated form or plotting of the data graphically. I have attached 4 photos that detail the errors that all users are encountering, see the details for each of these below:

• 1st Image: we see this message after we attempt to export data, ESdat appears to hang until we click anywhere on the screen and this message appears. We try the “switch to..” and “Retry” options and nothing happens and we end up back at this message in a repeating loop.
• 2nd image: Looking at the task manager we see that excel is running in the background. We end task on excel and this automation error appears.
• 3rd image: after selecting ok in the 2nd image this message follows on, selecting okay causes ESdat to close down.
• 4th image: after seeing the error message in the 1st image we attempt to right click on the ESdat icon on the task bar and close the software down manually. This message now appears, selecting okay asks us to sign in as an admin to Microsoft access.

See my comments regarding the suggested actions below:

*Does doing a “Repair” on Excel resolve it? No, issue remains. See below comment for other versions of Office being installed on the PC. One version removed, repaired installed version but error remains still.

*Does reverting your PC to a previous "Restore Point" resolve it? No, issue remains from a pervious version

*Are applications from different versions of Office on the same PC? Office 2016 and 365 were installed on the PC in question, removed Office 2016 but the error remains.

*Were other applications recently installed on the same PC? The following applications were install around the time of this error; ScreenConnect Client, Google Chrome, Microsoft Edge, Microsoft Edge WebView2 Runtime.

Edited by moderator Thursday, January 6, 2022 2:45:24 PM(UTC)  | Reason: Not specified

I have had my IT department uninstall and perform a fresh re-install of Office 365, this has not resolved the issue.

I have followed some of the tutorial documentation in regards to database issues and tried to load the sample contam database file and found that I am able to successfully export this data both graphically and tabulated in excel. I have also found that some of the existing projects ESdat databases are able to be exported as well. This is random as to which ones are able to be exported but it appears that the majority of the projects can not be exported at this time.

Could this be evidence of database corruption and, if so, is there a way that the databases can be recovered?

Originally Posted by: Support

Hi,

I can't see the messages mentioned in your post, however potentially Excel is running in the background but not visible.  Have you rebooted your PC?

Alex

Yes, the PC has been roebooted.

I have also tried to export the databases that I am having an issue with to the ".edif" file and tried to create a new database and importing this data into.

I have the same error occuring when I perform this as well.

Hello,

We've seen two other users with this issue, it is likely to be caused by a bug in a recent patch of Windows or Office and impacts users that are using ESdat Desktop with Access databases.   ESdat Server or ESdat Online systems aren't impacted.

A possible temporary workaround that may work in your case is to copy the Access database to your local c drive, and see if it works ok from there.

Other things to try are

See if restoring your PC to an earlier (say November or earlier) Restore Point resolves it.

If not try reinstalling the Microsoft Access drivers https://www.microsoft.com/en-us/download/details.aspx?id=13255 

Originally Posted by: Richard Lamendin

Hi, I think I might be having a similar issue (using ESdat desktop with access). There is a particular ESdat database which won’t let me export any exceedance tables. The program freezes and I am forced to close it using Task Manager.

When I do this I get a notification saying "ODBC microsft access driver login failed", follwed by a request to input an authorisation password which I've never come across before.

I got our IT team to restore the database to a previous version from December, but this has had no effect. Neither has reinstalling Office 365.

Last thing that I tried was copying the database to C drive - this worked, but obviously not a long-term solution.

Does this sound like the same problem that Emerge43 is experiencing?

Regards,

Richard

 

I  believe that we have resolved our issue with ESdat not exporting imported data. We have located a new PC and done a clean installation of ESdat on this new PC.

Initail checks this morning have allowed us full access to the data with the ability to export the project databases that we have not been previously able to export.

I would suggest either attempting this or trying to use a fresh installation of ESdat. I hope this helps you.

Hi Everyone,

See also this forum post.  https://www.ESdat.net/forum/posts/t1007-Application-busy