Empty PDF when printing from report

I have a number of reports where I want to be able to download the report as both CSV and PDF.
The CSV download works fine but the PDF only contains the headers, no data. The printer is set up otherwise I wouldn't be able to get a PDF at all.
Is there anything obvious I might have overlooked?
Thanks in advance.

Hi,
We have the exact same problem with an interactive report in Apex 3.2. The CSV export works fine, but the PDF file only shows the header.
The problem only occurs when using a page item in the where clause. Is that a bug ? How can I fix this ?
Thanks
Patrick

Similar Messages

  • Can I save as pdf when printing from a Java applet on a webpage in Safari?

    I am trying to use a webpage that is running a Java applet. A dialog comes up that asks me, "Do you want to run this application?" The dialog also says, "This application will run with limited access that is intended to protect your computer and personal information." I select "Run". The applet generates an image I want to print.  There is a "Print" button on the applet.  I select "Print". A Security Warning dialog comes up that says, "The applet has requested access to the printer. Do you want to allow this action?" I select "OK".  The Print dialog comes up.  I choose the PDF button in the lower left corner. I choose "Save as PDF...". A second Print dialog comes up.  I input a title in the Save As box.  I choose Desktop in the Where box.  I do not change anything else and select the "Save" button. A dialog appears that says, "Print Error while printing." There is an icon with paper, a pencil, a ruler and a paintbrush on the dialog. 
    Is this an issue with Apple and Java security?  Does "run with limited access" mean I can't print and save as PDF? Should I upgrade to Mavericks?  It seems like others have not been happy with Mavericks and have had problems saving as PDF with Mavericks. How do I let Apple know about this error?  The error dialog is useless. 
    I am on a Mac running OS X 10.8.5 and Safari 6.1.2.  My Java version is 7 update 51.
    What other information can I provide to help solve the problem (if it can be solved)?
    Thank you for your help!

    Correction I would like to save as PDF/A-1b
    for archiving.
    http://www.adobe.com/enterprise/standards/pdfa/

  • When printing from an online PDF, the page prints in extra large scale. How do I fix this?

    when printing from an online PDF, the page prints in extra large scale. How do I fix this?

    This can happen when Firefox has misread the paper size from the information supplied by Windows. Clearing it can involve finding some obscure settings, but here goes:
    (1) In a new tab, type or paste '''about:config''' in the address bar and press Enter. Click the button promising to be careful.
    (2) In the search box above the list, type or paste '''print''' and pause while the list is filtered
    (3) For each setting for the problem printer, right-click and Reset it. The fastest way is to right-click with the mouse and then press the r key on the keyboard with your other hand.
    Note: In a couple other threads involving Brother printers, the preference '''printer_printer_name.print_paper_data''' was set to 256 and when the user edited it to 1 that fixed the paper size problem. If you see a 256 there, you can edit the value by doubling-clicking it or using right-click>Modify.

  • Exported pdf from indesign drops punctuation when printed from adobe reader

    The pdf prints fine when printed from acrobat pro, but depending on the export pdf settings from indesign, it will drop most numbers and punctuation when printed from adobe reader.

    Is Adobe Reader installed on the same computer Adobe Acrobat is?

  • Does anyone know why when printing from light room to pdf the program just closes on me? I've talked to tech support and they are going to get back to me tomorrow but I am desperate I have tuns of homework to finish !!

    Does anyone know why when printing from light room to pdf the program just closes on me? I've talked to tech support and they are going to get back to me tomorrow but I am desperate I have tuns of homework to finish !!

    No, but if you really mean that the way you said it, I don't know that Print is the best way to this. If you haven't already, after selecting the images you want to get printed, try clicking the Export button in Book or Library module and then selecting format .PDF. Once you export the file to .PDF, try opening it where you saved it and printing from there, not in Lightroom but in Adobe Reader. If that doesn't help, here are a couple of videos that might--follow their instructions carefully with no shortcuts:
    Adobe Photoshop Lightroom 4's Export to PDF Using the New Book Module - YouTube
    Lightroom 5 - Exporting Images | Getting Started with Adobe Photoshop Lightroom 5 | Adobe TV
    If Lightroom keeps closing even when you try all this, you may need to reinstall Lightroom because your copy may be screwed up.

  • Windows 8 and IE 10 crashed after printing from Report Manager SQL server 2008 / 2008 R2

    We have a problem with Windows 8 in combination with IE 10 and printing reports.
    When we print a report from the Report Manager 'http://<servername>/reports' the browser crashed after a print.
    Sometimes before printing and somthimes after printing or when you close the browser.
    Al other operating systems like XP, Vista, Windows 7 with different IE versions have no problem.
    I tried the report manager from SQL Server 2008 and SQL Server 2008 R2.
    The same error occured when printing from our Internet application and the reportviewer.
    (ASP application written in Visual Studio 2010 and reportviewer version 10.)
    The event log shows two different messages.
    Faulting application name: IEXPLORE.EXE, version: 10.0.9200.16453, time stamp: 0x509b0dfb
    Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505aaa82
    Exception code: 0xc0000005
    Fault offset: 0x00061252
    Faulting process id: 0x780
    Faulting application start time: 0x01ce03a294f7d1d5
    Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: d4a72486-6f96-11e2-be6e-10604b6a74ed
    Faulting package full name:
    Faulting package-relative application ID:
    Faulting application name: IEXPLORE.EXE, version: 10.0.9200.16384, time stamp: 0x50107ee0
    Faulting module name: rsclientprint.dll, version: 2009.100.1600.1, time stamp: 0x4bb67a74
    Exception code: 0xc0000005
    Fault offset: 0x00017e7a
    Faulting process id: 0x9c8
    Faulting application start time: 0x01ce02f35c70ab85
    Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
    Faulting module path: C:\Windows\Downloaded Program Files\rsclientprint.dll
    Report Id: a13fccc6-6ee6-11e2-be67-10604b6a74ed
    Faulting package full name:
    Faulting package-relative application ID:
    Is there a fix for this problem?

    Dear Mike Yin,
    Thank you for your response. Your answer was the
    reason for finding the real problem.
    In december 2010 a SQL Server 2008 fix was the cause. I don't remember exactly the problem, but we changed the RSCLIENTPrint-x86.cab file. But instead to use the version of SQL Server 2008 we used the version of SQL Server 2008
    R2 (10.50.1600.1). This worked until
    Windows 8 (Internet Explorer crashed when printing).
    We fixed this problem by using the RSClientPrint-x86.cab file from SQL server 2008 (10.0.5500.0).
    But we now get the known problem that the
    activeX always must be installed again. 
    The reason for this is that the version of
    the SQL Server (10.0.5512.0) 
    and the rsclientprint.dll (10.0.5500.0) is different. SQL Server is newer (caused
    by a security patch (KB2716436)).
    Do you know when this problem will be resolved
    by Microsoft?
    Work arrounds
    I've also tried to install the RSClientprint.dll
    every time automatically (without user interaction).
    But this will be delayed the printing for more
    than 4 seconds. This
    is very annoying.
    Another workaround is to generate a PDF and print the PDF. But this is also
    a lot slower.
    Uninstall the security patch. but I don't know the security risk.

  • Printing from Reports

    Hi,
    I have HP Laser Jet 6L printer configured in Windows 98 machine and Windows 2000 machine. I have configured the Hp 6L drivers both in the client machines and linux servers. I made proper entry in uiprint.txt given by oracle for printing in Linux OS. When I am trying to print any report output from Reports Builder invoked in Linux thro' Open motif, I am getting junk characters printed in the paper.
    But the same works in a Network Jet Direct printer. Oracle ships some ppd files along with Oracle 9ias but hp6l is not there.
    Can anyone tell what should be done for this and how to configure the printer in linux inorder to print from reports.
    regds,
    R. Nanda Kumar

    Hello, dear Udo!
    In my mind, it is possible to solve your issues with Excel. How about Extract your statement to excel and do all necessary adjustments (font, etc....) in it and print it afterwards?
    Edited by: KhorkovAM on Sep 20, 2011 1:45 PM

  • Different Colors when printing from Photoshop and InDesign CS3

    Different Colors when printing from Photoshop and InDesign CS3
    I have the following problem:
    When printing from Photoshop or InDesign to a PostScript printer, Adobe recommends to let Photoshop handle the colors (I use the German version, so I don't know the exact term used, it changes slightly in all CS3 apps anyway).
    The manufacturer however told me to let the PostScript printer handle the colors.
    When I chose this option in Ps's print dialog and then choose ISO Coated as the printer pfofile, the results are fine.
    But when I place the exact same image in an InDesign file and print from InDesign or export to PDF and print via Acrobat, again using "Printer handles colors", the results are the exact same as if I had used Ps and chosen to let Ps handle the colors (way too saturated and a bit too red).
    ·Photoshop CS3
    ·InDesign CS3
    ·Test image is a TIFF in CMYK Fogra 27 Coated (which is also the working color space in Ps and ID.
    ·Printer: Xerox Docucolor 3535
    ·Printer profile: ISO Coated
    How can I make sure the printer handles the colors in other CS3 apps than Ps? I tried it with ID's print dialog (translated from the German version: Color Management > Options > Color Handling: PostScript-printer decides colors).
    Thanks a lot!

    RE: "You don't indicate what Xerox printers you have"
    In my first post I named it, is that the information you need?
    Docucolor 3535 using Splash 3535
    That's interesting, so I have to find a way to turn off the printer's Color Management function? I mailed them, hope they can tell me how to do it easily. They usually just tell me to not use any profiles and so on, but that's the general rule in this area, I'm really tired of hearing it. Everybody seems to think profiles and LAB mode are nuclear science and I should stay away from it.
    Anyway, the test image I'm using is a simple photograph (size A3, 300dpi), so no transparencies at all. I'm placing this image into an equally large ID file and print it from ID, then export it to PDF-X/3 and print it from Acrobat. Hope that helps.

  • Colors not printing correctly - Only When Printing from Reader 9

    I have recently been having problems printing color PDF's using Reader 9. Yellows are printing as blue, blues as pink, pink as grey, etc. I have no problems printing any other types of photos, documents, or powerpoint presentations so I am assuming it is some setting in Reader. My printer is an HP Color LaserJet CM1015. Any help diagnosing this problem would be greatly appreciated!
    Thanks in advance,
    Dave

    It is using sRGB and that is the only color profile available.
    In addition, when I try to print 4 slides per page and 1 slide per page, the colors are completely different than when I try to print 2 slides per page.
    I have tried changing settings in print options and put them back to default and nothing I do changes the issue. Again, it only occurs when printing from Reader. Everything else prints colors perfectly fine.

  • CUPS Error message when printing from some applications

    Hi. I've got an issue when printing from some apps, but not others. Up to a few months ago everything was fine, then it started when Word would not print direct to my printer (Epson Stylus Pro 3880), not a big deal as I don't use it a lot and could print it through Safari if needed. Then more worryingly as a designer I found that PDFs stopped printing direct too, again I can print through Safari and Preview. Last night I installed a firmware update and now InDesign (CS4) is refusing to print!! Not great as printing via Safari/Preview doesn't give me the same level of control over my prints. Just checked both Illustrator and Photoshop and they both print okay. I get the same error code each time "error: /usr/libexec/cups/filter/pstoraster failed" Does anyone know what could be causing this?
    Thanks in anticipation. D

    cytan,
    As Matt pointed, an application printing to CUPS controls only the format of the input.  It has no direct control over the chain of filters inside the printing pipeline.  Acrobat isn't coded to use pstoraster, it is simpling submitting postscript to the print queue.  In an un-molested Apple supplied CUPS setup, that works fine.
    What is going on is that the CUPS system configuration got mangled by some third party bits.  In the Unix tradition, the configuration is fairly transparent, in the form of plain text files.  In particular, in /usr/share/cups/mime you will find out exactly how the filter pipeline is configured via a table of what filter to use to convert data between two mime types.  So we can inspect how the filters are setup and how a broken pstoraster is getting into the chain.
    I don't have a handy "before mangling" state, but I can clearly see the Apple specified filters to be invoked when the input data is application/postscript (in apple.convs).  I can also see a conflicting filter definition referencing the broken pstopdf (in mime.convs) but with a higher precedence, overriding the apple specified filter.  This is why, in reference to your points #1 and #2, simply removing pstoraster fails, because the filter configuration is what needs fixing.
    On my system, I found the pstoraster filter to be a shell script referencing a MacPorts install of ghostscript. I've since removed MacPorts, but that evidentally left the CUPS configuration in this broken state.  Without knowing exactly how the CUPS system was put into the broken state, fixing it can be a bit tricky.  Another posting suggested replacing the broken pstoraster with the Apple supplied equivalent of pstocupsraster.  That might work, but it would be better to simply remove the conflicting filter specification, which on my system is this bit in /usr/share/cups/mime/mime.convs:
    # pstoraster is part of GPL Ghostscript...
    application/vnd.cups-postscript        application/vnd.cups-raster     100     pstoraster
    Removing that will restore the Apple specified filter chain for postscript input.  With the filter specification gone, you are free to remove the pstoraster filter itself.
    On wating for Adobe to fix this...
    Acrobat provides enough things to scream about without pinning non-Acrobat problems on it as well.  Not only is this problem not the fault of Acrobat, but suggesting that Acrobat should reach into a CUPS system broken by some unknown third party and fix it is only going to complicate the situation by having two third party products trying to un-do each other's configuration of a system resource.   Do you really trust Adobe to fiddle with system components it doesn't own?  No, I didn't think so.  Adobe installers and updaters have enough trouble with the stuff they do own.
    So, why does this problem only seem to affect Acrobat (your point #3)?  I suspect it is simply that Acrobat is in the minority of submitting Postscript to the print queue.  Any print job produced via CoreGraphics APIs is going to enter the system via a different path (namely, PDF), but the Postscript method is completely legitimate and any application that submits Postscript will be affected in the same way as Acrobat.
    I hope this sheds some useful light on what is really going on with this problem.
    -john

  • Adobe Reader bypasses "secure print" settings when printing from IE add-on

    We have the IE add-on for Adobe Reader enabled (Internet Explorer 9), and we've found that for some people this is causing PDFs to get printed without the "secure print" option, even though the print dialog shows it. Our printer settings all have the setting enabled for "secure print", which requires you to enter a PIN on the printer before the print job will be released. When printing PDFs from Adobe Reader (currently 11.0.3, but I couldn't see anything in the release notes for .4, .5. or .6 that are relevant) outside of IE, secure print works fine, but when it's opened within the Adobe Reader plugin for IE, the secure print setting is enabled but the print job gets sent to the printer without the PIN requirement... somehow.
    I'm completely stumped by it, and didn't even believe it until I saw it myself.
    Does anyone know what might be working differently when a PDF is printed from the add-on than when it's printed by a 'full' instance of Adobe Reader?
    On an affected PC, if you disable the add-on, the PDF opens in that full instance and works normally, so it's very definitely related (somehow) to the add-on specifically.

    Hey,
    I have been advised against monitor calibration, and I'm assuming if all of my other products have come back correct in terms of colour I see on screen that it should be ok?
    the person that told me about the Adobe workspace has the same printer, but she works in Photoshop, and had someone set it up for her. She tried to help over phone, but is difficult as we have different versions of Adobe software, and it was a while since she had it done.
    My workspace is currently in RGB, so would you suggest working in CMYK?
    If I have my workspace set to Adobe RGB (1998) should I then be changing my printer profile to the same one?
    I've attached the colour setting screen shot, I've not done anything to change this.
    I think I need the setting on bottom image set to 'colour sync' is that right?
    I'm also not sure about the relative colourimetric option. When at art college, I was always told to print in perceptual, but not sure which is best option here.

  • Relative hyperlinks in pdf documents printed from visio 2007

    Hello to all. The problem we are trying to solve is to maintain relative hyperlinks that were created in visio 2007 when we publish or print a pdf document. The pdf document that we printed is written in adobe reader 9, and it maintains the hyperlinks but as absolute ones and we required the hyperlinks to maintain as relatives. The idea is to distribute the pdf document with its hyperlinks and the documents that are linked to it in different computers that are not in the same network. The documents that we are trying to link are pdf, word and excel 2007 documents. The operating system we use is Microsoft vista home premium. Does anyone know how to maintain relative hyperlinks in a pdf document printed from visio 2007? Thanks in advance!

    Bernd Alheit, thanks for your answer. We print the pdf document from visio 2007 and then we read it in adobe reader 9. The relative hyperlinks work fine in visio 2007, but they change to absolute ones in the pdf document.

  • When printing from v10.1.3 or v9 from OSX Lion get Adobe Reader quit unexpectedly

    When printing from v10.1.3 or v9 from OSX Lion get Adobe Reader quit unexpectedly
    Click on the print button
    get the Print screen
    Click Print then get the error
    Am able to print fine from other applications
    Have tried uninstalling and restalling Adobe 10.1.3, downgrading to v9. reinstalling the printer driver.
    Process:         AdobeReader [2372]
    Path:            /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
    Identifier:      com.adobe.Reader
    Version:         9.4.0 (9.4.0)
    Code Type:       X86 (Native)
    Parent Process:  launchd [220]
    Date/Time:       2012-07-22 18:19:40.579 +1000
    OS Version:      Mac OS X 10.7.4 (11E53)
    Report Version:  9
    Interval Since Last Report:          265926 sec
    Crashes Since Last Report:           23
    Per-App Interval Since Last Report:  30 sec
    Per-App Crashes Since Last Report:   2
    Anonymous UUID:                      6710821A-4F63-46E6-AD7A-75FB91C7B394
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000014
    VM Regions Near 0x14:
    --> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL  /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
        __TEXT                 0000000000001000-0000000000003000 [    8K] r-x/rwx SM=COW  /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
    Application Specific Information:
    objc[2372]: garbage collection is OFF
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   AdobeAGM                                0x7e5f1824 PrintInstance::BuildEndPrintEvent() const + 84
    1   AdobeAGM                                0x7e5fa503 PrintInstance::NextPrintEvent() + 8157
    2   AdobeAGM                                0x7e5291f3 PrintSession::GetNextPrintEvent() + 151
    3   AdobeAGM                                0x7e529c60 _AGMPrintSessionGetNextPrintEventProc_GetNextPrintEvent(AGMPrintSession*) + 40
    4   com.adobe.Acrobat.framework             0x8077def8 0x7fe0a000 + 9912056
    5   com.adobe.Acrobat.framework             0x801d0749 AcroSecurityBailOutImpl + 2003525
    6   com.adobe.Acrobat.framework             0x801d08eb AcroSecurityBailOutImpl + 2003943
    7   com.adobe.Acrobat.framework             0x8004ffe0 AcroSecurityBailOutImpl + 428764
    8   com.adobe.Acrobat.framework             0x800511fd AcroSecurityBailOutImpl + 433401
    9   com.adobe.Acrobat.framework             0x7ffbaa3b CopiesPagesPDE_Prologue + 9523
    10  com.adobe.Acrobat.framework             0x7ffbadce CopiesPagesPDE_Prologue + 10438
    11  com.adobe.Acrobat.framework             0x7ffbb298 CopiesPagesPDE_Prologue + 11664
    12  com.adobe.Acrobat.framework             0x7ffcc2ca CopiesPagesPDE_Open + 50672
    13  com.adobe.Acrobat.framework             0x7ffcc495 CopiesPagesPDE_Open + 51131
    14  com.adobe.Acrobat.framework             0x800066c5 AcroSecurityBailOutImpl + 127425
    15  com.adobe.Acrobat.framework             0x80006852 AcroSecurityBailOutImpl + 127822
    16  com.adobe.Acrobat.framework             0x80006a9b AcroSecurityBailOutImpl + 128407
    17  com.adobe.Acrobat.framework             0x8018fe6e AcroSecurityBailOutImpl + 1739114
    18  com.adobe.Acrobat.framework             0x801ffb92 AcroSecurityBailOutImpl + 2197134
    19  com.adobe.Acrobat.framework             0x801ff925 AcroSecurityBailOutImpl + 2196513
    20  com.adobe.Acrobat.framework             0x802e19ac AcroSecurityBailOutImpl + 3122344
    21  com.adobe.Acrobat.framework             0x8001fa66 AcroSecurityBailOutImpl + 230754
    22  com.adobe.Acrobat.framework             0x80020e3a AcroSecurityBailOutImpl + 235830
    23  com.adobe.Acrobat.framework             0x80165925 AcroSecurityBailOutImpl + 1565729
    24  com.adobe.Acrobat.framework             0x8016346a AcroSecurityBailOutImpl + 1556326
    25  com.apple.AppKit                        0x93d05fc5 -[NSWindow sendEvent:] + 7533
    26  com.apple.AppKit                        0x93c9f163 -[NSApplication sendEvent:] + 4788
    27  com.apple.AppKit                        0x93c30d11 -[NSApplication run] + 1007
    28  com.adobe.Acrobat.framework             0x7fe0d28d RunAcrobat + 2557
    29  com.adobe.Acrobat.framework             0x7fe0c9ce RunAcrobat + 318
    30  com.adobe.Reader                        0x00002e8b start + 2371
    31  com.adobe.Reader                        0x0000264a start + 258
    32  com.adobe.Reader                        0x00002571 start + 41
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib                  0x9b0ac90a kevent + 10
    1   libdispatch.dylib                       0x98338e10 _dispatch_mgr_invoke + 969
    2   libdispatch.dylib                       0x9833785f _dispatch_mgr_thread + 53
    Thread 2:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 3:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 4:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 5:: WebCore: LocalStorage
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.JavaScriptCore                0x9c9a7e81 WTF::ThreadCondition::timedWait(WTF::Mutex&, double) + 81
    4   com.apple.WebCore                       0x91b97501 WTF::MessageQueue<WebCore::LocalStorageTask>::waitForMessage() + 135
    5   com.apple.WebCore                       0x91b97454 WebCore::LocalStorageThread::threadEntryPoint() + 74
    6   com.apple.WebCore                       0x91b973b1 WebCore::LocalStorageThread::threadEntryPointCallback(void*) + 17
    7   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    8   libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 6:: com.apple.NSURLConnectionLoader
    0   libsystem_kernel.dylib                  0x9b0a9c22 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x9b0a91f6 mach_msg + 70
    2   com.apple.CoreFoundation                0x95c619da __CFRunLoopServiceMachPort + 170
    3   com.apple.CoreFoundation                0x95c6ab04 __CFRunLoopRun + 1428
    4   com.apple.CoreFoundation                0x95c6a1dc CFRunLoopRunSpecific + 332
    5   com.apple.CoreFoundation                0x95c6a088 CFRunLoopRunInMode + 120
    6   com.apple.Foundation                    0x9c5d80c4 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 378
    7   com.apple.Foundation                    0x9c5cbe25 -[NSThread main] + 45
    8   com.apple.Foundation                    0x9c5cbdd5 __NSThread__main__ + 1582
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 7:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 8:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 9:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 10:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 11:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 12:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 13:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 14:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be78 _pthread_cond_wait + 914
    2   libsystem_c.dylib                       0x97b4382a pthread_cond_wait + 48
    3   AdobeAGM                                0x7e4b0bc4 pthread_condition_base::Wait(pthread_scoped_lock_base&) + 26
    4   AdobeAGM                                0x7e4b0b1d AGMMessageQueueImpl::Pull() + 65
    5   AdobeAGM                                0x7e8a2b94 AGMWorkQueueTask::operator()() + 84
    6   AdobeAGM                                0x7e8a3e1f boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 75
    7   AdobeAGM                                0x7e4b09e1 thread_proxy + 45
    8   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    9   libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 15:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be78 _pthread_cond_wait + 914
    2   libsystem_c.dylib                       0x97b4382a pthread_cond_wait + 48
    3   AdobeAGM                                0x7e4b0bc4 pthread_condition_base::Wait(pthread_scoped_lock_base&) + 26
    4   AdobeAGM                                0x7e4b0b1d AGMMessageQueueImpl::Pull() + 65
    5   AdobeAGM                                0x7e8a2b94 AGMWorkQueueTask::operator()() + 84
    6   AdobeAGM                                0x7e8a3e1f boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 75
    7   AdobeAGM                                0x7e4b09e1 thread_proxy + 45
    8   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    9   libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 16:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be78 _pthread_cond_wait + 914
    2   libsystem_c.dylib                       0x97b4382a pthread_cond_wait + 48
    3   AdobeAGM                                0x7e4b0bc4 pthread_condition_base::Wait(pthread_scoped_lock_base&) + 26
    4   AdobeAGM                                0x7e4b0b1d AGMMessageQueueImpl::Pull() + 65
    5   AdobeAGM                                0x7e8a2b94 AGMWorkQueueTask::operator()() + 84
    6   AdobeAGM                                0x7e8a3e1f boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 75
    7   AdobeAGM                                0x7e4b09e1 thread_proxy + 45
    8   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    9   libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 17:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 18:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 19:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 20:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 21:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 22:: com.apple.appkit-heartbeat
    0   libsystem_kernel.dylib                  0x9b0abbb2 __semwait_signal + 10
    1   libsystem_c.dylib                       0x97b4c7b9 nanosleep$UNIX2003 + 187
    2   libsystem_c.dylib                       0x97b4c558 usleep$UNIX2003 + 60
    3   com.apple.AppKit                        0x93e79816 -[NSUIHeartBeat _heartBeatThread:] + 2399
    4   com.apple.Foundation                    0x9c5cbe25 -[NSThread main] + 45
    5   com.apple.Foundation                    0x9c5cbdd5 __NSThread__main__ + 1582
    6   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    7   libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 23:
    0   libsystem_kernel.dylib                  0x9b0ac90a kevent + 10
    1   com.adobe.Acrobat.framework             0x804ff1fe AcroSecurityBailOutImpl + 5340410
    2   com.adobe.Acrobat.framework             0x8041adf7 AcroSecurityBailOutImpl + 4405491
    3   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    4   libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 0 crashed with X86 Thread State (32-bit):
      eax: 0x00000000  ebx: 0x7e5f17de  ecx: 0x7e3f96ac  edx: 0x00000001
      edi: 0x7eac1420  esi: 0x01ab4228  ebp: 0xbfffdea8  esp: 0xbfffde60
       ss: 0x00000023  efl: 0x00010286  eip: 0x7e5f1824   cs: 0x0000001b
       ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
      cr2: 0x00000014
    Logical CPU: 0
    Binary Images:
        0x1000 -     0x2fff +com.adobe.Reader (9.4.0 - 9.4.0) <8CEEE461-DF9E-46F5-816E-71DE8564A551> /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
       0x60000 -    0x61fff +com.adobe.eulaframework (??? - 1.0) <8AFCE794-4DCF-41B8-9D0F-30311D7BEB92> /Applications/Adobe Reader 9/Adobe Reader.app/Contents/Frameworks/EULA.framework/Versions/A/EULA
    0x2000000 -  0x210dfe7 +AdobeACE (??? - ???) /Applications/Adobe Reader 9/Adobe Reader.app/Contents/Frameworks/AdobeACE.framework/Versions/A/AdobeACE

    Right. After almost a day I finally sorted the problem.
    Adobe Reader worked under the spare Admin account so I deleted that in case it was confusing the installer.  I then rerpaired persmissions.  I then re-installed Reader.  Same problem "Internal Error"!!
    So, I re-created another Admin account and opened Reader.  No problem.  After clicking accept licence it opened up with a question to make default or not.  After this I hunted through every folder and found that Under 'User/Librarary/Application Support/Adobe' there was an Acrobat folder.  When I checked the account I normally use there wasn't, and never was??  So I copied pasted a copy of the Acrobat folder into the same location on the non working account and all is fine.
    Problem for me is, why did this happen?  I wasted almost a day on this. Is it a problem with the installer, the Macbook or Permissions.  I checked permissions and they are identical to those on the spare Admin account.  So why did the installer not create the Acrobat folder on the main account from where it was installed?  Reason it concerns me is with regard to updates.  Will they also screw up?
    I'll try to explore further as times goes on but for now I have to say I've had enough of Acrobat and Lion for one day.  "It just works".  Really???

  • Banding occurs when printing from Illustratror/InDesign on HP Designjet Z5200 PostScript Printer

    Recently we got the below printer for large-format prints such as posters, banners and the like.
    http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/18972-18972-3328061-12600-3328080-4122732.ht ml
    However so far when printing directly from InDesign and Illustrator there have been problems with "banding" (alternating stripes of darker and brighter colors on the paper when printing).
    It seems that this could have something to do with either the type of paper and/or the OS (we use both XP and Win7) on which CS5 runs but I am still unsure if these are the real causes.
    After having talked to a certified HP-technician (not only a support employee!) the technician pointed towards the CS5 package as the culprit.
    At the very moment we are using a workaround that the before mentioned technician advised us to use which is basically the following.
    Illustrator --> Saving the Ilustrator file, then opening it in Photoshop and saving as a tiff raster image in the relevant resolution, then importing the tiff raster image into HP's HP own "Instant Printing Pro" printing application.
    InDesign --> Saving the InDesign file as a pdf, then opening the pdf in Photoshop and saving as a tiff raster image in  the relevant resolution, then importing the tiff raster image into HP's  HP own "Instant Printing Pro" printing application.
    These two solutions both work without banding on the final print.
    However, sometimes - as mentioned before - it seems that the paper might absorb the ink better if it's of a better/thicker quality when banding doesn't seem to occur (at the moment we mostly use plain paper settings in the local printer settings display when loading a roll of paper which also is a cheaper type of paper) and while banding seems to occur mostly when printing from XP machines it doesn't always seem to occur when doing so from Win7 machines.
    What's the score on the above?
    Any help and input is welcome and appreciated!

    Well, I have no official
    connection to Adobe, but any manufacturer who sells a product targeted
    at the graphic arts industry, and then says that the reason it doesn't
    work is because there's a problem with the software produced by the
    graphics industry leader needs a reality check. Printer manuafacturers
    have had access to Adobe for years, so there's really no excuse for an
    incompatibility problem.
    Your company is a vendor? Get
    escalated. HP should be all over getting this to work correctly,
    including providing a RIP for you if that's what it's going to take to
    implement proper printing. How do the expect you to demonstrate or
    recommend this printer if it stripes the background?
    Peter -->
    You are right about basically anything that you said and I agree that this should be HP's headache. But it's not so simple at the moment.
    First of all I'd hate to stand back like a dummy if it would turn out to be a minor driver setting issue or another insignificant problem that creates the banding. On the other hand it would of course also be the local HP-support failing since they didn't manage to tell us about it in the first place and that's really their job and responsibility but under any circumstance, I'd like to give the ideas and suggestions from the other participants further up this thread a chance and see if the pdf-printing or other ideas work. In other words..., if I'd complain to HP it had to be bulletproof.
    Secondly we are supposed to sell these and similar products to our clients and if I should start a dicussion I'd have to argue not only with HP who would most likely claim that the workaround they told us works (in a way) and that this was a result - at least to them - as well. I might also have to start discussing with the CEO of our company, the purchasing department and the marketing director (the latter actually said some time ago when we had the first problems that if the printer didn't work according to the HP-consultant's promises they could have it back, so there is at least some hope there). At the moment I am too busy at work and too low paid to be getting into this. And I seriously doubt that HP would give us a RIP to be testing this off even though we'd argue that the clients won't be able to work this out if we don't do. They'd probably just say that it's mainly for plotting charts and architects or stuff or find a whole range of other excuses. It's not certain and there could be positive surprises but I'd say that that's not likely.
    There is one other thing Peter that I am still wondering about...
    If you take a look again at the fourth and last picture-link I posted you can see the exact same print as in link no. 3 but whereas the third link shows banding the last - the fourth image link - shows no banding at all. Now I am not a 100% sure anymore if these were both printed directly from Illustrator but to my best knowledge they were since I printed all of these banners the same day and I don't recall saving to tiff or using other programs. I might be wrong but if that's the case then the thick HP-paper doesn't band whereas the thin does. That's the reason why I stated previously that the banding might occur with thinner paper (or wrong paper load settings) and doesn't occur with thicker paper at all. As mentioned I don't recall this action a 100% but am pretty sure. Also therefore I would like to run another test when I get more time and won't be so busy at work as I am right now.
    Do you think there could be a difference there...?
    macinbytes wrote:
    I'm guessing they have the same crappy Colorburst software that shipped with the HP we got and it's never going to get good with InDesign or Illustrator transparency. We have the thermal printer that is 6x more expensive and the software is still bad. At version 9.3 it still fails on InDesign transparency.
    We just make tiffs or normalized PDFs for files containing InDesign transparency. Illustrator transparency generally works better than InDesign, but isn't infallible. Anything that uses the gradient feather tool in InDesign I don't even bother with a test print to see if it gets it because I know it will fail 100% of the time.
    If they are a vendor they are in a Catch 22 if they do it right and go for a solution that normalizes the files properly before sending to the garbage software that ships with it. When you are talking about an entry level thermal inkjet the software package isn't going to be robust. Something like a GMG or other solution to handle all the show devices files works, but at best you are disingenuous about how files are being handled with your clients and face pushback when they can't run all the cool tricks to them when they get it out in the field.
    Happens with Colorburst, happens with Colorgate, happens to a lesser degree even with the lower end Creo RIP. Fiery seems to get it good somehow, but doesn't power a ton of inkjets.
    HP support is phonetag hell anyway for inkjets. They buy out tons of companies that produce anything printing like ColorSpan and provide bare minimum support on the products they slap an HP tag on. They want to sell inks and papers. They don't make the software and license it in bulk like the crap they load on their computers. They also usually ship with old software that needs at least a couple point releases before it is current, but even the current software on their thermal printers sucks at InDesign transparency. HP may need a reality check on their software, but I doubt they get it. They've got a sufficient stranglehold and supporting what is essentially a bottom of the barrel portion of their printing business is in the high maintenance low yield square for them.
    macinbytes -->
    Wow, now THAT is scary reading...!
    If what you wrote is true then things really start looking bleak. But I can recognize some of the problems that you are mentioning although I am not into all of the details that you are writing about in your thread. But it sure looks like they just mass produce and try to keep support to a bare minimum whereas they are scoring big bucks on the media, inks and other accessories and then hope that complaints will die and people will just give up in the end.
    It does make sense also seen in light of the fact that our local HP-consultant who "introduced" us to the printer praised it to the sky with a lot of "sales mambo jambo", trying it out in HP's own "E-share & Print" (which I was told by the HP-technician was the wrong HP-print program, instead he made me download and install the "Instant Printing Pro") whereas he NEVER even tried it off in any of the Adobe programs or asked some of our employees to do so.
    If you are getting more info in regards to the development in these cases or solutions software-like speaking I'd love to hear from you.
    Thanks for your time and for posting.

  • CE 10 - Slow printing from Report Viewer in Win Server 2K3

    Post Author: JacobK
    CA Forum: General
    I'm not very familiar with Crystal reports, we are having slowness issues when printing from the web through report viewer in Win2K3.  Recently upgraded from Win 2000 to 2K3.  Same crystal version, CE 10.  On the 2000 system this report printed fine.  Now there is a delay in bringing up the report in viewer and then an extreme delay when printing.  This report prints normally when printing directly from Crystal.
    Any ideas?
    Thanks in advance.

    OK so I have updated VS 2010 to SP 1, and installed CR2010. Within my project I have updated the referenced .dlls
    CrystalDecision.CrystalReports.Engine
    CrystalDecision.ReportAppServer.ClientDoc
    CrystalDecision.ReportSource
    CrystalDecision.Shared
    CrystalDecision.Web
    I updated the web.config assembly entries to match the new version # (13.0.2000.0) and the app compiles.
    However, now when I try to run a report I receieve the following error...
    An error of type <System.Web.HttpException> occurred
    Error Details: The 'PageToTreeRatio' property cannot be set declaratively.
    I am sure I need to make some code changes but I cannot find this "PageToTreeRatio" attribute anywhere in my .asp code. Is this something you are familiar with? Is this parameter in the report itself?
    As I mentioned before the reports were built in CR10 Deveoper (not in Studio) is that the source of this problem? Will I have to rebuild all the reports in VS2010?
    Thank you for all the help so far, I am a lot closer than I was yesterday!!
    -C

Maybe you are looking for