Parse errors with 70_sare_obfu0.cf

I've installed various .cf rules into /etc/mail/spamassassin (correct owner:group & permissions). They all install fine into Spamassassin except 70sareobfu0.cf downloaded from here...
http://www.rulesemporium.com/rules.htm#obfu
...which produces screeds of parsing errors (total 610 'issues') reported by --lint as against 5 without that file (run as clamav user).
I've re-downloaded a couple of times but all the same. I cannot find any notes refering to compatibility issues. Can anyone confirm that this file is OK with them or same parsing errors?
Server 10.4.7, SpamAssassin version 3.0.1 running on Perl version 5.8.6.
Ta
-david

lint output... (I've ommitted repetitive bits)
===============================
debug: SpamAssassin version 3.0.1
debug: Score set 0 chosen.
debug: running in taint mode? yes
debug: Running in taint mode, removing unsafe env vars, and resetting PATH
debug: PATH included '/usr/local/bin', keeping.
debug: PATH included '/bin', keeping.
debug: PATH included '/sbin', keeping.
debug: PATH included '/usr/bin', keeping.
debug: PATH included '/usr/sbin', keeping.
debug: Final PATH set to: /usr/local/bin:/bin:/sbin:/usr/bin:/usr/sbin
debug: diag: module not installed: DBI ('require' failed)
debug: diag: module installed: DB_File, version 1.810
debug: diag: module installed: Digest::SHA1, version 2.10
debug: diag: module installed: IO::Socket::UNIX, version 1.21
debug: diag: module installed: MIME::Base64, version 3.05
debug: diag: module not installed: Net::DNS ('require' failed)
debug: diag: module not installed: Net::LDAP ('require' failed)
debug: diag: module not installed: Razor2::Client::Agent ('require' failed)
debug: diag: module installed: Storable, version 2.13
debug: diag: module installed: URI, version 1.35
debug: ignore: using a test message to lint rules
debug: using "/etc/mail/spamassassin/init.pre" for site rules init.pre
debug: config: read file /etc/mail/spamassassin/init.pre
debug: using "//usr/share/spamassassin" for default rules dir
debug: config: read file //usr/share/spamassassin/10_misc.cf
debug: config: read file //usr/share/spamassassin/20antiratware.cf
debug: config: read file //usr/share/spamassassin/20bodytests.cf
debug: config: read file //usr/share/spamassassin/20_compensate.cf
debug: config: read file //usr/share/spamassassin/20dnsbltests.cf
debug: config: read file //usr/share/spamassassin/20_drugs.cf
debug: config: read file //usr/share/spamassassin/20fake_helotests.cf
debug: config: read file //usr/share/spamassassin/20headtests.cf
debug: config: read file //usr/share/spamassassin/20htmltests.cf
debug: config: read file //usr/share/spamassassin/20metatests.cf
debug: config: read file //usr/share/spamassassin/20_phrases.cf
debug: config: read file //usr/share/spamassassin/20_****.cf
debug: config: read file //usr/share/spamassassin/20_ratware.cf
debug: config: read file //usr/share/spamassassin/20uritests.cf
debug: config: read file //usr/share/spamassassin/23_bayes.cf
debug: config: read file //usr/share/spamassassin/25body_testses.cf
debug: config: read file //usr/share/spamassassin/25body_testspl.cf
debug: config: read file //usr/share/spamassassin/25_hashcash.cf
debug: config: read file //usr/share/spamassassin/25head_testses.cf
debug: config: read file //usr/share/spamassassin/25head_testspl.cf
debug: config: read file //usr/share/spamassassin/25_spf.cf
debug: config: read file //usr/share/spamassassin/25_uribl.cf
debug: config: read file //usr/share/spamassassin/30textde.cf
debug: config: read file //usr/share/spamassassin/30textes.cf
debug: config: read file //usr/share/spamassassin/30textfr.cf
debug: config: read file //usr/share/spamassassin/30textit.cf
debug: config: read file //usr/share/spamassassin/30textnl.cf
debug: config: read file //usr/share/spamassassin/30textpl.cf
debug: config: read file //usr/share/spamassassin/30textsk.cf
debug: config: read file //usr/share/spamassassin/50_scores.cf
debug: config: read file //usr/share/spamassassin/60_whitelist.cf
debug: using "//etc/mail/spamassassin" for site rules dir
debug: config: read file //etc/mail/spamassassin/70sareadult.cf
debug: config: read file //etc/mail/spamassassin/70saregenlsubj0.cf
debug: config: read file //etc/mail/spamassassin/70sareheader0.cf
debug: config: read file //etc/mail/spamassassin/70sareobfu0.cf
debug: config: read file //etc/mail/spamassassin/70sareoem.cf
debug: config: read file //etc/mail/spamassassin/70sarespoof.cf
debug: config: read file //etc/mail/spamassassin/70sareunsub.cf
debug: config: read file //etc/mail/spamassassin/72sare_redirectpost3.0.0.cf
debug: config: read file //etc/mail/spamassassin/88FVGTheaders.cf
debug: config: read file //etc/mail/spamassassin/88FVGTsubject.cf
debug: config: read file //etc/mail/spamassassin/88FVGTuri.cf
debug: config: read file //etc/mail/spamassassin/bogus-virus-warnings.cf
debug: config: read file //etc/mail/spamassassin/chickenpox.cf
debug: config: read file //etc/mail/spamassassin/local.cf
debug: using "/var/clamav/.spamassassin" for user state dir
debug: using "/var/clamav/.spamassassin/user_prefs" for user prefs file
debug: config: read file /var/clamav/.spamassassin/user_prefs
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1c3b6f0) inhibited further callbacks
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1c3b6f0) inhibited further callbacks
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1c3b6f0) inhibited further callbacks
config: SpamAssassin failed to parse line, skipping: ??
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping: meta SAREOBFUALWAYS 0
config: SpamAssassin failed to parse line, skipping: meta SAREOBFUCIALIS 0
config: SpamAssassin failed to parse line, skipping: meta SAREOBFU_CREDITPOX 0
config: SpamAssassin failed to parse line, skipping: meta SAREOBFUGOALS 0
config: SpamAssassin failed to parse line, skipping: meta SAREOBFU_ORDERINGSPL 0
config: SpamAssassin failed to parse line, skipping: meta SAREOBFURELIABLE 0
config: SpamAssassin failed to parse line, skipping: meta SAREOBFURESULTING 0
config: SpamAssassin failed to parse line, skipping: meta SAREOBFUSOMA 0
config: SpamAssassin failed to parse line, skipping: meta SAREOBFUSTOCKS 0
config: SpamAssassin failed to parse line, skipping: meta SAREOBFUAFFORD 0
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping: full SAREOBFUAMP2B m'(?:(?!http://)h.?t.?t.?p.?:.?/.?/)[^/\?]{4,40}\&'is
config: SpamAssassin failed to parse line, skipping: describe SAREOBFUAMP2B invalid character within URI host/domain
config: SpamAssassin failed to parse line, skipping: score SAREOBFUAMP2B 2.555
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping: full SAREOBFUCONTENT01 /Content-Type: ;text\/plain;/
config: SpamAssassin failed to parse line, skipping: describe SAREOBFUCONTENT01 Obfuscation via content-type header
config: SpamAssassin failed to parse line, skipping: score SAREOBFUCONTENT01 2.500
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping: body SAREOBFU_DRUGDOL1SPC m{\$1\.\s$1.s+$1.s}i
config: SpamAssassin failed to parse line, skipping: describe SAREOBFU_DRUGDOL1SPC found apparent obfuscation of word used in spam
config: SpamAssassin failed to parse line, skipping: score SAREOBFU_DRUGDOL1SPC 2.333
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
config: SpamAssassin failed to parse line, skipping:
etc, etc,
lint: 614 issues detected. please rerun with debug enabled for more information.
===================================
If the obfu file is removed, it all goes fine.
-david

Similar Messages

  • Has anyone had a opf parse error with container.xml missing, when it is actually present plz ?

    Has anyone had a opf parse error with container.xml missing, when it is actually present plz ?

    Has anyone had a opf parse error with container.xml missing, when it is actually present plz ?

  • InfoPath 2010 form parsing error with 3600 execution timeout value in SharePoint 2010

    Hi,
    I have a list in SharePoint 2010 with 100 columns where 25 of them are calculated columns. This list is designed by InfoPath 2010 with two secondary data connections to pull a few data from another two lists. There are 25 set value rules with the submit
    button in InfoPath from. At present, the list is containing around 1000 items.
    The problem is, when I published the InfoPath form it throws an error:
    The SOAP message cannot be parsed.
    In fact, the execution timeout is set to 3600 in config file. When I delete items from the list and keep it around 700 the InfoPath form publish then.
    Could somebody tell me why this problem and what is the possible solution.
    Thanks in advance.

    Hi pointtoshare,
    According to your description, my understanding is that you got an error when you published InfoPath form.
    Please modify the web.config file like :
    <location path="_layouts/UploadEx.aspx">
         <system.web>
           <httpRuntime maxRequestLength="51200" executionTimeout="300" />
         </system.web>
       </location>
    And modify the <securityPolicy> section like :
    The web.config file is in C:\inetpub\wwwroot\wss\VirtualDirectories\spwebappname.
    There is another reason for this issue, please take a look at :
    http://www.heyweb.net/2011/07/infopath-the-soap-message-cannot-be-parsed/
    Here are some similar posts for you to take a look at:
    http://social.technet.microsoft.com/Forums/en-US/ea8da113-fe9a-4878-9994-c1f24cc85c37/soap-error-when-publishing-infopath-form-to-sharepoint?forum=sharepointcustomizationprevious
    http://sharepointshah.blogspot.in/2012/11/soap-message-cannot-be-parsed-error.html
    I hope this helps.
    Thanks,
    Wendy
    Wendy Li
    TechNet Community Support

  • Why do I get parsing errors with my WSDL URL for Web Services usage

    Hi,
    I am puzzled with the errors I get when I want to create a Web Service datastore.
    Scenario: I have created a SAP Web Service from CRM using SOAMANAGER. The WSDL URL produced by SOAMANAGER is accessibile when pasting the URL directly in Internet Explorer. WSDL URL [http://UXCIQ0M.WDF.SAP.CORP:50076/sap/bc/srt/wsdl/srvc_CBDCB34C89C29304E10000000A4282C0/wsdl11/allinone/ws_policy/document?sap-client=504]
    When using the WSDL URL in the Web Service datastore URL field, I get the error An error occurred while importing metadata: WSDLException; faultcode=PARSER_ERROR: Problem parsing: The element type "br" must be terminated by matching tag "/br". (BODI-1111469) (BODI-1112446)
    When I save the WSDL defintion in a local file and use a local file path, I get the errors An error occurred while importing metadata: WSDLException (at /wsdl:definitions/wsdl:portype/wsp:Policy): faultcode=INVALID_WSDL: Encountered unexpected element 'Policy. (BODI-1111469) (BODI-1112446)
    My questions:
    - Why do I get different parsing errors despite the fact that the XML is the same?
    - The WSDL is generated by SOAMANAGER. Shouldn't it work directly when integrating with Web Services generated from an SAP environment?
    - Is this related to confiurgation issue? I have set the Job Manager to Support adapter, message broker and SNMP communication
    - What is the difference between the datastore of type Adapter and the datastore Web Service? In the white paper [http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/20bd5e60-11f9-2b10-2bbb-b5109cceff08?quicklink=index&overridelayout=true] it is mentioned to use the Adapter type to consume a Web Service. It is not clear to me why we have those 2 types.
    Thanks & Best Regards
    Isabelle

    Some updates on this issue, which might help others in the community.
    - Data Service doesn't support ws_policy.
    - SAP NetWeaver 7.0 SOAMANAGER generate WDSL with ws_policy. In future releases, it is possible to specify not to use ws_policy
    - In most cases, replacing ws_policy with standard  in the URL directly, works. It doesn't work with Data Services :(.
    - Replacing ALL ws_policy in the XML directly is currently the only way to have the WSDL definition being parsed properly by Data Services.

  • Parse error with print

    Hi,
    I tried to build a custome web gallery into LR 4.3 on MAC.
    I started with example from LR SDK zip.
    In my index.html sample file, i simply declare some variables at the top like this:
    <%--[[ Define some variables to make locating other resources easier     firstPage was defined in our manifest.]]      local others = "content"    local theRoot = "."    local mySize = "large"    local firstImage    local title    local caption    local width    local height      local LrLogger = import 'LrLogger'    local myLogger = LrLogger( 'libraryLogger' )          myLogger:enable('print')          local debug, info, warn, err = myLogger:quick( 'debug', 'info', 'warn', 'err' ) %> 
    After, inside a script tag, i would like to print into index.html outputed file a json file with images name.
    Before that i simply tried to print a test string, and i got in Console app this message : SyntaxError: Parse error
    Where am i wrong ?
    Thanks
    Regards

    Hi , Welcome to the HP Forums! I see that you are getting a printhead error with your HP Officejet 6830. I am happy to help!  I would recommend to go through the steps within this guide, 'Problem with Printhead,' 'Printer Failure,' 'Ink System Failure,' or a '0x...' or a 'C2...' Error Message Displays. You will also want to make sure you are using Genuine HP Ink Cartridges, and that none of your Ink Cartridges are low or empty.  Hope this guide helps!  “Please click the Thumbs up icon below to thank me for responding.”

  • Parse error with show if region

    hi,
    i have a form, which has 2 parts to it.
    i added a checkbox and set the checked value to 1
    i wrapped the rest of the form in a div and applied show if region to it.
    when i uploaded to the web i receive this error:
    Parse error: syntax error, unexpected '@', expecting T_VARIABLE or '$'
    has anyone seen this before and know how to fix?
    many thanks for your help

    Thanks again albert, i think i see what my problem is.
    i tried your code but it did not work first time, but i noticed i was applying it to a div inside a table and as soon as i took that part out a table and into a new table but the table within the div it worked great so thanks for that.
    got one problem which is on a different matter.
    i applied send email from the server behaviours with addt, however it generates this line of code at the start and it does not like it:
    @@UrlFormat@@('@@ConnectionPath@@');
    any ideas how to fix this?
    many thanks

  • Parsing error with XDP using special character & in string.

    When writing an .XDP file from scratch, the following line give a parsing error at the ampersand. What command should I use to convert the ampersand to string?
    The XDP line is:
    <p3pName>17TH STREET BAR & GRILL</p3pName>
    This is the only line that gives a problem.
    Thanks

    There are five characters which MUST be escaped if they appear in
    regular XML text, this is a rule of XML. The characters are ampersand,
    single and double quote, less than, and greater than. They can be
    replaced by entities like & AMP ; (no spaces, semi-colon is part of
    it). If you use an XML library it should take care of it, but home
    grown XML programs and scripts should always keep this in mind.
    Aandi Inston

  • Parsing errors with CDATA tags using oracle xml parser v2

    I'm using the oracle.xml.parser.v2 parser to combine a
    generated xml document from a database with a static
    xsl file to produce html. Within the xml document, there
    are fairly large CDATA sections (500 lines) which happen
    to contain javaScript.
    Occasionally, I'm getting xml tags in the final html
    document! It seems that the oracle parser pukes
    on a certain type of data within a CDATA tag, and then
    replaces an angle bracket (<) of a tag with a #60. This
    can cause html tags being viewed in the document. At
    first, I thought the amount of JavaScript within the
    CDATA tag was too large for the parser to handle,
    because when I split it up into 2 or more parts the errors
    went away. But, re-arranging the JavaScript (String in the CDATA tag)
    can make the errors disappear. And, if I
    use the Saxon parser to manually combine the xsl with
    the xml, the output is fine. If anyone knows that this is
    a confirmed bug by Oracle, or any other relevant info on
    this, please let me know.

    Hi,
    Your lucky, i've just finished a project that used the oracle parser extensively.
    I think the problem may stem from your xsl. Although your cdata tags may be well formed, in the xsl you might need to escape the text again, this may mean that the xsl needs to print a further cdata tag around the data. This is because the parser (well the version I was using) strips the cdata tags before the transformation happens.
    This is the probably the cause of the nasty html output.

  • 10g Upgrade - XML Parser errors with certain escape codes (&#x0338)

    NLS_CHARACTERSET = WE8ISO8859P15
    NLS_NCHAR_CHARACTERSET = AL16UTF16
    Since our 10.2.0.3.0 upgrade (from 9.2.0.1.0) our xml fails with the following message:
    ORA-31011: XML parsing failed
    ORA-19202: Error occurred in XML processing
    LPX-00217: invalid character 824 (U+0338)
    Error at line 4
    We are using escape codes in our xml that have worked fine on 9i. Example xml:
    <PRINT_LAYOUT_FOOTER>&#x0338;&#x0338;&#x0338;&#x0338;This map was created with Promap</PRINT_LAYOUT_FOOTER>
    I am completely flummoxed - Any ideas?

    You've switched from a Java Based Parser to a 'C' based parser, which is much, much faster. However one of the requirements of the 'C' implementation is that all characters in the database character set. I'm guessing that if you switch to AL32UTF8 for the database character set the problem will go away. BTW 9.2.0.1.0 was desupported for XML related features when 9.2.0.3.0 was released.

  • Help a noob with a parse error. Completely new to Flex, doesn't know anything.

    Hi. I am completely new to Flex (and mxml and ActionScript) and have a silly little error right off the bat. I haven't written a line of code yet, and got the source files from a collegue (who is currently unavailable to help me out here) that obviously had this working before he gave it to me.
    I am getting a parse error with the following lines. From my experience with PHP, I have a general idea that a parse error is usually a syntax thing, like a missing semicolon or something along that line. I've already tried semicolons in a bunch of places, but nothing seems to work. Any help would be appreciated. The X is where the program highlights the error.
    <?xml version="1.0" encoding="utf-8"?>
    <!-- Build with 3.1 -->
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"  layout="absolute"  xmlns:tg = "EditableTextGrid.*" xmlns:ns1="com.testURL.commonClasses.grid.*" viewSourceURL="srcview/index.html"
    X verticalAlign="middle" implements="EditableTextGrid.ETGParent" >
    initialize= "setLogin('testUser'); loadMatrix('module=portal&amp;mode=i&amp;searchString=1111')"
    <!--initialize="setLogin('testUser'); loadMatrix('module=serviceview&amp;mode=i&amp;colName=SID&amp;searchString=290')"-->
        <mx:Style source="styles/AcctRequest.css"/>
    Severity and Description
    Path
    Resource
    Location
    Creation Time
    Id
    Parse error at '\n initialize= \"setLogin(\'ngorelik\'); loadMatrix(\'module=portal&mode=i&searchString=1111\')\"\n\n\t'.
    CV/src
    contactsSWF.mxml
    line 4
    1319810874686
    130
    Other info: it was actually written with Flex 3.2 SDK

    You are missing a quote at the end of your "setLogin(testUser)" function and you don't have that inside a tag (it's outside the greater than sign...
    You have:
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"  layout="absolute"  xmlns:tg = "EditableTextGrid.*" xmlns:ns1="com.testURL.commonClasses.grid.*" viewSourceURL="srcview/index.html"
    X verticalAlign="middle" implements="EditableTextGrid.ETGParent" >
    initialize= "setLogin('testUser'); loadMatrix('module=portal&amp;mode=i&amp;searchString=1111')"
    It should be:
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"  layout="absolute"  xmlns:tg = "EditableTextGrid.*" xmlns:ns1="com.testURL.commonClasses.grid.*" viewSourceURL="srcview/index.html"
    X verticalAlign="middle" implements="EditableTextGrid.ETGParent"  initialize= "{setLogin(testUser)}"...>

  • Parse Error in Java

    I am very new to java and I have a piece of code which is written in javascript which i want to replicate in java basically it validates the structure of and XML Dom passed into it.
    function XMLParseError(XMLIsland, XMLName)
    if (XMLIsland.parseError.errorCode != 0)
    alert('XML Parse Error with ' + XMLName + '\n\nreason: ' +
    XMLIsland.parseError.reason +
    '\nline: ' + XMLIsland.parseError.line +
    '\npos: ' + XMLIsland.parseError.linepos +
    '\nsrcText:' + XMLIsland.parseError.srcText +
    '\nurl: ' + XMLIsland.parseError.url);
    in java i have
    DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
    DocumentBuilder builder = factory.newDocumentBuilder();
    factory.setIgnoringComments(true); // We want to ignore comments
    // Now use the factory to create a DOM parser
    DocumentBuilder parser = factory.newDocumentBuilder();
    //final xml is an xml string
    xmldoc = parser.parse(new InputSource(new StringReader(finalXML)));
    if i want to catch the errors and print them to the screen similar to the javascript program how do i do this.....

    Create a class which extends the DefaultHandler(DefaultHanlder impleents the ErrorHandler interface)
    Set the ErrorHandler on the DocumentBuilder.
    builder.setErrorHandler(errorHandler);

  • 3D data parsing error in Adobe Reader X 10.1.2

    Hello,
    I'm getting the annoying (and once fixed in version 9) 3D data parsing error with reader X 10.1.2 (on Windows 7 64bit), reading files that used to have no issues with previous versions (Italian locale). Anyone is having the same problem - or is able to give some suggestions? I've already tried to repair the installation, with no result. Any comment is greatly appreciated - this issue is causing major problems.
    Best regards,
    SV

    Hello,
    unfortunately it's a reserved document. I'll try to reproduce the issue with a different design and, if possible, I'll post a link to it.
    Thank you!
    Best regards,
    SV

  • Error while parsing JSP with WebLogic 5.1/SP9/JDK 1.2.2

    Hello everybody,
              I get the error given below when calling a JSP in a WebLogic
              application which seems to work fine in all other (non-JSP) parts:
              java.lang.NullPointerException:
                   at weblogic.servlet.jsp.JspLexer.addSetPropertyValue(JspLexer.java:1432)
                   at weblogic.servlet.jsp.JspLexer.mXML_SET_PROPERTY(JspLexer.java,
              Compiled Code)
                   at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1726)
                   at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java, Compiled Code)
                   at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled
              Code)
                   at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
                   at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
                   at weblogic.servlet.jsp.JspParser.parse(JspParser.java:159)
                   at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:109)
                   at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
              Compiled Code)
                   at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
              Code)
                   at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
                   at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
                   at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
                   at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
                   at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
                   at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
                   at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
              Code)
              I know that this error has been reported more than once in these
              discussion groups, and all people who solved it say
              - that it occurs only wen running WebLogic 5.1 with JDK 1.3 instead of
              1.2.2
              - that it may also be caused by bad jsp code
              But in my case, it has to be another reason, because
              - I am using jdk 1.2.2
              - the same JSP file is running withour errors on WebLogic 6
              I wonder if it could have something to do with the operating system:
              the parsing error is produced on a Windows version of WL 5.1, while my
              WL 6 which doesn't cause errors is running with Linux.
              Many thanks in advance for any help,
              Eckhard Beisswenger
              

    Once again me!
              After a long time, I stumbled by accident across the answer that solves the problem I described above. It is explained at
              http://support.bea.com/application;JSESSIONID_WLCS_DEFAULT=2R2lzQfEBxFRMX2z0AxeU1Un3N1522I9fCIUI7GfjnjsiSYkPscz
              The clue is that weblogic complains about corresponding get and set methods, when the type of the set methods parameter is different from the return type of the corresponding get method. Unfortunately, the weblogic lexer class gives only a NullPointerException without any hint.
              

  • I am recieving an xml parsing error message on a website I use for work. It used to work on firefox but now it has stopped. It works with other browsers though.

    XML Parsing Error: XML or text declaration not at start of entity
    Location: https://evalue.internationaldelivers.com/service/SVCDOCS/Navistar/isisxsl.xsl
    Line Number 2, Column 1:<?xml version='1.0'?>
    ^
    That is the error I receive the page loads and half the content appears but the other half is blank and I receive that instead. I can attach a screenshot if needed.

    May be cookies issue try this
    Reload the webpage while bypassing the cache
    *Hold down the ''Shift'' key and click the ''Reload'' button with a left click.
    *Press ''Ctrl'' + ''F5'' or ''Ctrl'' + ''Shift'' + ''R'' (Windows and Linux)
    *Press ''Command'' + ''Shift'' + ''R'' (Mac)
    Clear the cache and the cookies from sites that cause problems.
    '''Clear the Cache''': Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
    '''Remove Cookies''' from sites causing problems:
    *Tools > Options > Privacy > Cookies: "Show Cookies"
    *https://support.mozilla.org/en-US/kb/websites-say-cookies-are-blocked-unblock-them

  • B2B-51566 Description: Parse stream error with RosettaNet 1.1

    Hi
    Need help with the following error message
    B2B-51566 Parse stream error
    We have a trading partner set up to use RosettaNet 1.1 protocol and we are getting 51566 error. We are NOT experiencing this error with a trading partner who is in RosettaNet 2.0
    we are currently patched up to 11.1.1.5
    One thing I notice is when i go to the message and open the packed message i get this "Cannot display Packed Message in binary format."
    Here is the payload
    XMessage-ID: <[email protected]d.e2open.com>
    MIME-Version: 1.0
    Content-Type: multipart/related;
         boundary="----=_Part_176_29725195.1331307008851";
         type="Application/x-RosettaNet"
    Content-Description: This is the RosettaNet Business Message
    Content-ID: "-15059242:135f6ea5e3c:-62b9"
    ------=_Part_176_29725195.1331307008851
    Content-Type: Application/xml; rnsubtype=preamble-header; name=Preamble
    Content-Transfer-Encoding: binary
    Content-Disposition: attachment; filename=Preamble
    Content-ID: <[email protected]>
    Content-Description: This is the Preamble Header part of the Business Message
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE Preamble SYSTEM "PreamblePartMessageGuideline.dtd">
    <Preamble>
    <DateTimeStamp>20120309T153008.852Z</DateTimeStamp>
    <GlobalAdministeringAuthorityCode>RosettaNet</GlobalAdministeringAuthorityCode>
    <GlobalUsageCode>Production</GlobalUsageCode>
    <VersionIdentifier>1.1</VersionIdentifier>
    </Preamble>
    ------=_Part_176_29725195.1331307008851
    Content-Type: Application/xml; rnsubtype=service-header; name=ServiceHeader
    Content-Transfer-Encoding: binary
    Content-Disposition: attachment; filename=ServiceHeader
    Content-ID: <[email protected]>
    Content-Description: This is the Service Header part of the Business Message
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ServiceHeader SYSTEM "ServiceHeaderPartMessageGuideline.dtd">
    <ServiceHeader>
    <ProcessControl>
    <ProcessIdentity>
    <description>
    <FreeFormText>NotNull</FreeFormText>
    </description>
    <GlobalProcessCode>Request Purchase Order</GlobalProcessCode>
    <GlobalProcessIndicatorCode>3A4</GlobalProcessIndicatorCode>
    <initiatingPartner>
    <GlobalBusinessIdentifier>007710825</GlobalBusinessIdentifier>
    </initiatingPartner>
    <InstanceIdentifier>PIPC0A85CB8135F814CB4200000EAFE56F0</InstanceIdentifier>
    <VersionIdentifier>V02.00</VersionIdentifier>
    </ProcessIdentity>
    <ServiceRoute>
    <fromService>
    <BusinessServiceDescription>
    <GlobalBusinessServiceCode>Seller Service</GlobalBusinessServiceCode>
    </BusinessServiceDescription>
    </fromService>
    <toService>
    <BusinessServiceDescription>
    <GlobalBusinessServiceCode>Buyer Service</GlobalBusinessServiceCode>
    </BusinessServiceDescription>
    </toService>
    </ServiceRoute>
    <TransactionControl>
    <AttemptCount>1</AttemptCount>
    <PartnerRoleRoute>
    <fromRole>
    <PartnerRoleDescription>
    <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
    </fromRole>
    <toRole>
    <PartnerRoleDescription>
    <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
    </toRole>
    </PartnerRoleRoute>
    <TransactionIdentity>
    <GlobalTransactionCode>Request Purchase Order</GlobalTransactionCode>
    <InstanceIdentifier>TIC0A85CB8135F814CB4200000EAFE5700</InstanceIdentifier>
    </TransactionIdentity>
    <SignalControl>
    <inResponseTo>
    <ActionIdentity>
    <GlobalBusinessActionCode>Purchase Order Request Action</GlobalBusinessActionCode>
    <InstanceIdentifier>C0A85CB8135F814C33C00000EAFE5670</InstanceIdentifier>
    </ActionIdentity>
    </inResponseTo>
    <InstanceIdentifier>20120309T153008.882Z</InstanceIdentifier>
    <PartnerRoute>
    <fromPartner>
    <PartnerDescription>
    <BusinessDescription>
    <GlobalBusinessIdentifier>364132837</GlobalBusinessIdentifier>
    </BusinessDescription>
    <GlobalPartnerClassificationCode>null</GlobalPartnerClassificationCode>
    </PartnerDescription>
    </fromPartner>
    <toPartner>
    <PartnerDescription>
    <BusinessDescription>
    <GlobalBusinessIdentifier>007710825</GlobalBusinessIdentifier>
    </BusinessDescription>
    <GlobalPartnerClassificationCode>null</GlobalPartnerClassificationCode>
    </PartnerDescription>
    </toPartner>
    </PartnerRoute>
    <SignalIdentity>
    <GlobalBusinessSignalCode>Receipt Acknowledge</GlobalBusinessSignalCode>
    <VersionIdentifier>1.1</VersionIdentifier>
    </SignalIdentity>
    </SignalControl>
    </TransactionControl>
    </ProcessControl>
    </ServiceHeader>
    ------=_Part_176_29725195.1331307008851
    Content-Type: Application/xml; rnsubtype=service-content;
         name=ReceiptAcknowledgement
    Content-Transfer-Encoding: binary
    Content-Disposition: attachment; filename=ReceiptAcknowledgement
    Content-ID: <[email protected]>
    Content-Description: This is the Service Content part of the Business Message
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ReceiptAcknowledgement SYSTEM "ReceiptAcknowledgementMessageGuideline.dtd">
    <ReceiptAcknowledgement>
    <fromRole>
    <PartnerRoleDescription>
    <ContactInformation>
    <contactName>
    <FreeFormText>E2open Support</FreeFormText>
    </contactName>
    <EmailAddress>[email protected]</EmailAddress>
    <telephoneNumber>
    <CommunicationsNumber>650-381-6000</CommunicationsNumber>
    </telephoneNumber>
    </ContactInformation>
    <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    <PartnerDescription>
    <BusinessDescription>
    <GlobalBusinessIdentifier>364132837</GlobalBusinessIdentifier>
    <GlobalSupplyChainCode>Information Technology</GlobalSupplyChainCode>
    </BusinessDescription>
    <GlobalPartnerClassificationCode>null</GlobalPartnerClassificationCode>
    </PartnerDescription>
    </PartnerRoleDescription>
    </fromRole>
    <receivedDocumentDateTime>
    <DateTimeStamp>20120309T153008.907Z</DateTimeStamp>
    </receivedDocumentDateTime>
    <receivedDocumentIdentifier>
    <ProprietaryDocumentIdentifier>337719</ProprietaryDocumentIdentifier>
    </receivedDocumentIdentifier>
    <thisMessageDateTime>
    <DateTimeStamp>20120309T153008.904Z</DateTimeStamp>
    </thisMessageDateTime>
    <thisMessageIdentifier>
    <ProprietaryMessageIdentifier>20120309T153008.905Z</ProprietaryMessageIdentifier>
    </thisMessageIdentifier>
    <toRole>
    <PartnerRoleDescription>
    <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    <PartnerDescription>
    <BusinessDescription>
    <GlobalBusinessIdentifier>007710825</GlobalBusinessIdentifier>
    <GlobalSupplyChainCode>Information Technology</GlobalSupplyChainCode>
    </BusinessDescription>
    <GlobalPartnerClassificationCode>null</GlobalPartnerClassificationCode>
    </PartnerDescription>
    </PartnerRoleDescription>
    </toRole>
    </ReceiptAcknowledgement>
    ------=_Part_176_29725195.1331307008851--

    I do have SR but hoping i can get quicker answer hereYou may always escalate the SR if you are not getting response timely. Anyways, give the reference of this thread in the SR and ask service engineer to file a bug.
    I will email you the wire messageI saw the wire message you mailed across. There are some junk characters in the starting of the payload and that's why parsing is failing. Most probably it is a BOM (Byte Order Mark). Ask your TP to send messages in UTF-8 encoding without BOM or any other junk character in the starting of the message. You may open the wire message payload you mailed across in notepad or textpad and you will able to see those junk characters in the starting of the payload.
    Regards,
    Anuj

Maybe you are looking for

  • Time Capsule Back to my Mac not working

    Hello, For the last two weeks I am not able to connect to my Time Capsule at work, before I saw it automatically on my iMac/MacBook Pro at home. I already removed and rentered my credentails on the time machine for Back to My mac, unfortonatelly this

  • Find Handling unit number using Serial number

    Hello MM experts! I am using handling unit with serial numbers. Is there any way in standard SAP to find the Handling unit number in which a particular serial number is packed? standard report o something similar? Thanks for your answers. Sara

  • AAMEE + Tivoli Endpoint Manager/BigFix

    Has anyone successfully used an AAMEE created Adobe CS6 package in combination with Tivoli Endpoint Manager (formerly known as BigFix)?

  • PrintJob() with Flex 3

    I have printableNote, which is a sprite. I try to do this: printableNote.graphics.beginFill(0xffffff); printableNote.graphics.lineStyle(1, 0x000000); printableNote.graphics.drawRect(0, 0, 100, 200); printableNote.graphics.endFill(); var pj:PrintJob =

  • Problems generating classes with JAXB

    Does anyone know where there might be a list of known problems with generating classes from an xsd with JAXB? I have a very deep and pretty complicated xsd, and it seems some elements get generated correctly and some don't. It's very hard to find any