Huge temp file

hi,
Am running forms on win xp. and suddenly when i ran the forms, The forms wouldn't come up. I tried clearing the temp folder and found that one file . (C:\Docume~\joey\Local Settings\Temp\s31o ) has been growing ... the file size reached upto 2GB and still the forms didnt show up?
any ideas on what can be done ???/
Thanks

That isn't normal. Is this happening with just one form? Have you tried creating a simple form to test?

Similar Messages

  • Need help -To Restrict Huge temp file, which grows around 3 GB in OBIEE 11g

    Hi Team,
    I am working on OBIEE 11.1.1.5 version for a client specific BI application. we have an issue concerning massive space consumption in OBIEE 11g installed linux environment whenever trying to run some detail level drill down reports. While investigating, we found that whenever a user runs the drill down report a temp file named nQS_xxxx_x_xxxxxx.TMP is created and keep's growing in size under the below given folder structure,
    *<OBIEE_HOME>/instances/instance1/tmp/OracleBIPresentationServicesComponent/coreapplication_obips1/obis_temp/*
    The size of this temp file grows huge as much as around 3 GB and gets erased automatically when the drill down report output is displayed in UI. Hence when multiple users simultaneously try to access these sort of drill down reports the environment runs out of space.
    Regarding the drill down reports:
    * The drill down report has around 55 columns which is configured to display only 25 rows in the screen and allows the user to download the whole data as Excel output.
    * The complete rows being fetched in query ranges from 1000 to even above 100k rows. Based on the rows fetched, the temp file size keeps growing. ie., If the rows being fetched from the query is around 4000 a temp file of around 60 MB is created and gets erased when the report output is generated in screen (Similarly, for around 100k rows, the temp file size grows up to 3 GB before it gets deleted automatically).
    * The report output has only one table view along side Title & Filters view. (No Pivot table view, is being used to generate this report.)
    * The cache settings for BI Server & BI Presentation services cache are not configured or not enabled.
    My doubts or Questions:
    * Is there any way to control or configure this temp file generation in OBIEE 11g?
    * Why the growing temp file automatically gets deleted immediately after the report output generation in screen. Is there any default server specific settings governing this behaviour?
    * As per certain OBIEE article reference for OBIEE 10g, I learnt that for large pivot table based reports the temp file generation is quite normal because of huge in-memory calculations involved . However we have used only Table view in output but still creates huge temp files. Is this behaviour normal in OBIEE 11g. If not, Can any one Please suggest of any specific settings to be considered to avoid generating these huge files or atleast generate a compressed temp file.
    * Any other work around solution available for generating a report of this type without the generation of temp files in the environment?
    Any help/suggestions/pointers or document reference on this regard will be much appreciated. Please advice
    Thanks & Regards,
    Guhan
    Edited by: 814788 on 11-Aug-2011 13:02

    Hello Guhan,
    The temp files are used to prepare the final result set for OBI presentation server processing, so as long as long you dataset is big the tmp files will be also big and you can only avoid this by reducing your dataset by for example filtering your report.
    You can also control the size of your temp files by reducing the usage of the BI server.I mean by this if you are using any functions like for example sorting that can be handled by your database so just push to the DB.
    Once the report finished the BI server removes automatically the tmp files because it's not necessary anymore.you can see it as a file that is used for internal calculations once it's done the server gets rid of it.
    Hope this helps
    Adil

  • 11g SOA with AIA suddenly creates huge temp files(sar files)!!

    Hi All,
    One of our clients that is on 11g SOA with AIA, the team observed while deploying applications, that it suddenly creates huge temp files(sar files) and the server slows down and then shuts down, has anyone seen such behavior or possible reasons?
    If anyone could share such prior experience would be apreciated!
    Thanks for your time!
    Regards,

    Hi Ajay,
    Could you check the managed server logs on the server you are deploying to? I prefer the soa_server1.out file if its available. Hopefully there is something more telling on that side.
    My gut feeling is that there is a schema required by the ProcessFulfillmentOrderBillingBRMCommsAddSubProcess process has not been deployed (which sometimes happens with this PIP in particular).

  • Cropping a pic is creating a 64gig temp file!

    Not sure what's going on here, but when I crop a picture I'm immediately filling all the available space on my hard drive which happens to be 64gigs! Once I get the scratch disk error due to filling up the hd and click Ok the temp file automatically gets rid of it's self.
    The crop settings are
    Width=800in
    Height=600in
    Resolution=400 pixels/INCH
    I have NO IDEA what the default crop settings should be and am wondering if someone really knocked these out of whack? Thanks so much for any help you can provide!
    Misc. Info
    2gigs of RAM
    Photoshop CS2

    64GB is a pretty huge Temp file for Photoshop. That will happen if you're working on HUGE files, or if you leave Photoshop open and you're working on the same image for a LONG time.
    But as long as it goes away when you quit and relaunch, things are working as they are supposed to.
    But, now for your
    REAL problem.
    All you need to do is click on the "CLEAR" button in the Options Bar when you have your Crop Tool selected. Default settings for the Crop Tool are to have the Width, Height and Resolution fields
    empty.
    With those settings you posted, you're asking Photoshop to take whatever area you define by the crop tool and expand it to a file that is 320,000px × 240,000px. That's a dang big file, by anyone's standards.
    I'm kind of surprised that doesn't just freeze your whole system...That says good things about your system!

  • Huge Acrobat temp files - is this right?

    Hi
    When using the reduce file size function, I have noticed that acrobat produces massive temp files.  I was running some files over night, and acrobat crashed, presumably because it ran out of HD space.  Upon looking for what was using all the space, I found a temp file in "C:\Documents and Settings\{user}\Local Settings\Temp".  This file was 75gig.  On another machine that I was running some files on, the file was 115gig.
    Is this right?  Why does acrobat produce files of such size when the original files are nowhere near that size combined?
    Why doesn't acrobat delete the temp file after it has finished 1 file, then create a new one for the next file?
    Running Acrobat 9 Pro on Windows XP, and Windows 7.
    Edit - I just ran a 3MB file through reduce file size, and acrobat created a temp file of 446MB

    Direct Download Links for Adobe Software
    Mylenium

  • Smart objects generate huge ( 10 GB) temp files ??

    Hi folks. I think there's a bug in CS3's smart object handling. Everytime I move (not resize!) a smart object, the temp file's size increases by some 100-200 MB. I easily get over 10 GB just by moving around a single object repeatedly.
    I find that quite weird, given that normal layer moving does not significantly alter the temp file's size. And PS only has to store the smart objects new X and Y coordinates as the object itself does not change. Am I missing something ? Anybody knows what's going on ?

    Converting Smart objects back to embedded layers would be a very useful addition. "Return to layers" would be a good term for it.
    If you are looking for real world examples where this would be useful Chris
    to simplify and bring down the file size of a file that has got out of hand with smart Objects. Some sort of global command "embed all Smart objects" in the layer/smart objects menu would also be useful for this purpose.
    Objects of the same res and profile could then be non-destructively edited by swapping them in and out of smart objects for direct editing within the master document.
    would be particularly useful when for example you need to detach a single instance of a duplicated SO from the others.
    There is sometimes a need to return layers, and adjustments back into the master document to directly modify how they interact with their surroundings in terms of color and masking - for compositing. Its useful for simplicity to have them tucked away as SO's still
    Of course data loss due to resampling, bit depth and modes could be greeted with a warning, perhaps the warning could be contextual "this operation will result in data loss, will decrease file size by 75%, change its mode from LAB, and resample the embedded pixels to 120%".
    What happens to the smart-filters? if they are there, a choice either to rasterise them or abandon them

  • Reader 10.1 update fails, creates huge log files

    Last night I saw the little icon in the system tray saying an update to Adobe Reader was ready to be installed.
    I clicked it to allow the install.
    Things seemed to go OK (on my Windows XP Pro system), although very slowly, and it finally got to copying files.
    It seemed to still be doing something and was showing that it was copying file icudt40.dll.  It still displayed the same thing ten minutes later.
    I went to bed, and this morning it still showed that it was copying icutdt40.dll.
    There is no "Cancel" button, so this morning I had to stop the install through Task Manager.
    Now, in my "Local Settings\TEMP" directory, I have a file called AdobeARM.log that is 2,350,686 KB in size and a file MSI38934.LOG that is 4,194,304 KB in size.
    They are so big I can't even look at them to see what's in them.  (Too big for Notepad.  When I tried to open the smaller log file, AdobeARM.log, with Wordpad it was taking forever and showing only 1% loaded, so after five minutes, I terminated the Wordpad process so I could actually do something useful with my computer.)
    You would think the installer would be smart enough to stop at some point when the log files begin to get enormous.
    There doesn't seem to be much point to creating log files that are too big to be read.
    The update did manage to remove the Adobe Reader X that was working on my machine, so now I can no longer read PDF files.
    Maybe I should go back Adobe Reader 9.
    Reader X never worked very well.
    Sometimes the menu bar showed up, sometimes it didn't.
    PDF files at the physics e-print archive always loaded with page 2 displayed first.  And if you forgot to disable the look-ahead capability, you could get banned from the e-print archive site altogether.
    And I liked the user interface for the search function a lot better in version 9 anyway.  Who wants to have to pop up a little box for your search phrase when you want to search?  Searching is about the most important and routine activity one does, other than going from page to page and setting the zoom.

    Hi Ankit,
    Thank you for your e-mail.
    Yesterday afternoon I deleted the > 2 GB AdobeARM.log file and the > 4.194 GB
    MSI38934.LOG file.
    So I can't upload them.  I expect I would have had a hard time doing so
    anyway.
    It would be nice if the install program checked the size of the log files
    before writing to them and gave up if the size was, say, three times larger
    than some maximum expected size.
    The install program must have some section that permits infinite retries or
    some other way of getting into an endless loop.  So another solution would be
    to count the number of retries and terminate after some reasonable number of
    attempts.
    Something had clearly gone wrong and there was no way to stop it, except by
    going into the Task Manager and terminating the process.
    If the install program can't terminate when the log files get too big, or if
    it can't get out of a loop some other way, there might at least be a "Cancel"
    button so the poor user has an obvious way of stopping the process.
    As it was, the install program kept on writing to the log files all night
    long.
    Immediately after deleting the two huge log files, I downloaded and installed
    Adobe Reader 10.1 manually.
    I was going to turn off Norton 360 during the install and expected there
    would be some user input requested between the download and the install, but
    there wasn't.
    The window showed that the process was going automatically from download to
    install. 
    When I noticed that it was installing, I did temporarily disable Norton 360
    while the install continued.
    The manual install went OK.
    I don't know if temporarily disabling Norton 360 was what made the difference
    or not.
    I was happy to see that Reader 10.1 had kept my previous preference settings.
    By the way, one of the default settings in "Web Browser Options" can be a
    problem.
    I think it is the "Allow speculative downloading in the background" setting.
    When I upgraded from Reader 9 to Reader 10.0.x in April, I ran into a
    problem. 
    I routinely read the physics e-prints at arXiv.org (maintained by the Cornell
    University Library) and I got banned from the site because "speculative
    downloading in the background" was on.
    [One gets an "Access denied" HTTP response after being banned.]
    I think the default value for "speculative downloading" should be unchecked
    and users should be warned that one can lose the ability to access some sites
    by turning it on.
    I had to figure out why I was automatically banned from arXiv.org, change my
    preference setting in Adobe Reader X, go to another machine and find out who
    to contact at arXiv.org [I couldn't find out from my machine, since I was
    banned], and then exchange e-mails with the site administrator to regain
    access to the physics e-print archive.
    The arXiv.org site has followed the standard for robot exclusion since 1994
    (http://arxiv.org/help/robots), and I certainly didn't intend to violate the
    rule against "rapid-fire requests," so it would be nice if the default
    settings for Adobe Reader didn't result in an unintentional violation.
    Richard Thomas

  • HUGE .cp file!

    I have a Captivate 3 movie, nothing special. Less than 50
    slides. No intense animations or huge graphics. The total of all
    the stuff in the library is maybe 90 meg. Yet my .cp file is 380
    meg! (382,127 KB to be exact.)
    I deleted all the audio from the library. The .cp file size
    did not change. I deleted each slide, one by one, saving the
    project after each deletion. The .cp file size did not change. I
    turned off the playback control bar and borders in the skin
    (grasping at straws here). The .cp file size did not change.
    One thing I've never seen before - when I close Captivate
    after working on this project, there is a .tmp file in the folder.
    So far all the temp files' names start with Ado. I've never seen
    Captivate leave a temp file behind like that.
    The movie itself publishes to a reasonable size, but the
    large .cp file size makes it hard to pass the file among coworkers,
    plus it seems to slow down the editing - I double-click a text
    caption box and it takes a few seconds to open up, stuff like that.
    Any ideas?
    Thanks,
    Doug

    Thanks, Rick. The first thing I did was sort the contents of
    the library by "use count" and deleted everything with a zero.
    I didn't create this project, I took it over, and I know that
    the original developer was importing from other files, as well as
    copying and pasting. I went through each slide and highlighted each
    object on the timeline, then looked at it's position. I was
    thinking that maybe something was imported but not showing on the
    slide because it was position waaaay off to the side.
    Unfortunately, I only found one instance of this.
    Plus, I inserted a blank slide, deleted all the other slides,
    and deleted everything in the library - and it still didn't shrink
    at all. It's like there's something in the file that Captivate
    doesn't recognize and therefore doesn't show in the library, yet is
    taking up huge amounts of space.
    And I'm still trying to figure out why I'm suddenly seeing
    these temp files in my folder...

  • After OS X reboot - temp file in Trash

    Please bear with me if this has been asked before concerning Dreamweaver CS4 (I saw an older post relevant to Dreamweaver CS3, but there was no real resolution).
    Situation:
    I purchased, downloaded and installed Dreamweaver CS4 onto my Mac Pro (early 2008) desktop running OS X (10.5.8). The installation, registration and loading of Dreamweaver was successful and proceeded as expected. I then rebooted my machine and noticed that the Trash was not empty as it had been prior to reboot. I checked the trash and found a 'Recovered Files' folder containing a file named '_xx41a7.TMP' inside. I placed this file on the Desktop and double-clicked it which resulted in Dreamweaver loading to a blank document workspace.
    Note - it is my understanding that OS X moves temp files that were not deleted when a program either crashes or does not quit properly.
    Attempted procedures:
    In order to troubleshoot my thought that Dreamweaver was the program in question, I performed a clean install of OS X (including updating it to 10.5.8 and installing all updates via Software Update). I then installed just Dreamweaver > launched and then quit Dreamweaver > rebooted. This resulted in the same named file being placed in the Trash about 2 seconds after reaching the Desktop.
    I tried a third test where I restored to the most recent Time Machine backup prior to performing the original Dreamweaver install and then installed Dreamweaver along with the additional software options during the install process in case a component was needed for the temp file to be handled correctly. Unfortunately, the result was the same with the '_xx41a7.TMP' file being placed in the Trash after reboot.
    System Specs:
    Mac Pro desktop (early 2008)
    OS X (10.5.8) with all updates
    Current installed software:
    Photoshop CS4
    Illustrator CS4
    Bridge CS4
    Exchange CS4
    Office 2008 (Home and Student)
    iLife '09
    iWork '09
    Aperture 2
    Painter X.1
    SketchBook Pro
    TechTool Deluxe (AppleCare provided)
    Stuff It Expander 2009
    World Book 2009
    I was hoping that there is a setting in preferences or elsewhere that can be set to prevent the constant need to delete this file each time I boot the machine if Dreamweaver has been loaded (this does not happen if Dreamweaver is not loaded prior to reboot).
    Note - I am new to Dreamweaver, but old to Photoshop and Illustrator.
    Thanks in advance for any help offered.

    Randy,
    Thanks for the reply and I apologize for not responding sooner.
    I did in fact close down all programs before shutdown or reboot (have been for quite a few years now). I also performed a search for said file using the basic searchlight function in OS X, but I have not gone to the trouble of running a terminal command to show all files in finder and I suspect this particular file is normally hidden.
    I also looked under 'Preferences/Preview in Browser' and saw that the 'Use temporary files..' was already deselected by default. I tried enabling the option by placing a check mark and then relaunching Dreamweaver and then closing the program, but after reboot the same result with the temp file in Trash. I then tried disabling the option and relaunching Dreamweaver and then closing, but again after reboot the same.
    Of note: I have upon three occasions had an empty 'Entourage' folder in the 'Trash/Recovered Files' folder as well. These were times when I had launched Entourage prior to launching Dreamweaver and then closing both before rebooting. Entourage never displayed this behaviour prior to installing Dreamweaver CS4. Not sure what to make of it.
    I have yet to hear back from Adobe Support where I placed a case three days ago via the Adobe Support page.
    Obviously not a huge deal, but it would seem that this particular piece of software either has a bug or has uncovered a bug in OS X or Office 2008. I tend to lean towards it being Dreamweaver as all my other software never displayed this type of behavior from the first day each was originally installed (all about as old as the original release dates and all patched with the latest updates available).
    Does anyone have an idea what function the '_xx41a7.TMP' file serves? It is always the same name, so I am thinking it serves a specific purpose for Dreamweaver.
    One other item that may or may not be relevant. I ran a test where I left the temp file in the trash and rebooted and then relaunched Dreamweaver, which resulted in Dreamweaver taking at least 30 seconds to fully load (the application frame loaded in the usual 1 - 2 seconds, but the content of all toolbars, panels and welcome screen took the 30 seconds or more to load). I ran the test a second time and the time improved slightly, but still around 25 seconds total.
    After the above testing, I deleted the files (Recovered Files & Recovered Files #1 - both of which had a copy of the same '_xx41a7.TMP' file). This returned the launch time to the usual 5 -7 seconds to load program including welcome screen content.
    BTW - I mistakenly listed 'Exchange CS4' in the software list in opening post, which should be 'Extension Manager CS4' (just for accuracy).

  • Unable to extend TEMP segment even after adding fresh temp files

    Hi All,
    I have a huge table with rows nearly 2 million. When this table is moved to another tablespace, the command failed giving the following error:
    ORA-01652: unable to extend temp segment by 128 in tablespace XYZ
    To overcome this error, an additional temp file was added with huge size. Unfortunately, the same error appeared again when the table was tried to move to another tablespace. I wonder if the new temp file was not recognized by database, so tried to see how many files belong to temporary tablespace, but the query listed the newly added temp file also.
    What could be the possible reason for this error? Suggestions or clues are most welcome.
    Thanks,
    ...

    The temp segment is for the table that is being moved.
    Oracle creates a temporary segment when doing a move. If the target tablespace has enough space, the move succeeds and the temp segment gets converted to a Table segment. Else, if the move fails because of lack of space (the temp segment itself unable to grow), then the temp segment is dropped on failure.
    Thus, in a
    alter table ABC move tablespace MY_TBS;or
    the target tablespace MY_TBS should have enough space for ABC. While Oracle is building the copy of ABC in MY_TBS, it is being built as a temporary segment. If the copy succeeds, the temporary segment is renamed as a Table segment 'ABC' and the original table segment 'ABC' is dropped.
    This behaviour also happens when you do an ALTER TABLE .. MOVE ; into the same tablespace that it is existing in. The new copy of the table is a temporary sgement till the copy succeeds.

  • Photoshop Using All RAM And Making 15gb TEMP Files-HELP!?

    Hey Guys,
    Having a massive issue with Photoshop CC right now and need help asap!
    I was recently working a on a really big PSB file (about 6gb or so) I finished the job, saved it, sent it to client, all went nicely. However now when I open Photoshop for whatever reason it instantly uses all of my RAM, and creates a huge 15gb RandomPrice TEMP file on my SSD scratch disk (as shown in the screenshot, excuse the crude snipping tool skills.) I have tried deleting the TEMP file, restarting my PC and opening PS again but it just starts making the file again, it has also drastically slowed down the time it takes to open PS which used to be about 2 seconds, and is now approximately 20 seconds. I'm pretty well clueless what to do here so throw some suggestion my way guys! EDIT: This temp file always reverts to the exact same size after deleting it, right down to the KB. I can sit in explorer refreshing it, watching the size of the temp file going up, and as soon as it reaches 15,276,080KB Photoshop opens up correctly.
    Cheers,
    Tom

    The rule of thumb I follow to figure out scratch space says to figure on 50 to 100 times the size of your largest file ever multiplied by the number of files you have open.  I have seen the scratch file exceed 800 GB once, an admittedly rare occurrence, but it often exceeds 200 GB when stitching large panoramas and the like.
    As an example—and stressing that I'm aware that others have even more scratch space than I do—I keep two dedicated, physically separate hard drives as my primary and secondary Photoshop scratch disks and a lot of GB free on my boot drive for the OS.  I also have 16 GB of RAM installed.
    Additionally, if you only have a single HD, i.e. your boot drive, you'd need it to be large enough to accommodate both the swap files of the OS as well as Photoshop's scratch.

  • Very slow performance in CS6 X64 compared to CS5 X64 and temp file very big

    Hello to everyone,
    I have the same problem as described on this link and the same "solution" to move to layer "easily without delay" !
    http://forums.adobe.com/message/4290563
    the solution to remove these huge delays is:
    http://forums.adobe.com/message/4290563
    "1.  Go the Layers Palette fly-out menu and select Panel Options... "
    "2.  Set Thumbnails to "None"
    My computer setup:
    Windows 7 x64 SP1
    CPU Core i7 (@3.7 GHz)
    NVIDIA GTX295 (latest drivers)
    Total 12Gb RAM (8Gb for system + 4Gb for RAMDISK R:\)
    C:\ = SSD
    D:\ = Velociraptor 150Gb
    E:\ = Velociraptor 300Gb
    R:\ 4Gb (temp files for windows, user, winzip and more)
    My tests with file 66.4 MB with much layer, text, group. Photoshop is already running and I use the menu "File / Open" :
    IN CS5 (12.0.4) X64:
    about 6.13 seconds
    size of the temporary file on C:\ = 2951296 KB
    Setup in photoshop:
    10943 Mo memory seen
    Percent of possible use memory 82% (8974 Mo)
    IN CS6 X64:
    about 137 seconds
    size of the temporary file on C:\ = 20216832 KB
    Setup in photoshop:
    10991 Mo memory seen
    Percent of possible use memory 82% (9012 Gb)
    Sorry for my bad English, I do my best to explain the problem identified.
    Steve

    Hi Adam,
    I did the test and that's exactly the right solution. Actually if I put "128" (which is default in CS5) instead of 1024 (which is default in CS6), charging is as fast as with CS5 and in addition the temporary file is also much less fat (the same size with CS5 !)
    I note that the speed problem that I mentioned is not really a problem, but only because of a difference in configuration "default" of the two versions.
    Still the problem of activation or none of "Thumbnails" which creates delays (even unable to work properly) to move layers or group. Problem mentioned (and shown in video) on the link I put in my first message !
    Thank you,
    Steve

  • Programatically delete Photoshop Temp##### files

    XP Pro
    CS3
    1GB Ram
    Scripting with JavaScipt
    We run photoshop doing batch processes all week long. Is there anyway to include in the javascript batch process a command to delete the temp file that gets built up. I realize they are normally deleted upon proper program termination but that doesn't always happen.
    Since the name appears somewhat with random numbers I am not sure how I could point directly at that, the constant appears to be "Photoshop Temp" but there is also the numbers at the end of that file name to consider.
    or for another consideration (secondary).
    Can I put at the end of the batch command a line of code to close Photoshop? If so what would that be?
    Thank you,
    Jeff

    Yes, I am talking about scratch files.
    Two parts...
    If the Photoshop application is run all week and we process 1GB of files through there it is going to make a huge scratch file correct? That is also why am curious if I can put a line of code at the end of the script to terminate Photoshop which will delete the scratch file.
    As far as workflow goes in our environment the best way is to take the recommendation of "try67" and use the getFiles() function of the currently logged in user and delete that scratch file if Photoshop will allow me to do that while the Photoshop application is still running.
    Concerning the automatic deletion of scratch files...
    I will take a closer look. I just had to go in delete 4 different scratch files on the day I originally posted this thread (3/7/2009).
    I am going to confirm that the installation is up to date.
    Another question which you will probably be able to answer right away. If I (user "A") am bumped out due to an application crash and someone else (user "B") logs in will it still delete the scratch file upon Photoshop launch?
    Thank you very much for your time in reviewing my question and replying.
    Jeff

  • Crystal Server 2013: How to troubleshoot "Can not create temp file---- Error code:-2147215357"

    We have a Java7 web app, which generate PDF report by calling Crystal Server 2013 SP4.
    The app is being deployed on many different servers. We sometimes got the error below when generating report:
    com.crystaldecisions.sdk.occa.report.lib.ReportSDKException: Can not create temp file---- Error code:-2147215357 [CRSDK00000615] Error code name:internal
    at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.controllerExportInternal(PrintOutputController.java:280)
    at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(PrintOutputController.java:152)
    at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(PrintOutputController.java:130)
    at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(PrintOutputController.java:113)
    Problem is, this seems to be  a pretty generic exception. It could be caused by many different reasons.
    e.g. network connection problem, wrong DB login, wrong folder path, lack of folder access right, etc.
    Each time we could only guess what's wrong.
    We are running into it again, and this time everything seems correctly configured so far.
    We wonder if there are more info we can get to troubleshoot? For example, any log file of Crystal Server we should look into? Or does Crystal Server has debug mode which prints more details to tell us what goes wrong?

    Prithviraj Shekhawat wrote:
    Hi Henry,
    I believe you are using RAS SDKs to export the reports to PDF.
    Apply trace on RAS server and check what you find in RAS logs.
    Check whether you can see timeout error is RAS logs. Usually if connection is lost and the RAS server no more have the session to write to the temp directory, we do see these errors.
    Also, does the account that runs RAS have permissions to create a file in RAS's default temp directory? Are you getting any out of memory or out of disk space exceptions on App server or RAS, tracing RAS server is the way to move forward.
    Thanks,
    Prithvi
    >>I believe you are using RAS SDKs to export the reports to PDF.
    Yes
    >>Apply trace on RAS server and check what you find in RAS logs.
    >>Check whether you can see timeout error is RAS logs.
    How to configure tracing, and where are RAS logs? Is it configured in CMC --> Servers --> Crystal Report Services?
    >>Also, does the account that runs RAS have permissions to create
    >>a file in RAS's default temp directory?
    Pretty sure yes.
    >> Are you getting any out of memory or out of disk space exceptions
    >>on App server or RAS, tracing RAS server is the way to move forward.
    Not on App server.
    For RAS, that's the problem, I am not sure where to look.......

  • Can not create temp file---- Error code:-2147215357 [CRSDK00000615] Error code name:internal

    Hello,
    While exporting Export reporting from BI4 getting exception
    Can not create temp file---- Error code:-2147215357 [CRSDK00000615] Error code name:internal
    In Trace Log I am getting
    com.crystaldecisions.xml.serialization.XMLWriter||Failed to create an object instance for CrystalReports.TextObjectFormat
    java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key CrystalReports.TextObjectFormat
      at java.util.ResourceBundle.getObject(ResourceBundle.java:374)
      at java.util.ResourceBundle.getString(ResourceBundle.java:334)
    I tried following solution according to the all forums but still issue exist.
    Done changes mention in KB article In <Installation-dir-of-BO>\Common\4.0\java\CRConfig.XML we have to increase the JAVA heap MIN and Max size
              <JVMMaxHeap>64000000</JVMMaxHeap>          <JVMMinHeap>32000000</JVMMinHeap>
    Increase the value in the ReportApplicationServer Services in the CMC for "Number of database records to read when previewing or refreshing a report". The value -1 is for unlimited records but not recommended for performance.
    Check for temporary read write permission on server
    Using SDK library from C:\Program Files (x86)\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\java\lib
    Can you please let me know is there anything missing.

    Hi,
    We face the same problem with some BI4 reports.
    The same report works well with the "Crystal Reports Viewers API", as used in Infoview, but not with the "Report Application Server (RAS) API".
    This error appears after some time working on a report. If we reproduce the same report, but from zero, no problem.
    Hope it can help.
    Ludovic.

Maybe you are looking for