Cannot write to KDBF file, No file write permission

[ryancasey]

Hello --

We're running into some errors when indexing a site. (We're using Webinator 5.1.54-Windows on Windows 2003.)

There are several error messages logged, and they are similar to:

Cannot write to KDBF file C:\Program Files\Thunderstone Software\Webinator\texis\site-prodb\db2\refs.tbl: No file write permission in the function kdbf_free

----

I've found other people posting similar errors in the past. I checked the NTFS permissions, and "Everyone" has full control so I don't believe it is a file permissions error.

Once these errors start to appear in the vortex.log file, texis.exe begins to consume 100% of the CPU until it is forcibly killed.

Is there a solution to this problem?

Thank you,
-Ryan Casey

[Kai]

`No file write permission' means that when Webinator opened the file, it was unable to obtain write permission, so file perms are still the likely cause. However, the actual user that is lacking the perms might not be in the group `Everyone'.

If you are using the Texis ISAPI filter, then the user that Webinator is running as is typically admin or whoever started the Texis Monitor service: restart the Texis Monitor service as a user with privileges to your dataspaces (ie. the dir in the error).

If you are not using the Texis ISAPI filter, then the user that Webinator is running as is whatever user IIS uses for CGI programs. This is typically I_USR or another low-privilege user; check your IIS config for the CGI path that you gave at Webinator install time.

You can also of course check the user that is running dowalk via Task Manager.

In any event, the true user that is running dowalk must have full control to the dataspace for the profile and its files (ie. all of Thunderstone Software\Webinator).

[ryancasey]

Well, that's interesting. It is running as a CGI program.

I did run the indexing process as via the NT Scheduler with an administrator account. I also re-set the permissions and I'm still getting the errors.

I'm working on creating a new profile to see if the problem goes away.

Thanks.

[Kai]

Ok; perhaps the NT Scheduler ran it as still another user (that KDBF message is from a walk, not a web admin page or search).

A new profile might not fix the issue, unless the dataspace for that new profile has full control for the user running the walk (the actual user running `texis', not necessarily the user pushing the `Go' button).

Once you start a walk, confirm the user running `texis' via the Task Manager; that is the user that must have full control to the walk profile.

[mark]

Something to keep in mind...
You may wish to switch to ISAPI which will fix most of this kind of problem. Using the NT scheduler would still be an issue. Is there some reason you can't use Webinator's built-in scheduler?

[ryancasey]

We had been using the webinator scheduler for quite a while, but then we started having the file permission errors as well as a texis.exe process consuming 100% of the CPU for hours.

I switched to using the NT scheduler so that the texis.exe process would run as an administrator (which it did, I checked the task manager).

Creating a new profile seems to have resolved it for the time being.

I'll also look into switching to an ISAPI module.

Thanks.