Thank you for your post.
The error code at the end refers to no records found (401) and record access denied (200). Since these are occurring a minute apart, do you have any kind of schedule running at a minute interval? Do some of these scripts involve a Perform Find script step? If so, you may want to turn on error capture and check for FoundCount = 0.
I will need additional information before progressing any further.
Only schedule is a daily backup.
The "wpc" leads me to believe it has something to do with Web Publishing (?).
Could it be the WPE that is unable to access a file that it needs?
The web functionality appears to be working correctly - I am able to create rcds in my web-interfaces pages.
Does the WPE attempt to access each file that has sharing enabled (once each minute)?
The corresponding pe_application_log is empty.
The WPC Access Log shows entries such as:
188.8.131.52:0 - <loginname> 2009-03-02 13:01:36 -0800 "/fmi/xml/FMPXMLRESULT.xml" 200 1184
184.108.40.206:0 - <loginname> 2009-03-02 13:01:36 -0800 "/fmi/xml/FMPXMLRESULT.xml" 200 455
220.127.116.11:0 - <loginname> 2009-03-02 14:23:00 -0800 "/fmi/xml/FMPXMLRESULT.xml" 200 1177
18.104.22.168:0 - <loginname> 2009-03-02 14:23:00 -0800 "/fmi/xml/FMPXMLRESULT.xml" 200 455
22.214.171.124:0 - <loginname> 2009-03-02 14:25:33 -0800 "/fmi/xml/FMPXMLRESULT.xml" 200 1709
126.96.36.199:0 - <loginname> 2009-03-02 14:25:33 -0800 "/fmi/xml/FMPXMLRESULT.xml" 200 455
I'm not getting any complaints from the web users. According to your note, the "200" would imply an access denied. But again, they are able to create the rcds they need. Unless the "200" has a different meaning for xml results. And these are just occasional in the Access Log.
It is deployed as a "single machine" - all in one.
The rcd identifyer at the end of the ip address (127.0.0.1) sequences from 1024-5000. Here is an example of the transition in the pe_interal_access log:
127.0.0.1:4997 - - 2009-03-02 12:20:04 -0800 "/fmi/conf/config.wpc?-no_status=" 401 0
127.0.0.1:4998 - fmsadmin 2009-03-02 12:20:04 -0800 "/fmi/conf/config.wpc?-no_status=" 200 2190
127.0.0.1:1027 - - 2009-03-02 12:21:04 -0800 "/fmi/conf/config.wpc?-no_status=" 401 0
127.0.0.1:1028 - fmsadmin 2009-03-02 12:21:04 -0800 "/fmi/conf/config.wpc?-no_status=" 200 2190
Thank you for the clarification.
I totally missed the "no_status" line in the original post. My fault. These are WPC health checks, and they are checked every minutes. However, these do not show up in my logs. Are you using FileMaker Server 10 or an earlier version?
Yikes, sorry I forgot to add that to my original post:
FMS 188.8.131.526 on Win2003
Installed in the default dir. No additional User or Active Directory changes made - I just ran the install program. I don't want to direct you in the wrong direction, but maybe it has something to do with permissions. On a unix/mac box, this would definitely be a consideration. Not sure on a Win2003 box. Are there permission/rights issues that I should look into? Or does this msg imply that I'm missing a file somewhere. Is there a config option that I can review?
I turned of IWP; XSLT Publishing was changed from Dev to Production; Since I didn't have any plugins, I turned of plugins; then I turned off XSLT. None of these affected the log entries. I did see the WPC restart entries in the log, then these "health check" entries start back up again.
After talking to a few people, this DOES occur with FileMaker Pro 9. It was removed from FileMaker Pro 10, because these WPC Health checks clutter up the log. Sorry I didn't get this information earlier as it would have saved both of us some time.
So, the bottom line is that these health checks do appear in the logs and you should not worry about them.