FMServer 7 Advance Unknown Error 802

[heath762]

I have a Windows 2K3 server and Filemaker 7 Server Advance with Web publishing enabled and working correctly, and all of a sudden a connecting web client machine gets an "Unknown Error 802" and can't connect. The authentication to the IIS server is anonymous(without Windows Authentication checked). When I restart the Filemaker server service everything is fine again, for a while. Also, the normal Filemaker Pro 7 clients can still connect without a problem. Help!!!

[Zardoz]

I've seen this Error 802 as well. We're also running FMS 7 Advanced on W2K3, and we're doing some testing with Instant Web Publishing.

What started happening, seemingly out of the blue, was that whenever I would click to open a specific file on the database home page, the response would be very sluggish and the file would never open. Turns out that the Web Publishing Engine service on W2K3 was eating up 50% or more of the CPU resources for some unknown reason. We would then stop and restart this service and everything would seem back to normal at the server end. For the first 2-3 minutes after starting the service, if I clicked to open the file, the 802 error message would be generated. It seems as if the Web Publishing Engine service needs a few minutes to start up fully, and that it is not possible to open a file until the startup process is complete. However, once the startup process was complete, clicking the file to open it would recreate the sluggishness problem all over again, with that one service again consuming an unusually high percentage of the CPU resources. It was a vicious cycle.

The problem was isolated to this one file only; clicking to open the other file that we were testing with did not cause this problem. So I examined the startup script for the problem file and, although all script steps were showing as web compatible, some script steps were using the Get (UserName) function. This UserName is the name that is set in the Preferences or File Options area on desktop clients; I don't believe it has any meaning in the Web context. So when I revised the script to bypass these script steps for Web clients, the sluggishness problem went away.

I'm not sure why this problem suddenly started happening in the first place, as many successful logins via the Web to this database had occurred previously. As part of the testing, I have been playing around with accounts and privilege sets and various other settings, so it is possible that I changed something that brought this problem to the surface.

Hope this helps.

[heath762]

This problem seems to be authentication to the FM files to be served from the WPE. I am not sure how this works and what accounts need access through the WPE if any. I am assuming that the account that opens the FM database is an internal account to FM or the IUSR account for the Web Server.

The fact that is works after I cycle the FM Server service and then stops again is a bit confusing. This Error 802 happens after normal operation for some period of time. Should I update to the latest version of the FM, I am running v1 and I think there is a v2. I will do that and keep the thread up to date with the results. Thanks for the info Zardoz.