CR 2008 paramteres, export and print windows language localization

Hi, i want to use in my application Crystal Reports. I installed a trail version of CR 2008. My application is written in Delphi 7. I connected my application with Crystal Reports through the official VCL downloaded from http://ftp1.businessobjects.com/outgoing/products/vcl/crystalvcl11.zip and edited it to work with CR 2008 (12.x.x.x).
Everything works with this VCL. When i have parameters the Enter Values window where i enter the values for parameters and in the Viewer window the Export and Print Dialog are in English. I want to have them in Polish Language ( or operating system language). In CR i set in View -> Preferred Viewing Locale -> More ... Polish but the viewer window, export, print and parameters are still in English. I tried this also on computers without installed CR 2008 but installed CR Runtime and it is still English.
Operating system in Windows XP SP3 Polish.
Any ideas what i can do to have this windows localized in my language?
Robert

Hello Robert:
I am not sure that you will be able to do much. The VCL has not been updated since version 10 of Crystal Reports and it may be that the functionality you require will just simply not be possible. (I'll get someone else who used to work with the VCL to have a look too.)
In the meantime, you may want to have a look at the following:
Go [here|http://devlibrary.businessobjects.com/BusinessObjectsXIR2SP2/en/devsuite.htm], then check out Crystal Reports .NET SDK > Tutorials and Sample Code > Other Tutorials > Configuring Multilingual Client Support. (The above is for CR XI R2, it's the same for CR 2008 - I just don't have a link handy.) I am not sure if the above will help.
Also, note that you do not have to use the VCL. You can use the CR assemblies for .NET with Delphi. See the following for more details:
/people/trevor.dubinsky/blog/2009/10/09/introduction-to-delphi-prism-applications-development
/people/trevor.dubinsky/blog/2009/10/19/delphi-prism-how-to-setup-the-environment-for-crystal-reports-2008-and-bobj-enterprise-r3-development
/people/trevor.dubinsky/blog/2009/10/26/crystal-reports-and-enterprise-net-developer-resources
Samples:
[Net Delphi CR2008 Simple Previewer|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/90f71e6a-cc13-2d10-7c8c-e38ce6d278be]
[Net-Delphi-CR2008-LogonInfo-subreport|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f02665e4-cc13-2d10-b180-e0a7b3770ae3]
[Net-Delphi-BOE12_Simple_View_Report|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/702f1223-cc13-2d10-c383-967a1e8d11ac]
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup

Similar Messages

DPI and PPI in Aperture 'Export' and 'Print' windows

Hi,
As mentioned in an earlier post, I just bought an Epson 3880 printer and some Epson Hot Press paper, so now I have to pay attention to PPI (term used for displays) and DPI (term used for printers).
In Aperture however, files being exported require DPI specs(!), while files being printed require that we specify PPI specs. How is that?
Also, my Epson manual indicates that I can print at 5 distinct "DPI" settings, from 180 to 2880. My Aperture Print window, however, only offers 3 options with 360 "PPI" as the highest (considered Draft quality by Epson - if "DPI"), plus a 4th referred to as Custom.
Also, I have a note jotted down a while back that says: "1440 dpi for most papers with 240 dpi files, at 2880 if 360" - whatever that meant 6 months ago at an Epson 3880 seminar, before I got the printer.
Can you guys sort this out for me? Please?
Thanks a lot,
Raphael

I'm not at my studio. My current driver is 8.x. The newest driver is 9.33. My remarks here may not fit with your more current version of the driver (but that would surprise me — the printer came out about 4 years ago, iirc).
The profiles are not, afaik, included with the driver, at least when you download it from Epson's site.
There are two profiles for each Epson Fine Art paper — one at 1440 and one at 2880. You should try each with every kind of print you make, and determine which is better. IME, _for my needs_, 2880 was never worse. I use the 2880 profiles.
The profile is selected from the "Color Profile" drop-down at the top of the "Rendering" section of Aperture's "Print" dialog.
(Set "Render Intent" to "Perceptual" for, in general, photographs or anything with smoothly graduated changes in color. Set "Render Intent" to "Relative Colorimetric" for, in general, graphics or anything with smooth areas of constant color and sharp transitions between areas of color. Generally, if "Render Intent" is "Perceptual", check "Black Point Compensation"; otherwise uncheck it.)
Leave "Print Resolution" at "Auto". I know of no reason to ever change this. (I don't, in fact, know what this control does, and have never changed it.)
When you click "Print" in Aperture's "Print" dialog, a short dialog opens asking you if you want to save any changes you made to your Preset. I always save my changes. Prints often need to be immediately remade — all transitions of data from electronic to physical media are problematic — and I like to return to my Preset ready to print the same Image(s) again.
When that dialog closes, the OS print dialog opens. Your 3880 printer should already be selected in the "Printer" drop-down. You need to create and should save an OS Preset for your paper. Note that on the "Color Matching" page (this dialog has pages, not tabs; direct complaints to Cupertino), all (two) options should be grayed-out. This indicates that Aperture is handling color matching, which is what you want (for best prints and anything approaching a color-calibrated workflow). On the "Paper Handling" page, the "Destination Paper Size" drop-down is grayed-out, but should show you the selection you made in the Aperture Print dialog. The "Printer Settings" page has two tabs. On the "Basic" tab, in the "Media Type" drop-down, select your paper ("Fine Art Paper ▹ Hot Press [Bright or Natural])*. The "Ink" drop-down should be grayed-out, but show "Matte". Matte is proper selection for Hot Press [Bright or Natural]. This dialog knows this from your color profile selection in the Aperture Print dialog. Chose "16-bit" output and any other options your want (you can experiment; I find no difference). I ignore the warning about print quality at the bottom area — this has never been an issue. On the "Advanced" tab of the "Printer Settings" page, it should tell you that "Epson Driver Color Management is Off". That's what you want. You want Aperture to manage the color.
Save your OS print dialog Preset. Use it every time you print to the same paper.
*If you cannot select your paper, you have not selected the correct paper size in the "Printer" section of Aperture's Print dialog. Note that the "Paper Size" selection includes not only the paper size, but also whether the feed is by sheet-feeder or manual, and whether or not the print is borderless. (I didn't design this; I assume there are reasons to have shoe-horned these options into the "Paper Size" selection.
This is all tricky on top of being actually complex and next to being new. It takes everyone time and mistakes (read: ink and paper) to canalize a flow that works for producing the prints they want. I hope this gets you there a little faster. Report back with what doesn't work.
—Kirby.

Crystal Reports export and print fails with SSL / https but works with http

Windows 2008 Server, 32-bit (IIS7)
ASP.NET 2.0
Ajax 1.0
Crystal Reports version 10.5.3700.0
http: printing works, export works
https: printing not working, only export to MS Excel and MS Word work.
I am able to generate reports using both http and https, and the toolbar icons are all showing. However, I am unable to print or export properly with SSL.
Printing prompts me with a select printer window, and then a window 'Retrieving Page 1' follow by two messages from Crystal Print Control both stating:
A communication error occured. Printing will be stopped.
Exporting generates various errors depending on which export method is being selected (however Excel and Word work over https).
I've found the same problem on this site and other forums, but never a resolution to get exporting and printing to work with SSL. Will someone please provide me assistance or possibly relay what settings they're using if they have Crystal Reports export or printing working over SSL in IIS7? Everything works fine when I change the address from https to http.
Please let me know if I can help by providing further information. We've gone through a great deal of possible solutions with code and I'm currently looking in to IIS settings again.
Thank you.

Thanks Ludek. I got it by searching KB number.
Unfortunately, it didn’t fix my problem even my IE (IE8 and IE 9) has correct setting. I double check my version. PrintControl.CAB is version 10.2.0.1146. we use VS 2005 Crystal report and VB .NET. It works fine on HTTP. But when we use HTTPS (SSL Certificate from go daddy).
1: Crystal report export
            Export to MS Excel, Word: pop us “File download”, then click “Save”. It says “Internet Explorer cannot download ReportView.aspx from my site. Internet Explorer was not able to open this internet site. the requested site is either unavailable or cannot be found. Please try it again later”
            Export to RPt, Rich text format: It says “Internet Explorer cannot download ReportView.aspx from my site. Internet Explorer was not able to open this internet site. the requested site is either unavailable or cannot be found. Please try it again later”
            Export to PDF : nothing happened.
2: Print:
            Pop up dialog to select printer, click “Print” “. Shows windows “Crystal Report Viewer” and pop us error message box. Title is “Crystal Print Control”. Message is “An communication error occurred. Printing will be stopped”. Click “OK” and pop up error message box again.
Please advise.
Thank you very much!

CR Viewer tool bar images are missing; Export and Print are not working

Hi There
I used Crystal report 10.5(VS 2008 base crytal report -- CRRedist2008_x86.msi), i developed ASP.net application using VB.net program(i used .net 3.5). One of the pages in the application is having crystal report viewer, which is calling a crystal report to populate the result. The report is working as expected on development machine (Win Vista). Hence, I moved the application onto Server (Windows Server Web; 32Bit OS and IIS). I installed the CRRedist2008_x86.msi, which added the "aspnet_client" under default website. As my site is a made as an application under default webiste. I tried...
a) By copying the aspnet_client folder into the website folder
b) By adding a virtual directory called "aspnet_client" under my website pointing it into the folder under "default website"
None of the trials are working for me.
When I click on Print or Export buttons (although their images are missing), I get the error sigh on bottom left (status bar) of the browser and the popping up the same giving me below error details
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; HPNTDF; InfoPath.3; MS-RTC LM 8; .NET4.0C)
Timestamp: Tue, 2 Nov 2010 15:11:12 UTC
Message: Object doesn't support this action
Line: 41
Char: 1
Code: 0
URI: http://65.123.xxx.x:37188/xyzweb/(S(uhgxkx45iwlrbancwzfunp55))/reportpage.aspx
Any help in resolving this issue would be greatly appreciated.
Thank You,
Edited by: skbo007 on Nov 2, 2010 4:11 PM

Hello All.
I am excited to let you know that the issue is being resolved.
Here is steps that lead me to resolution and solution..
I installed Fiddler2 and looked into every the debugging details of the transaction while running the report.
Learned that the crystal report is using the aspnet_client foler under "Default website" NOT under the crrent website.
Hence I tried to access the image via http path from local machine
http://myserver/aspnet_client/system_web/2_0_50727/CrystalReportWebFormViewer4/images/toolbar/export.gif.
(Notice, "mysite" folder is been removed)
I was expecting to see the gif on my browsers' body. It gave me an error.
Investigated further more on the error and found that the "Managed Pipe Line" of the respective application pool is to be changed to "Classic" instead of "Integrated"
changed it .. Boom...
Tool bar is showing up with proper images and as well the "Export" and "Print" functions are working as expected..
Hope this helps to those in the same situation.
Again.. this is one of many many solutions on this issues.
Thank You
Edited by: skbo007 on Nov 3, 2010 9:42 PM

PDF Export And Printing Problem

I am using VB 2005 and the Crystal Reports that is bundled with it. I have reports on my website in the Crystal Report Viewer. I have the tool bar showing the Export and Print buttons. When you try to print (or export to PDF) you get an error from Adobe Reader "Adobe Reader could not open 'AcrXXX.tmp' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded)."
I can see the file in my temp folder on my c-drive and the file (AcrXXX.tmp) does not contain a pdf instead it contains html for the report (including the report viewer). I tried deleting everything in my temp folder and I still get the error. My desktop is Adobe Reader 8.0 and IE 6 and Windows XP.
The same code will create the PDF on all development and test web servers just not on my production server.
I have no problem exporting a report to Word.

Hello Wendy,
if you are not too sure whether this errro is CR or VS related pls simply try to use one of our samples and see if you can export from htere or if you get the same error:
Sample site for NET:
https://boc.sdn.sap.com/dotnet/samples
general docu:
https://smpdl.sap-ag.de/~sapidp/012002523100005853792008E/walkthrough_supportfiles.zip
specific samples:
https://smpdl.sap-ag.de/~sapidp/012002523100006252712008E/csharp_web_smpl.exe
https://smpdl.sap-ag.de/~sapidp/012002523100006252812008E/net_web_smpl.exe

Is there a way to export and print the browser data as a spread sheet?

I'm in the process of logging approximately 1,500 shots for a documentary (the old fashioned way - long hand: shot #, TC in, descriptions... ) and I'm wondering if there's a way to export and print the data in the browser as a spread sheet. It seems like a pretty simple thing, but I don't see it any where. Am I missing something?

Yes, people I work with use it, assistants fill the fields out for me. As far as I know there is no "Print Browser" option. Some folks have assistants copy and paste the info into text, csv or xml files. Since everthing has gone to meta tags, this approach is going the way of the electric spoon or feeding mayonnaise to Tuna.
Peace & Covering Fire,
B.S.

Export and Print icons missing from report viewer

I'm currently embedding crystal within a wicket application in which I'm making use of the getHtmlContent() method to retrieve the report's HTML. For whatever reason, I'm not able to get either the export or print icons (on the top left side of the viewer). Is this because I'm using the getHtmlContent() method or do I have something misconfigured somewhere? Setting the setHasExportButton(true) and setHasPrintButton(true) on the report viewer object has no effect.
If I run the same report using the generated JSP outside of my application (within tomcat), I see the export/print buttons. I notice the JSP makes use of the processHttpRequest() method. Any help will be greatly appreciated.
Thanks!
Louis

Hi Louis
- The getHtmlContent() method handles the user's request to generate the HTML for the report and returns the HTML as a String.
Note: Either the getHtmlContent method or the processHttpRequest method can be used to handle the user's request to generate the HTML for the report, depending on how you write your JSP. If the viewer's content is displayed more than once, then the getHtmlContent method is more efficient, because the request is processed once and the resulting HTML string can be used multiple times. In this case, you must set the content type of the HTML, as recommended in the table. Additionally, using getHtmlContent sets setOwnPage to false and disables exporting and printing.
- The setOwnPage(true) and processHttpRequest() method should be used if you want the export and print button to appear in the report viewed through Crystal Report Viewer.
Following is the snippet of code which shows you how to use these 2 methods.
//Get the IReportSource object from sesion and pass it to the viewer
     IReportSource reportSource = (IReportSource)session.getAttribute("reportSource");
Create the viewer and render the report -
     //create the CrystalReportViewer object
     CrystalReportViewer oCrystalReportViewer = new CrystalReportViewer();
     //set the reportsource property of the viewer
     oCrystalReportViewer.setReportSource(reportSource);
     //set viewer attributes
     oCrystalReportViewer.setOwnPage(true);
     oCrystalReportViewer.setOwnForm(true);
     //set the CrystalReportViewer print mode
     //oCrystalReportViewer.setPrintMode(CrPrintMode.ACTIVEX);
     oCrystalReportViewer.setPrintMode(CrPrintMode.PDF);
     //process the report
     oCrystalReportViewer.processHttpRequest(request, response, getServletConfig().getServletContext(), null);
Hope this helps you .
Thanks
Soni

[CS5.5] Lock PDF export and print presets

Hi,
With this post I would like to ask a question regarding locking certain features in Indesign.
Does anyone know if it is possible to ...
- lock PDF export and print presets so a user is not abble to change/override any preset properties, and is forced to use a preset without the possibility to override any of the properties when using it?
- force a user to use one of the predefinied presets to print or export a document without the ability to create a new preset?
- verify PDF-files to check what Indesign print/export preset was used?
Being part of a larger prepress team, we would like to make sure that, every PDF-file created by each team member, is created with the same specs.
Does anyone know of any plugin, tool or release that enables such a functionality?
Kind regards
John

If the employees cannot follow company policy, they need to know that there are other people looking for work who can. Yes, mistakes happen, but that would be a case of choosing the wrong preset from a list (which, if you leave more than one installed, can't be avioded). Changing settings against policy is not a mistake.

Export and print logging

Hi experts:
If we need to track records in regard to the exporting and printing behavior of users, that is, the usage of "export answer" or "print answer" functionalities on dashboard, is there any log files saved during the process? If yes, what's the files name?

hi 12261114,
A) cheat. create a single report using UNION ALL, you might add a different "TYPE" column, and setting a column break with that column (move it to the front, break column 1). probably reports have different number of columns, add NULL columns in a query when using UNION
display this/hide other reports when page in print mode, or some other state. you can have a dropdown or a checkbox for that.
create page item if needed for switching page to print or other mode
B) show all lines on all reports. use PDF printer on client site.. ..no CSV though
Simon

Export and print of Peports

Hi All,
I got stuck with a problem. Need your help.
Actulally, I have 5 reports in a single page and have to provide common export and print functionality so that
all the reports get exported in a single excelsheet and get generated in one PDF.
Thanks
PK

hi 12261114,
A) cheat. create a single report using UNION ALL, you might add a different "TYPE" column, and setting a column break with that column (move it to the front, break column 1). probably reports have different number of columns, add NULL columns in a query when using UNION
display this/hide other reports when page in print mode, or some other state. you can have a dropdown or a checkbox for that.
create page item if needed for switching page to print or other mode
B) show all lines on all reports. use PDF printer on client site.. ..no CSV though
Simon

Testing Export and print of additional web items

Hi,
Please do let me know how to carry on testing for Export and print of additional web items.
Thanks & Regards,
Lavanya.

Following are some of the things you should test -
Export -
1. Exporting to File: For different file types check the way data is getting extracted as compared to report results in URL. Here you need to check - a. if the correct values are getting exported (w/o any conversion of data types, or any format changes). b. Layout of the exported data (ex. row data is appearing in rows, etc.),
2. Check files for any missing data.
3. Check if exporting the data, with selected drill levels, filters, etc. is working fine (or is exporting everything irrespective of the data from current report reults).
Print -
Print your report using the default printer on your machine & check the following -
1. Reports is getting printed as expected in terms of data & layout.
2. The rows or columns are well within the page defined in your printer settings (ie nothing is running out of page).
3. When printing, change in orientation works for both the options without any loss of data.
All web items will not be printed, so you need to make a note of this.

"Missing parameter values." -- Export and Print only...

I have a web application and I am using CrystalReportViewer. I am passing several parameters to Crystal using:
report.SetParameterValue(field.Name, Session[field.Name]);
I have session variables which will hold parameters needed to pass into the report. The session variables are populated from controls on my webpage after an onclick event. This even not only populates session, but also passes parameters to the report with the following code:
ReportDocument report = new ReportDocument();
Session["MapPathName"] = "./Reporting/CaseStudy.rpt";
report.FileName = Server.MapPath(Session["MapPathName"].ToString());
ParameterFields fields = new CrystalDecisions.Shared.ParameterFields();
fields = report.ParameterFields;
foreach (ParameterField field in fields)
report.SetParameterValue(field.Name, Session[field.Name]);
CrystalReportViewer1.ReportSource = report;
This works great for reporting and is very extensible. However, when clicking on the "Print" or "Export" buttons on the toolbar I get "Missing parameter values." I attempted to export manually in code using the .ExportToStream function but I still get the error, "Missing parameter values."
I received this error also in Refresh, Search, and Navigate functions. This was corrected by calling a function that supplies the above code block to these functions. However, I do not see any events for controlling the Print nor the Export events.
QUESTION: How can I print or export a report when passing parameters using CrystalReportViewer? Thanks in advance!
P.S. - Crystal Reports XI Release 2
Edited by: KyleSavant on Jun 18, 2009 5:42 PM

There are no Export or Print events accessible for the viewer
Since it sounds like you are creating the reportdocument object in your click event, the settings on this object become out of scope on successive postbacks executed by other events.
to get around this without major changes, you can place your "report" object in session in this event and retrieve it from session on successive postbacks. This should solve your problems around navigation, printing and exporting. What you will need to do is check if the session object exists (usually in page_load or page_initialze) and if so, retrieve it from session and bind it to the viewer's reportsource. If the session object does not exist, then do nothing (ie you have not clicked your button yet that retrieves the parameter values from session and loads the report). Also, in your click event you can check if the report session object exists and if so, remove it so that it can be re-created with your new parameter values (ie i'm assuming the only time you want to set parameter values is in this event).
Dan

My InDesign crashes when it's about to export and print a file

Yes, it closes down whenever I perform those tasks, making me unable to export or print a file. I always need to reopen the Indesign and this thing keeps on happening. Please help. I don't know what to do with this.
It gives me these details of the problem though:
Process:         Adobe InDesign CS6 [618]
Path:            /Applications/Adobe InDesign CS6/Adobe InDesign CS6.app/Contents/MacOS/Adobe InDesign CS6
Identifier:      com.adobe.InDesign
Version:         8.0.1.406 (8010)
Code Type:       X86 (Native)
Parent Process: launchd [111]
Date/Time:       2013-05-21 03:24:52.686 -0700
OS Version:      Mac OS X 10.7.4 (11E2617)
Report Version: 9
Interval Since Last Report:          497575 sec
Crashes Since Last Report:           17
Per-App Interval Since Last Report: 611 sec
Per-App Crashes Since Last Report:   3
Anonymous UUID:                      6278EACB-CD51-4302-98ED-B3038A380CCF
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
VM Regions Near 0:
--> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL /Applications/Adobe InDesign CS6/Adobe InDesign CS6.app/Contents/MacOS/Adobe InDesign CS6
    __TEXT                 0000000000001000-0000000000005000 [   16K] r-x/rwx SM=COW /Applications/Adobe InDesign CS6/Adobe InDesign CS6.app/Contents/MacOS/Adobe InDesign CS6
Application Specific Information:
objc[618]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   ???                                     0xac00a630 _XHNDL_trapback_instruction + 0
1   ???                                     0xffffffff 0 + 4294967295
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib                  0x9493b90a kevent + 10
1   libdispatch.dylib                       0x962ace10 _dispatch_mgr_invoke + 969
2   libdispatch.dylib                       0x962ab85f _dispatch_mgr_thread + 53
Thread 2:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae78 _pthread_cond_wait + 914
2   libsystem_c.dylib                       0x9b13af7b pthread_cond_timedwait_relative_np + 47
3   com.apple.CoreServices.CarbonCore          0x9004a3a7 TSWaitOnConditionTimedRelative + 178
4   com.apple.CoreServices.CarbonCore          0x900ac67f MPWaitOnQueue + 200
5   PMRuntime.dylib                         0x005b9581 SetVSizeBaseline(unsigned long) + 1473
6   com.apple.CoreServices.CarbonCore          0x900ad5e0 PrivateMPEntryPoint + 68
7   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
8   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 3:
0   libsystem_kernel.dylib                  0x94938c22 mach_msg_trap + 10
1   libsystem_kernel.dylib                  0x949381f6 mach_msg + 70
2   com.apple.CoreServices.CarbonCore          0x900d70ec TS_exception_listener_thread + 90
3   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
4   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 4:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x900d8e62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9004a37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x900ac67f MPWaitOnQueue + 200
6   com.adobe.ACE                           0x00607a69 0x5c8000 + 260713
7   com.adobe.ACE                           0x00606d99 0x5c8000 + 257433
8   com.apple.CoreServices.CarbonCore          0x900ad5e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 5:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x900d8e62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9004a37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x900ac67f MPWaitOnQueue + 200
6   com.adobe.ACE                           0x00607a69 0x5c8000 + 260713
7   com.adobe.ACE                           0x00606d99 0x5c8000 + 257433
8   com.apple.CoreServices.CarbonCore          0x900ad5e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 6:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x900d8e62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9004a37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x900ac67f MPWaitOnQueue + 200
6   com.adobe.ACE                           0x00607a69 0x5c8000 + 260713
7   com.adobe.ACE                           0x00606d99 0x5c8000 + 257433
8   com.apple.CoreServices.CarbonCore          0x900ad5e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 7:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x900d8e62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9004a37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x900ac67f MPWaitOnQueue + 200
6   com.adobe.ACE                           0x00607a69 0x5c8000 + 260713
7   com.adobe.ACE                           0x00606d99 0x5c8000 + 257433
8   com.apple.CoreServices.CarbonCore          0x900ad5e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 8:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x900d8e62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9004a37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x900ac67f MPWaitOnQueue + 200
6   com.adobe.ACE                           0x00607a69 0x5c8000 + 260713
7   com.adobe.ACE                           0x00606d99 0x5c8000 + 257433
8   com.apple.CoreServices.CarbonCore          0x900ad5e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 9:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x900d8e62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9004a37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x900ac67f MPWaitOnQueue + 200
6   com.adobe.ACE                           0x00607a69 0x5c8000 + 260713
7   com.adobe.ACE                           0x00606d99 0x5c8000 + 257433
8   com.apple.CoreServices.CarbonCore          0x900ad5e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 10:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.apple.CoreServices.CarbonCore          0x900d8e62 TSWaitOnCondition + 124
4   com.apple.CoreServices.CarbonCore          0x9004a37d TSWaitOnConditionTimedRelative + 136
5   com.apple.CoreServices.CarbonCore          0x900ac67f MPWaitOnQueue + 200
6   com.adobe.ACE                           0x00607a69 0x5c8000 + 260713
7   com.adobe.ACE                           0x00606d99 0x5c8000 + 257433
8   com.apple.CoreServices.CarbonCore          0x900ad5e0 PrivateMPEntryPoint + 68
9   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 11:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.adobe.InDesign.AppFramework          0x14722556 GetPlugIn + 876822
4   com.adobe.InDesign.AppFramework          0x1471e8ff GetPlugIn + 861375
5   com.adobe.InDesign.AppFramework          0x1471f3c5 GetPlugIn + 864133
6   com.adobe.InDesign.AppFramework          0x1472098e GetPlugIn + 869710
7   com.adobe.InDesign.AppFramework          0x147209fa GetPlugIn + 869818
8   com.adobe.InDesign.AppFramework          0x14720a66 GetPlugIn + 869926
9   com.adobe.boost_threads.framework          0x01c6840d thread_proxy + 141
10 libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
11 libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 12:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.adobe.InDesign.AppFramework          0x14722556 GetPlugIn + 876822
4   com.adobe.InDesign.AppFramework          0x1471e8ff GetPlugIn + 861375
5   com.adobe.InDesign.AppFramework          0x1471f3c5 GetPlugIn + 864133
6   com.adobe.InDesign.AppFramework          0x1472098e GetPlugIn + 869710
7   com.adobe.InDesign.AppFramework          0x147209fa GetPlugIn + 869818
8   com.adobe.InDesign.AppFramework          0x14720a66 GetPlugIn + 869926
9   com.adobe.boost_threads.framework          0x01c6840d thread_proxy + 141
10 libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
11 libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 13:
0   libsystem_kernel.dylib                  0x9493abb2 __semwait_signal + 10
1   libsystem_c.dylib                       0x9b0eb7b9 nanosleep$UNIX2003 + 187
2   com.adobe.InDesign.Support for JavaScript          0x19798acb GetPlugIn + 317883
3   com.adobe.InDesign.Support for JavaScript          0x1977df79 GetPlugIn + 208489
4   com.adobe.InDesign.Support for JavaScript          0x19798e38 GetPlugIn + 318760
5   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
6   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 14:
0   libsystem_kernel.dylib                  0x9493aa9a __recvfrom + 10
1   libsystem_c.dylib                       0x9b0eb4a2 recv$UNIX2003 + 54
2   ServiceManager-Launcher.dylib           0x1e499733 Invoke + 47867
3   ServiceManager-Launcher.dylib           0x1e498846 Invoke + 44046
4   ServiceManager-Launcher.dylib           0x1e497988 Invoke + 40272
5   ServiceManager-Launcher.dylib           0x1e497a0f Invoke + 40407
6   ServiceManager-Launcher.dylib           0x1e492baf Invoke + 20343
7   ServiceManager-Launcher.dylib           0x1e492ea7 Invoke + 21103
8   ServiceManager-Launcher.dylib           0x1e493685 Invoke + 23117
9   ServiceManager-Launcher.dylib           0x1e4938f9 Invoke + 23745
10 ServiceManager-Launcher.dylib           0x1e4962a0 Invoke + 34408
11 ServiceManager-Launcher.dylib           0x1e4963fd Invoke + 34757
12 ServiceManager-Launcher.dylib           0x1e496c91 Invoke + 36953
13 ServiceManager-Launcher.dylib           0x1e496db2 Invoke + 37242
14 ServiceManager-Launcher.dylib           0x1e489656 Login + 461
15 ServiceManager-Launcher.dylib           0x1e48d09a Login + 15377
16 ServiceManager-Launcher.dylib           0x1e497165 Invoke + 38189
17 ServiceManager-Launcher.dylib           0x1e4992eb Invoke + 46771
18 libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
19 libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 15:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.adobe.ape.engine                    0x25ab804f APXGetHostAPI + 2633743
4   com.adobe.ape.engine                    0x2584962f APXGetHostAPI + 83439
5   com.adobe.ape.engine                    0x25ab813e APXGetHostAPI + 2633982
6   com.adobe.ape.engine                    0x25ab81a7 APXGetHostAPI + 2634087
7   com.adobe.ape.engine                    0x25ab82c6 APXGetHostAPI + 2634374
8   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
9   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 16:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.adobe.ape.engine                    0x25ab804f APXGetHostAPI + 2633743
4   com.adobe.ape.engine                    0x2584962f APXGetHostAPI + 83439
5   com.adobe.ape.engine                    0x25ab813e APXGetHostAPI + 2633982
6   com.adobe.ape.engine                    0x25ab81a7 APXGetHostAPI + 2634087
7   com.adobe.ape.engine                    0x25ab82c6 APXGetHostAPI + 2634374
8   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
9   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 17:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.adobe.ape.engine                    0x25ab804f APXGetHostAPI + 2633743
4   com.adobe.ape.engine                    0x2584962f APXGetHostAPI + 83439
5   com.adobe.ape.engine                    0x25ab813e APXGetHostAPI + 2633982
6   com.adobe.ape.engine                    0x25ab81a7 APXGetHostAPI + 2634087
7   com.adobe.ape.engine                    0x25ab82c6 APXGetHostAPI + 2634374
8   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
9   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 18:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.adobe.ape.engine                    0x25ab804f APXGetHostAPI + 2633743
4   com.adobe.ape.engine                    0x2584962f APXGetHostAPI + 83439
5   com.adobe.ape.engine                    0x25ab813e APXGetHostAPI + 2633982
6   com.adobe.ape.engine                    0x25ab81a7 APXGetHostAPI + 2634087
7   com.adobe.ape.engine                    0x25ab82c6 APXGetHostAPI + 2634374
8   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
9   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 19:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae78 _pthread_cond_wait + 914
2   libsystem_c.dylib                       0x9b13af7b pthread_cond_timedwait_relative_np + 47
3   com.adobe.ape.engine                    0x25ab8017 APXGetHostAPI + 2633687
4   com.adobe.ape.engine                    0x25ad120e APXGetHostAPI + 2736590
5   com.adobe.ape.engine                    0x25ab813e APXGetHostAPI + 2633982
6   com.adobe.ape.engine                    0x25ab81a7 APXGetHostAPI + 2634087
7   com.adobe.ape.engine                    0x25ab82c6 APXGetHostAPI + 2634374
8   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
9   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 20:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae78 _pthread_cond_wait + 914
2   libsystem_c.dylib                       0x9b13af7b pthread_cond_timedwait_relative_np + 47
3   com.adobe.ape.engine                    0x25ab8017 APXGetHostAPI + 2633687
4   com.adobe.ape.engine                    0x25c46168 APXGetHostAPI + 4264232
5   com.adobe.ape.engine                    0x25ab813e APXGetHostAPI + 2633982
6   com.adobe.ape.engine                    0x25ab81a7 APXGetHostAPI + 2634087
7   com.adobe.ape.engine                    0x25ab82c6 APXGetHostAPI + 2634374
8   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
9   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 21:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   MultiProcessor Support                  0x27f30eac boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 140
4   MultiProcessor Support                  0x27f14513 ThreadFunctor::operator()() + 99
5   MultiProcessor Support                  0x27f1425a boost::detail::thread_data<ThreadFunctor>::run() + 22
6   MultiProcessor Support                  0x27f30547 thread_proxy + 167
7   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
8   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 22:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   MultiProcessor Support                  0x27f30eac boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 140
4   MultiProcessor Support                  0x27f14513 ThreadFunctor::operator()() + 99
5   MultiProcessor Support                  0x27f1425a boost::detail::thread_data<ThreadFunctor>::run() + 22
6   MultiProcessor Support                  0x27f30547 thread_proxy + 167
7   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
8   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 23:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   MultiProcessor Support                  0x27f30eac boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 140
4   MultiProcessor Support                  0x27f14513 ThreadFunctor::operator()() + 99
5   MultiProcessor Support                  0x27f1425a boost::detail::thread_data<ThreadFunctor>::run() + 22
6   MultiProcessor Support                  0x27f30547 thread_proxy + 167
7   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
8   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 24:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   MultiProcessor Support                  0x27f30eac boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 140
4   MultiProcessor Support                  0x27f14513 ThreadFunctor::operator()() + 99
5   MultiProcessor Support                  0x27f1425a boost::detail::thread_data<ThreadFunctor>::run() + 22
6   MultiProcessor Support                  0x27f30547 thread_proxy + 167
7   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
8   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 25:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   MultiProcessor Support                  0x27f30eac boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 140
4   MultiProcessor Support                  0x27f14513 ThreadFunctor::operator()() + 99
5   MultiProcessor Support                  0x27f1425a boost::detail::thread_data<ThreadFunctor>::run() + 22
6   MultiProcessor Support                  0x27f30547 thread_proxy + 167
7   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
8   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 26:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   MultiProcessor Support                  0x27f30eac boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 140
4   MultiProcessor Support                  0x27f14513 ThreadFunctor::operator()() + 99
5   MultiProcessor Support                  0x27f1425a boost::detail::thread_data<ThreadFunctor>::run() + 22
6   MultiProcessor Support                  0x27f30547 thread_proxy + 167
7   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
8   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 27:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   MultiProcessor Support                  0x27f30eac boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 140
4   MultiProcessor Support                  0x27f14513 ThreadFunctor::operator()() + 99
5   MultiProcessor Support                  0x27f1425a boost::detail::thread_data<ThreadFunctor>::run() + 22
6   MultiProcessor Support                  0x27f30547 thread_proxy + 167
7   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
8   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 28:: com.apple.NSURLConnectionLoader
0   libsystem_kernel.dylib                  0x94938c22 mach_msg_trap + 10
1   libsystem_kernel.dylib                  0x949381f6 mach_msg + 70
2   com.apple.CoreFoundation                0x93e6d9da __CFRunLoopServiceMachPort + 170
3   com.apple.CoreFoundation                0x93e76b04 __CFRunLoopRun + 1428
4   com.apple.CoreFoundation                0x93e761dc CFRunLoopRunSpecific + 332
5   com.apple.CoreFoundation                0x93e76088 CFRunLoopRunInMode + 120
6   com.apple.Foundation                    0x94a5c0c4 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 378
7   com.apple.Foundation                    0x94a4fe25 -[NSThread main] + 45
8   com.apple.Foundation                    0x94a4fdd5 __NSThread__main__ + 1582
9   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
10 libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 29:: com.apple.CFSocket.private
0   libsystem_kernel.dylib                  0x9493ab42 __select + 10
1   com.apple.CoreFoundation                0x93ec4e15 __CFSocketManager + 1557
2   libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
3   libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 30:
0   libsystem_kernel.dylib                  0x9493a83e __psynch_cvwait + 10
1   libsystem_c.dylib                       0x9b13ae21 _pthread_cond_wait + 827
2   libsystem_c.dylib                       0x9b0eb42c pthread_cond_wait$UNIX2003 + 71
3   com.adobe.InDesign.AppFramework          0x14722556 GetPlugIn + 876822
4   com.adobe.InDesign.AppFramework          0x1471e97a GetPlugIn + 861498
5   com.adobe.InDesign.AppFramework          0x1471f3c5 GetPlugIn + 864133
6   com.adobe.InDesign.AppFramework          0x1472098e GetPlugIn + 869710
7   com.adobe.InDesign.AppFramework          0x147209fa GetPlugIn + 869818
8   com.adobe.InDesign.AppFramework          0x14720a66 GetPlugIn + 869926
9   com.adobe.boost_threads.framework          0x01c6840d thread_proxy + 141
10 libsystem_c.dylib                       0x9b136ed9 _pthread_start + 335
11 libsystem_c.dylib                       0x9b13a6de thread_start + 34
Thread 31:
0   libsystem_kernel.dylib                  0x9493b02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x9b138ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x9b13a6fe start_wqthread + 30
Thread 32:
0   libsystem_kernel.dylib                  0x9493b02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x9b138ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x9b13a6fe start_wqthread + 30
Thread 33:
0   libsystem_kernel.dylib                  0x9493b02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x9b138ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x9b13a6fe start_wqthread + 30
Thread 34:
0   libsystem_kernel.dylib                  0x9493b02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x9b138ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x9b13a6fe start_wqthread + 30
Thread 35:
0   libsystem_kernel.dylib                  0x9493b02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x9b138ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x9b13a6fe start_wqthread + 30
Thread 36:
0   libsystem_kernel.dylib                  0x9493b02e __workq_kernreturn + 10
1   libsystem_c.dylib                       0x9b138ccf _pthread_wqthread + 773
2   libsystem_c.dylib                       0x9b13a6fe start_wqthread + 30

I think exporting to IDML only works for some errors. I had an Indesign error 4 recently and it didn't work for that - in fact I had to recreate the whole document. There is a file recovery service though at the following url but unfortunately you have to pay a fee:
http://markzware.com/support/faq/recover-bad-file-service/
Alternatively, you could try resetting your Indesign preferences.
My knowledge is quite limited when it comes to reading the crash code that you posted - perhaps someone-else on the forums may be able to be of more help.

Lightroom 2 colour difference in lightroom vs. export and print

Hi,
I am currently using Lightroom 2 and Windows Vista, monitor profile is Dell's E248WFP Color profile.
The problem I have is that everything looks fine in lightroom, I was able to see the black backdrop with some defining detail on it. However, when I export the photo (export colour space: sRGB) and view it, the photo darkens, I could no longer see any detail in the black backdrop (I've tried othercolour space like the adobeRGB but results is the same). I understand that there could be difference using Windows viewer as someone has pointed out to me. I tried importing what I've just exported from lightroom back into lightroom and I could see all the original details.
So I am guessing it's just an issue with windows viewer not able to display all the colours intended. I than send the file to "Blacks photography" (photo developing store) for printing and the same issue exists, it's darker than what is displaying in lightroom. Could someone please point me to the right direction?
Thanks in advance for your help!
Gi

Hi,
Thanks for the advice, I bought a Spyder pro 3 thinking that might solve the problem but I think the problem is what is being exported? (not sure)
Photo looks good in LR but after exporting, open the file and looks different in windows photo gallery than what's in LR.
So I tried looking at the exported jpg in LR and it looks good in LR. I assume that's normal as people has mentioned that LR will display more colour and do it correctly. The problem for me than is printing. I send the photos to local photo processing stores and the colour is still off. Sorry for the ramble but here are some of my questions:
I assume it's completely ok that photos look different in LR and windows photo gallery (or even other viewer). As look as it looks ok in LR than it's fine?
Is the problem with a low quality monitor (Dell's E248WFP)?
I might not be calibrating it correctly? (will try again)
Thanks again!!
Gi

Help with exporting and printing

I only recently started to use FW and I am stuck and can't
find an answer. First whenever I go to print a item through FW it
is always to big for the paper. I know I can shrink it but wouldn't
that look different. Second I export it as a jpeg and import it
into word 03, fit it to the size of the page, but when I print it
it comes out blurry and hardly readable. does anyone know why it
does that and how to fix it? Please help.

On Wed, 27 Sep 2006 23:22:04 +0400, fallenanbu
<[email protected]> wrote:
> I only recently started to use FW and I am stuck and
can't find an
> answer.
> First whenever I go to print a item through FW it is
always to big for
> the
> paper. I know I can shrink it but wouldn't that look
different. Second I
> export
> it as a jpeg and import it into word 03, fit it to the
size of the page,
> but
> when I print it it comes out blurry and hardly readable.
does anyone
> know why
> it does that and how to fix it? Please help.
>
I guess your problem is too small resolution. Create youre
image at
resolution like 200 ppi. As long as I remember Word 2003
correctly reads
PNG resolution, so after creating and saving the image you
may try simply
importing the image saved in FW into Word.
Ilya Razmanov
http://photoshop.msk.ru -
Photoshop plug-in filters

CR 2008 paramteres, export and print windows language localization

Similar Messages

Maybe you are looking for