Recently I got a "Error Connecting to ZWO Focuser" The details of the error are : Access to the path 'C:\Program Files (x86)\Common Files\ASCOM\SystemLogs\ASIEAF\Logs 2025-02-05' is denied. (Error Code: 0x80070005)
The solution:
1) Create SystemLogs and under it ASIEAF folder as they did not exist
2) Try again still failure so under folder properties give these two files full permissions to all users listed.
3) Success
YMMV
Recent ASCOM EAF Error
Forum rules
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
-
kaymann
- Posts: 297
- Joined: Thu Jun 16, 2022 2:59 pm
- Location: https://azkayfes.blogspot.com/
- admin
- Site Admin
- Posts: 17468
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Recent ASCOM EAF Error
Thanks for sharing - helpful to have this sort of thing documented in case someone else runs into it.
cheers,
Robin
cheers,
Robin
Re: Recent ASCOM EAF Error
That’s Windoze “being helpful”, and blocking access to the logs directory - check the security center logs…
I find it easiest to set up exemptions for all of the Astro related apps in Security Center.
Cheers,
Carl
I find it easiest to set up exemptions for all of the Astro related apps in Security Center.
Cheers,
Carl
- admin
- Site Admin
- Posts: 17468
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Recent ASCOM EAF Error
Hi,
actually, now I read the error above again, Windows is probably doing the right thing here... By design the 'Program Files' directiory (and the x86 one, and everything inside both) is supposed to be only writable by admin users - this is a security boundary to try to keep people from planting things in there that could possibly contain malicious code. The ASCOM driver should be putting its logs somewhere else - %LOCALAPPDATA%, %PROGRAMDATA%, etc.
cheers,
Robin
actually, now I read the error above again, Windows is probably doing the right thing here... By design the 'Program Files' directiory (and the x86 one, and everything inside both) is supposed to be only writable by admin users - this is a security boundary to try to keep people from planting things in there that could possibly contain malicious code. The ASCOM driver should be putting its logs somewhere else - %LOCALAPPDATA%, %PROGRAMDATA%, etc.
cheers,
Robin