No IP address in Webserver (HTTPServer)

[InAws]

Hi,

 

for some while I've been using the HTTPServer to remotely configure programs to be recorded. Well beta version works for this, not the 'release' version.

 

Unfortunately since yesterday when I start the HTTPServer (beta) it does not list the IP interfaces in the drop down box, and it ignore the ip and port settings from the ini file. It also ignores the other settings from the ini file. I can select the activate button and the connect on start. When I try to connect with a browser there is nothing listening on the Port which appears in the port window (always 80, regardless of the setting in the ini file) and nothing listening on the Port from the ini file either.

 

The 'release' version simply wont start - it's window flashes on screen and then disappears.

 

There are no error messages (why are there never any error messages from the DVBViewer software - it is very annoying and wastes hours trying to fix problems) and I can find no log file anywhere.

 

I did recently have to reinstal DVBViewer (3.5.0.1) because it was no longer adding scheduled recordings to the Task Scheduler and the HTTPServer was always reporting that the DVBViewer was not running - even when I was sitting in front of it and it obviously running - again with no hint of an informative error message or log file entry. Following the reinstallation of DVBViewer the task scheduling is working again.

 

What is wrong with the HTTPServer? Is there some way I can enable a logging mode which can help me diagnose the problem? Does HTTPServer make some registry entries which have become invalid (if so, why doesn't it give a message?????) Is some required file missing (surely there would be some sort of message if this were the case)?

 

Any help appreciated,

 

InAws

[Guest Lars_MQ]

The httpserver doesn't write registry values. The http-server doesn't write a log. It only needs the exe file and the web folder with the html templates, all needed is included in the zip file you can download from the membersarea. Remember you have to have writing rights for the ini file in the folder the webserver resides.

 

rename the inifile and start the server clean. Do set the Port to a not used port. If it doesn't report the IPs there may something wrong with your system.

[InAws]

The httpserver doesn't write registry values. The http-server doesn't write a log. It only needs the exe file and the web folder with the html templates, all needed is included in the zip file you can download from the membersarea. Remember you have to have writing rights for the ini file in the folder the webserver resides.

 

rename the inifile and start the server clean. Do set the Port to a not used port. If it doesn't report the IPs there may something wrong with your system.

 

well, I agree, all it should need is what you said! I think it would be a very good idea if http-server did write a log file when it encounters a problem instead of simply not functioning. It would certainly have saved me hours of trying to figure out what was going wrong.

 

In the end I got it to work by restoring the english .lng file which must have been removed when I uninstalled DVBViewer. Why the application should fail simply because a language file is missing is beyond me, since the captions are already present in the application - and as I said, a log file or message indicating that a file was not found would have saved alot of time.

 

Unfortunately HTTPServer is still not working correctly with DVBViewer. After the machine is restarted the first time I try to start DVBViewer from the web page the Viewer gets started but hangs so I have to kill it from the task manager - this is inconvenient when I am 600km away from my machine. After this HTTPServer can start DVBViewer OK. Unfortunately I can't use the 'release' version of HTTPServer because it can't create new Timer entries (no indication of what goes wrong).

 

Any idea how HTTPServer could be causing DVBViewer to hang? Any chance of looking at the source code so maybe I could figure out the cause of the problem (in the absence of any logging).