infiniteg

For anyone that's interested, here is a simple xsl file that uses server-side sessions. No database is needed for it to work. I made it while I was learning how to use them. Feel free to take and use for your own purposes. session_demo.zip

I solved the problem. See this thread

Problem solved! I uninstalled FM Advanced server and put it on another computer running Windows 2000 Server. Now everything works fine. Someday I would like FM Server & FM Advanced Server to live together on one machine but for now I'm happy. Martin - Thanks for helping me try to solve this problem!

You would have to use custom web publishing to do this... 1) Split the file into multiple sections. For example, area codes 001..300 go in one file, 301..600 in another, etc. You might have to break it into smaller pieces but you get the idea. 2) Make a web form with one input field for the phone number. 3) Make a javascript function that checks the form input (on submit) then, based on the area code, directs the request to the corresponding table. Just an idea. I don't know enough yet to verify that this would work but I'm pretty sure that it will.

Do you know how to turn on debugging for the FMICustomWebPublishingEngine servlet?

I just repeated the exercise to see what a successful request looks like in the log files when debugging is turned on. Unfortunately, it looks the same. Here's what a successful request looks like: ------------- 2005-05-06 19:36:04 StandardHost[localhost]: Mapping request URI '/fmi/xsl/quotes/recordlist.xsl' 2005-05-06 19:36:04 StandardHost[localhost]: Trying the longest context path prefix 2005-05-06 19:36:04 StandardHost[localhost]: Mapped to context '/fmi' 2005-05-06 19:36:04 StandardContext[/fmi]: Mapping contextPath='/fmi' with requestURI='/fmi/xsl/quotes/recordlist.xsl' and relativeURI='/xsl/quotes/recordlist.xsl' 2005-05-06 19:36:04 StandardContext[/fmi]: Trying exact match 2005-05-06 19:36:04 StandardContext[/fmi]: Trying prefix match 2005-05-06 19:36:04 StandardContext[/fmi]: Trying extension match 2005-05-06 19:36:04 StandardContext[/fmi]: Mapped to servlet 'FMICustomWebPublishingEngine' with servlet path '/xsl/quotes/recordlist.xsl' and path info 'null' and update=true ------------- Here's a request that resulted in the 'unexpected error': ------------- 2005-05-06 19:36:06 StandardHost[localhost]: Mapping request URI '/fmi/xsl/quotes/home.xsl' 2005-05-06 19:36:06 StandardHost[localhost]: Trying the longest context path prefix 2005-05-06 19:36:06 StandardHost[localhost]: Mapped to context '/fmi' 2005-05-06 19:36:06 StandardContext[/fmi]: Mapping contextPath='/fmi' with requestURI='/fmi/xsl/quotes/home.xsl' and relativeURI='/xsl/quotes/home.xsl' 2005-05-06 19:36:06 StandardContext[/fmi]: Trying exact match 2005-05-06 19:36:06 StandardContext[/fmi]: Trying prefix match 2005-05-06 19:36:06 StandardContext[/fmi]: Trying extension match 2005-05-06 19:36:06 StandardContext[/fmi]: Mapped to servlet 'FMICustomWebPublishingEngine' with servlet path '/xsl/quotes/home.xsl' and path info 'null' and update=true -------------

Do you think that the FMICustomWebPublishingEngine servlet is misconfigured somehow?

I think I've uncovered some more information. I read some tomcat documentation and figured out how to enable debugging. In the server.xml file, you have to change the verbosity to 4 for the &ltlogger&gt element and change the debug level to a number greater than zero (I used 3) for any component that you want to debug. Anyway, I did that and recreated the error. Here's what turned up in the logfiles: ---------------- Tomcat log (...jakarta-tomcatlogslocalhost_log.2005-05-05.txt) 2005-05-05 18:25:45 StandardContext[/fmi]: Mapping contextPath='/fmi' with requestURI='/fmi/xsl/quotes/browserecord.xsl' and relativeURI='/xsl/quotes/browserecord.xsl' 2005-05-05 18:25:45 StandardContext[/fmi]: Trying exact match 2005-05-05 18:25:45 StandardContext[/fmi]: Trying prefix match 2005-05-05 18:25:45 StandardContext[/fmi]: Trying extension match 2005-05-05 18:25:45 StandardContext[/fmi]: Mapped to servlet 'FMICustomWebPublishingEngine' with servlet path '/xsl/quotes/browserecord.xsl' and path info 'null' and update=true 2005-05-05 18:25:46 HostConfig[localhost]: Deploying discovered web applications pe_application_log.txt [05/May/2005:18:25:45 -0500] XSLT-CWP: An unexpected error has occurred (null) File: /fmi/xml/fmresultset.xml IIS logfile (timestamp is GMT, system time is -5 GMT) 2005-05-05 23:25:45 192.168.1.104 - 192.168.1.5 8080 POST /jakarta/isapi_redirect.dll - 200 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322) ---------------- That last message in the tomcat log, "Deploying discovered web applications", seems to always appear a few seconds after I get an "unexpected error" from browsing the site.

The corresponding IIS logfile entries all have a status code of 200. Here's the &ltconnector&gt tag from my conf.xml file: &ltConnector acceptCount="10" bufferSize="2048" className="org.apache.coyote.tomcat4.CoyoteConnector" connectionTimeout="0" debug="0" disableUploadTimeout="false" enableLookups="true" maxProcessors="75" minProcessors="5" port="16018" protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" proxyPort="0" redirectPort="8443" scheme="http" secure="false" tcpNoDelay="true" useURIValidationHack="false"> &ltFactory className="org.apache.catalina.net.DefaultServerSocketFactory"/&gt &lt/Connector&gt I also tried clicking through the site very slowly (i.e. waiting at least five seconds between clicks) and still experienced the same problem. Another piece of information that may be related to my problem is that I can't enable database sessions for xslt publishing. In the web console, when I toggle the radio button for database sessions to yes and click the apply button an error message appears at the top of the page. It says "An unexpected error has occurred."

Yes, there is. Here's a list of all the folders contained in the web publishing folder for my installation: conf jakarta-tomcat java logs publishing-engine Setup tools web-configuration xslt-template-files

Hi. I'm pretty new to custom web publishing so I used the site assistant to generate a few stylesheets so I could see how it works. I had site assistant generate all possible pages (insert, update, find, browse, home page, etc.) and for the most part it works pretty well. However, I randomly get sent to an error page after clicking a link or button. Here's what the error page looks like: ----------------------------------------------- FileMaker Custom Web Publishing with XSLT An unexpected error has occurred File: /fmi/xml/fmresultset.xml Line: Column: Note: If a source file and line number are indicated, this is the location where the error was detected and not necessarily the exact location of the problem. ----------------------------------------------- There is no pattern that I can figure out. It sometimes happens when I try to edit a record, other times it happens when I try to view the record list, etc. I checked logfile, pe_application_log.txt, and found some entries that might correspond to the error I'm getting. Here's what they all look like: ----------------------------------------------- [04/May/2005:13:51:26 -0500] XSLT-CWP: An unexpected error has occurred (null) File: /fmi/xml/fmresultset.xml ----------------------------------------------- If I wait a minute or so and try again it usually works. If I try again too soon I get the error. Can anybody help me troubleshoot this problem? I don't know what to do.

Why do you need to debug if you already know what the problem is? FileMaker Pro 7 is able to edit scripts, right? BTW.. I'm not sticking up for FileMaker, I'm not happy with version 7 either.

If you're running windows then all you have to do is restart the two web publishing services to have access again. At least it works for me. Go to control panel -> administrative tools -> services. The names of the services are... FileMaker Publishing Engine (CWPE & CONFIG) FileMaker Publishing Engine (WPC) ... Just select the FileMaker Publishing Engine (WPC) service and press the restart button on the menu bar (it's a little square with a triangle next to it).

I did and nothing seemed to break. It's just a log file. I'm running windows so I had to stop the web publishing services to change the file. I'm not sure if you need to on a Mac.

Hi all. I get an error when I try to enable database sessions for XSLT publishing. When I toggle the radio button to yes and click the apply button an error message appears at the top of the page. Fortunately, it's extremely informative. It says "An unexpected error has occurred." Is this happening to anyone else? More information: Windows 2000 Server, FileMaker Server 7 Advanced (v2 update), using port 8080 for web publishing.