Hi

We have seen the following Line in the edaprint.log file.
HTTP Listener Crashed.

What are the Possible Reasons for this to Occur?
what are the Consequnces after this Crash?
What should we do, so that this will not occur in future?

Thanks in Advance..
Viswakanth

Hi Viswa,

Please contact Tech Support and open up a case.

While these forums are hosted by Information Builders, this is not an official support channel. It is intended for sharing of ideas, tips, techniques, etc. To report serious product issues or a production down problem, please contact Tech Support. Before you call, be sure to have your information at hand. Alternatively, you can open a case via InfoResponse Online.

monte2000
I do Contact regularly Tectsupport guys of IBI. but i haven't got any concrete solution from them. i thought, anyone from this forum could helpme int his regard.


Thanks
Viswa

The reason monte2000 made that recommendation is a crash can be due to different things, and without specific information any advice we gave you would be without value... specifically for the listener, it might be configured to use an occupied port on the machine. The listener serves the server console, and also can be used as a lightweight web server when using WF Developer Studio; possibly a request was interrupted, or there was a network error, or...

If it's critical to find out why a crash could happen, it's strongly recommended to contact our support personnel and provide them with information on your installed products, versions, and configuration.

Vis, i've had the same exact thing. http listener crashed. it was a real mess. I asked for a caster specialist on the tech support line , and they dialed into my machine (that cool downstream tech support thing they do) and i can't tell you what they did to fix it, it was way over my head.
all i know is that when it happened, even rebooting the box didn't work. it was definitely a priority 1 down. it hasn't happened again since we up'd from 5.2.1.