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?
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?
Duncan Brown
Cannot find correct place for new variable to the situation, however we have machines with this problem which after logging in as administrator and applying the 2 stage fix allowed the administrator to open the database. Returning to the original user who now has administrator privileges the problem persists, any way of clearing the problem, registry clean up etc. ?
Kevin - I don't really understand why an different log ins would produce different results. Until we can generate a programmatic solution for this, my best recommendation would be to roll the last Windows update back.Regards,
Also...Please note I have created a service ticket for this query. This will help us keep the same issues controlled.