For firefox make sure NoScript is not enabled
Thank you, Plex Ninja.
Okay, so now I've found those files. Deleted them (several times). Deleted the server app. Downloaded it again. Same thing. Tried putting localhost:32400/web in my Firefox browser, it never connects, just clocks. (What is that supposed to do, anyway?)
I see the logs y'all are talking about but have no idea what I'm supposed to look at.
Now what?? Thanks.
1. Restart PMS
2. Recreate issue.
3. Upload the log (Plex Media Server.log) somewhere so we can take a look through it.
Thanks again, guys. Actually, I restored an older version (from going into my Time Machine), and it worked perfectly.
But I can undo it, I guess, and then upload the logs for you a little later today if you wish, since otherwise, it appears that newer versions of the server app won't work.
HI Guys,
I still have this problem. However, I do not even have the "Plex Media Server" directory under the "Application Support" library.
Is there anyway to completely remove Plex from the Mac Pro and start over?
Thank you,
Randy
Hi all
I had the same problem after upgrading to the new Plex Media Server. I tied all what was written in this thread. Nothing helped. I finally solved it. What helped was this thread:
https://forums.plex.tv/topic/123603-update-from-099-to-09103-plexpass-version/
I upgraded to Yosemite, put I also upgraded from PMS 9.8.11 directly to PMS 9.11.1. Obviously the db migration tool cannot handle such high jumps...
I really installed 9.9.15, then 9.10.3 and only then to 9.11.1. And e voilà. It works... Finally!
Thank you other linux thread.
HELP Needed
after upgrade my PMS stops at ...starting.
i don´t know what to do. i worked fine until the upgrade.
i can´t find any files regarding plex in the folder library :(
what to do
If you upgraded from before version 0.9.9.14 then it could be the database migration issue - upgrade first to 0.9.9.14 and run for 10 minutes then upgrade to 0.9.11.1HELP Needed
after upgrade my PMS stops at ...starting.
i don´t know what to do. i worked fine until the upgrade.
i can´t find any files regarding plex in the folder library :(
what to do
HI All,
My conclusion is that Plex is not compatible with OS X Yosemite.
I tried the fix and I could not find these subfolders and files in the Library folder.
I have tried to reinstall several times. Unless there are hidden files, I have literally cleaned out files containing "Plex", reinstalled and end up with the same problem of the server stuck at starting.
I am giving up on Plex at this point. Someday there may be an installation version that actually works on Yosemite.
I guess my only solution for now is to get the 128GB phone.
Hi,
I'm experiencing a simular issue. I tried to upgrade to the newest version (probably 0.9.11) from an unknown version (I thought I wasn't that far behind, but who knows). Plex starts and keeps "starting". I downloaded all previous versions from 0.9.9.14 and started each one of them (0.9.9.14 -> 0.9.9.15 -> 0.9.9.16 -> 0.9.10.0 -> 0.9.10.1 -> 0.9.10.3). 0.9.10.1 is the last one that works. When I try to start 0.9.10.3, I get this in the log file:
Nov 09, 2014 20:32:17 [0x10b4f0000] INFO - Plex Media Server v0.9.10.3.665-c9109e2 - Apple Mac - build: darwin-x86_64 macosx Nov 09, 2014 20:32:17 [0x10b4f0000] DEBUG - Opening 20 database sessions to library, SQLite 3.8.6, threadsafe=1 Nov 09, 2014 20:32:17 [0x10b4f0000] INFO - SQLITE3:0x10, 283, recovered 14 frames from WAL file /Users/svenmoleman/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal Nov 09, 2014 20:32:17 [0x10b4f0000] DEBUG - Running migrations. Nov 09, 2014 20:32:17 [0x10b4f0000] DEBUG - Running migration 20140811001121. Nov 09, 2014 20:32:17 [0x10b4f0000] ERROR - Exception inside transaction (inside=1) (/Users/admin/jenkins/pms-r-build/BUILD_TAG/darwin-x86_64/Library/DatabaseMigrations.cpp:115): Cannot convert data to std::tm. Nov 09, 2014 20:32:17 [0x10b4f0000] ERROR - Exception thrown during migrations, aborting: Cannot convert data to std::tm ... Nov 09, 2014 20:32:22 [0x10b573000] DEBUG - Crash Reporter: Starting up.
It looks like it cannot run the migration 20140811001121 successfully. Although I thought this one was already done by an earlier version (saw it in the log file while starting all previous versions one by one).
For now I'm glad I can run 0.9.10.1. Please let me know if I can assist in any way.
P.S. I'm running OSX 10.10 Yosemite
HI All,
Thank you to Sven Moleman. I had to install 0.9.9.16. It is working with Yosemite.
For some reason, there is no access to the more recent versions that may be working. Clearly, the most recent does not work with Yosemite.
Best regards,
Randy
Just wanted to add that I had this issue as well. I am glad I checked here. I installed 0.9.9.16 and it is now working again.
Yes, correct. 0.9.9.16 is working. I wish we can upgrade this a little to 10.x.
My understanding is that the latest update is the one that does not work. What ever you do, do not update to the latest version 11.x.
Anyway, I am happy that 0.9.9.16 is working !!!
Where are the migration scripts located?
0.9.11.1 would not start for me due to exceptions at migration 20140811001121. I just inserted 20140811001121 in the SQLite migrations table and now Plex starts. I want to validate whether the changes in the migration 20140811001121 are populated in my database (I believed I saw the same migration in the log file with an earlier Plex version. There were even newer migrations listed in the table, 20140811001121 was just missing). Perhaps I can save these changes manually.
Update: So far so good, all seems well on 0.9.11.1 (PHT and iOS work as expected). Plex for Xbox360 throws errors. Could be related to 20140811001121. could also be something entirely different.
I am new to Plex. I am very interested in keeping it, but I am having a problem getting movies to play as well. I would like to install an older version, but I am still in the trial period and do not have a Plexpass, therefore I can't download the older versions. I am reluctant to purchase a pass before trying it out. Just to make sure that I am having the same problem, this is what is happening:
I downloaded the server app and created a library, everything looks ok, my movies all show up correctly both on the server and on my tv with Roku, but if I try to play the movies on the server, the screen comes up and just shows the orange "working" ball forever. The movies won't start. If I try to view them from my Roku, orange ball for a long time then I get a message to make sure my server is on and connected.
I have tried deleting the files as was mentioned earlier in this thread, also uninstalling and reinstalling, etc.
I am also running Yosemite.
Any suggestions???
Thanks
Hi,
I have had this issue since installing Yosemite, I have tried deleting the framework and system bundles as suggested. This did not work and I noticed when I reopened the PMS app the bundles returned by themselves. Is that supposed to happen? I have tried a new install of the PMS and a newer version of Plex Home Theater. Still got the server is starting issue. Can anyone help?
So my plex was working perfectly fine until last update. New version it's giving me "A problem has been detected with core component of Plex Media Server", nothing works not reseting server setup from scratch, nothing on cleaning caches, nothing on resetting system and framework bundles. Even if I completely clean the whole Plex install and try old version (any version) then it's just stuck on "starting".
So pretty much after trying last version in update, none of versions work. Any ideas?
Most likely it's related to this:
Known bug. Fixed in next PHT release.
Most likely it's related to this:
No. I was referring to the PHT bug.
Sorry Atrus but you made me wonder. I quoted the post where you stated it was related to the PHT bug and you say "No. I was referring to the PHT bug". So what's the difference between the jumping icons, one being the PHT bug and the other being what h666 mentioned while both seem to describe "A problem has been detected with core component"?
Sorry Atrus but you made me wonder. I quoted the post where you stated it was related to the PHT bug and you say "No. I was referring to the PHT bug". So what's the difference between the jumping icons, one being the PHT bug and the other being what h666 mentioned while both seem to describe "A problem has been detected with core component"?
"A problem has been detected with a core component" is always PMS, and is 99% of the time solved by deleting the System.bundle and Framework.bundle
