Rendering error whilst writing to file /filename etc./ An output module failed

I'm trying to render my composition in the latest AE CC 2014.  I get the following error with all composition sizes and with different codecs:  Rendering error whilst writing to file /filename etc./ An output module failed. The file may be damaged or corrupted (-1610153464). Can anyone help me sort this problem?

AE build number? Codec used? System OS? 

Similar Messages

  • Rendering error while writing to file...Quicktime

    Hi all,
    I am brand new here and have an urgent question. I have been getting an error in After Effects CS6 whenever I try to render to a quicktime movie that says "Rendering error while writing to file...An output module failed. The file may be damaged or corrupted."
    I have spent days trying to fix this and I have read other peoples posts with the same question but I have cleared my disk cache and reinstalled quicktime without success.
    Any help would be great I am not super technology advanced so try to keep it simple if you can.
    Computer Specs:
    750gb Hard Drive
    8gb Ram
    Intel Core i5
    Nvidia Geforce GTX 660M graphics

    Start by going through all of the troubleshooting suggestions here:
    http://blogs.adobe.com/aftereffects/2011/02/troubleshooting-quicktime-errors-with-after-ef fects.html
    If you need additional help, please provide answers to all of the questions listed here: "FAQ: What information should I provide when asking a question on this forum?"

  • After Effect error: Rendering error while writing to file

    Greetings,
    I'm a beginner and am starting to learn most of the basics but every time I try to render a specific type of composition, I get this massage:
    After Effect error: Rendering error while writing to file "C:Users\Admin\Videos\720p.mp4".Unknown Error! (-1610153453)
    RENDER SETTINGS:
    LENGTH: 8min. and 30 sec
    FORMAT:H.264
    CODEC: mp4
    RESOLUTION: 1280 x 720
    AUDIO: 48.000 kHz, Stereo
    OUTPUT LOCATION: C DRIVE (22GB FREE)
    I got Windows Ultimate 64-bit and Adobe After Effect CS5.5 64-bit (both on C drive) installed in my laptop.
    When I first installed after effect, I rendered a part of the whole composition (AVI, 720p) and it worked but after that when I rendered with
    format H.264 it showed this massage. Then I tried to change it back to AVI. and rendered. again the same massage.
    My C drive isn't full, I have 22GB SPACE AVAILABLE.
    And when I try to save it on D (114GB free) or E drive (33GB free), It shows me the SAME MASSAGE.
    PLEASE HELP
    Thanks in advance.

    Hi HR and everyone that have the problem error (-1610153453)
    In my case I solved the problem changing the destination folder, I was rendering in a folder with a non english character! in my spanish language we have the "Ñ" ('n' with a wave on top ) after effects mp4 codec NO Ñ or cyrillic, etc...
    I finally solve it thanks the russian friends: (http://nix-studio-edition.ru/tutorials/faq/1083-ae-1610153453.html) and Google translator
    Hope it helps to desperate workers
    Thanks

  • After effects error: rendering error while writing to file. Disk full.

    Hi,
    I tried to render a video in AE CC 2014, with RGB + Alpha as I wanted to keep the background transparent (rotoscoped) so that I can then use it in Premiere.
    I chose to export in Quicktime, with uncompressed 8bit.
    After it rendered it for a little while I had a window pop-up saying
    After effects error: rendering error while writing to file "E:...blabla". Disk full. The file may be damaged or corrupted. (-1610153463).
    I read a thread posted in the forums but i do not understand the solution provided there.. What is a POD??
    I have a Win7 Ultimate, x64. Plenty of disk space, and 16 Go ram.
    Please help, I canoot go further in my project with this bug...
    Jaywaii

    Is the drive you are rendering to formatted FAT32 by any chance? If so you can only render up to 4Gb for one file. Try rendering out a TIFF sequence instead. Litte tip - push the LZW compression tickbox in format options for a lossless compression, this will keep you file size way down.

  • After Effects Error: rendering error while writing to file...Output Module failed - 1610153646

    Hi – I’m currently working with someone who is running After Effects 5.5v10.5.0.253 on a PC which is running Windows 7 Ultimate. The computer has just recently been built and the software is newly installed. (ie. a couple of weeks old, max). Up until now, we have been using After Effects with no real issues. But tonight, we started to see the following error message, when trying to render something out:
    “After Effects Error: rendering error while writing to file xxxxx. Output Module failed, the file may be damaged or corrupted -1610153646” – displayed during render, which meant the render failed.”
    We started to review forums to see if we could come up with a fix and tried a few of the more common suggested solutions, including:
    Make sure there are no third-party plug-ins or Windows incompatible elements installed - as it’s a pretty new install, we haven’t added anything except out-of-the box elements.
    Clear the render queue – did this, no change.
    Reinstall Quicktime – did this, no change.
    Reinstall Creative Suite – also no change.
    Check the default program to open .mov files is Quicktime – Quicktime was already the default.
    A bit more detail about the machine...
    Ram is 32gb
    GPU is GeForce GTX 660ti
    250gb soild states
    2tb raid drive
    Any help would be much appreciated. This is now happening on all AE files, even files that worked fine earlier in the week. Other than the AE and QT reinstalls mentioned above, nothing new has been added to the machine this week. On a deadline – so a quick response would be amazing, right about now. Thanks.

    Hi Mylenium- thx for the quick response. We have have tried a bunch of different settings. AVIs work and we can do image sequences too. The only major problem seems to be with Quicktime files. While I appreciate your suggetion to convert with AME - this is only a workaround. Was really hoping for a solution that will fix the problem in After Effects? Heard rumor from a few friends in the biz, that this is a major bug... if possible, some feedback from Adobe product devs or someone with a technical background would be great! Thx.

  • AE error: Rendering error while writing to file "E:\[file name].avi". An output module failed. The file may be damaged or corrupted.

    I am running Adobe After Effects CC 2014.0.2 on a Windows 7 Ultimate Machine.
    When the user begins to render an uncompressed file she receives the following error message:
    I have been searching all day for solutions to this error with no luck so far. All that I have found deal with Mac OS (which does not apply here) or .mov files (also not the issue here) and I am stumped. Any suggestions on how to resolve this error?

    Here you go:

  • After Effects Error: Rendering error while writing to file... Unable to open file.(-1610153459)

    Hi there,
    As the title states, this is the error message I get ONLY when trying to render .mov files.
    I have posted here before with a similar problem related to quick time files.
    After Creative Cloud does its own updating, I can no longer render .mov files.
    I have been through the trobleshooting list for QuickTime file errors, none of that works.
    This is now the 3rd time that I have reinstalled AE CC.  On a clean install, everything works fine, but after updates it starts bugging out.
    ALSO
    I cannot install the lates AE update...12.1.
    CC says that I there are no new updates.
    The manual update function within AE is greyed out so I cant click it.
    I downloaded the entire patch and tried installing but I get another error stating that 'Udates have been surpressed by the Administrator.'
    I am the Admin user, and I have tried running the patch as admin too.
    I am getting extreemely frustrated with this CC package.
    Please....please, someone help.

    So....its been a few peacuful days.....but here I am again....with the same issue.
    There have been no new Windows updates, quicktime updates or CC updates that I know of.
    The problem however seems to be quite random.  Sometimes it doesnt  happen if I restart After Effects, while other times it occurs even If I restart the whole machine.
    The best part though:
    I contacted Adobe technical support for the patching issue as I am still running 12.0
    The technician remotely takes over my machine and proceedes to uninstal After Effects.  Then he tries to log onto Adobe's download site only to find out it is down (not quite sure how this isnt known to him before the fact).  He says the site will be back up after an hour and asks that I wait while still connected.  I do so.
    Sure enough, the site is back online, but the tecnician is not responding to my communications even after a direct email to him and an aditional 30 minutes of waiting.
    I have no option but to cut off the remote control and reinstall After Effects......again.
    I count my bleesings and carry on the next day with normal work.  I have a product that can at least render the format I require.  I brush off the notion of getting the latest update.
    So here I am today, with a 'brand new' quicktime issue.
    I contact support again and explain the problems, but I am told that the technical staff are only online in 5 hours.

  • Every time I try to render in .mov or h264 the following error appears. After Effects error: Rendering error while writing to file (-1610153453), I´ve

    I´ve try reinstalling AE and Quicktime but it hasn´t worked. Any recommendations on how to fix the issue?

                  FAQ: What information should I provide when asking a question on this forum?

  • An output module failed. The file may be damaged or corrupted.

    Whenever I try to render something in After Effects CC 13.1.1, an error message pops up, saying "After Effects error: Rendering error while writing to file '[not going to disclose]' An output module failed. The file may be damaged or corrupted (-1610153464)."
    Screenshot of the error message:
    I tried reinstalling QuickTime (7), repaired it, updated After Effects to the latest version(as I am writing this), checked firewall software, and used other formats such as AVI.
    Adobe Media Encoder (CC 2014-latest version) won't work with me, either.
    I sent the composition to Adobe Media Encoder, and this is what I got, no progress here.
    Screenshot:
    It took a while to connect to the dynamic link server, and failed.
    This is a log of what has happened in Adobe Media Encoder.
    - Source File: C:\Users\Default.BronyGue\Documents\not done\pinkcoverart_AME\tmpAEtoAMEProject-Pink Intro1.aep
    - Output File: C:\Users\Default.BronyGue\Documents\not done\pinkcoverart_AME\Pink Intro.mp4
    - Preset Used: YouTube HD 720p 29.97
    - Video: 1280x720 (1.0), 29.97 fps, Progressive
    - Audio: AAC, 320 kbps, 48 kHz, Stereo
    - Bitrate: VBR, 2 pass, Target 5.00 Mbps, Max 5.00 Mbps
    - Encoding Time: 00:00:12
    06/29/2014 02:29:14 PM : Encoding Failed
    The Operation was interrupted by user
    (no need to worry about the above part)
    - Source File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\tmpAEtoAMEProject-montage1.aep
    - Output File: C:\Users\Default.BronyGue\Videos\chilledup.wmv
    - Preset Used: Custom
    - Video: 1280x720 (1.0), 29.97 fps, Progressive
    - Audio: Windows Media Audio 10 Professional, 96000 Hz, Stereo, 24 bit
    - Bitrate: CBR, 2 pass, Max 10000.00 kbps
    - Encoding Time: 00:01:42
    11/22/2014 12:24:39 AM : Encoding Failed
    The Operation was interrupted by user
    - Source File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\tmpAEtoAMEProject-montage1.aep
    - Output File: C:\Users\Default.BronyGue\Videos\chilledup.mpg
    - Preset Used: Custom
    - Video: 1280x720, 29.97 fps, Progressive, Quality 75
    - Audio: MPEG Audio, 384 kbps, 48 kHz, Stereo, 16 bit
    - Bitrate: VBR, 1 Pass, Min 4.00, Target 15.00, Max 18.50 Mbps
    - Encoding Time: 00:00:11
    11/22/2014 12:52:11 AM : Encoding Failed
    The Operation was interrupted by user
    - Encoding Time: 00:00:51
    11/22/2014 12:53:51 AM : Encoding Failed
    Export Error
    Error compiling movie.
    Unknown error.
    - Encoding Time: 00:00:46
    11/22/2014 08:39:46 AM : Encoding Failed
    Export Error
    Error compiling movie.
    Unknown error.
    - Source File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\tmpAEtoAMEProject-montage4.aep
    - Output File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\montage.mpg
    - Preset Used: Match Source - High bitrate
    - Video:
    - Audio:
    - Bitrate:
    - Encoding Time: 00:00:00
    11/22/2014 10:06:45 AM : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.
    I need some help! Any solutions?.
    Computer Specs:
    AMD FX-6300
    8GB 1600MHz DDR3 RAM
    NVIDIA GeForce GTX 650 Ti BOOST
    1TB 7200RPM Hard Drive
    Windows 8.1 Update 1(with latest updates)
    EDIT(11/23/2014 8:31PM PST): For some reason, other projects work for me just fine. I am not sure why it is not working on one project.
    Screenshot of a new project other than this I am rendering at the time of writing this edit:

    Can other projects can output to the same output location? Yes
    Can other projects render with the same render settings (codec, format, etc.)? Yes.
    If you create a new composition and just add a solid layer to it with no effects in the same project does it render? No. I still get the error.
    Can you render that brand new comp with the same render settings, output settings, output location etc.? Yes.
    If so, what effects are present in the offending comp? Twixtor Pro in all the cinematics/clips, Motion Tile and Transform for pan/crop & wiggle, Magic Bullet Looks and Bad TV Warping preset with just Wave Warp & Venetian Blinds for color correction, Gradient Ramp for text, Bad TV Warping preset with everything for effect, Transform for fade in/out, and ReelSmart Motion Blur v4.1.2 for motion blur.
    Also, what scripts are you using? Just the Move Anchor Point script I found from one of Mt. Mograph's videos, Summit 16 - 2.5D Minecraft Steve - After Effects - YouTube.
    Have you ever installed any third-party codec packs? (I've heard of some codec packs causing weird issues like this.) Yes, (not everything I have, just everything I can think of and find) I have K-Lite codec pack, Fraps, x264vfw, and Xvid MPEG-4 codec.

  • "...an Output Module failed" error screen...

    Greetings AE Peeps!!
    Long time - no see - been stupid busy. My Studio has just ponied up and upgraded our 5 Edit Stations to AE CS5. I personally am a huge advocate of not upgrading software while in the middle of a project, but this was out of my control. I am having a lot of crashing (app just quits for no reason while scrubbing) and other weirdness...like today. I am rendering a 3 minute piece in ProRes 4:2:2 (1280x720p) to my RAID (no special plug-ins or anything) and I get the following error at the very end of every render:
    After Effects Error: Rendering error while writing to file (insert my RAID path here). An output module failed. The file may be damaged or corrupted (-1610153464)
    I have never in 11 years got a "failed Output Module error". Can anyone speak to this and tell me how to get rid of it short of reinstalling AE?
    Grazie! Ciao!
    Joey

    First, make sure that you've installed the After Effects CS5 (10.0.1) update.
    Regarding the output module failure: It may be that this is because you have an output module created in a previous version of After Effects that refers to a codec or set of settings that isn't working in After Effects CS5. The best thing to do is to remove the output modules from the render items and then rebuild them in After Effects CS5. That may sound tedious, but you only need to do it once, and then you can save output module templates that you know work with After Effects CS5.
    As Mylenium suggested, there are some challenges associated with the fact that there is no 64-bit QuickTime, so we had to create our own 32-bit-to-64-bit QuickTime conversion layer (QT32 Server). QuickTime does work with After Effects CS5, but there are some hiccups in some cases on first use.
    If this doesn't help, answer back and we'll help you through.
    Oh, this might be useful, too:
    http://blogs.adobe.com/toddkopriva/2011/02/troubleshooting-quicktime-errors-with-after-eff ects.html

  • AE CC Render error output module failed

    Hi, I tried my best to find this answer on the forums but couldn't find anything current.
    I have isolated two issues in AE CC where I can duplicate a failed render with this message:
    After Effects error: Rendering error while writing file "xxx". An output module failed. The file may be damaged or corrupted. (-1610153464)
    This happens when opening an AE CS6 project and trying to render a simple comp with only one text layer and a moving mask. It also just happened after my first round trip test with Cinema 4D. I could RAM preview the c4d layer but the output to Quicktime h.264 failed.
    I have even tried a full reinstall of AE CC. I have the basic FxFactory Pro plugins and MagicBullet Looks installed, but neither are being used since this is a single 1280x720 comp with a single C4D layer. Plus like I said it failed with the same error in past CS6 files.
    I don't know how to force disable a plugin to test that, but I can't see how an unused plugin could cause a render to fail like this.
    I'm on a new (late 2012) 27" iMac
    3.4 GHz Intel Core i7
    8GB RAM
    NVIDIA GeForce GTX 680MX with 2GB VRAM
    OS X 10.8.4
    AE CC 12.0.0.404
    CUDA driver 5.0.59
    Thanks for any suggestions!
    Matt

    Olaf, did you read my reply where I explained my solution? First you should try the steps outlined in the article Todd references:
    http://blogs.adobe.com/aftereffects/2011/02/troubleshooting-quicktime- errors-with-after-effects.html
    There seems to be a good way to isolate if it's the same issue I had, though. Let me go into a bit of depth for you.
    The trick was to launch the OS X app called Console, located in Applications > Utilities. It is a program that compiles and displays the system logs in real time. It's great to see the little things happening in the system that don't make it into the user interface. When I had my Console up and generated that same error you're having, I noticed this error in the log:
    The key here is the Adobe QT32 Server, which is mentioned in the TCP part of the article I linked to above from Todd. In my case at least, what was happening was that a third party app called AirServer was talking to the system's QuickTime over the same TCP ports the QT32 Server engine was trying, and it resulted in Adobe QT32 Server crashing, and that alert being thrown up in AfterEffects.
    If you're in the same boat, it means you have some sort of app or system extension that is also talking to QuickTime over TCP. That may not make any sense, but the easy thing to do is quit ALL third party apps, then quit AE, then restart AE.
    In my situation if AE gave me the error and then I quit AirServer, the error still happened because Adobe QT32 had already crashed. You have to relaunch AE after closing the offending third party app.
    To be sure you've quit all third party apps, open Activity Monitor (Applications > Utilities), chose "My Processes" from the dropdown menu, and scan through the list to make sure. You don't have to recognize all the processes there, but you should be able to recognize any third party ones you put there.
    Hope that helps!
    Matt

  • Error while writing wsdl file

    Hi,
    i' m working on jdeveloper 10.1.3.1.0 and when i want to add a partner link to my BPEL project i get 'error while writing wsdl file' 'exception null' error then i couldn't create file.
    so how can i solve this problem?
    HELP:)

    Once the wrapper procedure is created by the adapter, the adapter does a second search to obtain the information about the wrapper (i.e. parameters, their data types, etc.). What's likely happening here is that the wrapper is getting created, but the adapter can't find it. The XSD is based on the wrapper, so if it can't be found, then no XSD can be generated. Try removing the existing wrapper package or choose that option in the wizard when it generates a new one.

  • EXPORT XFA error while writing XFA files

    Hello Experts,
    We are facing an error while exporting to PDF from BEx report.
    We are on EP7 SP14. BI on SP16.
    After the report is displayed and Export to PDF button is clicked, a new window opens which shows following:
    1. Error:
    Message: No message was provided.
    Stack trace: java.lang.NullPointerException
    at com.sap.ip.bi.export.model.layout.impl.Margins.<init>(Margins.java:32)
    at com.sap.ip.bi.export.model.layout.impl.CellLayout.<init>(CellLayout.java:48)
    at com.sap.ip.bi.export.model.layout.impl.CellLayout.dub(CellLayout.java:57)
    at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.createCell(TableContentIterator.java:170)
    at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.next(TableContentIterator.java:104)
    at com.sap.ip.bi.export.xfa.xftextensions.TableSubFormSet.writeXFD(TableSubFormSet.java:1189)
    at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
    at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
    at com.sap.ip.bi.export.xfa.core.Xft_template.writeXFD(Xft_template.java:216)
    at com.sap.ip.bi.export.xfa.core.Xft.writeXFD(Xft.java:62)
    at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:294)
    at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
    at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:96)
    at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:626)
    at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:405)
    at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:325)
    at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:71)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:593)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:132)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:349)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.buildRenderingTree(Page.java:4494)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:4568)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:4204)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:4150)
    at com.sap.ip.bi.webapplications.runtime.impl.Page._processRequest(Page.java:2948)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2794)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:994)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller._processRequest(Controller.java:883)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:860)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:359)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:276)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java
    :33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Message: EXPORT XFA error while writing XFA files
    Stack trace: com.sap.ip.bi.base.exception.BIBaseRuntimeException: EXPORT XFA error while writing XFA files
    at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:311)
    at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
    at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:96)
    at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:626)
    at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:405)
    at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:325)
    at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:71)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:593)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:132)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:349)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.buildRenderingTree(Page.java:4494)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:4568)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:4204)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:4150)
    at com.sap.ip.bi.webapplications.runtime.impl.Page._processRequest(Page.java:2948)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2794)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:994)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller._processRequest(Controller.java:883)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:860)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:359)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:276)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java
    :33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NullPointerException
    at com.sap.ip.bi.export.model.layout.impl.Margins.<init>(Margins.java:32)
    at com.sap.ip.bi.export.model.layout.impl.CellLayout.<init>(CellLayout.java:48)
    at com.sap.ip.bi.export.model.layout.impl.CellLayout.dub(CellLayout.java:57)
    at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.createCell(TableContentIterator.java:170)
    at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.next(TableContentIterator.java:104)
    at com.sap.ip.bi.export.xfa.xftextensions.TableSubFormSet.writeXFD(TableSubFormSet.java:1189)
    at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
    at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
    at com.sap.ip.bi.export.xfa.core.Xft_template.writeXFD(Xft_template.java:216)
    at com.sap.ip.bi.export.xfa.core.Xft.writeXFD(Xft.java:62)
    at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:294)
    2. Message:
    No metadata is available for "DISABLE_NAVIGATION":
    <parameterList>
      <param name="BI_COMMAND_TYPE" value="OPEN_DIALOG_DISABLE_NAVIGATION"/>
      <param name="TARGET_DIALOG_REF" value="DISABLE_NAVIGATION"/>
    </parameterList>
    In this window, complete screen of report is displayed as an image instead of PDF.
    Please let me know if anybody faced similar issue earlier.
    It was working perfect earlier, but suddenly error started.
    regards
    Kedar Kulkarni

    No proper findings, but issue resolved.
    Problem i found that we got a domain change and service values were not refreshed until we apply new patch.
    So when we applied patch level 6 on BI WEBAPP& BI BASE S URL for ADS got refreshed and we faced the issue.
    After resetting the URL to new domain problem got resolved.
    Regards
    Kedar Kulkarni

  • Error in writing to file

    Hai,
    I am installing Oracle9.2.0 on my RH8.0 system. I got an error like this after running runInstaller: Error in writing to file: .../oracle/jre/1.3.1/bin/i386/native_threads/java
    Someone know a solution for this ?
    thx
    ramesh

    Your error has been completely addressed here http://www.puschitz.com/InstallingOracle9i.html. This is very informative. You may want to check this out before proceeding. The straight solution to this is when this error shows up, leave it open, find the native_threads/java file from the CD to the directory Oracle is asking for this. I had this problem and it turned out when I extracted and burnt it to a CD, it didn't copy the native_threads directory and others, so you want to check this as well.
    Del

  • Error in Writing to File \Winnt\System32\mfcans32.dll

    Error window with msg "Error in Writing to File \Winnt\System32\mfcans32.dll" is being popuped while trying to install 9.0.3 on windows 2000 Advanced Server.
    My System Configuration Details are as follows.
    Compaq Proliant
    Ram : 2GB
    HARD DISK : 80GB
    PROCESSOR : 2.6
    Please help me to install.
    Thanks,
    Srinivas Chowdhary Annamareddy.

    You might want to investigate why it became Read-Only in the first place and are there any other files that should not be Read-Only read only.

Maybe you are looking for