11g and Could not compile stylesheet

Hello,
I using Oracle 11g R2.
I'm using a Java Stored Procedure.
And I'm using the Oracle's XSL file example.
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:math="http://www.oracle.com/XSL/Transform/java/java.lang.Math">
<xsl:template match="/">
<xsl:value-of select="math:ceil('12')"/>
</xsl:template>
</xsl:stylesheet>
And I get the following exception :
javax.xml.transform.TransformerConfigurationException: Could not compile stylesheet
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:824)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:619)
Can anybody help me ?

I believe you should ask this question at some XML forum.
Aman....

Similar Messages

  • Error while transforming XSLT,"Could not compile stylesheet"

    Hi,
    During transformation of my XSLT I needs to fetch data from method named *"myMethod(String str)"*, which is in *"mypackage.test.MyClass"* class. MyClass is in{color:#000000} XXX.jar. {color}
    This XXX.jar is not in context of my web application.*
    Following is part of XSLT which I am using.
    <?xml version="1.0"?>
    <xsl:stylesheet version="1.0" xmlns:aaa="mypackage.test.MyClass">
    <xsl:template match="/responseData">
    <xsl:for-each select="response">
    <XMLResponse>
    <xsl:for-each select="status">
    <xsl:variable name="Vvar_ResResponseType" select="."/>
    <xsl:attribute name="ResResponseType">
    <xsl:value-of select="aaa:myMethod($Vvar_ResResponseType)"/>
    </xsl:attribute>
    </xsl:for-each>
    </XMLResponse>
    </xsl:for-each>
    </xsl:template>
    </xsl:stylesheet>So I tried to use reflection API to load XXX.jar file at runtime.
    But while transforming Transformer does not find "myMethod(String str)" and gives error like "Could not compile stylesheet"
    Following is full exception stacktrace
    ERROR:  'The first argument to the non-static Java function 'myMethod' is not a valid object reference.'
    FATAL ERROR:  'Could not compile stylesheet'
    javax.xml.transform.TransformerConfigurationException: Could not compile stylesheet
    at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:829)
    at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:623)
    at com.actl.dxchange.utilities.Transformation.transform(Transformation.java:83)
    at com.actl.dxchange.base.BaseConnector.transform(BaseConnector.java:330)
    at com.actl.dxchange.connectors.KuoniConnector.doRequestProcess(KuoniConnector.java:388)
    at com.actl.dxchange.connectors.KuoniConnector.hotelAvail(KuoniConnector.java:241)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    ...........Please suggest is there any other way, so that Transformer can find required bean class from XXX.jar duruing transformation process.
    Thanks & Regards,
    Rohit Lad
    Edited by: Rohit_Lad on Jan 29, 2009 7:38 PM
    Edited by: Rohit_Lad on Jan 30, 2009 9:57 AM
    Edited by: Rohit_Lad on Jan 30, 2009 10:02 AM

    Got the solution from forum named
    "Reflections & Reference Objects"
    Following is link for whom encountered this issue.
    http://forums.sun.com/thread.jspa?threadID=5362426
    Edited by: Rohit_Lad on Jan 30, 2009 2:35 PM

  • XSLT Exception: FATAL ERROR:  'Could not compile stylesheet'

    Hi....
    Am getting Folowing Exception while parsing the XSL file. Am using java 1.4 and MSXML4.2 SP2 parser andSDK.
    but when I installed SQLServer2005, with that MSXML 6.0 Parser is Installed.
    It is working fine before instalation of SQLServer2005.
    java.lang.NullPointerException
         at com.sun.org.apache.xalan.internal.xsltc.compiler.FunctionCall.translate(FunctionCall.java:826)
         at com.sun.org.apache.xalan.internal.xsltc.compiler.ValueOf.translate(ValueOf.java:114)
         at com.sun.org.apache.xalan.internal.xsltc.compiler.SyntaxTreeNode.translateContents(SyntaxTreeNode.java:490)
         at com.sun.org.apache.xalan.internal.xsltc.compiler.XslAttribute.translate(XslAttribute.java:252)
    Compiler warnings:
    file:///F:/Data/JRun4/servers/ABC/MainXSL.xsl: line 155: Attribute 'LenderBranchIdentifier' outside of element.
    file:///F:/Data/JRun4/servers/ABC/MainXSL.xsl: line 156: Attribute 'LenderRegistrationIdentifier' outside of element.
    ERROR: 'null'
    FATAL ERROR: 'Could not compile stylesheet'
    javax.xml.transform.TransformerConfigurationException: Could not compile stylesheet
         at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:753)
         at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:548)
         at com.ls.lsglobal.common.CLOUTSQLXML.TransXml2Xml(CLOUTSQLXML.java:274)
    And My XSL is
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="2.5" xmlns:lsjava1="com.ls.lsglobal.common" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="lsjava1" >
         <xsl:output method="xml" indent="yes" encoding="utf-8" doctype-system="MyRequest.1.3.DTD"/>
         <xsl:template match="/" >
              <REQUEST_GROUP>
                                       <TRANSMITTAL_DATA>
                                            <xsl:if test="AppraisedVal!=''">
                                                 <xsl:attribute name="AppraisedValueAmount"><xsl:value-of select="AppraisedVal"/></xsl:attribute>
                                            </xsl:if>
                                            <xsl:if test="StatedVal!=''">
                                                 <xsl:attribute name="EstimatedValueAmount"><xsl:value-of select="StatedVal"/></xsl:attribute>
                                            </xsl:if>
                                            <xsl:for-each select="ROOT/AppMain/MyLoop/Liab">
                                                 <xsl:if test=" normalize-space(LiabTypCd) = 'SMG' and (normalize-space(PresFutTypCd) = 'BOTH' or normalize-space(PresFutTypCd) = 'PRES') and PresLienPos='1' and normalize-space(RefCd) != 'LOAN'">
                                                      <xsl:attribute name="CurrentFirstMortgageHolderType"><xsl:value-of select="LiabId"/></xsl:attribute>
                                                 </xsl:if>
                                            </xsl:for-each>
                                            <xsl:attribute name="LenderBranchIdentifier">0001</xsl:attribute>
                                            <xsl:attribute name="LenderRegistrationIdentifier"><xsl:value-of select="ROOT/AppMain/MyNum"/></xsl:attribute>
                                       </TRANSMITTAL_DATA>
              </REQUEST_GROUP>
         </xsl:template>
    </xsl:stylesheet>
    And My Java Code is
    public String TransXml2Xml(String xmlInFile, String xslFile, String xmlOutFile) throws Exception
              try
                   DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
                   factory.setIgnoringElementContentWhitespace(true);
                   Document document;
                   File stylesheet = new File(xslFile);
                   File dataInfile = new File(xmlInFile);
                   DocumentBuilder builder = factory.newDocumentBuilder();
                   document = builder.parse(dataInfile);
                   System.err.println("-->AVC:::xslFile="+xslFile+" xmlInFile="+xmlInFile+" xmlOutFile="+xmlOutFile);
                   StreamSource stylesource = new StreamSource(stylesheet);
                   TransformerFactory t=TransformerFactory.newInstance();
                   Transformer transformer = t.newTransformer(stylesource);
                   DOMSource source = new DOMSource(document);
                   javax.xml.transform.stream.StreamResult result = new javax.xml.transform.stream.StreamResult(new File(xmlOutFile));
                   transformer.setOutputProperty(javax.xml.transform.OutputKeys.INDENT , "yes");
                   transformer.setOutputProperty(javax.xml.transform.OutputKeys.ENCODING, "UTF-8");
                   transformer.setOutputProperty("{http://xml.apache.org/xslt}indent-amount", "2");
                   if(strCLUTDTD_PATH.equals(""))
                        java.util.Properties props = new java.util.Properties();
                        java.io.FileInputStream fis = new java.io.FileInputStream("DataFileBasePath.properties");
                        props.load(fis);
                        fis.close();
                        strCLUTDTD_PATH = checkNull(props.get("CLUTREQDTD_PATH"));
                   transformer.setOutputProperty(javax.xml.transform.OutputKeys.DOCTYPE_SYSTEM , strCLUTDTD_PATH);
                   transformer.transform(source, result);
              catch(Exception e)
                   e.printStackTrace();
                   throw e;
              return "";
    can any one know what solution for this problem. It is very help full for me.

    So look at your code and find out what you are passing to the TransformerFactory. Then find out why it's null. Don't just sit there and say "Duh", it's your code.
    And remember that nobody but you can see it yet. If you like you could post it here and then others could see it and comment on it.

  • NewTransformer - Could not compile stylesheet exception

    Using the following code:
    Transformer transformer = factory.newTransformer( new StreamSource(xsltFile) );
    If I fill the xsltFile string variable with "contents.xslt" it goes through fine.
    But, if I put the following into the xsltFile variable, it throws the following exception:
    "C:\\test\\src\\xslt\\contents.xslt"
    Failed to transform file C:\DB Documenter\output\xml\main.xml due to: javax.xml.transform.TransformerConfigurationException: Could not compile stylesheet
    I am formatting the the source and result strings in the actual transform the same way, and they work fine pointing to a c:\ directory. Any reason this blows up on the newTransformer call?
    Here is the whole code:
    public void performTransform(String xsltFile, String xmlFile, String htmlFile) {       
    try {           
    TransformerFactory factory = TransformerFactory.newInstance();
    /* xsltFile = "contents.xslt"; */
    xsltFile = "C:\\DB Documenter\\src\\xslt\\contents.xslt";
    Transformer transformer = factory.newTransformer( new StreamSource(xsltFile) );
    StreamSource xmlSource = new StreamSource(xmlFile);
    StreamResult htmlResult = new StreamResult(htmlFile);
    transformer.transform(xmlSource, htmlResult);
    } catch (Exception e) {
    JOptionPane.showMessageDialog(null, "Failed to transform file " + xmlFile + " due to: " + e);
    }

    StreamSource/Results are simple POJOs: the interpretation of the the system ID you construct them from is left to the interpretation of the object that will use them. This is why the behavior is not consistent.
    For this reason, I never use StreamSource/Result(String) constructors but prefer either the constructor that takes a File or a Reader.

  • TransformerConfigurationException...Could not compile stylesheet

    So far my XSLT stylesheet was executed in operations mapping without problems.
    However I had to make some changes (e.g. adding some additional xsl:choose elements) and now I get the following compilation error:
    TransformerConfigurationException occured when loading XSLT xxxxxxx; details: Could not compile stylesheet
    I develop and change the XSLT externally using XML Spy and there I could run a test transformation without problems or errors.
    Only after reimporting as IA archive and selecting the new version in operations mapping I get the error.
    How is this possible? How can I debug to find the root cause for the error?
    Edited by: Florian Guppenberger on Nov 13, 2009 6:05 PM

    Hello,
    what I have done is to add an additional <xsl:choose> to an already existing <xsl:choose> in the <xsl:otherwise> branch at several locations. Example below.
    I hope that there was not typo somwhere else, however what is very strange is that XML Spy says that the XSLT is well-formed and a test transformation executes successfully too.
    For that XSLT it is not such a big problem, because I can roll-back to the previous version but I am really concerned if you build a big XSLT from scratch in XML Spy an after import in PI you get a compilation error. So it would be really good to find a root cause for this.
    <xsl:choose>
    <xsl:when test="RET_DATE">
      <xsl:attribute name="nullFlavor"><xsl:value-of select="RET_DATE"/></xsl:attribute>
    </xsl:when>
    <xsl:otherwise>
        <xsl:choose>
            <xsl:when test="RET_DATE_VALUE='00000000'">
                 <xsl:attribute name="nullFlavor"><xsl:text>NA</xsl:text></xsl:attribute>
            </xsl:when>
            <xsl:otherwise>
                 <xsl:attribute name="value"><xsl:value-of select="RET_DATE_VALUE"/></xsl:attribute>
            </xsl:otherwise>
          </xsl:choose>  
    </xsl:otherwise>
    </xsl:choose>
    Edited by: Florian Guppenberger on Nov 16, 2009 11:05 AM
    Edited by: Florian Guppenberger on Nov 16, 2009 11:06 AM

  • Exception : Could not compile stylesheet

    Dear All,
    I'm using SimpleTransform.java (renamed as ReceiptTransformer.java for custom use) found in xalan-j_2_7_0 samples directory for transformations in my custom application. The program compiles successfully but gives the following error during runtime:
    ERROR: 'org/apache/avalon/framework/configuration/Configuration'
    FATAL ERROR: 'Could not compile stylesheet'
    Exception in thread "main" javax.xml.transform.TransformerConfigurationException: Could not compile stylesheet
    at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:824)
    at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:619)
    at ReceiptTransformer.main(ReceiptTransformer.java:29)
    Any help in this regard is greatly appreciated.

    StreamSource/Results are simple POJOs: the interpretation of the the system ID you construct them from is left to the interpretation of the object that will use them. This is why the behavior is not consistent.
    For this reason, I never use StreamSource/Result(String) constructors but prefer either the constructor that takes a File or a Reader.

  • XSLTC Giving Could Not Compile Stylesheet.

    Hi All,
    Till now i am using xalan.jar and my xsl is as fallows
    <xsl:stylesheet xmlns:js="javascriptcode" xmlns:java="http://xml.apache.org/xslt/java" exclude-result-prefixes="js java" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:lxslt="http://xml.apache.org/xslt" version="1.0">
    <xsl:template match="/">
    <xsl:apply-templates select="b"/>
    </xsl:template>
    <xsl:template match="b">
    <tar:target xmlns:tar="http://target">
    <tar:Element>
    <xsl:value-of select="js:fnMathematicalAbsolute(/b/b12)"/>
    </tar:Element>
    </tar:target>
    </xsl:template>
    <lxslt:component prefix="js">
    <lxslt:script lang="javascript">function fnMathematicalAbsolute(iNum) {return(Math.abs(iNum))}</lxslt:script>
    </lxslt:component>
    </xsl:stylesheet>
    This works fine Xalan . It is able to call the js extensions .
    I want to move from xalan to JDK 1.5 XSLTC .If ia m using this xsl It is giving Could not compile the stylesheet.
    Can anyone tell me why JDK1.5 doent compiling the stylesheet or is it a problem with my stylesheet. .This is urgent for me as i need to move to jdk 1.5 xsltc.
    Thanks in advance ,
    Sasi.A

    The problem is that J2SE 5 (unlike J2SE 6) does not include a JavaScript engine which is, however, required to interpret the JavaScript code embedded in XSLT stylesheets. You either have to keep on using Xalan (this utilizes Mozilla's Rhino JavaScript engine through the org.apache.bsf.BSFManager class) or switch to J2SE 6.
    Below are download links to three components that make up an applicable unit to compile your stylesheet:
    Xalan (xalan.jar, 3078601 bytes)
    http://apache.mirrors.ebizlab.hit.bme.hu/dist/xml/xalan-j/binaries/xalan-j_2_7_0-bin.zip
    Rhino JavaScript engine (js.jar, 708951 bytes)
    ftp://ftp.mozilla.org/pub/mozilla.org/js/rhino1_6R5.zip
    Jakarta BSF (bsf.jar, 113369 bytes)
    http://apache.mirrors.crysys.hit.bme.hu/dist/jakarta/bsf/binaries/bsf-bin-2.4.0.zip

  • Could not compile stylesheet error on tomcat environment.

    I have created xslt for generating pdf report.It's working fine on OPM when I run through OPM.
    But when I deployed same XSL on tomcat enviroment it doesn't compile error.
    Following the XSLT I have created
    and it give me the error for this line
    i.e ERROR: 'Syntax error in 'name() eq'attribute' '.'
    <?xml version="1.0" encoding="iso-8859-1"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:fo="http://www.w3.org/1999/XSL/Format"
    xmlns:fn="http://www.w3.org/2005/xpath-functions">
    <xsl:output method="xml" indent="yes" encoding="utf-8" omit-xml-declaration = "yes" />
    <xsl:template match="/">
    <fo:root>
    <fo:layout-master-set>
    <fo:simple-page-master master-name="my-page">
    <fo:region-body margin="1in"/>
    </fo:simple-page-master>
    </fo:layout-master-set>
    <fo:page-sequence master-reference="my-page">
    <fo:flow flow-name="xsl-region-body">
    <fo:block >
    <xsl:apply-templates mode="dump" select="/session/entity/instance/attribute"/>
    </fo:block>
    </fo:flow>
    </fo:page-sequence>
    </fo:root>
    </xsl:template>
    <xsl:template match="*" mode="dump" priority="100">
    <fo:block >
    <xsl:if test="name() eq'attribute' ">
              <fo:block margin-left="1cm">
              <xsl:for-each select="@question-text">
              <xsl:value-of select="."/>=
              </xsl:for-each>
              <xsl:if test="string-length(normalize-space(text())) > 0">
                             <xsl:value-of select="text()"/>
                   </xsl:if>
              </fo:block>
    </xsl:if>
    <xsl:apply-templates mode="dump" select="*"/>
    </fo:block>
    </xsl:template>
    </xsl:stylesheet>

    Not every xslt parser acts the same, the one in OPM is not so restrictive (unfortunately)
    Try adding a space between eq and 'attribute'.

  • Adobe Pro delete pages error. One or more pages are in use and could not be deleted.

    Adobe Pro delete pages error. One or more pages are in use and could not be deleted.
    Hi, can anyone assit. I am compiling a pdf by inserting several documents and am unable to delete specific pages. I have used this function on a previous Adobe Pro version but have a problem editing.

    I use this feature once a month to extract / delete some 200 pages from an 800 page file. I found the release notes for 10.1.4 stated that this issue was fixed. I updated my Acrobat to the 10.1.4 release and i was still having the problem. I finally fixed it by disabling the Win XP compatability feature that i had enabled in the properties of the Acrobat executable. I had enabled this feature a couple of months ago as a fix to this specific problem, now it's not necessary.
    Environ: Win 7 32-bit and Acrobat X, 10.1.4.

  • When I attempt to open a PDF file I saved from a website, I get the message "There was an error opening this document. The file is damaged and could not be repaired." Is there any way to correct this problem?

    When I attempt to open a PDF file I saved from a website using Safari, I get the message "There was an error opening this document. The file is damaged and could not be repaired." When I save the same PDF file using FireFox it opens up immediately. Is there any way to correct this problem with Safari?

    Back up all data.
    Triple-click the line of text below to select it, the copy the selected text to the Clipboard (command-C):
    /Library/Internet Plug-ins
    In the Finder, select
    Go ▹ Go to Folder
    from the menu bar, or press the key combination shift-command-G. Paste into the text box that opens (command-V), then press return.
    From the folder that opens, remove any items that have the letters “PDF” in the name. You may be prompted for your login password. Then quit and relaunch Safari, and test.
    The "Silverlight" web plugin distributed by Microsoft can also interfere with PDF display in Safari, so you may need to remove it as well, if it's present.
    If you still have the issue, repeat with this line:
    ~/Library/Internet Plug-ins
    If you don’t like the results of this procedure, restore the items from the backup you made before you started. Relaunch Safari again.

  • "The file is damaged and could not be repaired" error when trying to open a PDF in Reader

    A few of our employess (only 3 out of over 100 so far) have been getting the error, "The file is damaged and could not be repaired" when trying to open some PDFs. Other people are able to open the same PDF files with no error. It's happening on about 10% of the time. I've read a bunch of threads here with this isue and tried some suggested fixes and nothing has resolved the issue. Here is what I have found works and does not work and the info on their computers:
    Computers:
    1 Dell Vostro desktop running WIndows 7
    1 Toshiba Satellite C55 runnign Windows 8
    1 Samsung ATIV Book 4 running Windows 8
    All using Adobe Reader XI but we did uninstall that version and tried previous versions and still got the error.
    Did Not Work:
    As suggested by the company that we use online for claims adjustments where this error is occuring, we tried using a different PDF creator since the files were created using a free PDF creator by the employees. PDF995 and PDFcreator (pdfforge) did not resolve the issue. I then created the PDFs with my Adobe Acrobat, uploaded from my computer to the online program, and that did not resolve the issue.
    Saving the file to hard drive and then opening in Adobe did not work.
    Turning off Protected Mode and Enhanced Security did not work.
    Compatibility View settings enabled in Internet Explorer 10 did not resolve the issue. The previously mentioned claims adjustment software company we use online was code for IE so is not fully compatible with other browsers.
    That being said I did try to open the PDF files in Chrome and it also did not work. Same error message.
    Does work:
    I download the file they cannot open onto my hard drive, open in Adobe Acrobat, Save as a pdf, then email it to them and they can open it via email attachment.
    If they close the error and continue trying to open the file over and over sometimes it will eventually open.
    Is there a setting in Windows that is preventing them from opening a small % of files some of the time? Thanks in advance for any help!
    James

    If anyone is reading this still looking for what caused the issue and how to fix it here is what I discovered.
    The antivirus program our company uses, Bitdefender Antivirus Plus, was causing some of the PDF files not to open. After troubleshooting the different modules and settings the culprit was..
    Scan SSL in Privacy Control Settings. Turning it OFF solved the problem and all the PDF files that previously would not open now open just fine. This issue has been sent to Bitdefender for them to review. If you use a different antivirus program and are having this issue try locating the Scan SSL setting and see if turning it off solves the problem.

  • With OSX10.7.5 and Adobe Reader 11.0.02 when I try to open a PDF downloaded from the web I get 'There was an error opening this document. This file is damaged and could not be repaired. Preview will not open either. Older PDFs OK.

    I am running OS X 10.7.5 and Adobe Reader 11.0.02. In the last few days I have been unable to open PDF's downloaded from the web. Reader gives the error message 'There was an error opening this document. The file is damaged and could not be repaired'. Removing Reader and trying to use Preview to open these files give the error 'Preview cannot open this file. It may be damaged or use a file format that Preview doesn't recognise' (or something like that). Downloading the same files with Reader removed from my Mac Preview opens the files OK.
    I was recently prompted to update Adobe software but did not note exactly what the update was nor when it was done.
    Reader and Preview will both open PDFs I downloaded a week ago. Reader will also open files downloaded on another Mac running OS X 10.0.0 and copied to my Mac. Any ideas?

    Back up all data.
    Triple-click the line of text below to select it, the copy the selected text to the Clipboard (command-C):
    /Library/Internet Plug-ins
    In the Finder, select
    Go ▹ Go to Folder
    from the menu bar, or press the key combination shift-command-G. Paste into the text box that opens (command-V), then press return.
    From the folder that opens, remove any items that have the letters “PDF” in the name. You may be prompted for your login password. Then quit and relaunch Safari, and test.
    The "Silverlight" web plugin distributed by Microsoft can also interfere with PDF display in Safari, so you may need to remove it as well, if it's present.
    If you still have the issue, repeat with this line:
    ~/Library/Internet Plug-ins
    If you don’t like the results of this procedure, restore the items from the backup you made before you started. Relaunch Safari again.

  • I keep getting the message, "the file is damaged and could not be repaired"

    I have a newer Gateway PC equipped with Windows Vista Ultimate, and recently downloaded the free Adobe Reader 8.1.1 version to it.
    I'm not very computer literate, so I'm not sure which terminology to use all the time...sorry.
    When I attempt to open (view, read, download?) a pdf file, it starts the download process, showing the progress at the bottom of the page....for example, it might say, "downloading (16.2kb out of 543.5kb)"
    Usually, about a minute or so into the download, the word "downloading" changes to "downloaded", the action stops, and shortly after (on the window with the gray Adobe Reader background), a smaller message window pops up, declaring, "the file is damaged and could not be repaired".
    A friend suggested that there was probably a problem with the original downloading of Reader and recommended that I completely remove it from my system, then re-install it. Reluctantly, with a very slow dial-up connection network, I did as he suggested, then painfully sat through about a two-hour download AGAIN of Reader 8.1.1
    After the download was completed again, I successfully opened a few of the pdf files which I was previously having the problems with. Problem solved??? NOT QUITE!!! After about three or four successful file downloads (openings/readings of the files), it again started to do the same thing, where it would not complete the downloading/opening process and again leaving the message, "the file is damaged and could not be repaired."
    I am very confident that the files are not the problem, as many of my friends have viewed/opened those same pdf files repeatedly with no issues, BUT WHAT IS CAUSING THIS??? As I said before, I'm not very computer savvy as it is, and adding the newer Windows Vista Ultimate OS probably hasn't helped any.
    1. Is the problem with Windows Vista?
    2. Is the problem with Adobe Reader 8.1.1 (or the downloading of it)?
    3. Is the problem related to the security settings of my computer?
    4. Is the problem likely virus related (I use the purchased McAfee protection)?
    I just don't know where or how to start looking for the solution, other than thru this forum, and I simply can't afford the time to remove and re-install Adobe Reader 8.1.1 each time I need the use of my computer.
    Any assistance would be greatly appreciated, and you can e-mail me with suggestions to [email protected], or else call me on my cell
    THANK YOU,
    Don Maycumber
    Republic, WA
    509-570-8114 Verizon mobile

    I'm having the same problem but with high speed access.
    Anyone know the answer?
    ~Chris

  • I uploaded music to my MacBook and I went to open my iTunes account on another computer and could not access them. How do I do that?

    I uploaded music to my MacBook and I went to open my iTunes account on another computer and could not access them. How do I do that?

    Welcome to the Apple Community.
    The following article(s) may help you.
    Understanding Home Sharing
    Setting Up Home Sharing On A Computer

  • There was an error opening this document.  The file is damaged and could not be repaired.

    Good Day all
    When busy doing internet banking on www.absa.co.za and I try to print a confirmation, I get the following error message: "C:\Documents and Settings\%user profile%\Local Settings\Temporary Internet Files\Content.IE5\%folder name%\%file name%.pdf
    Could not open file.
    File not found."
    I've managed to locate the actual file that it's looking for, but when I try and open the file using either Adobe or Foxit Reader, I get the following error message: "There was an error opening this document. The file is damaged and could not be repaired."
    I've un-installed Adobe and installed version 9.1 for this particular user. This happened a while ago and then an un-installation and re-installation of Adobe solved the issue. This time, unfortunately, it didn't. I then un-installed Adobe and tried again, UNSUCCESSFULLY. So I loaded Foxit Reader, also without any success.
    If there's anyone out there who could possibly help, please do so... It's extremely urgent.
    Please find the errors attached as well.
    Regards,
    ME

    I contacted the company and they asked me to try using another browser, which I did... and using FireFox worked
    thanks for the help ʇɐb ɹəuəllıʍ
    cheers!

Maybe you are looking for