sec39

Here is a little update on my progress. I am still having the problems, below are the steps I took to try and fix the problem, attached with a picture. 1. Uninstalled Filemaker Web Publishing. 2. Searched through the registry for 'filemaker' and deleted out entries. 3. Reboot. 4. Installed Filemaker Web Publishing. 5. Reboot. 6. Logged onto localhost/fmi/config and set up administrator account. 7. Restarted IIS and Filemaker Publishing services in the mmc. 8. Error. Full size: http://www.lrdc.pitt.edu/compserv/fmerror.jpg The Web Publshing services are in fact running on the machine, but for some reason, filemaker does not recognize this. Any ideas?

I am having problems configuring the Web Publishing Engine. When I go to the /fmi/config page and input the IP address of the engine, it asks me to restart the filemaker service. When I try to restart the service through the website, I get the "An unexpected error has occurred." Instead of restarting the service through the website, I restarted the service through the MMC. When I log back onto the configuration page, it doesn't recongize that the Web Publishing Service is installed, the following error I get is: I have tried to install the Publishing Engine both locally on the Web Server and on the Filemaker Server itself. I receive the above error both ways. I decided to take a look at the logs and I noticed this error at the bottom, when I restart IIS. Both the web server and the filemaker server are running Windows Server 2003 with the latest updates. Both have the 7.03 update installed. Any ideas?

Is anyone aware of a cleaner type program that will wipe everything related to filemaker from a machine?

If that is the case and I couldn't access the administration console because I didn't log out, the only way to fix the problem would be to uninstall and reinstall -- both of which aren't working. I'm not able to access the administration console after reinstalling because the wpe and wpc services arent even running (they dont even show up in the services list).

One day I could not access the /fmi/config page on my webserver. I checked to see if the Web Publishing Engine service was running, and in fact, it was. I decided to go ahead and restart the service. Tried /fmi/config again and got nothing. At this point I decided to just go ahead and uninstall the Web Publshing Engine and reinstall. Upon uninstalling I got this error: then this error after hitting OK. Just hitting OK, I decided to reinstall the Web Publishing Engine and was then prompted with this error. After getting this error, the Web Publishing Engine does not show up in the services tab.. but it does say that its installed in Add/Remove programs. At this point, I am not sure what to do now. Does anyone have any ideas?

Does anyone know how I can set up virtual directories and have them Filemaker web publishing extensions enabled for them? For example, I want www.bob.com/fmi/config to be able to databases for bob.com but also have www.bob2.com/fmi/config to be able to configure bob2.com's databases. Any ideas? When I created a new virtual server in IIS, I'm not sure how to extended filemaker web publishing to the new virtual server.

Can someone explain to me what this means: For example, suppose an XSLT stylesheet references an image file called logo.jpg by using the HTML tag "img src="logo.jpg"". the logo.jpg file must be located in the following location on the web server: /fmi/xsl/logo.jpg" what defines the root folder? i've tried putting the image files everywhere with no luck.

Yep, I just tried and it didn't work I did notice a weird error when I load up the testxml database in Filemaker Pro. I get the error, "Filemaker cannot share files because another user is already sharing files using Filemaker Pro on this computer." I stopped the Filemaker server service to see if that has anything to do with it, and I still get the error. Is this contributing to the problem with site assistant?

Update for everyone: I've been continuing this thread here: http://www.fmforums.com/threads/showflat.php?Cat=0&Number=143937&an=0&page=0#143937 If anyone has any ideas or help, I'd really appreciate it, thank you.

Here's an update on my progress with this problem. I installed Filemaker server on a Windows machine and created a new database called testxml. I added fmxml and fmxslt to the database so that they show up as available for web publishing. I created a new user called test and password test and gave it full access. I then went on to the webserver and configured it to connect to the new Windows Filemaker server. The database page displayed the testxml database that I just created. I loaded up Site Assistant to connect to the database. Entered localhost as the server, hit connect, testxml came up. I click on testxml and it asks me for a username and password. I put in test/test, and bam, still Access Denied. Since I've tried it on mac and pc, I've found out that its not a communication issue between mac and pc. Is there a configuration that I am missing when setting up the Filemaker server or configuration of the web module?

Yep, I've tried creating a new user and giving it full access to the db and still nothing. I'm not sure if its related or not, but when I open up the database in the filemaker client (ver 7), I can just put in a password and leave the username blank, and it gives me access to the db. I've tried this on the web server, but still no luck.

Wow, finally I got a response, thanks. However, I'm still not able to connect to any database using Site Assistant. I created a new database from scratch. Added in the extended privaledges that are necessary for Site Assistant to see the database. I added a user to the database that had full access privaledges. I headed over to the web server, fired up Site Assistant, saw the new database that I created, and bam, same error. This is a brand new database and I can't even connect to it. Is there a problem or anything with going from a Windows web server to a Mac filemaker server? I'm not sure what to do next. Any information from anyone would be helpful. Whether its the filemaker server that isn't configured correctly or the web module on the web server. I'm not sure.

I've oringally posted this in the Filemaker Online section of this forum but have recieved 0 responses for the last couple days. Hopefully regulars in the section will be able to help me out. Here is a link to my original post. http://www.fmforums.com/threads/showflat.php?Cat=0&Number=143571&an=0&page=0#143571 Here is the content of my post also..

An update on my progress: I found a thread in the fmforums about someone who was having the same problem. Here is a link to the thread: http://www.fmforums.com/threads/showflat...true#Post138567 I tried creating a user account on the database that has just read only access and I'm still having the problem.

I'm not sure if this is the right forum to post this in, but here we go. I managed to get Filemaker Site Assistant to notice my database as being accessible. When I click on the db, it asks for a username and password.. I enter the information and I get access denied. I've tried resetting the password, all that jazz, and keep getting access denied. Any information would be appreciated. EDIT: I guess it will be a good idea to let you know the background of my setup. I have filemaker advance server 7 running on a mac g4. I am putting up a webserver on windows 2003. I installed the filemaker web module and tools so that I can have the web server access the filemaker server. I added extended prvialedges to the database for xml and xslt and it shows up in the filemaker web administrator area. I'm just having trouble using Filemaker Site Assistant. Hope this little bit of information is useful.