Hello,

I have 6 databases shared, all in the same folder, using FMS8. I can connect remotely to each using the FM server client. I can "see" and work with 5 of six using web publishing. I don't know why i cannot see the 6th database in the web listing.

I do not see the database in /fmi/config either. Is there something in the setup of the database that needs to be done? I don't ever use Filemaker, but am forced to support this, so I'm over my head for the moment. any help is appreciated.

In the database, you need to have at least one account that has privilege set assigned to it, and in that privilege set you need to have the fmiwp or fmxml extended privilege bit set.

If no active account has a privilege set with those extended bits set the file won't show up.

Edited December 17, 200619 yr by Guest

Everything that Wim said. Also, be sure that the file is actually being hosted by FileMaker Server. Check in the SAT Tool under files to be sure.

Steven

I just upgraded from FMSA 7 to FMSA 8. I can load custom web pages such as search.xsl, add.xsl, etc. The problem is none will perform a search or addition to the databases. Furthermore none are visible in /fmi/config. FMSA shows it is connected to the Web Publishing Engine. All database files work properly when I connect remotely to FMS via FMP client. Each database has an account with an extented priviledge set with fmxslt assigned. I assigned fmiwp to see if this would make files visible and it did not. File ownership and permissions I feel are correct. Is there anything else I should look at?

Moche:

fmiwp won't do anything for you since you're using custom web publishing and not IWP. Use the fmxslt extended privilege bit in your relevant privilege set.

I wanted to see if WPE could publish any of the databases via IWP. That is why I enabled fmiwp in the file. None of my databases were published but the example one included with FMSA does publish. It seems there is something wrong with my databases. I opened a database and did a "Save a copy as...". Figuring this may fix something. Unforturnated it did not. Also I do have fmxslt enabled in the relevant privilege set.

Problem solved! Re-installed Mac OS and FMSA. All works well now. There was nothing wrong with my database files. And it really did not take long to do this.