Ran the Plex Server application as administrator one time, now...

General Discussions
1

I decided to test out the hardware decoder PMS version, and during my testing/troubleshooting I ran the app (not the installer, the application after installing it) one time as the administrator (right click, run as administrator). Now, when I try to run it as the normal user it refuses to allow any access to the server. It seems I’m stuck having to start it as the administrator now (right click, run as administrator). @sa2000, do you know any way to revert this back?

OS: Server 2012R2 Essentials

2

See where it is giving errors when not running as administrator and then check the related files / folders paths and ownership and permissions and correct them propagating down the hierarchy

3

No permissions errors, however there are differences between the non-admin and admin runs. The non-admin starts the crash log after retrieving the OCSP response, then there’s a 2 minute pause after updating the 28 access tokens, then a 1 minute pause after BPQ Processing IDLE, finally two errors after that - plug-in pipe com.plexapp.system and reading configuration for com.plexapp.system, both times resulting the stopping com.plexapp.system.

Dec 28, 2016 14:20:20.340 [4148] DEBUG - HTTP 200 response from GET http://ocspx.digicert.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBSnVdbEyh8T3xvVlkPGHNCJxnqCPgQUlIuJ90hyifJRStmIe%2BVhtaqc1QECEAGS1Frkpqqb5LNo6zJt0L4%3D
Dec 28, 2016 14:20:20.340 [4148] INFO - Successfully retrieved OCSP response
Dec 28, 2016 14:20:20.996 [8216] DEBUG - Job running: C:\Program Files (x86)\Plex\Plex Media Server\CrashUploader.exe "--directory=d:\pms\Plex Media Server\Crash Reports\1.4.0.3173-04b80c8" --version=1.4.0.3173-04b80c8 "--platform=windows-i386 (6.3 (Build 9600))" --serverUuid=7c32ba49023a1901017e64f284c3f38efbb386b4 --userId=kegobeer@outlook.com --url=https://crashreport.plexapp.com 
Dec 28, 2016 14:20:21.028 [7788] DEBUG - HTTP 200 response from GET https://plex.tv/servers/7c32ba49023a1901017e64f284c3f38efbb386b4/access_tokens.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&includeProfiles=1&includeProviders=1
Dec 28, 2016 14:20:21.028 [7788] DEBUG - MyPlex: updating with 28 access tokens
Dec 28, 2016 14:22:19.016 [7056] DEBUG - BPQ: [Starting] -> [Processing]
Dec 28, 2016 14:22:19.016 [7056] DEBUG - BPQ: generating queue items from 0 generator(s)
Dec 28, 2016 14:22:19.016 [7056] DEBUG - BPQ: generated 0 item(s) for queue
Dec 28, 2016 14:22:19.016 [7056] DEBUG - PlayQueue: 0 generated IDs compressed down to a 2 byte blob.
Dec 28, 2016 14:22:19.016 [7056] DEBUG - PlayQueue: 0 generated IDs compressed down to a 2 byte blob.
Dec 28, 2016 14:22:19.031 [7056] DEBUG - BPQ: [Processing] -> [Idle]
Dec 28, 2016 14:23:20.327 [6096] ERROR - Timeout or error reading status line from plug-in pipe [com.plexapp.system], we're killing it.
Dec 28, 2016 14:23:20.327 [6096] DEBUG - Stopping [com.plexapp.system].
Dec 28, 2016 14:23:20.327 [6096] DEBUG - [com.plexapp.system] Killing.
Dec 28, 2016 14:23:20.327 [6096] ERROR - Error received reading configuration for com.plexapp.system
Dec 28, 2016 14:23:20.327 [6096] DEBUG - Stopping [com.plexapp.system].
Dec 28, 2016 14:23:20.327 [6096] DEBUG - Done with 1 synchronous plug-in starts, starting the rest in parallel.

Compare those same lines in the admin run:

Dec 28, 2016 14:25:52.051 [6172] DEBUG - HTTP 200 response from GET http://ocspx.digicert.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBSnVdbEyh8T3xvVlkPGHNCJxnqCPgQUlIuJ90hyifJRStmIe%2BVhtaqc1QECEAGS1Frkpqqb5LNo6zJt0L4%3D
Dec 28, 2016 14:25:52.051 [6172] INFO - Successfully retrieved OCSP response
Dec 28, 2016 14:25:52.645 [6612] DEBUG - HTTP 200 response from GET https://plex.tv/servers/7c32ba49023a1901017e64f284c3f38efbb386b4/access_tokens.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&includeProfiles=1&includeProviders=1
Dec 28, 2016 14:25:52.660 [6612] DEBUG - MyPlex: updating with 28 access tokens
Dec 28, 2016 14:25:52.723 [3656] DEBUG - Job running: C:\Program Files (x86)\Plex\Plex Media Server\CrashUploader.exe "--directory=d:\pms\Plex Media Server\Crash Reports\1.4.0.3173-04b80c8" --version=1.4.0.3173-04b80c8 "--platform=windows-i386 (6.3 (Build 9600))" --serverUuid=7c32ba49023a1901017e64f284c3f38efbb386b4 --userId=kegobeer@outlook.com --url=https://crashreport.plexapp.com 
Dec 28, 2016 14:25:55.679 [6384] DEBUG - Reading 486 bytes in the body, code is 200
Dec 28, 2016 14:25:55.679 [6384] DEBUG - [com.plexapp.system] Plug-in running on port 65143.
Dec 28, 2016 14:25:55.679 [6384] DEBUG -  * Plug-in handles prefix: /system
Dec 28, 2016 14:25:55.679 [6384] DEBUG -  * Plug-in handles prefix: /player
Dec 28, 2016 14:25:55.679 [6384] DEBUG - Read configuration for [com.plexapp.system], had 2 prefixes
Dec 28, 2016 14:25:55.679 [6384] DEBUG - Done with 1 synchronous plug-in starts, starting the rest in parallel.
Dec 28, 2016 14:25:55.679 [6384] DEBUG - Updating the list of agents known by the system.
Dec 28, 2016 14:25:55.679 [5588] DEBUG - Image transcode cache directory: d:\pms\Plex Media Server\Cache\PhotoTranscoder
Dec 28, 2016 14:25:55.679 [6384] DEBUG - [com.plexapp.system] Sending command over HTTP (GET): /system/agents
Dec 28, 2016 14:25:55.679 [5588] DEBUG - Cleaning old transcode directories.
Dec 28, 2016 14:25:55.679 [6384] DEBUG - HTTP requesting GET http://127.0.0.1:65143/system/agents
Dec 28, 2016 14:25:55.679 [5588] DEBUG - MyPlex: using cached data for request for https://plex.tv/servers/7c32ba49023a1901017e64f284c3f38efbb386b4/access_tokens.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&includeProfiles=1&includeProviders=1

If I give the non-admin run enough time, eventually Plex responds. The admin run is immediate.

4

I went to the location I have the Plex data and I noticed that the user had special permissions for just the folder. I went to the root folder and edited permissions giving him full control over that and all items under it and that seems to have fixed things.

Thanks.

5

@kegobeer-plex said:
I went to the root folder and edited permissions giving him full control over that and all items under it and that seems to have fixed things.

I’d start a chkdsk run right away, just for safety.

6

Disks and file systems, plus OS all check out 100%.

7

When you ran as administrator it must have created some files within d:\pms\Plex Media Server with inappropriate permissions - ones that would not later be ok when running as non admin

The main difference between the 2 sets of logs is that when non admin, the python process started by PlexScriptHost.exe does not appear to have run correctly leading to the timeout