connect : the attempt to connect was rejected

mct0 · Post by **mct0** » Sun Jan 18, 2009 10:49 pm

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

Post by **John** » Mon Jan 19, 2009 12:06 am

Which web server are you using? Especially if using the included web server you may want to make sure that the monitor program keeps running. If Windows you can register it as a service:

monitor -R

or on Unix make sure it runs on startup.

You can also check the monitor.log and vortex.log for errors.

mct0 · Post by **mct0** » Mon Jan 19, 2009 12:12 am

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

Post by **John** » Mon Jan 19, 2009 10:18 am

The 3 copies of monitor.exe is probably correct, one overall, and then one for each database in use, and there is probably the settings database and the actual profile you are using.

Are you using the CGI texis.exe or ISAPI filter?

Making sure that the Texis Monitor is registered as a service should help. It is possible that the permissions issues you see were caused by the monitor running as you when you ran the license check, and then quitting when you log off. If you are using texis.exe then it would try and start the monitor as the IUSR_MACHINE, which typically does not have enough permissions. Using the Service means it should run as the Local System account which should have permissions.

mct0 · Post by **mct0** » Mon Jan 19, 2009 4:39 pm

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?

Post by **jason112** » Tue Jan 20, 2009 10:05 am

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 · Post by **mct0** » Thu Jan 22, 2009 1:11 am

Thanks... that sorted us out.