8 Replies Latest reply on Jun 27, 2014 11:14 AM by philmodjunk

    FMS 13 XSLT Import Errors 718 and 2035, Yet Works on FMA 13?

    smower

      Summary

      FMS 13 XSLT Import Errors 718 and 2035, Yet Works on FMA 13?

      Product

      FileMaker Server

      Version

      13

      Operating system version

      Windows 2012 Server

      Description of the issue

      Hello,

      I have a script to import xml from eBay after transforming it with a FileMaker xslt stylesheet.  It works fine on FMA 11 and a scheduled script on FMSA 11 and FMA 13, however when I try to run the scheduled script with FMS 13 it gives me errors 718 and 2035?

      718 seems to be the following: Error in parsing XML file (from Xerces)

      I can't find FM error 2035 documentation.

      Anyway, I don't understand why it works in the other products but not the 13 server.  Is the Xerces parser different in the server from the client or is this a bug?  I don't know how to troubleshoot it since it works when I run it with FileMaker Advanced 13 on the desktop and it works from FMSA 11 on the server.

      Thanks in Advance!

      Steps to reproduce the problem

      eBay XML
      <?xml version="1.0" encoding="UTF-8"?>
      2014-01-23T17:30:02.962ZSuccess857E857_CORE_APISELLING_16635281_R12006323805281T42RD1410998125529023613072407336524720069643248088307pr1309762928167935414081541729955220130879735204126814107429663801514140816073357BT-662-GG14067606836816660

      FileMaker StyleSheet to Transform
      <?xml version="1.0" encoding="UTF-8" ?>



      0









              
             
             
             

             
             
             
             
             

             
             
             
             
             

             


      </xsl:for-each>



      Expected result

      Server 13 should import this but instead gives an error: <?xml version="1.0" encoding="UTF-8"?>
      02006323805281T42RD

      Actual result

      Schedule "BestOffers" completed; last scripting error (718). 
      Schedule "BestOffers" scripting error (2035) at "BestOffersServer : Startup : Import Records".

      Exact text of any error message(s) that appear

      Schedule "BestOffers" completed; last scripting error (718). 
      Schedule "BestOffers" scripting error (2035) at "BestOffersServer : Startup : Import Records".

      Configuration information

      Client is Windows 7 and has FMPA 11 and FMPA 13 and both of those transform and import just fine.

      FMSA 11 is on a Windows small business server and it transforms and imports just fine.

      FMS 13 is on a Windows 2012 Server and it gives errors when trying to transform and import.
      Schedule "BestOffers" completed; last scripting error (718). 
      Schedule "BestOffers" scripting error (2035) at "BestOffersServer : Startup : Import Records".

      Workaround

      Use Base Elements plugin to transform the file before FileMaker Server imports since FM Server 13 imports the xml file from the documents folder fine if it doesn't have to do the xslt transformation. The following imports fine.
      <?xml version="1.0" encoding="UTF-8"?>
      02006323805281T42RD