Psycnotics 11 Posted January 28, 2016 Posted January 28, 2016 hello, my Emby takes since last Update to Version 3.0.5818.0 more than 2 hours to Scan my Library, befor takes arround 20 mins. Anyone with the same or similar Problems? Martin
Psycnotics 11 Posted January 29, 2016 Author Posted January 29, 2016 Why i have tons of this Error in my log : 2016-01-29 01:00:02.5140 Error App: Error getting response from http://api.themoviedb.org/3/person/1285448?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=credits,images,external_ids *** Error Report *** Version: 3.0.5818.0 Command line: C:\Users\Administrator\AppData\Roaming\MediaBrowser-Server\System\MediaBrowser.ServerApplication.exe -service Operating system: Microsoft Windows NT 6.2.9200.0 Processor count: 4 64-Bit OS: True 64-Bit Process: True Program data path: C:\Users\Administrator\AppData\Roaming\MediaBrowser-Server Application Path: C:\Users\Administrator\AppData\Roaming\MediaBrowser-Server\System\MediaBrowser.ServerApplication.exe Mindestens ein Fehler ist aufgetreten. System.AggregateException bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) bei System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult() bei MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__1b.MoveNext() InnerException: System.Net.WebException Der Remoteserver hat einen Fehler zurückgegeben: (404) Nicht gefunden. bei System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) bei System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
Happy2Play 9783 Posted January 29, 2016 Posted January 29, 2016 (edited) Your getting a (404) error so the people id 1285448 Emby is looking for doesn't exit. Edited January 29, 2016 by Happy2Play
ebr 16187 Posted January 29, 2016 Posted January 29, 2016 Update to the new beta and those should go away.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now