Hi all, over the past few weeks we there have been several large Windows 10 updates. Following one such update Hevacomp on each of our Windows 10 machines has stopped working with the above error message. We are able to open the main Hevacomp Design Software panel with the icons but, for example, when we select DDB we get the run-time error dialogue straight away. When we click Netsys, we clock a system type, say heating, then get the project explorer window but it cannot see any of our windows files. Our Windows 7 machines are working fine.
We have uninstalled Hevacomp, and deleted any residual files, although left Crystal Reports. We then restarted the machine, then reinstalled Hevacomp with the latest Update 6 but we still get exactly the same error messages.
The same thing happens on all three of our Windows 10 machines.
Any suggestions?
Hi Keith - Can you check inC:\Program Files (x86)\Common Files\Microsoft Shared\DAO\and let me know what files you find in there?Thanks,
Duncan Brown
Hi Duncan, the only thing I can see in there on all 3 machines is a file "dao360.dll".
Also, our IT people thought you should know that we are using Windows 10 1803.
One of the machines has just had a rebuild, so we are reinstalling on a "clean" machine and we get the same error.
I'm still not 100% convinced its an 1803 issue. Let me know about creating a new user account and running that.Thanks.
Our IT team created a new user account on machine 1. Same issues.
We also have a Windows 7 machine which I've just installed Update 6 and it still works fine.
I came across an article that suggested having a large amount of files linked off from things like Documents folder could cause the issue - it was an old issue, but I thought it might be worth a try, as creating the new user wouldn't be linked to all the other users folders.If you check the folders for Documents, downloads, etc, are there a large number of files in there?
Nothing at all in Downloads as we try and keep that empty. Some stuff in Documents, but I wouldn't call it lots. There is an old "Hevacomp Projects" folder in there.
I didn't recall seeing anything particularly extreme in our remote session. At this stage about the only suggestion I have left is a rollback for the Windows update or a computer rebuild, even though I'm still not 100% convinced it was an issue with the 1803 update as you have an updated Windows that is working with the software.Can you ask your IT to roll back one of your computers?