EPG123 Permission Issues

[sethamin]

I just ran into some permission issues that I wanted to share. My updates didn't seem to be working, and I have Cablevision, so I followed instructions in this thread here. I also upgraded to EPG v1.2.1 at the same time (which was probably a mistake). After that, even though I got my lineups back (as per the above thread), the updates still didn't seem to be importing. My scheduled task was also not working (even though it reported exit status of 0x00000000). However, when I ran EPG123 as Administrator, it did work and import correctly.

I think the issue this was all a permission issue; I changed the permissions of the epg123 directory to allow "Full Control" by all users, and now everything seems to work again. Again, I'm not sure if the upgrade to v1.2.1 caused this, but it seems possible. Just wanted to share in case anyone else hits this issue.

[garyan2]

The update shouldn't have been a cause. Was there anything in the trace.log file?

[sethamin]

No, nothing interesting. Not in the event viewer, either. Though I noticed when I ran EPG123 without administrator privileges the trace.log timestamp didn't seem to update. So I think it failed to update the MXF file and/or the log file (or both).

[garyan2]

Where did you install epg123? It didn't have write permission to the folder. If you installed in the Program Files folder, then changing the permissions to Full Control for all users is my goto suggestion.

[sethamin]

Yup, that's where it was installed, and that's what I did. Still not sure how or why the permissions changed, though.

[garyan2]

Yah, that doesn't make since if you already had epg123 installed in that location and it was working. I'll take a look at my installation scripts to see if it does anything, or if there is anything I can do to avoid this.

[12noon]

Even if the user elevates the permissions of the installer in order to put EPG123 in Program Files, the EPG123 folder's permissions aren't changed. That means the user (and, by extension, EPG123) still doesn't have permission to write to the installation folder.

Instead of changing the permissions of the EPG123 folder in Program Files, you'd be better off uninstalling it and installing it to another folder.

Gary, you might consider adding text to the installer to discourage people from using the Program Files folder. Alternatively, instead of creating the EPG123 config and cache files in the installation folder, maybe use a folder in AppData/Local/. (That'd probably be a lot easier than dealing with the issues that regularly arise from people installing to Program Files, and it's the solution recommended by Microsoft for app-created files.)

Not that you need it, but...

Code: Select all

	string pathFolder = System.IO.Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData), "EPG123");

Of course, EPG123 would have to do something like look for the config file in the installation folder and move it to the new folder, but that's not too bad. (Easy for me to say, of course.)