connect : the attempt to connect was rejected

[mct0]

I did a reinstall of Webinator Commercial (long story), and all appeared to go well.

Then, out of the blue, I get this message when I try to do a search.

A bit of a hunt about and I found some permissions errors in the copying of a licence file, and I have opened permissions on the relevant directories (I believe) wide open.

It went away. It then recurred. Then it went away again... and all I can credit with the "went away" is that I had done a command line license check!

Thing is, short of sitting there watching the damn thing, I have no way to know when it is going to fail again!

Help?!

Mark Trescowthick
GUI Computing

[mct0]

Using IIS 5 on Win 2k.

Logs don't show anything during the period it was refusing connections.

My task list currently has *3* copies of monitore.exe running. Which doesn't seem right??

I have a suspicion (and only that) that it is somehow getting confused by the fact that I routinely connect to it using two different URLs... could that be an issue?

eg : http://<machinename> and http://intranet.clientdomain.com.au

Certainly, that does seem to get login routinely tied up in knots, and would about match the timimng of the failures...

Mark

[mct0]

We are using the ISAPI filter.

Perhaps you're correct, and the second instance of it stopping was because the permissions had only just been changed and something got confused... it has been going now for 12 hours with no issues.

You say runing it as a service is the best option... can I do that at any time and will that have any impact on current activity?

[jason112]

Yes, registering it as a service can be done at any time.

It definitely sounds like the Monitor Web Server (which Texis ISAPI communicates with) ends up stopping. Running it as a service should help make sure it stays running.

[mct0]

Thanks... that sorted us out.