Serious Cert and hostname problem
Running Server 2012 with Exchange 2013 since 2012, all ok. SSL Cert ran out recently, bought new from Comodo. In the old UC Cert I had 4 names incleded: mail.domain.ch, autodiscover.domain.ch, hostname.domain.ch and the hostname alone. Comodo (and probably
other Certs) do no longer accept single hostnames in Certs so I omitted that. Now login to EMC is no longer possible and Outlook can no longer connect. EMS works but obviously with limited command set. Tried
Set-ClientAccessServer command. It is not recognized as are others. There are some commands working with "get-excommand" but not those needed to configure FQDN instead of hostname to access the Server. Any help is greatly appreciated.
Marcel
Dicicert test shows: Certificate does not match FQDN.
https://testconnectivity.microsoft.com/ Shows (unfortunately all in German):
Error testing Acrtive Sync
Fehler beim Testen der AutoErmittlung für Exchange ActiveSync (Error testing autodiscover for Active Sync)
Fehler beim Testen der AutoErmittlung (Error testing autodiscover) (same for the next 3 steps)
Der AutoErmittlungsdienst konnte mit keiner Methode erfolgreich kontaktiert werden (the autodiscover service could by no means be contacted)
Es wird versucht, DNS-MX-Einträge für Domäne 'snnet.ch' abzurufen.
Mindestens ein MX-Eintrag wurde erfolgreich aus DNS abgerufen.
Weitere Details
MX-Einträge Host snlemon.snnet.ch, Einstellung 10
Verstrichene Zeit: 135 ms.
Mail-Exchanger snlemon.snnet.ch wird getestet.
Dieser Mail-Exchanger wurde erfolgreich getestet.
(MX entry ok, SMTP mail exchange ok)
Es wird versucht, für die IP-Adresse 62.2.148.162 Reverse-DNS-Lookups auszuführen.
Die Microsoft-Verbindungsuntersuchung hat die IP-Adresse 62.2.148.162 erfolgreich über Reverse-DNS-Lookup aufgelöst.
Weitere Details
Die Microsoft-Verbindungsuntersuchung hat die IP-Adresse 62.2.148.162 als Host 62-2-148-162.static.cablecom.ch aufgelöst.
Verstrichene Zeit: 376 ms.
RBL-Test (Real-Time Black Hole List) wird ausgeführt
Ihre IP-Adresse wurde in keiner der ausgewählten Sperrlisten gefunden.
Weitere Details
Verstrichene Zeit: 9379 ms.
Testschritte
Sperrliste "SpamHaus Block List (SBL)" wird überprüft
Die Adresse befindet sich nicht in der Sperrliste.
Weitere Details
Die IP-Adresse 62.2.148.162 wurde nicht in RBL gefunden.
Verstrichene Zeit: 30 ms.
Sperrliste "SpamHaus Exploits Block List (XBL)" wird überprüft
Die Adresse befindet sich nicht in der Sperrliste.
Weitere Details
Die IP-Adresse 62.2.148.162 wurde nicht in RBL gefunden.
Verstrichene Zeit: 53 ms.
Sperrliste "SpamHaus Policy Block List (PBL)" wird überprüft
Die Adresse befindet sich nicht in der Sperrliste.
Weitere Details
Die IP-Adresse 62.2.148.162 wurde nicht in RBL gefunden.
Verstrichene Zeit: 186 ms.
Sperrliste "SpamCop Block List" wird überprüft
Die Adresse befindet sich nicht in der Sperrliste.
Weitere Details
Die IP-Adresse 62.2.148.162 wurde nicht in RBL gefunden.
Verstrichene Zeit: 39 ms.
Sperrliste "NJABL.ORG Block List" wird überprüft
Die Adresse befindet sich nicht in der Sperrliste.
Weitere Details
Die IP-Adresse 62.2.148.162 wurde nicht in RBL gefunden.
Verstrichene Zeit: 8717 ms.
Sperrliste "SORBS Block List" wird überprüft
Die Adresse befindet sich nicht in der Sperrliste.
Weitere Details
Die IP-Adresse 62.2.148.162 wurde nicht in RBL gefunden.
Verstrichene Zeit: 91 ms.
Sperrliste "MSRBL Combined Block List" wird überprüft
Die Adresse befindet sich nicht in der Sperrliste.
Weitere Details
Die IP-Adresse 62.2.148.162 wurde nicht in RBL gefunden.
Verstrichene Zeit: 53 ms.
Sperrliste "UCEPROTECT Level 1 Block List" wird überprüft
Die Adresse befindet sich nicht in der Sperrliste.
Weitere Details
Die IP-Adresse 62.2.148.162 wurde nicht in RBL gefunden.
Verstrichene Zeit: 206 ms.
Sender ID wird überprüft.
Fehler bei der Überprüfung der Sender ID
(error testing sender ID, other tests OK)
IMAP wird für Benutzer 'snnet\admin' auf Host 'snlemon.snnet.ch:993:SSL' getestet.
Fehler beim IMAP-Test.
Weitere Details
Verstrichene Zeit: 21023 ms.
Testschritte
Es wird versucht, den Hostnamen snlemon.snnet.ch im DNS aufzulösen.
Der Hostname wurde erfolgreich aufgelöst.
Weitere Details
Zurückgegebene IP-Adressen: 62.2.148.162, 2002:3e02:94a2::3e02:94a2
Verstrichene Zeit: 8 ms.
Es wird getestet, ob TCP-Port 993 auf Host snlemon.snnet.ch überwacht wird/geöffnet ist.
Der angegebene Port ist blockiert, wird nicht überwacht oder sendet nicht die erwartete Antwort
(error TCP port 993)
Command set-outlookprovider not recognized by EMS.
Would like to add that the old Cert, containing the hostname, is still valid and could probably be used but would need to get advice how to do it since EMC cannot be accessed. Thank you.
Similar Messages
-
Serious and Sudden Problem with Z10 NEED HELP PLEASE
I have a z10, one of the first that came out in Toronto (if it makes a
difference), a couple of hours ago I came across a serious and sudden
problem.
I was able to swipe left and right between pages of apps, even drop down
from the top, but I cannot open anything, not even make a call or settings
options.
Any time I try to, for a split second it looks like its about to load
something then nothing. (image slides to the right quickly and goes back on
every attempt)
So I first did a reset, same problem, then I did a battery pull (about 15 minutes) and problem presisted.
I tried through USB to do a backup on blackberry manager and perhaps do a
re-install of everything, however when I was prompted for the password of
my device on my PC it kept telling me it was an incorrect password (I use
this blackberry on my computer 4-7 days a week, twice a day sometimes for a
year and I have never miss typed my password nor have i changed it)
After trying everything to make sure the first letter maybe was upper/lower
case, even my other possible phone password, nothing worked..
On the 5th failed attempt my phone prompted me to type 'blackberry', which
i did, then i typed my password on my phone which i type in about 15 times
a day becuase I set my phone to a 5 minute lock and still said it was incorrect.... I am no on 9/10 attempts and lost
for options.
Please if anyone can give me any suggestions, or even how to backup my phone
and whipe it now, or I have an earlier backup form 4 months ago that I
wouldnt mind going back to in worst case scenario.
Thank you for your help in advance,
Solved!
Go to Solution.Sorry, no I haven't experienced that. It could be from an app you downloaded but that's just a guess. Wiping the device will tell us a lot. If the device still doesn't work you'll want to reload the OS using BB Link. if it still doesn't work after that then warranty support will be necessary through Rogers.
1. Please thank those who help you by clicking the "Like" button at the bottom of the post that helped you.
2. If your issue has been solved, please resolve it by marking the post "Solution?" which solved it for you! -
Serious M-Audio Profire 610 sync and dropout problem
After an, over a month, waiting for a solution to the problem from m-audio, I have to post the problem to the community:
I m using an early 2009 8-core MAC PRO with M-Audio Profire 610, using it for video editing with Final Cut Pro (and sound design with Pro Tools).
The problem is that since I've updated the machine to 10.6.7, I m experiencing VIDEO dropouts in Final Cut, the very first playback seconds of EVERY video track (on every codec) that I try to preview and at any point of it.
Also, occasionally, the audio-video sync is lost and I have to pause-play in order to gain the sync back on..
When I switch the audio output to Built in audio or Display audio, the dropout and sync problem disappears. When I switch back to Profire 610 the dropout starts again.
The video and audio settings and the tracks encoding are the same for at least 2 years now, since I m working ALLWAYS with my P2 panasonic DCVPROHD camera, with which I have shot and edit in my MAC PRO multiple videos, including a feature film..
I have tested the problem on two Macbook pros (early 2007) that I use for the shootings and the problem is there also !(when I plug the Profire 610)
The last think that I 've tried on my main unit, was:
-do a zero data format to my vertex 2 ssd boot drive,
-do a clean install of Snow Leopard (10.6.0)
-restore the system from a time machine backup (the os still remains 10.6.0)
-run 10.6.6 combo update
-uninstall the profire driver
-repair permissions
-install the profire driver (for 32 bit 10.6.6)
-repair permissions.
The problem's still here.
I m stuck with my projects here… Is there a solution out there?
Thank you very much for the attention
DiamantisSo, to be clear, it happens when the FirePro 610 in connected, and does not happen when it's diconnected?
That is obviously directly related to the FirePRo 610 having some hardware latency issues on an OS level. That's up to M-Audio to fix. There was never anything wrong with your Mac, there's something wrong with the M-Audio unit, obviously.
Do you have a FW hard drive plugged in? If so, will it work correctly without any other FW devices connected?
It could be defective.
http://forums.m-audio.com/showthread.php?10302-Firepro-610-on-Mac-OS-10.5.7&p=46 873 -
How to get ip and hostname in application server 10g
when i am using sys_context('USERENV','HOST') IN MY value based audit trigger it return ip address of application server.
i want to get client's ip address and hostname that connect to application server 10g.
Regards,
Muhammad TouseefCKPT wrote:
i want to get client's ip address and hostname that connect to application server 10g.you can find in listener.log file for all the client connections, or if any active sessions you can find from
select username,machine from v$session;LOL
You gave a totally correct answer. Unfortunately not relevant, though.
Now take a look at that answer in context of the question. The question is "given that the environment is 3 tier, and given that the client to the database is an application server, how do we get the information about the client to the application server - one tier further out?"
OP - this is a known problem with current application server configurations and applications. The only current way of providing that info is for the app server to capture and pass that info on. An easy way to pass it on, available to the app developer, is to use the DBMS_APPLICATION_INFO package.
Perhaps one day the WebLogic Server folk will see fit to make that transparent. ;-) -
Firewire 400 and 800 problem ? Need confirmation
OK, I have been running 2 external Lacie HD's over a USB hub into my MacBook Pro. A couple of weeks ago I decided that I needed more storage so purchased 2 Western Digital MyBook Pro's at 500GB.
I got these two specifically because I knew they supported Firewire 800 and wanted to take advantage of the high speed connection.
All is going well until yesterday.... Let me explain my set up. Firstly I am a DJ and use a Firewire Audiophile soundcard from M-Audio, this connects to the 400 port on my MacBook Pro, and the HD's connect to the 800... When I play music I get audio drop outs... I have looked through the forums and I am under the impression that both the 400 and 800 ports on my MacBook Pro run on the same connect, so is this the cause of the audio drop outs ?
I connect the 2 HD's via USB and have no problems, am I right in thinking that I have wasted good money on getting 2 HD's that I'm not going to be able to use the 800 port with ? When I run the audio through the internal soundcard I get no drop outs !
Also.... Just to annoy me even more I have a 20" cinema display so if I have use USB I decided to connect the two HD's to this and then to the MacBook Pro, now the problem here is when my MacBook Pro goes to sleep one of the HD's wakes up the MacBook Pro as it has been removed incorrectly ??? Do I now have a problem with one of my USB ports on the cinema screen also ????? I have put my iPod in the port and no problems ?
Does anyone know how I can solve these problems without having to spend even more money ?
And can someone confirm if the 400 and 800 ports are on the same connection, if so, whats the point ???
Thanks
- Neilneil,
I wouldn't do that right away.. USB audio interfaces are usually at the more consumer end of the market, I don't think it's the best way to go just to solve your problem.
did you read the part in my post about PCexpress cards that give you a totally new and independent FW800 bus? seriously, I think this is your best bet. these cards first came out when the original series of MBP didn't have FW800 on them (only 400) much to the consternation of video pros.. so 3rd party vendors made a card solution. as I said, they aren't expensive, I would have thought around or under $100 US. connect one of those to your MBP's express slot and your problem is solved. you'll have a powerful, dedicated FW channel just for those FW800 drives you bought. then, your m-audio interface will be fine. and even if you still want to get rid of it and get a better interface, you won't be forced to go to USB which generally means opting for a lower end of the market interface.
also one other thing.. I don't know what your actual audio i/o needs are. but if you only ever work with stereo out and stereo in, ie, you never need more than 2 physical outputs and 2 physical inputs, then you have other options. the MBP (and in fact all macs) have optical digital audio built in. you can buy a 2in 2out digital to analog/analog to digital converter and connect it to the opticals. then, you'll never need to worry about FW or USB bandwidth ever again, nor will you ever need to think about drivers or compatibility or updates either.
on my MBP I use logic pro. and on this system, I only ever need a stereo out to hear what I'm working on with good quality.. and when I record actual audio tracks, it's only ever one source at a time, like a mic input or an instrument. so I do not need an interface at all, I use the opticals and I love it. I bought a mindprint trio, not the USB one, but the one that uses optical i/o. it just connects to the same connectors on the MBP that you would connect headphones or a mic, but obviously uses the digital optical signal not analog audio. it sounds really very good. the trio itself is a very handy little box that conveniently lets you do a lot of things to work comfortable when recording. and I just use built-in sound, no drivers needed ever, which is very much a rare relief in the audio world, believe me.
anyway, hope this helps. and seriously check out a card for FW800, in my opinion it's the best solution to your problem no matter which way you go. -
On save as: Unexpected and unrecoverable problem has occurred. Photoshop will now exit. (Mac 10.7.3)
Hello,
We are working on Macinthosh intel - Mac Pro Intel Xeon september 2007, with MacOs 10.7.3.
After trying to install the beta version of Photoshop CS6, we got serious problems.
- The CS5 Photoshop and Acrobat 9 is not working anymore.
When we want to "save as…", both application will crash.
When we do "save as weboptimized", un error says that the file already exists.
We did not manage to install the CS6 Photoshop beta neither.
I tried EVERYTHING supposed to do in other forums and in the adobe forums, like:
- latest version of AdobeApplication Manager
- Adobe cleaner tool
- Adobe support advisor
- cleaning manually everything on the disk which containes CS6
- Reparing Autorisation
- Trying to reinstall CS5 (but without issue
- trash prefs
- deactivate and reactivate PHotoshop
and some others…
When trying to "save as" or save as weboptimized…", the following errors appears:
The operation could not be completed.
An unexpected and unrecoverable problem has occurred. Photoshop will now exit.
When trying to "save as weboptimized" the following error appears:
A file or directory already exists with the same name.
When exporting or "save as" in Acrobat:
Acrobat is blocked, everything in the application menu is turned gray but there is not open window.
I have to exit with "esc+Alt+Command"
All this problems occured after installation of Photoshop Beta CS6, which could not be completed because of some more errors causing a licence conflict with CS5.
We were also trying the Adobe support advisor, we got the following error massage:
Exit Code: 16
Please see specific errors and warnings below for troubleshooting. For example, ERROR: DW039 ...
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 1 error(s), 0 warning(s)
ERROR: DW039: Failed to load deployment File
AND
Exit Code: 7
Please see specific errors and warnings below for troubleshooting. For example, ERROR: DW013 ... WARNING: DW017 ...
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 1 error(s), 1 warning(s)
WARNING: DW017: PayloadPolicyNode.SetAction: IN payload {463D65D7-CD43-4FAC-A6C7-7D24CB5DB93B} Adobe Media Player 1.8.0.0 is required by {7DFEBBA4-81E1-425B-BBAA-06E9E5BBD97E} Adobe Photoshop CS5 Core 12.0.0.0 but isn't free. Reason: Language not supported
ERROR: DW013: Unable to locate volume for path. Please verify that path [UserDocuments] is a valid path. Please ensure that if any intermediate directories exist, they are valid directories and not files/symlinks
Here is the content of the Crash Report:
Process:
Adobe Photoshop CS5 [1403]
Path:
/Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/MacOS/Adobe Photoshop CS5
Identifier:
com.adobe.Photoshop
Version:
12.0.4 (12.0.4x20110407.r.1265] [12.0.4)
Code Type:
X86-64 (Native)
Parent Process: launchd [299]
Date/Time:
2012-04-17 10:10:50.329 +0200
OS Version:
Mac OS X 10.7.3 (11D50)
Report Version: 9
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
objc[1403]: garbage collection is OFF
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib
0x00007fff86d78ce2 __pthread_kill + 10
1 libsystem_c.dylib
0x00007fff90a0c7d2 pthread_kill + 95
2 libsystem_c.dylib
0x00007fff909fda7a abort + 143
3 com.adobe.Photoshop
0x00000001002369eb 0x100000000 + 2320875
4 libc++abi.dylib
0x00007fff897d8001 safe_handler_caller(void (*)()) + 11
5 libc++abi.dylib
0x00007fff897d7ff6 __cxxabiv1::__terminate(void (*)()) + 9
6 libc++abi.dylib
0x00007fff897d8346 __cxa_call_terminate + 59
7 libc++abi.dylib
0x00007fff897d87c3 __gxx_personality_v0 + 207
8 libunwind.dylib
0x00007fff8a21f4c6 unwind_phase2 + 160
9 libunwind.dylib
0x00007fff8a21e96e _Unwind_RaiseException + 218
10 com.apple.FinderKit
0x00007fff8b3a2b64 -[FI_TColumnViewController closeTarget] + 243
11 com.apple.FinderKit
0x00007fff8b3de1d0 -[FIFinderViewGutsController destroyBrowserView] + 238
12 com.apple.FinderKit
0x00007fff8b3dbdcc -[FIFinderViewGutsController prepareToHide] + 369
13 com.apple.FinderKit
0x00007fff8b3dbee4 -[FIFinderViewGutsController setExpanded:] + 44
14 com.apple.FinderKit
0x00007fff8b3e40ab -[FIFinderView viewWillMoveToWindow:] + 265
15 com.apple.AppKit
0x00007fff8c5b9e31 -[NSView _setWindow:] + 238
16 com.apple.AppKit
0x00007fff8c4e6c08 __NSViewRecursionHelper + 25
17 com.apple.CoreFoundation
0x00007fff8fbecea4 CFArrayApplyFunction + 68
18 com.apple.AppKit
0x00007fff8c5ba766 -[NSView _setWindow:] + 2595
19 com.apple.AppKit
0x00007fff8c4e6c08 __NSViewRecursionHelper + 25
20 com.apple.CoreFoundation
0x00007fff8fbecea4 CFArrayApplyFunction + 68
21 com.apple.AppKit
0x00007fff8c5ba766 -[NSView _setWindow:] + 2595
22 com.apple.AppKit
0x00007fff8c4e6c08 __NSViewRecursionHelper + 25
23 com.apple.CoreFoundation
0x00007fff8fbecea4 CFArrayApplyFunction + 68
24 com.apple.AppKit
0x00007fff8c5ba766 -[NSView _setWindow:] + 2595
25 com.apple.AppKit
0x00007fff8c4e6c08 __NSViewRecursionHelper + 25
26 com.apple.CoreFoundation
0x00007fff8fbecea4 CFArrayApplyFunction + 68
27 com.apple.AppKit
0x00007fff8c5ba766 -[NSView _setWindow:] + 2595
28 com.apple.AppKit
0x00007fff8c6dfb57 -[NSWindow dealloc] + 1262
29 com.apple.AppKit
0x00007fff8c9e34f4 -[NSSavePanel dealloc] + 612
30 com.apple.AppKit
0x00007fff8c4e0145 -[NSWindow release] + 535
31 libobjc.A.dylib
0x00007fff897ed03c (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 434
32 com.apple.CoreFoundation
0x00007fff8fbecb05 _CFAutoreleasePoolPop + 37
33 com.apple.Foundation
0x00007fff8423a51d -[NSAutoreleasePool release] + 154
34 com.adobe.Photoshop
0x00000001012f2d2e AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16869522
35 com.adobe.Photoshop
0x00000001000824f8 0x100000000 + 533752
36 com.adobe.Photoshop
0x0000000100c3243c AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 9789344
37 com.adobe.Photoshop
0x0000000100080e25 0x100000000 + 527909
38 com.adobe.Photoshop
0x0000000100c327e2 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 9790278
39 com.adobe.Photoshop
0x00000001004ca733 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 2024087
40 com.adobe.Photoshop
0x0000000100074b6f 0x100000000 + 478063
41 com.adobe.Photoshop
0x00000001000711ba 0x100000000 + 463290
42 com.adobe.Photoshop
0x00000001000665d3 0x100000000 + 419283
43 com.adobe.Photoshop
0x0000000100066696 0x100000000 + 419478
44 com.adobe.Photoshop
0x00000001012e1ef4 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16800344
45 com.apple.AppKit
0x00007fff8c4a31f2 -[NSApplication run] + 555
46 com.adobe.Photoshop
0x00000001012e04a4 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16793608
47 com.adobe.Photoshop
0x00000001012e0f01 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16796261
48 com.adobe.Photoshop
0x00000001000682e6 0x100000000 + 426726
49 com.adobe.Photoshop
0x00000001002371f1 0x100000000 + 2322929
50 com.adobe.Photoshop
0x0000000100237281 0x100000000 + 2323073
51 com.adobe.Photoshop
0x00000001000022f4 0x100000000 + 8948
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib
0x00007fff86d797e6 kevent + 10
1 libdispatch.dylib
0x00007fff84b045be _dispatch_mgr_invoke + 923
2 libdispatch.dylib
0x00007fff84b0314e _dispatch_mgr_thread + 54
Thread 2:
0 libsystem_kernel.dylib
0x00007fff86d79192 __workq_kernreturn + 10
1 libsystem_c.dylib
0x00007fff90a0c594 _pthread_wqthread + 758
2 libsystem_c.dylib
0x00007fff90a0db85 start_wqthread + 13
Thread 3:
0 libsystem_kernel.dylib
0x00007fff86d79192 __workq_kernreturn + 10
1 libsystem_c.dylib
0x00007fff90a0c594 _pthread_wqthread + 758
2 libsystem_c.dylib
0x00007fff90a0db85 start_wqthread + 13
Thread 4:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.adobe.amt.services
0x0000000108723c53 AMTConditionLock::LockWhenCondition(int) + 37
3 com.adobe.amt.services
0x000000010871ccce _AMTThreadedPCDService::PCDThreadWorker(_AMTThreadedPCDService*) + 92
4 com.adobe.amt.services
0x0000000108723cbe AMTThread::Worker(void*) + 28
5 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
6 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 5:
0 libsystem_kernel.dylib
0x00007fff86d79192 __workq_kernreturn + 10
1 libsystem_c.dylib
0x00007fff90a0c594 _pthread_wqthread + 758
2 libsystem_c.dylib
0x00007fff90a0db85 start_wqthread + 13
Thread 6:
0 libsystem_kernel.dylib
0x00007fff86d776ce semaphore_timedwait_trap + 10
1 com.apple.CoreServices.CarbonCore
0x00007fff8761e3be MPWaitOnSemaphore + 77
2 MultiProcessor Support
0x0000000110a00b93 ThreadFunction(void*) + 69
3 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
4 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
5 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 7:
0 libsystem_kernel.dylib
0x00007fff86d776ce semaphore_timedwait_trap + 10
1 com.apple.CoreServices.CarbonCore
0x00007fff8761e3be MPWaitOnSemaphore + 77
2 MultiProcessor Support
0x0000000110a00b93 ThreadFunction(void*) + 69
3 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
4 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
5 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 8:
0 libsystem_kernel.dylib
0x00007fff86d776ce semaphore_timedwait_trap + 10
1 com.apple.CoreServices.CarbonCore
0x00007fff8761e3be MPWaitOnSemaphore + 77
2 MultiProcessor Support
0x0000000110a00b93 ThreadFunction(void*) + 69
3 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
4 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
5 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 9:
0 libsystem_kernel.dylib
0x00007fff86d776ce semaphore_timedwait_trap + 10
1 com.apple.CoreServices.CarbonCore
0x00007fff8761e3be MPWaitOnSemaphore + 77
2 MultiProcessor Support
0x0000000110a00b93 ThreadFunction(void*) + 69
3 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
4 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
5 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 10:
0 libsystem_kernel.dylib
0x00007fff86d776ce semaphore_timedwait_trap + 10
1 com.apple.CoreServices.CarbonCore
0x00007fff8761e3be MPWaitOnSemaphore + 77
2 MultiProcessor Support
0x0000000110a00b93 ThreadFunction(void*) + 69
3 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
4 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
5 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 11:
0 libsystem_kernel.dylib
0x00007fff86d776ce semaphore_timedwait_trap + 10
1 com.apple.CoreServices.CarbonCore
0x00007fff8761e3be MPWaitOnSemaphore + 77
2 MultiProcessor Support
0x0000000110a00b93 ThreadFunction(void*) + 69
3 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
4 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
5 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 12:
0 libsystem_kernel.dylib
0x00007fff86d776ce semaphore_timedwait_trap + 10
1 com.apple.CoreServices.CarbonCore
0x00007fff8761e3be MPWaitOnSemaphore + 77
2 MultiProcessor Support
0x0000000110a00b93 ThreadFunction(void*) + 69
3 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
4 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
5 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 13:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore
0x00007fff87646bae TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore
0x00007fff875d928a TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore
0x00007fff8761dfd1 MPWaitOnQueue + 181
5 AdobeACE
0x000000010598b18d 0x105951000 + 237965
6 AdobeACE
0x000000010598ab3a 0x105951000 + 236346
7 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
8 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
9 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 14:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore
0x00007fff87646bae TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore
0x00007fff875d928a TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore
0x00007fff8761dfd1 MPWaitOnQueue + 181
5 AdobeACE
0x000000010598b18d 0x105951000 + 237965
6 AdobeACE
0x000000010598ab3a 0x105951000 + 236346
7 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
8 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
9 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 15:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore
0x00007fff87646bae TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore
0x00007fff875d928a TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore
0x00007fff8761dfd1 MPWaitOnQueue + 181
5 AdobeACE
0x000000010598b18d 0x105951000 + 237965
6 AdobeACE
0x000000010598ab3a 0x105951000 + 236346
7 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
8 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
9 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 16:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore
0x00007fff87646bae TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore
0x00007fff875d928a TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore
0x00007fff8761dfd1 MPWaitOnQueue + 181
5 AdobeACE
0x000000010598b18d 0x105951000 + 237965
6 AdobeACE
0x000000010598ab3a 0x105951000 + 236346
7 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
8 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
9 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 17:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore
0x00007fff87646bae TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore
0x00007fff875d928a TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore
0x00007fff8761dfd1 MPWaitOnQueue + 181
5 AdobeACE
0x000000010598b18d 0x105951000 + 237965
6 AdobeACE
0x000000010598ab3a 0x105951000 + 236346
7 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
8 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
9 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 18:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore
0x00007fff87646bae TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore
0x00007fff875d928a TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore
0x00007fff8761dfd1 MPWaitOnQueue + 181
5 AdobeACE
0x000000010598b18d 0x105951000 + 237965
6 AdobeACE
0x000000010598ab3a 0x105951000 + 236346
7 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
8 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
9 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 19:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore
0x00007fff87646bae TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore
0x00007fff875d928a TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore
0x00007fff8761dfd1 MPWaitOnQueue + 181
5 AdobeACE
0x000000010598b18d 0x105951000 + 237965
6 AdobeACE
0x000000010598ab3a 0x105951000 + 236346
7 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
8 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
9 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 20:
0 libsystem_kernel.dylib
0x00007fff86d78e42 __semwait_signal + 10
1 libsystem_c.dylib
0x00007fff909c0dea nanosleep + 164
2 com.adobe.PSAutomate
0x00000001166dbe4b ScObjects::Thread::sleep(unsigned int) + 59
3 com.adobe.PSAutomate
0x00000001166bdd83 ScObjects::BridgeTalkThread::run() + 163
4 com.adobe.PSAutomate
0x00000001166dbf46 ScObjects::Thread::go(void*) + 166
5 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
6 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 21:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.adobe.adobeswfl
0x000000012dbb289d APXGetHostAPI + 2465805
3 com.adobe.adobeswfl
0x000000012d96b5e9 APXGetHostAPI + 77145
4 com.adobe.adobeswfl
0x000000012dbb29b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl
0x000000012dbb2d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl
0x000000012dbb2e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
8 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 22:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.adobe.adobeswfl
0x000000012dbb289d APXGetHostAPI + 2465805
3 com.adobe.adobeswfl
0x000000012d96b5e9 APXGetHostAPI + 77145
4 com.adobe.adobeswfl
0x000000012dbb29b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl
0x000000012dbb2d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl
0x000000012dbb2e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
8 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 23:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.adobe.adobeswfl
0x000000012dbb289d APXGetHostAPI + 2465805
3 com.adobe.adobeswfl
0x000000012d96b5e9 APXGetHostAPI + 77145
4 com.adobe.adobeswfl
0x000000012dbb29b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl
0x000000012dbb2d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl
0x000000012dbb2e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
8 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 24:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.adobe.adobeswfl
0x000000012dbb289d APXGetHostAPI + 2465805
3 com.adobe.adobeswfl
0x000000012d96b5e9 APXGetHostAPI + 77145
4 com.adobe.adobeswfl
0x000000012dbb29b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl
0x000000012dbb2d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl
0x000000012dbb2e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
8 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 25:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.adobe.adobeswfl
0x000000012dbb289d APXGetHostAPI + 2465805
3 com.adobe.adobeswfl
0x000000012d96b5e9 APXGetHostAPI + 77145
4 com.adobe.adobeswfl
0x000000012dbb29b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl
0x000000012dbb2d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl
0x000000012dbb2e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
8 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 26:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.adobe.adobeswfl
0x000000012dbb289d APXGetHostAPI + 2465805
3 com.adobe.adobeswfl
0x000000012d96b5e9 APXGetHostAPI + 77145
4 com.adobe.adobeswfl
0x000000012dbb29b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl
0x000000012dbb2d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl
0x000000012dbb2e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
8 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 27:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.adobe.adobeswfl
0x000000012dbb289d APXGetHostAPI + 2465805
3 com.adobe.adobeswfl
0x000000012d96b5e9 APXGetHostAPI + 77145
4 com.adobe.adobeswfl
0x000000012dbb29b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl
0x000000012dbb2d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl
0x000000012dbb2e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
8 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 28:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.adobe.adobeswfl
0x000000012dbb289d APXGetHostAPI + 2465805
3 com.adobe.adobeswfl
0x000000012d96b5e9 APXGetHostAPI + 77145
4 com.adobe.adobeswfl
0x000000012dbb29b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl
0x000000012dbb2d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl
0x000000012dbb2e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
8 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 29:
0 libsystem_kernel.dylib
0x00007fff86d7767a mach_msg_trap + 10
1 libsystem_kernel.dylib
0x00007fff86d76d71 mach_msg + 73
2 com.apple.CoreFoundation
0x00007fff8fbeb6fc __CFRunLoopServiceMachPort + 188
3 com.apple.CoreFoundation
0x00007fff8fbf3e64 __CFRunLoopRun + 1204
4 com.apple.CoreFoundation
0x00007fff8fbf3676 CFRunLoopRunSpecific + 230
5 com.apple.CoreMediaIO
0x00007fff90148541 CMIO::DAL::RunLoop::OwnThread(void*) + 159
6 com.apple.CoreMediaIO
0x00007fff9013e6b2 CAPThread::Entry(CAPThread*) + 98
7 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
8 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 30:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e2a6 _pthread_cond_wait + 890
2 com.adobe.adobeswfl
0x000000012dbb2869 APXGetHostAPI + 2465753
3 com.adobe.adobeswfl
0x000000012dbcf0ec APXGetHostAPI + 2582620
4 com.adobe.adobeswfl
0x000000012dbb29b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl
0x000000012dbb2d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl
0x000000012dbb2e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
8 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 31:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e2a6 _pthread_cond_wait + 890
2 com.adobe.adobeswfl
0x000000012dbb2869 APXGetHostAPI + 2465753
3 com.adobe.adobeswfl
0x000000012dd4ce6f APXGetHostAPI + 4146655
4 com.adobe.adobeswfl
0x000000012dbb29b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl
0x000000012dbb2d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl
0x000000012dbb2e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
8 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 32:
0 libsystem_kernel.dylib
0x00007fff86d78d7a __recvfrom + 10
1 ServiceManager-Launcher.dylib
0x0000000119885982 Invoke + 54020
2 ServiceManager-Launcher.dylib
0x0000000119884adf Invoke + 50273
3 ServiceManager-Launcher.dylib
0x0000000119883b26 Invoke + 46248
4 ServiceManager-Launcher.dylib
0x0000000119883b81 Invoke + 46339
5 ServiceManager-Launcher.dylib
0x0000000119883c02 Invoke + 46468
6 ServiceManager-Launcher.dylib
0x000000011987e30d Invoke + 23695
7 ServiceManager-Launcher.dylib
0x000000011987e4a6 Invoke + 24104
8 ServiceManager-Launcher.dylib
0x000000011987ef2f Invoke + 26801
9 ServiceManager-Launcher.dylib
0x000000011987f01d Invoke + 27039
10 ServiceManager-Launcher.dylib
0x000000011988231f Invoke + 40097
11 ServiceManager-Launcher.dylib
0x00000001198825c5 Invoke + 40775
12 ServiceManager-Launcher.dylib
0x0000000119882b84 Invoke + 42246
13 ServiceManager-Launcher.dylib
0x0000000119882d71 Invoke + 42739
14 ServiceManager-Launcher.dylib
0x0000000119874daf Login + 1773
15 ServiceManager-Launcher.dylib
0x0000000119876295 Login + 7123
16 ServiceManager-Launcher.dylib
0x00000001198832a8 Invoke + 44074
17 ServiceManager-Launcher.dylib
0x00000001198856c1 Invoke + 53315
18 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
19 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 33:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e2a6 _pthread_cond_wait + 890
2 com.adobe.adobeswfl
0x000000012dbb2869 APXGetHostAPI + 2465753
3 com.adobe.adobeswfl
0x000000012dbcf0ec APXGetHostAPI + 2582620
4 com.adobe.adobeswfl
0x000000012dbb29b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl
0x000000012dbb2d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl
0x000000012dbb2e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
8 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 34:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e2a6 _pthread_cond_wait + 890
2 com.adobe.adobeswfl
0x000000012dbb2869 APXGetHostAPI + 2465753
3 com.adobe.adobeswfl
0x000000012dd4ce6f APXGetHostAPI + 4146655
4 com.adobe.adobeswfl
0x000000012dbb29b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl
0x000000012dbb2d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl
0x000000012dbb2e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
8 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 35:
0 libsystem_kernel.dylib
0x00007fff86d776b6 semaphore_wait_trap + 10
1 com.adobe.CameraRaw
0x00000001279ec791 EntryFM + 2523937
2 com.adobe.CameraRaw
0x0000000127a1eaa3 EntryFM + 2729523
3 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
4 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 36:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore
0x00007fff87646bae TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore
0x00007fff875d928a TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore
0x00007fff8761dfd1 MPWaitOnQueue + 181
5 com.adobe.CameraRaw
0x00000001276e86c9 0x12749b000 + 2414281
6 com.adobe.CameraRaw
0x00000001276e7920 0x12749b000 + 2410784
7 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
8 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
9 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 37:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore
0x00007fff87646bae TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore
0x00007fff875d928a TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore
0x00007fff8761dfd1 MPWaitOnQueue + 181
5 com.adobe.CameraRaw
0x00000001276e86c9 0x12749b000 + 2414281
6 com.adobe.CameraRaw
0x00000001276e7920 0x12749b000 + 2410784
7 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
8 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
9 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 38:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore
0x00007fff87646bae TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore
0x00007fff875d928a TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore
0x00007fff8761dfd1 MPWaitOnQueue + 181
5 com.adobe.CameraRaw
0x00000001276e86c9 0x12749b000 + 2414281
6 com.adobe.CameraRaw
0x00000001276e7920 0x12749b000 + 2410784
7 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
8 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
9 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13
Thread 39:
0 libsystem_kernel.dylib
0x00007fff86d78bca __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff90a0e274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore
0x00007fff87646bae TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore
0x00007fff875d928a TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore
0x00007fff8761dfd1 MPWaitOnQueue + 181
5 com.adobe.CameraRaw
0x00000001276e86c9 0x12749b000 + 2414281
6 com.adobe.CameraRaw
0x00000001276e7920 0x12749b000 + 2410784
7 com.apple.CoreServices.CarbonCore
0x00007fff8761ee36 PrivateMPEntryPoint + 58
8 libsystem_c.dylib
0x00007fff90a0a8bf _pthread_start + 335
9 libsystem_c.dylib
0x00007fff90a0db75 thread_start + 13Hi again,
We found the solution. I trie to give some details, if some other folks have a similar problem, perhaps they can find their solution with everything discussed in this topic.
All this was not working, after trying it several times:
Disk Utility> Repair Disk & Repair Permissions
Cocktail OSX (clear all caches)
Reboot and test
delete all printers
then look for a CS6 cleaner like http://www.adobe.com/support/contact/cscleanertool.html
rebuild diskstructure and filestructure with several utilities like Techtool, Onyx.
We could not uninstall the complete Photoshop cs5 only, because in case of uninstalling the whole Mastercollection, this is much to much work to reinstall all of the extension from Dreamweaver which have to be activated and installed one by one.
What has been working is:
TRY a New User Account (to rule out User preference/settings) !!!
So this gave us un idea:
Compare the library of both USER-ACCOUNTS : "ALICE" and the new one we called "TEST".
Then we RENAMED the following folders in the /USER/LIBRARY: "Caches", "Recent Servers", "Saved Application State" and crated a new folder with the same name (we deleted it after, in case there will be some problems to restore the old ones)
We put all the INVISIBLE FILES and FOLDERS present in the USER folder which names are beginning with a .dot, like .filename (e.g.: ".adobe", ".bash_history", ".BridgeCache", etc.) into another folder which we are going to delete later on.
Finally we deleted all files "suspected" not to be there in the ALICE user account, in comparision to the TEST USER ACCOUNT.
And "miracle": Everything is working again, after 2 days of searching…
Thanks to everyone of you.
Best regards,
Alice -
Hi
I have a problem and i can't seem to find anything relevant when i am looking around and wondering if someone has had the same problem or if its a bug.
I have a self signed cert and it works most of the time but sometimes cherokee stops responding on HTTPS but still works with HTTP.
I get alot of error messages looking like:
cryptor_libssl.c:343: ERROR: Init OpenSSL: unknown
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:343: ERROR: Init OpenSSL: unknown
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:343: ERROR: Init OpenSSL: unknown
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
cryptor_libssl.c:395: ERROR: SSL_write (1723390601, ..) -> err=-1 'error:00000005:lib(0):func(0):DH lib'
So i guess something is wrong with that file... ive looked in their bug report but no one reported anything about ssl, anyone got any idea?I would open a bug in their bugtracker if I were in your shoes.
Last edited by cactus (2009-01-17 00:24:52) -
Titler has serious error and shuts down program
I have been using the titler in Premier CS3 and every time I try to make a font change the program says that there is a serious error and must shut down the program. I have never lost any information since the program has been able to recover from the error and save the data. It is a pain since I can't change the font. Does anyone have any ideas how to remedy this.
I have looked on the Adobe site for answers but the site is a nightmare of never ending loops when trying to report a problem.I have not heard of any nVidia drivers causing problems with fonts, though there were several driver versions, about a year ago, where some gamer-only functions did not work in Adobe programs.
Now, with Titler, this ARTICLE might be helpful.
Good luck,
Hunt -
An unexpected and unrecoverable problem
An unexpected and unrecoverable problem has occurred because of a program error. Photoshop will now exit.
How do I fix this problem?
I have recently upgraded my OS on my iMac and now I can't get into Photoshop Elements 2.0. what do I need to do?First, it means that you posted in the Photoshop forum by mistake, and aren't likely to get answers about Elements issues.
So I'm moving your post to the Elements forum.
But the error message means that something is seriously wrong with the OS or the Photoshop preferences.
Most likely it is a problem with your upgraded OS that (old) Elements 2 cannot work with. -
ACE SSL - Modifying certs and keys
I'm having a problem updating the certs and keys I have in my ssl-proxy service.
My cert is about to expire and I've purchased a new cert. I've uploaded the new cert and key, but I still see the old cert when I go to the VIP with my browser. I thought that by deleting the proxy-service and re-adding I could get the ACE to recognize that it's got new certs but that didn't seem to work.
Is there a trick to make the ACE see the new certs? Does it cache the certs instead of reading them from flash? What's going on here.
Thanks!I changed my certs hot while the application was still running worked like a charm.
What i did was.
- import the new certificate into the crypto store (pkcs12)
- prepare a textfile with the necessary commands
no key old
key new
no cert old
cert new
- paste the commands into the running config.
I had several Customers and Application Admins test the App. while i was changing certs. They didn't even notice something happened. After approx. 60 seconds all new connections were using the new cert old connections were using the old cert. No trouble at all.
And yes the ACE caches the certs if i am not mistaken.
If you want to make sure that it works just create a test context or try it on a test farm first. That's what i did prior to changing the certs and the config on the production enviroment.
Hope it helps.
Roble -
Error: this application, or a library it uses, has passed an invalid numeric value (NaN, or not-a-number) to CoreGraphics API. This is a serious error and contributes to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
This console log is a note to the developers of whatever application you are using. You can safely ignore it.
-
Audio (and other) problems noted with Keynote version 4.0.1
Since installing Keynote 4 and the 4.0.1 update, I have noted the following situations and/or problems:
1) When doing a "save-as" the filename is appended with the suffix ".key" but when I subsequently "save" this file, the suffix disappears. The file seems to open and operate OK nonetheless, but this puzzles and somewhat concerns me that someday Keynote may not recognize the file. This happens whenever I "save" a slideshow after I have made any changes to it.
2) When playing back a "soundtrack," the audio "glitches" frequently at slide transitions: this occurs repeatedly on my G5 desktop system but not on my MacBook Pro-17. The "glitches" always seem to occur at the same places in the track - which, of course, is also at the same slide transitions. (This problem has spawned several similar questions and threads in this forum.)
3) Related to #2 above, the "glitches" also interrupt or corrupt the "recording" of that soundtrack, so that the synchronization is off when the slideshow is played back.
4) If I want to have an audio track play under a series of slides, the only way I have found to accomplish this is to create a separate slideshow with the audio track running as a "soundtrack" and "record" the Builds and Transitions in sync with the audio. If I want to incorporate several of these shows together, I can create a "master" slideshow and Hyperlink each segment to the next. HOWEVER...
5) When I "record" a "soundtrack" and "synchronize" the Builds and Transitions within the slideshow, everything plays back properly in sync ONLY when the slideshow is played as a stand-alone presentation (i.e. a cold start from the desktop). If I initiate playback of the slideshow via a Hyperlink from another presentation, the soundtrack plays but NONE of the synchronization works at all.
6) The only way I have found to have an audio track "fade-in" or "fade-out" is to use off-line editing software to record these fades prior to importing the tracks into Keynote. The "Start Audio" Build function is simply a hard "cut" in, and the end of the track is a hard "cut" out.
These problems are consistent and repeatable facts. Whether they are "bugs" in the software or "design shortcomings" is uncertain. Nonethtless ...
At the risk of offending the moderators of this forum, I feel compelled to comment that these problems render the audio operations of Keynote less than satisfactory and should be addressed as soon as possible with another update to this visually stunning but audio-challenged application.Well Ron S, I re-confirmed why I prefer not to look to tech support for support.
It seems to me that support's main function is to deflect any critical comments and push the blame back to the user.
Frankly, I have better things to do with my time and money than try to help a multi-billion dollar enterprise learn about itself.
So, for the benefit of you and the nearly 400 who have followed this thread, I offer you my latest and probably last attempt to have Apple acknowledge in some small way that "Houston, we have a problem".
I expect this reply will result in this thread being yanked as well, since I'm expressing negative thoughts about Apple's product and wishing they would do better, which is a non-technical gasp of utter frustration and disappointment. Note that "product" is singular, defining Keynote. My other Apple products serve me loyally and superbly, which is why my huge disappointment with Keynote.
So here is my correspondence with Tech Support. I've removed names except mine.
I think it speaks for itself. They have notes from my conversations with them that I have current Apple computers, including a MacBookPro, not an old PowerBook, nevertheless, they have told me that the problem is mine because the fabulous hyper-performing Keynote software is choking my poor old machine (paraphrased muchly).:
Hi (support),
That's disappointing news, especially since this test was done on 3 machines: an old G4 400, a 2.0G Dual G5 and an Intel core duo MacBookPro which yielded identical results.
It is not a hardware issue.
I do not accept a brush-off that it is my hardware that is causing Keynote to be problematic.
I will assume that Apple is not interested in addressing these issues in public and that Keynote is substandard software that is in need of re-authoring.
Sorry to be so blunt, but Apple has set this tone with Keynote, and used its considerable reputation as a leading a/v technology innovator to imply that Keynote will deliver the excellence we Mac users have come to expect.
I have been a loyal mac user since the SE series and have enjoyed success with the machines and software offered by Apple, and depend on them for my livelihood. I'm currently using FC Studio6 and know that Apple is capable of maintaining its high standards.
However, Keynote fails to do that, instead behaving like a product that was invented in a teenager's basement and is in beta. I realize that it's not designed as a FCP level product, but it fails at the basic tasks that you advertise it will complete.
A version 4 product should work as advertised. Keynote certainly does not.
I'm deeply saddened that Apple seems to have become an iPod entertainment company, interested mainly in profits from entertainment rather than serious useful technology.
On 2007-Oct-19, at 10:14 AM, (tech support) wrote:
Hello Sir,
Unfortunately, this does look like it's mostly a case of some of the new Keynote features slowing down the performance on the PowerBook.
At this point, there isn't much else we can do in the way of troubleshooting.
If you are not satisfied with the performance on the PowerBook, using the previous version of Keynote is probably his best option at this point.
We will continue to research this issue, but at this point it's unlikely I'll be able to find additional suggestions for improving performance, as it looks like it is is reproducible and limited to older models.
On Oct 16, 2007, at 11:27 PM, Ron Tucker wrote:
Hi (support),
Thanks for your recent followup calls. I'm directing a video shoot so am a bit preoccupied.
Here are the tests I mentioned.
These are as simple as it gets, and I think highlights the synchronization problem with Keynote.
Test 1 is straightforward, and demonstrates that a single unedited recorded audio track will maintain mouse click synchronization.
Test 2 is the same file, but with audio modifications applied to each slide in succession.
This demonstrates a dramatic synchronization slippage.
The visuals occur before the click (and audio) markers. Keynote seems to be create delay in audio at each "record and replace" point. This accumulates as the audio is revised in successive slides.
These tests demonstrate that there is a fundamental flaw in how Keynote handles audio in its most basic application.
This does not address the slim toolset available, such as lack of insert capability and other basic audio tools, which is a separate design issue, and I suppose subject to "request for enhancement" feedback.
I've reluctantly abandoned Keynote for my project work at present until these basic issues are addressed and it can be demonstrated that Keynote can successfully execute its feature set.
<TuckerKeynoteTest.zip>
Message was edited by: Ron Tucker1 -
MSI Z87 MPower Max - Bad board? Failed SATA and B2 problems????
So here's the thing, been having problems with my system, I have a SSD as the boot drive and a RAID 5 array using the intel controller as a Data drive. It started infrequently that occassionally the system would lock up with the HDD LED on solid, Then it became progressively more and more frequently while troubleshooting.
I started out thinking it was the RAID array since after it freezes it would reboot do a verification and find some errors, so I disabled the array and tried running the WD lifeguard on each drive, each one passed a full disk scan. I tried booting the system with 1 or the 3 drives unplugged, still froze so cycled through each drive, froze each time.
Started suspecting the SSD so I cloned the drive onto a mechanical hard drive, still froze.
Unplugged the entire array and just ran the HDD alone..... didn't freeze as frequently but would still freeze.
Swapped out the RAM with good ram... Still froze.
Swapped power supplies with a good supply... Still froze.
Removed all the components except the boot drive, the RAM and the CPU..... stopped freeze up completely, instead I would get microstutters where the system would freeze for .25 to .5 seconds then continue, could tell if you played a audio stream it would keep repeating (Even a buffered stream) did a latency test and interupts were flying like mad and taking a long time to process, with no specific driver or process assigned.
Plugged the RAID array back in and it was working with the microstuttering, while trying to backup data off the array it froze again.
Rebooted the system, bios would die at B2
unplugged the RAID drives, cleared the cmos the system would boot.
Plug back in the raid drives , clear the cmos and it dies at B2.
Took out a hardware RAID controller (LSI 9260) and connected the drives up to that, dies at B2
unplug the controller... Bios boots
Plug in the controller with no drives attached, dies at B2.
Take the controller out, bios boots.
Sometimes the system gets to A2 and the screen shows snowy static
What is also strange is this occurs on both bios's.... the primary bios which I have flashed to 1.5 and the backup bios which I had left at 1.1 as a fail safe and never flashed.
Thoughts?Hi
Almost same story happened to me.
I have now 2 pieces of Z87 MPOWER boards and both have the same issues.
1. Board came with BIOS 1.5. I left BIOS B to 1.5 and flashed BIOS A to 1.7 with MFLASH method. I installed W8.1 on my onto my SAMSUNG SSD and the PC was working for 2 or 3 days.
Then I noticed strange behavior while booting. The SSD was not found sometimes. I hit F11 and the list was full of USB pen drive entries. Then I entered the BIOS and I have seen only two menu entries: Security and one more I don't remember. Inside of the menu items it was empty or some chinese letters. So I thought the Bios was currupted. Due to missing MFLASH menu I couldn't flash the bios via MFLASH, so I had to study the German MSI Forum. Then I prepared the USB pendrive with ABUDE method and I brought back BIOS A alive. Fine, I thought: It can happen but it shouldn't. But the boot problems came back....
2. The second board came and had BIOS 1.4 installed and I didn't touch board #1 anymore . So I flashed BIOS A again to 1.7 and you know already what's coming up. Totally the same story which I had with board #1.
I switched back to BIOS B and no problems at all with booting.
After a while I noticed some BSODs because of Killer EThernet driver (bwcW8x64.sys). I had so serious problems with that driver. The problem is: If the driver fails, you are even unable to go to the internet and look for a new driver, because your ethernet is dead. Very funny, but not for me. I got the drivers from antother PC and I tried to install them. During installation it was fine. The card was working, but I was forced to do a reboot. After the reboot, the ethernet card was disabled because windows coudn't load the driver. OK, that's a windows issue or a poor driver. I tried several times. No chance to get ethernet back alive. Finally I disabled the Killer Ethernetboad and plugged my former Intel Gigabit ET Dual Port Sever Adapter in. I thought, now I get rid of all the problems. Ha ha...
First was everything fine. Then the PC didn't want to boot anymore: BIOS message --> B2.
I hit del key: "Entering setup" message came up. Nothing more. Several times. Dead.
I plugged out the Intel ethernetboard. Bios came up. I put the ethernet board to another PCI slot. 2 days of working. later on, same story.
Then I switched back to BIOS B and no problems at all.
So what's up here with my 2 MPOWER boards, showing the same issues with BIOS 1.7? What I did wrong?
- MFLASH? May be. But I don't use it anymore. I use the MSIHQ USB Flashing Tool from this forum now which was also spread in the German forum.
- I never flashed BIOS beta versions, I always red articals how to flash and I think I did nothing wrong here.
- Overclocking? No. Unfortunatelly I bought an Intel i4770 CPU without K. Funny. So no overclock issues at all.
- Memory? I have fully equipped 32GB (G.Skill F3-2400C10Q-32GTX) and did the MEM86+ test successfully.
Day before yesterday I flashed BIOS 1.6 to BIOS A. All looks good until now. The intel ethernet board behaves well. No B2 messages.
I will further comment as soon there is anything new.
Do we have some issues with BIOS 1.7? I strongly belief....
I have seen BIOS V1.81 beta is out. But where is V1.8 official release? Anyway, I am tired of testing. If I do not have issues with 1.6 then I will use it.
Unfortunately the MSI Z87 MPOWER board is not yet widely spread. Otherwise we would have more user experiences.
Ok, any comments are highly appreciate it.
@ Corellon: Sometime I got A2 messages with black screen with BIOS V1.7
Which bios version had you installed when you experienced severe problems?
I guess V1.5 & V1.6 are save. 1.7 has got problems. -
I've followed the docs found regarding concatinating an intermediary CA cert and the server cert. So I now have a text file containing the CA first, a new line, and the server cert. It's in PEM format and trasferred to the CSS. My ssl-proxy-list and ssl-server have been configured and SSL works. It all works, the problem is that I get that annoying "untrusted SSL cert" window all the time. I know the original server worked.
Help?Ensure the sequence of the certification chain.
http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_tech_note09186a00801de89b.shtml -
Question
I am not able to launch FF everytime i try to open it, it says FF has to submit a crash report,and restore yr tabs. I even tried doing that and the report was submitted too, but still FF did not start, and the problem still persists, please help me solve this issue
'''(in English)'''Hi Danny,
Per my understanding that you can't get the expect result by using the expression "=Count(Fields!TICKET_STATUS.Value=4) " to count the the TICKET_STATUS which value is 4, the result will returns the count of all the TICKET_STATUS values(206)
but not 180, right?
I have tested on my local environment and can reproduce the issue, the issue caused by you are using the count() function in the incorrect way, please modify the expression as below and have a test:
=COUNT(IIF(Fields!TICKET_STATUS.Value=4 ,1,Nothing))
or
=SUM(IIF(Fields!TICKET_STATUS=4,1,0))
If you still have any problem, please feel free to ask.
Regards,
Vicky Liu
Vicky Liu
TechNet Community Support
Maybe you are looking for
-
How to create Incoming Email Activity using BAPI or Function module
To create an Incoming Email Activity using BAPI 'BAPI_ACTIVITYCRM_CREATEMULTI' or using 'CRM_ORDER_MAINTAIN' . what parameters i need to pass to a bapi. Suggest me with a solution. Regards, Sanjani
-
FBL3N XXL export format change
Hi, I am using fbl3n to generate listing of g/l line items. my output contains profitcenter, vendor, account number and other fields. when i export this data to spreadsheet, the above fields are prefixed with 0. i do not want the same to be prefixed
-
LiveCycle ES 8,2 JBoss : will it work under Windows PC 2007
LiveCycle ES 8,2 JBoss : will it work under Windows PC 2007 virtual machine? (Turnkey or non turnkey version) Thanks Yog
-
Conditional Suppression Page Header
My report contains one subreport placed in RFb. The data in the subreport is unrelated to the data in the primary report, so each report requires its own set of column headers. When printed, the subreport requires at least several page. Subreports ha
-
I see some success with Oracle 8.1.6 on Mandrake, so that would be something to try. Unfortunately, the link on Technet does not work for me. Did they remove the TAR_GZ but left the link? Is the link outdated? Thanks!