Initialization error. Please try again later.

Post your questions here if you need help to use NewsLeecher or if you have a question about a feature.

Post Reply
rmhochman42
Posts: 31
Joined: Fri Sep 20, 2019 6:57 pm

Initialization error. Please try again later.

Post by rmhochman42 »

Been getting this now for more than 24 hours windows 10 , Newsleecher 7.0 final - does NOT happen under Windows 7, Beta 8.0 v4

Submitted to tech support yesterday, no response

log shows:

1:17:32 PM Launching NewsLeecher v7.0 Final.
1:17:32 PM .
1:17:32 PM File & Folder Locations ...
1:17:32 PM * NewsLeecher App Folder: C:\Program Files (x86)\NewsLeecher\
1:17:32 PM * Settings File Location: C:\Users\BOB\AppData\Roaming\NewsLeecher\setup.v2.dat
1:17:32 PM * Data Folder Location : C:\Users\BOB\AppData\Roaming\NewsLeecher\
1:17:32 PM * Temp Folder Location : C:\Users\BOB\AppData\Local\Temp\!NewsLeecher\
1:17:32 PM File logging is: Disabled.
1:17:32 PM Loaded and initialized PAR2 checking and repairing functionality ( DLL v1.0.12.0 )...
1:17:33 PM Loading Download Queue ...
1:17:33 PM * Group Entries Active : 0 ( total cache loadtime was 0ms )
1:17:33 PM * Total load time : 0.19ms.
1:17:33 PM Loading Repair & Extract Queue...
1:17:33 PM * Total load time : 0.00ms.
1:17:33 PM Loaded ID-list and CRC check numbers for downloaded files in 2.5ms. ...
1:17:33 PM * 0 of 17,429 IDs deleted from list because they were older than 90 days. Loaded CRC check numbers : 382.
1:17:33 PM Loaded 1 SuperLeech entry in 0.008ms.
1:17:33 PM Loaded 2 SuperSearch Bookmarks / Recents in 0.003ms.
1:17:33 PM Secure Socket Layer Helper Files Versions <1.0.2.1> & <1.0.2.1>
1:17:33 PM Successfully confirmed version of helper file "nlpar.dll" to be >= 1 (1.0.12.0).
1:17:33 PM Successfully confirmed version of helper file "unrar.dll" to be >= 5 (5.1.100.1066).
1:17:34 PM Could not properly contact the NewsLeecher servers for news updates, etc. (ID:7121). Please report to author if problem persists. [ Socket Error # 10054
Connection reset by peer. ]
1:17:34 PM SuperSearch was unable to be initialized ... Using Cached Initialization Info ...
1:17:34 PM * SuperSearch Conn. Info: Gen.IP="136.243.76.160" :: Ero.IP="136.243.76.160" :: Ports="443", "443" :: Retention="3250".

Antonin
Posts: 86
Joined: Mon Aug 01, 2005 12:51 am

Re: Initialization error. Please try again later.

Post by Antonin »

I also experienced the same thing yesterday. I reset my router & modem and it went away. It would be nice if this was not a serious error.

rmhochman42
Posts: 31
Joined: Fri Sep 20, 2019 6:57 pm

Re: Initialization error. Please try again later.

Post by rmhochman42 »

Didn't help (and also rebooted desktop). And as I said, it is not happening on my Win 7 machine running 8.0 beta 4, just my windows 10 box running 7.0 final. Still would like feedback from Tech Support.

Post Reply