You are here

[solved] 1.1.1/53 fails

15 posts / 0 new
Last post
Christoph21x
Offline
Joined: 11 years
Last seen: 5 years
[solved] 1.1.1/53 fails

Dear Jan - when I saw, you really released an update, I wanted to write you, telling you, that I'm still a huge fan & use it on a daily basis.
Again: thanks!!
Nevertheless, the /53 version doesn't work on my system - see log below.
(Nothing's produced but the channel header in the guide.xml file)
I use the previously existing config file - do I have to add or change something?
Sending you kindest regards from Switzerland - Chris
LOG:
WebGrab+Plus/w MDB & REX Postprocess -- version 1.1.1/53.17 -- Jan van Straaten
-------------------------------------------------------------------------------
job started at 25.06.2014 10:14:23

reading config file: C:\ProgramData\ServerCare\WebGrab\WebGrab++.config.xml
loading timezone data
embedded timezones source: WebGrab_Plus.TimezonesData.txt
 

WGMaker
Offline
WGMaker's picture
WG++ Team memberDonator
Joined: 12 years
Last seen: 1 hour
Is the support helpful?
support us

Hi Christoph
 
difficult to see what goes wrong. Is that the whole log file, nothing else, no error message?
What OS are you running? It's been tested on Windows and Linux. Can you try it on an other machine? What version did you use before this one that gave no problems?
Send us the log and the config.
 
Jan

Christoph21x
Offline
Joined: 11 years
Last seen: 5 years
WGMaker wrote:

difficult to see what goes wrong. Is that the whole log file, nothing else, no error message?
What OS are you running? It's been tested on Windows and Linux. Can you try it on an other machine? What version did you use before this one that gave no problems?
Send us the log and the config.

Hi Jan!
Yes, that was the whole log. The one produced just now was even shorter - see attachment.
OS: Win 7 x64 Ultimate; previous WebGrab+Plus version was 1.1.1/52 - and this produces still valid output if I exchange the *.exe back. Same result on other machine.
Greetz - Chris

Attachments: 
francis
Offline
francis's picture
Has donated long time agoWG++ Team member
Joined: 12 years
Last seen: 8 months
Is the support helpful?
support us

Well,
I see a few things here.
 
1. put <logging>on</logging>
now it is off in your config file.
 
If you then run WG++ again, I hope you get the full logging (not sure, but if you could try that)
 
2.
there are several duplicate channel definitions in the config file. Those have to be removed.
 
Hope this helps?

Christoph21x
Offline
Joined: 11 years
Last seen: 5 years
francis wrote:

I see a few things here.
1. put <logging>on</logging>
now it is off in your config file.

Hi francis, thanks for your help - no change then, log is identical with aboves post :(
 

francis wrote:

2. there are several duplicate channel definitions in the config file. Those have to be removed.

Not a cause - they're not identical as they all have different xmltv id's - thus for WG++ they seem to be (ARE) different, they just are read from the same source. This is needed on my system as I use Argus TV and if I assign the same xmltv id to 2 channels (HD/SD) I can't differ, on which channel they're recorded (either both or none :) )
Any more idea? :)
From my perception sth with timezone or the new statistics collection. I also see that the exe's file size is nearly twice as big - why?

francis
Offline
francis's picture
Has donated long time agoWG++ Team member
Joined: 12 years
Last seen: 8 months
Is the support helpful?
support us

Do you have more logging on the command line?
So not the logging from the log file, but the logging in the console when you run WG++.

Christoph21x
Offline
Joined: 11 years
Last seen: 5 years

Unfortunately not. It shows just:
         WebGrab+Plus/w MDB & REX Postprocess -- version 1.1.1/53.17

                           Jan van Straaten
                         Francis de Paemeleere

        many thanks to Paul Weterings and all the contributing users
        ------------------------------------------------------------
.. and then ends - nothing more

Christoph21x
Offline
Joined: 11 years
Last seen: 5 years

Wait...
found just one old client machine on which the new version works - very old config, though.
Let me investigate and try a bit on this one and I'll come back with hopefully some information.
Either I'm dull (which can be, I know me :D ) or we might find an issue which occurs on certain setups...

francis
Offline
francis's picture
Has donated long time agoWG++ Team member
Joined: 12 years
Last seen: 8 months
Is the support helpful?
support us

I hope the first option laugh

Christoph21x
Offline
Joined: 11 years
Last seen: 5 years
francis wrote:

I hope the first option

Thanks, very friendly :lol:
Have to talk to Jan, until just now, I was Oranje-Fan! :D

Christoph21x
Offline
Joined: 11 years
Last seen: 5 years

Ok, found it.
If any of the channel.ini files contains @MinSWversion entry which isn't exactly following the rules of the expected format, WG++/53 quits without notice. (/52 not, working correctly). Happened because I re-newed the ini file, kept mine (but Jan adjusted the re-newed to correct format before publishing)
Example:
Working: @MinSWversion: V1.1.1/51
NOT working: @MinSWversion: V1.1.1/51-09
You should put back the "ignore if can't be recognized" in place like in version /52
Everything's working now. Thanks, Francis, for your help & kind regards from Switzerland - Chris

francis
Offline
francis's picture
Has donated long time agoWG++ Team member
Joined: 12 years
Last seen: 8 months
Is the support helpful?
support us

Whow, nice one.
"ignore if can't be recognized" OK, but with a warning (please)

Christoph21x
Offline
Joined: 11 years
Last seen: 5 years

PS: ... WG++ should perform the other source.ini files nevertheless (which is not), which are correct. And there should be a log entry, that the source.ini is skipped due to wrong version

WGMaker
Offline
WGMaker's picture
WG++ Team memberDonator
Joined: 12 years
Last seen: 1 hour
Is the support helpful?
support us

Hi Christoph

 

actually I was not aware that 53 makes problems with the syntax of the SWMinVersion. I will add this to the todo for the next build. Can you give me a few examples of what goes wrong and what not?

 

Oranje-fan? Didn't know there are any in Switserland!

 

Jan

Christoph21x
Offline
Joined: 11 years
Last seen: 5 years
WGMaker wrote:

Hi Christoph
actually I was not aware that 53 makes problems with the syntax of the SWMinVersion. I will add this to the todo for the next build. Can you give me a few examples of what goes wrong and what not?
 
Oranje-fan? Didn't know there are any in Switserland!
Jan

Hi, dear Jan!
You find an example of what is working and not working in a post above... attached to this, I added a zip with two tvtoday.ini.xml files - one woring, one not. But I tried the differences and thus found out that it's the SWMinVersion, that actually makes the difference. I think, it's rather "cosmetic", as nearly none of the user would ever stumble over it...
In fact the only real "error" is, that not any of the ini files will be processed if a single ONE fails in SWMinVersion checkk fails.
For the one which is faulty, there should be a logged error - that's it.
For what concerns Oranje (even more important :D ): SURE!!! MANY!! Since the Euro 08... since many visitors from the Netherlands were here in Switzerland and were the MOST DELIGHTFUL people - according to the majority of Swiss. They were just full of fun and joy and friendliness, living openness and internationalism - everything was orange here. And really (I would say) the most of the Swiss were very very positively surprised. And since then, you can feel it here...
You see, such things and events may have an effect. Hup Oranje! (Now that we are out :) )
Kindrest regards - Chris

Attachments: 
Log in or register to post comments

Brought to you by Jan van Straaten

Program Development - Jan van Straaten ------- Web design - Francis De Paemeleere
Supported by: servercare.nl