Issues with running Server 2012R2 Essentials as an Offline Standalone Root CA?

Hi everyone,
   I've searched this forum as well as Google and have not been able to find any concrete answers so I am hoping one of you experts will be able to assist me.  
   I have an all Windows 2008 server/domain enviroment.   I was looking at implementing a two-tier PKI with an offline, standalone root CA and an enterprise issuing CA (2008 member server).   Budgets are tight so I was hoping
I could get away with using Server 2012R2 Essentials as the offline standalone root.  
   It is my understanding that 2012 Essentials is configured as a DC by default and needs to remain that way per licensing.   I know the recommended configuration for an offline root would be to have the server be in a workgroup and not
on a domain.
   So question 1 is will 2012 Essentials work as an offline standalone root?
   Question 2 is will there be any issues with it running as described?   In other words will the fact that it is the sole DC in its own domain cause issues with its use as an offline root?  
   Thank you in advance for your help!

The essentials experience role runs on server standard and is very different from the essentials product in both licensing and pricing. While you can indeed buy standard and deploy the essentials experience role as a "standalone" server, there
would be ZERO benefit in a PKI offline root scenario the essentials role has no automation or configuration options in the dashboard for that use case, and pricing, you'd still be paying for server standard.
 The essentials product (or SKU) has the benefit of reduced cost, but cannot be deployed standalone and has enough other restrictions that it is not well suited for the given desired use.
So either way, my answer stands. Essentials (prodct it role) is not the right tool for the job in this case.

Similar Messages

  • Licensing issue with Windows Server 2012 R2 Essential

    Hi,
    we purchased a server that came with Windows Server 2012 Essentials. and we found out some of the issue regarding the licensing. I would like to verify it with the experts here.
    1. This Essential O.S. cannot be deployed as a member server in the domain, only Windows server 2012 r2 Standard and data center is capable as deploy as a member server? 
    2. does it work with a single domain with multiple domain controllers and one primary domain controller? Example, 10 offices in different states, each location has a domain controller in their office, I'm installing to install this Essential server as another
    domain controller in one of the offices for redundancy purpose. I promoted this server into domain controller with success, but it gives me an fsmo error everyday, and warning about shutting down if i don't transfer the fsmo role to this server.
    3. which leads to this question, so this Essential OS can only be deploy as a single domain as the primary domain controller? Up to 25 user and 50 device license?
    4. Is it possible to deploy it as a domain controller (that office has less than 25 users) in that office while syncing correctly with the other 10 domain controllers in other offices, they are all in the same single domain? I can't make this work, and I
    think due to the Essential O.S.'s limitation.
    5. we use a vpn connection to connect all the office together, and all the domain controller uses lan ip address to communicate with each other.
    Thank you for the help in advance. I have been researching for the past couple days, but I still couldn't get a clear answer. Thank you again.

    Hi Cliff,
    Thank you for your reply.
    1. We will get a new server 2012 r2 standard to deploy as member server.
    2 and 3. Only ONE domain controller can hold all FSMO roles in a single domain, correct? Currently an windows 2003 enterprise, this is our first server in our domain, it holds all the FSMO roles currently. 
    4. Yes, we realized essentials will not work for us, so we are switching to 2012 r2 standard to deploy for the new
        domain controller for our new office, still under the same domain. 
    5. This wasn't a question, just wanted to give out the connection information.
    The problem was that We didn't read the Essentials in detail when buying the new server, on dell website, it said it was perfect for small business, we didn't know it has to run as a primary DC. it was great in price, and it doesn't need CALs.
    but we quickly realized after deploying it as a DC, it gives us error about Server Licensing compliance, and will shut down automatically. Then we were going to use it as a member server to run application, and realized we couldn't. So we are returning the
    server, and getting a new one with standard r2 2012 and CALs license. 
    It was a costly mistake.
    Thank you again.

  • Issue with Dreamweaver - Server Busy error message

    Hi,
    Whenever i open Dreamweaver, i see "Server Busy" error message. I am unable to use the application due to this. Can you please help resolve this right away?
    Regards,
    Raghu

    I am using Dreamweaver CC. This problem started after a recent update I think.
    Operating system - Windows 8.1 Professional
    Basic system config in case you need it - 8 GB RAM, 2 TB HDD, Intel i7
    Regards,
    Raghu
    Date: Fri, 20 Dec 2013 11:18:44 -0800
    From: [email protected]
    To: [email protected]
    Subject: Issue with Dreamweaver - Server Busy error message
        Re: Issue with Dreamweaver - Server Busy error message
        created by Nancy O. in Dreamweaver support forum - View the full discussion
    Which ver and build # of DW?
    Which operating System?
    Do you use a testing server?
    If so, which one and is it running?
       Nancy O.
         Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5948026#5948026
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5948026#5948026
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5948026#5948026. In the Actions box on the right, click the Stop Email Notifications link.
               Start a new discussion in Dreamweaver support forum at Adobe Community
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

  • System Center Essentials on Windows Server 2012R2 Essentials

    is it possible to install SCE 2010 on Server 2012R2 Essentials?
    I already have WSUS up and running on this sever and know that SCE will try to install an older version WSUS.  don't really need full SCCM so would like to use SCE instead.

    The Windows Server 2012 R2 is not in the supported list of SCE 2010 and considering SCE is discontinued. You may have a try. It will still try to install older version WSUS.
    Juke Chou
    TechNet Community Support

  • Issues with JMS Server migration

    Hi All,
    I have issue with JMS server migration.
    I have configured clustred environment with 2 Managed server (MS1 & MS2) and with one JMS Server which is running on MS1 and configured for auto migration, when I start both my managed server once and access the application very functionality works fine and when I stop the MS1 the JMS server successfully geting migrated to MS2 and in this scenarion also my application works as expected and when I restart the MS1 and access the application all the functionalities related to MDBs are executed twice.
    However once we restart the MS1 we observe that in the monitor tab of MDB the connection status for both managed servers it show as connected.
    As a result there is a redundancy when the MDB is executed
    I am using Weblogic Server 10.3.0 & normal topics in the MDBs.
    Please let me know is this a bug or am I missing any configuration.

    Hi Suresh,
    There is a "Bug-10007947" in WLS 10.3.0 version which dose not displays the values properly on admin-console once the migration has taken place, however I am assuming that bug may fix your issue so try that out in your test environment. If that dose not work try out the below suggestions.
    Suggestion:
    - Try the same test on different versions of WLS lower as well as on higher versions compared to WLS 10.3.0 (i.e WLS 9.2.X and WLS 10.3.x) and check what are the result.
    - If in any other version your test runes properly, then you can create a simple test case and open a service request with Oracle asking for creating a BUG and let them do their job.
    Hope above information helped you.
    Regards,
    Ravish Mody

  • Memory leak issue with link server between SQL Server 2012 and Oracle

    Hi,
    We are trying to use the linked server feature with SQL Server 2012 to connect SQL server and Oracle database. We are concerned about the existing memory leak issue.  For more context please refer to the link.
    http://blogs.msdn.com/b/psssql/archive/2009/09/22/if-you-use-linked-server-queries-you-need-to-read-this.aspx
    The above link talks about the issues with SQL Server versions 2005 and 2008, not sure if this is still the case in 2012.  I could not find any article that talks about if this issue was fixed by Microsoft in later version.
    We know that SQL Server process crashes because of the third-party linked server provider which is loaded inside SQL Server process. If the third-party linked server provider is enabled together with the
    Allow inprocess option, the SQL Server process crashes when this third-party linked server experiences internal problems.
    We wanted to know if this fixed in SQL Server 2012 ?

    So your question is more of a information type or are you really facing OOM issue.
    There can be two things for OOM
    1. There is bug in SQL Server which is causing the issue which might be fixed in 2012
    2. The Linked server provider used to connect to Oracle is not upto date and some patch is missing or more recent version is to be used.  Did you made sure that you are using latest version.
    What is Oracle version you are trying to connect(9i,10g, R2...)
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Installing MS Exchange on Windows Server 2012R2 Essentials?

    Hi Guys, 
    I am having trouble finding the appropriate answer to my question - is it possible to install MS Exchange 2013 on Windows Server 2012R2 Essentials edition? Needless to say that this server will be a DC as well - I am aware that it is ot recommended to install
    Exchange on domain controller but that is not my question here. I just need to know if it can be installed on 2012R2 Essetials edition? Thank you.
    Dino

    No.  I'm not aware of any documentation showing how this can be done.
    Too complicated, the sharing of the IIS the needed ARR.....  not supported...not recommended.  You get the idea. 
    That ship has sailed.
    Unfortunately TechNet subscriptions aren't coming back, sorry folks :-(

  • HT3131 Are there any ventilation issues with running a macbook air in clamshell mode?

    Are there any ventilation issues with running a macbook air in clamshell mode?

    ...that makes sense to me. 
    but, why do so many MBA users (on this forum and others) claim that ventilation occurs through the keyboard?  Is this claim based on an old macbook design?
    for example, here's a related discussion (although fairly old): 
    11-08-2010, 12:16 PM
      #6 (permalink)
    SP Forsythe 
    Notebook Evangelist
    Join Date: Jul 2007 
    Location: California
    Posts: 660
    Rep Power: 14
    Re: Is it safe to use MBP with screen lid closed? Leave charge on always?
    Quote: 
    Originally Posted by tHE j0KER
    Actually I you shouldn't close the lid while running on an external screen. The keyboard of the Macbook is an air intake for the fan. Close the lid, and it could overheat.
    A common misconception of unknown origin. The intake and the exhaust for the cooling fan on the 13" MB and MBP are both located on the rear slot at the base of the hinge. In fact, you can actually see the divider that separates the intake flow from the output flow. If it were through the keyboard crevices, then an awful lot of overheats would result from people using impermeable keyboard covers, as well as Apple's warranty department would be flipping out over the Apple store carrying such covers. iSkin ProTouch FX Keyboard Cover for all MacBooks - Black Printed Keys on White - Apple Store (U.S.) 
    Does one think that Apple sells these only for use when the Notebook is off??? http://store.apple.com/us/product/TW...co=MTM3OTUwMDE Closing the lid, whilst operating the unit actually results in cooler operation due to reduction in power consumed by operating the display, which in supporting the on-board display generates heat far greater than simply powering the video port.. 
    Does one think that Apple sells these for use only when the MacBook is off? http://store.apple.com/us/product/TW...co=MTM3OTUwMDEApples direction for use is specifically for when using with an external display.
    Currently using:
    Apple MacBook Air 13" mid 2011 1.8GHz Core i7 4GB 256 GB SSD Lion & Ubuntu Linux via Fusion
    MacBook Air 11.6" late 2010 1.6 GHZ, 320M, 4GB 180 GB SSD Upgraded OWC), OS X Lion
    11-08-2010, 02:34 PM
      #7 (permalink)
    ajreynol 
    Notebook Virtuoso
    Join Date: Mar 2009 
    Location: Ann Arbor, MI
    Posts: 2,542
    Rep Power: 18
    Re: Is it safe to use MBP with screen lid closed? Leave charge on always?
    once again, I've tried a few of these keyboard covers. the Moshi keyboard cover is the ONLY one I can recommend. the others are too thick or change the keyboard experience too much.
    17" Apple MacBook Pro | i7 2720m | 160GB SSD + 750GB | 16GB | HD 6750M 1GB
    Dell 435MT | i7 920 | 10GB RAM | 7.64TB HDDs | HD 6970 | Win7+SL
    HP Elitebook 2710p Tablet PC | 1.8GHz C2D | 4GB RAM | 160GB HDD | X3100
    Apple iPhone 4 32GB | Apple iPad 64GB (Gen 3)
    Stop random laptop wakeup | 5K500.B bench data | How to Disable PowerMiser
    Disable Vaio beep when pressing volume or special keys
    11-08-2010, 03:34 PM
      #8 (permalink)
    doh123 
    Without ME its just AWESO
    Join Date: Feb 2009 
    Posts: 3,282
    Rep Power: 22
    Re: Is it safe to use MBP with screen lid closed? Leave charge on always?
    1. Closing the cover will cause more heat. This is not because of covering the keyboard very much (though it does help some heat be retained). It's mainly because of the shape of the hinge and the fact when closed it covers up the back vent a lot more. For the best cooling, it is best to have the screen open. Just run it as a dual monitor, but make the external the Primary monitor, and if you don't want to use the built in, just turn its backlight off and don't use it.
    2. The thing you plug into the wall is not a battery charger. The actual "charger" is built into the computer. It knows when to charge and when not to. If the little light on the power plug is amber, then its charging your battery. When its green, its just powering the laptop and NOT charging your battery at all.
    Mac OS X Gamer/Porter
    (We do exist!)
    Wineskin 2.5 is available!. Turn Windows apps into Mac apps for free!
    11-08-2010, 03:38 PM
      #9 (permalink)
    Wolfpup 
    Notebook Virtuoso
    Join Date: Jun 2007 
    Posts: 3,871
    Rep Power: 28
    Re: Is it safe to use MBP with screen lid closed? Leave charge on always?
    I'd leave the lid open, at least partially...yes it may be fine not doing that, but you are making heat dissipate worse, of course could even theoretically hurt the screen.
    As for the battery...well there's really only two choices, have it plugged in or not. As others mentioned, you can't overcharge the battery. It can be damaged a bit from heat, but of course the number one thing that's going to damage it is discharging it...so it's a no brainer-use it plugged in whenever possible, and try to charge it whenever possible when it's not plugged in.
    11-08-2010, 03:45 PM
      #10 (permalink)
    SP Forsythe 
    Notebook Evangelist
    Join Date: Jul 2007 
    Location: California
    Posts: 660
    Rep Power: 14
    Re: Is it safe to use MBP with screen lid closed? Leave charge on always?
    Quote: 
    Originally Posted by doh123
    1. Closing the cover will cause more heat. This is not because of covering the keyboard very much (though it does help some heat be retained). It's mainly because of the shape of the hinge and the fact when closed it covers up the back vent a lot more. For the best cooling, it is best to have the screen open. Just run it as a dual monitor, but make the external the Primary monitor, and if you don't want to use the built in, just turn its backlight off and don't use it.
    Nope. Apple would disagree with you on that one. Any "closure", which is, when compared to the amount of CFM, is insignificant. In fact, the opening size remains the same. it is only deflected at a slight angle when the lid is closed. Tilt your MBP and see. As well, shutting down the display lowers the heat being generated, even in the lower case. As I said, if it were a problem, Apple would not be selling stands designed to operate your unit in the closed position as the original poster of this thread proposes to do.
    Currently using:
    Apple MacBook Air 13" mid 2011 1.8GHz Core i7 4GB 256 GB SSD Lion & Ubuntu Linux via Fusion
    MacBook Air 11.6" late 2010 1.6 GHZ, 320M, 4GB 180 GB SSD Upgraded OWC), OS X Lion

  • Compatibility issue with outgoing server; they suggest downloading Thunderbird.  Any suggestions?

    My internet provider says there is a compatibility issue with outgoing server and suggest downloading Thunderbird.   Any comments?

    Not without some details from you.
    What version of OSX
    Who is the mail provider
    If not iCloud mail what type is it (POP or Imap)
    That's a start.

  • Issue with AFP server dropping connections on 10.8.5 server 2.2.2

    We are having issues with users getting dropped from their AFP server shares.
    These issues did not start happening until we upgraded to 10.8.5 and server 2.2.2
    the first symptoms were an occasional user would lose his / her active connection while copying files. They were unable to disconnect from the network shares without physically disconnecting the LAN or disabling the network on their system. Once the connection was removed they could reconnect to the network and establish their AFP shares again.
    However this his escalated to every user losing connections to their AFP shares at the same time.
    The server has no AFP error in the AFP error log however we are getting diskutil crash reports at around the same time. (See Below)
    The server has
    smalltree 1x6 8254 with latest drivers supporting a LACP bonded 6 pair connecting to an edgecore (LACP configured)switch.
    small tree 10Gb card directly connected to an edit station.
    onboard ethernet connected to switch in support of DHCP & DNS. (previous version of server would not see the bonded pair)
    Two Accusys A12S2's
    (we did not have this dropping connection issue before the upgrade to server 2.2.2 and OSX 10.8.5)
    Users connected to any network connection to the server appear to be affected when the AFP shares are disconnected. Direcet connect, onboard ethernet port and Bonded pair connections)
    diskutil verifies all shared drives appear to be ok. (All Green)
    SYSTEM LOG
    Feb 23 11:15:44 doghouse.local diskutil[1067]: -[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8
    Feb 23 11:15:44 doghouse.local diskutil[1067]: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8'
              *** First throw call stack:
                        0   CoreFoundation                      0x00007fff91b2bb06 __exceptionPreprocess + 198
                        1   libobjc.A.dylib                     0x00007fff901403f0 objc_exception_throw + 43
                        2   CoreFoundation                      0x00007fff91bc240a -[NSObject(NSObject) doesNotRecognizeSelector:] + 186
                        3   CoreFoundation                      0x00007fff91b1a02e ___forwarding___ + 414
                        4   CoreFoundation                      0x00007fff91b19e18 _CF_forwarding_prep_0 + 232
                        5   diskutil                            0x000000010c1eb550 diskutil + 83280
                        6   diskutil                            0x000000010c1ea0af diskutil + 77999
                        7   diskutil                            0x000000010c1e7abe diskutil + 68286
                        8   diskutil                            0x000000010c1dd0ef diskutil + 24815
                        9   diskutil                            0x000000010c1e5161 diskutil + 57697
                        10  Foundation                          0x00007fff8d29dd05 __NSFireDelayedPerform + 358
                        11  CoreFoundation                      0x00007fff91ae8804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
                        12  CoreFoundation                      0x00007fff91ae831d __CFRunLoopDoTimer + 557
                        13  CoreFoundation                      0x00007fff91acdad9 __CFRunLoopRun + 1529
                        14  CoreFoundation                      0x00007fff91acd0e2 CFRunLoopRunSpecific + 290
                        15  Foundation                          0x00007fff8d2c57ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
                        16  Foundation                          0x00007fff8d25e1aa -[NSRunLoop(NSRunLoop) run] + 74
                        17  diskutil                            0x000000010c1e5126 diskutil + 57638
                        18  diskutil                            0x000000010c1e51cd diskutil + 57805
                        19  libdyld.dylib                       0x00007fff86bf87e1 start + 0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Saved crash report for diskutil[1061] version 680 to /Library/Logs/DiagnosticReports/diskutil_2014-02-23-111544_doghouse.crash
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/diskutil_2014-02-22-164711_dogh ouse.crash
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local diskutil[1071]: -[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Saved crash report for diskutil[1067] version 680 to /Library/Logs/DiagnosticReports/diskutil_2014-02-23-111544-1_doghouse.crash
    Feb 23 11:15:44 doghouse.local diskutil[1071]: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8'
              *** First throw call stack:
                        0   CoreFoundation                      0x00007fff91b2bb06 __exceptionPreprocess + 198
                        1   libobjc.A.dylib                     0x00007fff901403f0 objc_exception_throw + 43
                        2   CoreFoundation                      0x00007fff91bc240a -[NSObject(NSObject) doesNotRecognizeSelector:] + 186
                        3   CoreFoundation                      0x00007fff91b1a02e ___forwarding___ + 414
                        4   CoreFoundation                      0x00007fff91b19e18 _CF_forwarding_prep_0 + 232
                        5   diskutil                            0x0000000100e49550 diskutil + 83280
                        6   diskutil                            0x0000000100e480af diskutil + 77999
                        7   diskutil                            0x0000000100e45abe diskutil + 68286
                        8   diskutil                            0x0000000100e3b0ef diskutil + 24815
                        9   diskutil                            0x0000000100e43161 diskutil + 57697
                        10  Foundation                          0x00007fff8d29dd05 __NSFireDelayedPerform + 358
                        11  CoreFoundation                      0x00007fff91ae8804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
                        12  CoreFoundation                      0x00007fff91ae831d __CFRunLoopDoTimer + 557
                        13  CoreFoundation                      0x00007fff91acdad9 __CFRunLoopRun + 1529
                        14  CoreFoundation                      0x00007fff91acd0e2 CFRunLoopRunSpecific + 290
                        15  Foundation                          0x00007fff8d2c57ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
                        16  Foundation                          0x00007fff8d25e1aa -[NSRunLoop(NSRunLoop) run] + 74
                        17  diskutil                            0x0000000100e43126 diskutil + 57638
                        18  diskutil                            0x0000000100e431cd diskutil + 57805
                        19  libdyld.dylib                       0x00007fff86bf87e1 start + 0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/diskutil_2014-02-22-164712_dogh ouse.crash
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Saved crash report for diskutil[1071] version 680 to /Library/Logs/DiagnosticReports/diskutil_2014-02-23-111544-2_doghouse.crash
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/diskutil_2014-02-23-093307_dogh ouse.crash
    diskutil crash report
    Process:         diskutil [1061]
    Path:            /usr/sbin/diskutil
    Identifier:      diskutil
    Version:         680
    Code Type:       X86-64 (Native)
    Parent Process:  sh [1060]
    User ID:         0
    Date/Time:       2014-02-23 11:15:43.719 -0800
    OS Version:      Mac OS X 10.8.5 (12F45)
    Report Version:  10
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8'
    terminate called throwing an exception
    abort() called
    Application Specific Backtrace 1:
    0   CoreFoundation                      0x00007fff91b2bb06 __exceptionPreprocess + 198
    1   libobjc.A.dylib                     0x00007fff901403f0 objc_exception_throw + 43
    2   CoreFoundation                      0x00007fff91bc240a -[NSObject(NSObject) doesNotRecognizeSelector:] + 186
    3   CoreFoundation                      0x00007fff91b1a02e ___forwarding___ + 414
    4   CoreFoundation                      0x00007fff91b19e18 _CF_forwarding_prep_0 + 232
    5   diskutil                            0x000000010124a550 diskutil + 83280
    6   diskutil                            0x00000001012490af diskutil + 77999
    7   diskutil                            0x0000000101246abe diskutil + 68286
    8   diskutil                            0x000000010123c0ef diskutil + 24815
    9   diskutil                            0x0000000101244161 diskutil + 57697
    10  Foundation                          0x00007fff8d29dd05 __NSFireDelayedPerform + 358
    11  CoreFoundation                      0x00007fff91ae8804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
    12  CoreFoundation                      0x00007fff91ae831d __CFRunLoopDoTimer + 557
    13  CoreFoundation                      0x00007fff91acdad9 __CFRunLoopRun + 1529
    14  CoreFoundation                      0x00007fff91acd0e2 CFRunLoopRunSpecific + 290
    15  Foundation                          0x00007fff8d2c57ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
    16  Foundation                          0x00007fff8d25e1aa -[NSRunLoop(NSRunLoop) run] + 74
    17  diskutil                            0x0000000101244126 diskutil + 57638
    18  diskutil                            0x00000001012441cd diskutil + 57805
    19  libdyld.dylib                       0x00007fff86bf87e1 start + 0
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib                  0x00007fff86519212 __pthread_kill + 10
    1   libsystem_c.dylib                       0x00007fff8a31ab24 pthread_kill + 90
    2   libsystem_c.dylib                       0x00007fff8a35ef61 abort + 143
    3   libc++abi.dylib                         0x00007fff85dc39eb abort_message + 257
    4   libc++abi.dylib                         0x00007fff85dc139a default_terminate() + 28
    5   libobjc.A.dylib                         0x00007fff90140873 _objc_terminate() + 91
    6   libc++abi.dylib                         0x00007fff85dc13c9 safe_handler_caller(void (*)()) + 8
    7   libc++abi.dylib                         0x00007fff85dc1424 std::terminate() + 16
    8   libc++abi.dylib                         0x00007fff85dc261b __cxa_rethrow + 85
    9   libobjc.A.dylib                         0x00007fff90140575 objc_exception_rethrow + 40
    10  com.apple.CoreFoundation                0x00007fff91acd146 CFRunLoopRunSpecific + 390
    11  com.apple.Foundation                    0x00007fff8d2c57ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
    12  com.apple.Foundation                    0x00007fff8d25e1aa -[NSRunLoop(NSRunLoop) run] + 74
    13  diskutil                                0x0000000101244126 0x101236000 + 57638
    14  diskutil                                0x00000001012441cd 0x101236000 + 57805
    15  libdyld.dylib                           0x00007fff86bf87e1 start + 1
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib                  0x00007fff86519d16 kevent + 10
    1   libdispatch.dylib                       0x00007fff8a0dddea _dispatch_mgr_invoke + 883
    2   libdispatch.dylib                       0x00007fff8a0dd9ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib                  0x00007fff865196d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8a31bf1c _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff8a31bce3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff8a306191 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib                  0x00007fff865196d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8a31bf1c _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff8a31bce3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff8a306191 start_wqthread + 13
    Thread 4:
    0   libsystem_kernel.dylib                  0x00007fff865196d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8a31bf1c _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff8a31bce3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff8a306191 start_wqthread + 13
    Thread 0 crashed with X86 Thread State (64-bit):
      rax: 0x0000000000000000  rbx: 0x0000000000000006  rcx: 0x00007fff5e9c9ad8  rdx: 0x0000000000000000
      rdi: 0x0000000000000707  rsi: 0x0000000000000006  rbp: 0x00007fff5e9c9b00  rsp: 0x00007fff5e9c9ad8
       r8: 0x00007fff764be278   r9: 0x00007fff5e9c9ae0  r10: 0x0000000020000000  r11: 0x0000000000000206
      r12: 0x00007fff5e9c9c60  r13: 0x0000000000000001  r14: 0x00007fff764bf180  r15: 0x00007fff5e9c9b40
      rip: 0x00007fff86519212  rfl: 0x0000000000000206  cr2: 0x00007fff764b7ff0
    Logical CPU: 0
    Binary Images:
           0x101236000 -        0x10126efff  diskutil (680) <47174BB8-7EAC-39F7-96F7-99FE93C9CAF3> /usr/sbin/diskutil
        0x7fff60e36000 -     0x7fff60e6a93f  dyld (210.2.3) <6900F2BA-DB48-3B78-B668-58FC0CF6BCB8> /usr/lib/dyld
        0x7fff85d6f000 -     0x7fff85d6ffff  libkeymgr.dylib (25) <CC9E3394-BE16-397F-926B-E579B60EE429> /usr/lib/system/libkeymgr.dylib
        0x7fff85dc0000 -     0x7fff85de5ff7  libc++abi.dylib (26) <D86169F3-9F31-377A-9AF3-DB17142052E4> /usr/lib/libc++abi.dylib
        0x7fff85de6000 -     0x7fff85e4eff7  libc++.1.dylib (65.1) <20E31B90-19B9-3C2A-A9EB-474E08F9FE05> /usr/lib/libc++.1.dylib
        0x7fff85e4f000 -     0x7fff85ef5ff7  com.apple.CoreServices.OSServices (557.6 - 557.6) <FFDDD2D8-690D-388F-A48F-4750A792D2CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
        0x7fff85f54000 -     0x7fff85f62ff7  libkxld.dylib (2050.48.12) <B8F7ED1F-CF84-3777-9183-0A1C513DF81F> /usr/lib/system/libkxld.dylib
        0x7fff861de000 -     0x7fff86353ff7  com.apple.CFNetwork (596.5 - 596.5) <22372475-6EF4-3A04-83FC-C061FE4717B3> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
        0x7fff86354000 -     0x7fff863d5fff  com.apple.Metadata (10.7.0 - 707.12) <69E3EEF7-8B7B-3652-8320-B8E885370E56> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
        0x7fff86468000 -     0x7fff86470ff7  libsystem_dnssd.dylib (379.38.1) <BDCB8566-0189-34C0-9634-35ABD3EFE25B> /usr/lib/system/libsystem_dnssd.dylib
        0x7fff86499000 -     0x7fff86506ff7  com.apple.datadetectorscore (4.1 - 269.3) <5775F0DB-87D6-310D-8B03-E2AD729EFB28> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
        0x7fff86507000 -     0x7fff86522ff7  libsystem_kernel.dylib (2050.48.12) <4B7993C3-F62D-3AC1-AF92-414A0D6EED5E> /usr/lib/system/libsystem_kernel.dylib
        0x7fff865b1000 -     0x7fff865b2ff7  libremovefile.dylib (23.2) <6763BC8E-18B8-3AD9-8FFA-B43713A7264F> /usr/lib/system/libremovefile.dylib
        0x7fff86764000 -     0x7fff86769fff  libcache.dylib (57) <65187C6E-3FBF-3EB8-A1AA-389445E2984D> /usr/lib/system/libcache.dylib
        0x7fff86784000 -     0x7fff86785fff  libDiagnosticMessagesClient.dylib (8) <8548E0DC-0D2F-30B6-B045-FE8A038E76D8> /usr/lib/libDiagnosticMessagesClient.dylib
        0x7fff86bf6000 -     0x7fff86bf9ff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
        0x7fff8715b000 -     0x7fff8715bfff  com.apple.vecLib (3.8 - vecLib 3.8) <6CBBFDC4-415C-3910-9558-B67176447789> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
        0x7fff871a8000 -     0x7fff87235ff7  com.apple.SearchKit (1.4.0 - 1.4.0) <C7F43889-F8BF-3CB9-AD66-11AEFCBCEDE7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
        0x7fff87236000 -     0x7fff87243fff  libbz2.1.0.dylib (29) <CE9785E8-B535-3504-B392-82F0064D9AF2> /usr/lib/libbz2.1.0.dylib
        0x7fff872d9000 -     0x7fff87373fff  libvMisc.dylib (380.10) <A7F12764-A94C-36EB-88E0-F826F5AF55B4> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
        0x7fff87455000 -     0x7fff87455fff  com.apple.CoreServices (57 - 57) <9DD44CB0-C644-35C3-8F57-0B41B3EC147D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
        0x7fff87874000 -     0x7fff87947ff7  com.apple.DiscRecording (7.0 - 7000.2.4) <6DCA9535-E276-3D77-BEB3-296B537AA6BB> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
        0x7fff879ab000 -     0x7fff879aefff  libutil.dylib (30) <EF3340B2-9A53-3D5E-B9B4-BDB5EEECC178> /usr/lib/libutil.dylib
        0x7fff87da3000 -     0x7fff87da5ff7  com.apple.EFILogin (2.0 - 2) <51A470D7-1F72-3369-AF0F-AD2340B42C12> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin
        0x7fff880b1000 -     0x7fff880e9fff  libncurses.5.4.dylib (37.3) <68D5B5F5-8252-3F1E-AFF1-C6AFE145DBC1> /usr/lib/libncurses.5.4.dylib
        0x7fff881ed000 -     0x7fff881faff7  com.apple.NetAuth (4.0 - 4.0) <F5BC7D7D-AF28-3C83-A674-DADA48FF7810> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
        0x7fff88571000 -     0x7fff8859fff7  libsystem_m.dylib (3022.6) <B434BE5C-25AB-3EBD-BAA7-5304B34E3441> /usr/lib/system/libsystem_m.dylib
        0x7fff887e7000 -     0x7fff887e8ff7  libSystem.B.dylib (169.3) <5ED23C27-47AF-3C93-984A-172751CF745A> /usr/lib/libSystem.B.dylib
        0x7fff887e9000 -     0x7fff8883aff7  com.apple.SystemConfiguration (1.12.2 - 1.12.2) <581BF463-C15A-363B-999A-E830222FA925> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
        0x7fff8883b000 -     0x7fff88b52ff7  com.apple.CoreServices.CarbonCore (1037.6 - 1037.6) <1E567A52-677F-3168-979F-5FBB0818D52B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
        0x7fff88b53000 -     0x7fff88b54ff7  libsystem_sandbox.dylib (220.3) <B739DA63-B675-387A-AD84-412A651143C0> /usr/lib/system/libsystem_sandbox.dylib
        0x7fff88be0000 -     0x7fff88bf3ff7  libbsm.0.dylib (32) <F497D3CE-40D9-3551-84B4-3D5E39600737> /usr/lib/libbsm.0.dylib
        0x7fff88dd0000 -     0x7fff88dd1fff  libsystem_blocks.dylib (59) <D92DCBC3-541C-37BD-AADE-ACC75A0C59C8> /usr/lib/system/libsystem_blocks.dylib
        0x7fff892df000 -     0x7fff892e5fff  libmacho.dylib (829) <BF332AD9-E89F-387E-92A4-6E1AB74BD4D9> /usr/lib/system/libmacho.dylib
        0x7fff892e6000 -     0x7fff89335ff7  libcorecrypto.dylib (106.2) <CE0C29A3-C420-339B-ADAA-52F4683233CC> /usr/lib/system/libcorecrypto.dylib
        0x7fff89336000 -     0x7fff89536fff  libicucore.A.dylib (491.11.3) <5783D305-04E8-3D17-94F7-1CEAFA975240> /usr/lib/libicucore.A.dylib
        0x7fff89537000 -     0x7fff89537fff  libOpenScriptingUtil.dylib (148.3) <F8681222-0969-3B10-8BCE-C55A4B9C520C> /usr/lib/libOpenScriptingUtil.dylib
        0x7fff89538000 -     0x7fff89581ff7  com.apple.DiskManagement (5.3.1 - 680) <5438A1FF-B92C-3D28-A8E4-FB41F03144C2> /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/DiskManag ement
        0x7fff89589000 -     0x7fff895abff7  libxpc.dylib (140.43) <70BC645B-6952-3264-930C-C835010CCEF9> /usr/lib/system/libxpc.dylib
        0x7fff895b6000 -     0x7fff895cdfff  com.apple.CFOpenDirectory (10.8 - 151.10) <F7AD9844-559A-366E-8192-BB4FCF9EE7A3> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
        0x7fff895ce000 -     0x7fff895d9fff  libsystem_notify.dylib (98.5) <C49275CC-835A-3207-AFBA-8C01374927B6> /usr/lib/system/libsystem_notify.dylib
        0x7fff8960f000 -     0x7fff89614fff  libcompiler_rt.dylib (30) <08F8731D-5961-39F1-AD00-4590321D24A9> /usr/lib/system/libcompiler_rt.dylib
        0x7fff899f3000 -     0x7fff89a3fff7  libauto.dylib (185.4) <AD5A4CE7-CB53-313C-9FAE-673303CC2D35> /usr/lib/libauto.dylib
        0x7fff89b9a000 -     0x7fff89b9cff7  libunc.dylib (25) <92805328-CD36-34FF-9436-571AB0485072> /usr/lib/system/libunc.dylib
        0x7fff89bd8000 -     0x7fff89c09ff7  com.apple.DictionaryServices (1.2 - 184.4) <FB0540FF-5034-3591-A28D-6887FBC220F7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
        0x7fff8a01f000 -     0x7fff8a0afff7  libCoreStorage.dylib (296.18.2) <2FFB6BCA-3033-3AC1-BCE4-ED102DCBECD5> /usr/lib/libCoreStorage.dylib
        0x7fff8a0d9000 -     0x7fff8a0eeff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
        0x7fff8a0ef000 -     0x7fff8a11afff  libxslt.1.dylib (11.3) <441776B8-9130-3893-956F-39C85FFA644F> /usr/lib/libxslt.1.dylib
        0x7fff8a2e9000 -     0x7fff8a2f3fff  libcsfde.dylib (296.18.2) <08092C5B-2171-3C1D-A98F-CF499A315DDC> /usr/lib/libcsfde.dylib
        0x7fff8a305000 -     0x7fff8a3d1ff7  libsystem_c.dylib (825.40.1) <543B05AE-CFA5-3EFE-8E58-77225411BA6B> /usr/lib/system/libsystem_c.dylib
        0x7fff8a5c9000 -     0x7fff8a628fff  com.apple.AE (645.6 - 645.6) <44F403C1-660A-3543-AB9C-3902E02F936F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
        0x7fff8a679000 -     0x7fff8a776fff  libsqlite3.dylib (138.1) <ADE9CB98-D77D-300C-A32A-556B7440769F> /usr/lib/libsqlite3.dylib
        0x7fff8a8e3000 -     0x7fff8a9e0ff7  libxml2.2.dylib (22.3) <47B09CB2-C636-3024-8B55-6040F7829B4C> /usr/lib/libxml2.2.dylib
        0x7fff8afa9000 -     0x7fff8afdffff  libsystem_info.dylib (406.17) <4FFCA242-7F04-365F-87A6-D4EFB89503C1> /usr/lib/system/libsystem_info.dylib
        0x7fff8afe6000 -     0x7fff8afeefff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
        0x7fff8b2b7000 -     0x7fff8b368fff  com.apple.LaunchServices (539.9 - 539.9) <07FC6766-778E-3479-8F28-D2C9917E1DD1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
        0x7fff8b3bc000 -     0x7fff8b3c0ff7  com.apple.TCC (1.0 - 1) <F2F3B753-FC73-3543-8BBE-859FDBB4D6A6> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
        0x7fff8c051000 -     0x7fff8c0b9fff  libvDSP.dylib (380.10) <3CA154A3-1BE5-3CF4-BE48-F0A719A963BB> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
        0x7fff8c15b000 -     0x7fff8c17cff7  libCRFSuite.dylib (33) <736ABE58-8DED-3289-A042-C25AF7AE5B23> /usr/lib/libCRFSuite.dylib
        0x7fff8c1bc000 -     0x7fff8c1c2ff7  libunwind.dylib (35.1) <21703D36-2DAB-3D8B-8442-EAAB23C060D3> /usr/lib/system/libunwind.dylib
        0x7fff8c58d000 -     0x7fff8c984fff  libLAPACK.dylib (1073.4) <D632EC8B-2BA0-3853-800A-20DA00A1091C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
        0x7fff8c985000 -     0x7fff8c993ff7  libsystem_network.dylib (77.10) <0D99F24E-56FE-380F-B81B-4A4C630EE587> /usr/lib/system/libsystem_network.dylib
        0x7fff8c994000 -     0x7fff8c99bfff  libcopyfile.dylib (89) <876573D0-E907-3566-A108-577EAD1B6182> /usr/lib/system/libcopyfile.dylib
        0x7fff8c99c000 -     0x7fff8c9aafff  libcommonCrypto.dylib (60027) <BAAFE0C9-BB86-3CA7-88C0-E3CBA98DA06F> /usr/lib/system/libcommonCrypto.dylib
        0x7fff8ccbc000 -     0x7fff8cf8dff7  com.apple.security (7.0 - 55179.13) <F428E306-C407-3B55-BA82-E58755E8A76F> /System/Library/Frameworks/Security.framework/Versions/A/Security
        0x7fff8d22a000 -     0x7fff8d589fff  com.apple.Foundation (6.8 - 945.18) <1D7E58E6-FA3A-3CE8-AC85-B9D06B8C0AA0> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
        0x7fff8d939000 -     0x7fff8d950fff  com.apple.GenerationalStorage (1.1 - 132.3) <FD4A84B3-13A8-3C60-A59E-25A361447A17> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Gene rationalStorage
        0x7fff8d951000 -     0x7fff8d952fff  liblangid.dylib (116) <864C409D-D56B-383E-9B44-A435A47F2346> /usr/lib/liblangid.dylib
        0x7fff8d953000 -     0x7fff8d95afff  com.apple.NetFS (5.0 - 4.0) <82E24B9A-7742-3DA3-9E99-ED267D98C05E> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
        0x7fff8d968000 -     0x7fff8d9d1fff  libstdc++.6.dylib (56) <EAA2B53E-EADE-39CF-A0EF-FB9D4940672A> /usr/lib/libstdc++.6.dylib
        0x7fff8dbde000 -     0x7fff8dc4cff7  com.apple.framework.IOKit (2.0.1 - 755.42.1) <A90038ED-48F2-3CC9-A042-53A3D7985844> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
        0x7fff8e11b000 -     0x7fff8e11dfff  libquarantine.dylib (52.1) <143B726E-DF47-37A8-90AA-F059CFD1A2E4> /usr/lib/system/libquarantine.dylib
        0x7fff9012f000 -     0x7fff9024792f  libobjc.A.dylib (532.2) <90D31928-F48D-3E37-874F-220A51FD9E37> /usr/lib/libobjc.A.dylib
        0x7fff91567000 -     0x7fff91568ff7  libdnsinfo.dylib (453.19) <14202FFB-C3CA-3FCC-94B0-14611BF8692D> /usr/lib/system/libdnsinfo.dylib
        0x7fff91952000 -     0x7fff919b5fff  com.apple.audio.CoreAudio (4.1.2 - 4.1.2) <FEAB83AB-1DE5-3813-BA48-7A7F2374CCF0> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
        0x7fff91a98000 -     0x7fff91c82ff7  com.apple.CoreFoundation (6.8 - 744.19) <0F7403CA-2CB8-3D0A-992B-679701DF27CA> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
        0x7fff91c83000 -     0x7fff91e09fff  libBLAS.dylib (1073.4) <C102C0F6-8CB6-3B49-BA6B-2EB61F0B2784> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
        0x7fff91e13000 -     0x7fff91e25ff7  libz.1.dylib (43) <2A1551E8-A272-3DE5-B692-955974FE1416> /usr/lib/libz.1.dylib
        0x7fff91e76000 -     0x7fff91e7cfff  com.apple.DiskArbitration (2.5.2 - 2.5.2) <C713A35A-360E-36CE-AC0A-25C86A3F50CA> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
        0x7fff91f14000 -     0x7fff91f54ff7  com.apple.MediaKit (14 - 687) <8AAA8CC3-3ACD-34A5-9E57-9B24AD8AFD4D> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit
        0x7fff92028000 -     0x7fff92037ff7  libxar.1.dylib (105) <370ED355-E516-311E-BAFD-D80633A84BE1> /usr/lib/libxar.1.dylib
        0x7fff921bd000 -     0x7fff921c1fff  libpam.2.dylib (20) <C8F45864-5B58-3237-87E1-2C258A1D73B8> /usr/lib/libpam.2.dylib
        0x7fff921c2000 -     0x7fff92314fff  com.apple.audio.toolbox.AudioToolbox (1.9.2 - 1.9.2) <DC5F3D1B-036A-37DE-BC24-7636DC95EA1C> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    External Modification Summary:
      Calls made by other processes targeting this process:
        task_for_pid: 0
        thread_create: 0
        thread_set_state: 0
      Calls made by this process:
        task_for_pid: 0
        thread_create: 0
        thread_set_state: 0
      Calls made by all processes on this machine:
        task_for_pid: 240
        thread_create: 0
        thread_set_state: 0
    VM Region Summary:
    ReadOnly portion of Libraries: Total=89.5M resident=64.1M(72%) swapped_out_or_unallocated=25.4M(28%)
    Writable regions: Total=82.6M written=784K(1%) resident=1340K(2%) swapped_out=0K(0%) unallocated=81.3M(98%)
    REGION TYPE                      VIRTUAL
    ===========                      =======
    MALLOC                             72.3M
    MALLOC guard page                    32K
    STACK GUARD                        56.0M
    Stack                              10.0M
    VM_ALLOCATE                           8K
    __DATA                             3472K
    __LINKEDIT                         52.1M
    __TEXT                             37.4M
    __UNICODE                           544K
    mapped file                        18.1M
    shared memory                        12K
    ===========                      =======
    TOTAL                             250.0M

    That kind of crash is usually caused by system corruption. I suggest you reinstall.

  • Issue with MSSQL server connectivity from ODI 10.1.3

    Hi,
    In one of the interface we are populating data to target table in MSSQL server version 2005.
    The physical topology connection results successful.
    Since so long there is no problem and it is running successful. But suddenly I'm facing issues with this.
    I cannot see teh datastores under the model created for this table. When expanding the model, when trying to reverse the model or when I am trying to save any changes in the package I am getting the below error.
    java.lang.UnsupportedClassVersionError: com/microsoft/sqlserver/jdbc/SQLServerDriver (Unsupported major.minor version 49.0)
         at java.lang.ClassLoader.defineClass0(Native Method)
         at java.lang.ClassLoader.defineClass(Unknown Source)
         at java.security.SecureClassLoader.defineClass(Unknown Source)
         at java.net.URLClassLoader.defineClass(Unknown Source)
         at java.net.URLClassLoader.access$100(Unknown Source)
         at java.net.URLClassLoader$1.run(Unknown Source)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.net.URLClassLoader.findClass(Unknown Source)
         at java.lang.ClassLoader.loadClass(Unknown Source)
         at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
         at java.lang.ClassLoader.loadClass(Unknown Source)
         at java.lang.ClassLoader.loadClassInternal(Unknown Source)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Unknown Source)
         at com.sunopsis.sql.SnpsConnection.a(SnpsConnection.java)
         at com.sunopsis.sql.SnpsConnection.u(SnpsConnection.java)
         at com.sunopsis.sql.SnpsConnection.connect(SnpsConnection.java)
         at com.sunopsis.dwg.reverse.Reverse.a(Reverse.java)
         at com.sunopsis.graphical.component.b.a.g.a(g.java)
         at com.sunopsis.graphical.component.b.a.g.a(g.java)
         at com.sunopsis.graphical.component.b.a.d.a(d.java)
         at com.sunopsis.graphical.component.b.h.e(h.java)
         at com.sunopsis.graphical.component.b.h.b(h.java)
         at com.sunopsis.graphical.component.b.h.b(h.java)
         at com.sunopsis.graphical.component.b.h.b(h.java)
         at com.sunopsis.graphical.component.b.h.a(h.java)
         at com.sunopsis.graphical.frame.module.SnpsSplitFrame.refreshSplitFrame(SnpsSplitFrame.java)
         at com.sunopsis.graphical.frame.module.SnpsSplitFrame.refreshNode(SnpsSplitFrame.java)
         at com.sunopsis.graphical.frame.bp.bN(bp.java)
         at com.sunopsis.graphical.frame.bp.bL(bp.java)
         at com.sunopsis.graphical.frame.a.is.bH(is.java)
         at com.sunopsis.graphical.frame.bo.r(bo.java)
         at com.sunopsis.graphical.frame.bo.bv(bo.java)
         at com.sunopsis.graphical.frame.bo.z(bo.java)
         at com.sunopsis.graphical.frame.bo.b(bo.java)
         at com.sunopsis.graphical.frame.w.actionPerformed(w.java)
         at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
         at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
         at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
         at java.awt.Component.processMouseEvent(Unknown Source)
         at java.awt.Component.processEvent(Unknown Source)
         at java.awt.Container.processEvent(Unknown Source)
         at java.awt.Component.dispatchEventImpl(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Window.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.EventQueue.dispatchEvent(Unknown Source)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.run(Unknown Source)
    I have verified below:
    The SQL server version is: MSSQL server 2005
    the "sqljdbc.jar" file is there in place "<ORACLE_HOME>/oracledi/drivers"
    Java version: jdk1.5.0
    There is no change in source or target db. Please help me to fix this issue

    Hi,
    Thanks for the reply. The link is helpful and its the same what is there in the environment.
    "The JDK version is 1.5 and JRE version is 1.4.2."
    But, this was working fine till last week. I am worried, if the issue is due to version compatability why we were not facing this issue before. There is no changes in the environment since go live of this interface.
    Thanks,

  • Mavericks permission issues with Windows Server deduplicated shares.

    We have a number of 10.9-10.9.3 - Mavericks - machines installed throughout our facility. Much of the user content is pulled from shares stored on our Windows Server 2012 fileservers with deduplication enabled. I have found that files newly written or unoptimized are able to be accessed without issue - read, written, modified, etc. Once the file gets optomized/deduplicated and Windows adds the P & L attributes - sparse and symlink - the Macs running Mavericks begin to have access issues.
    Once the files get deduplicated, users begin receiving read access errors when copying files (see error1 below). This happens when copying to folders within the current folder tree or copying somewhere to the local system. If you 'stop' the copy operation and retry a few more times, it may eventually work for the specific instance but fail again later. I am however, able to copy these files without issue via the terminal.
    Other systems running 10.7 do not experience the same issues and are able to access file server resources without issue. Many of the systems having issues are newer and thus not able to be downgraded to 10.8 or 10.7.
    I have tried finder replacements such as Pathfinder but the results are the same. I know this is at least similar to the issues many Mac users are already experiencing and posting about but I haven't seen it directly linked to deduplication and the attributes written by Windows server. Has anyone seen this issue? Have any solutions been found? 
    Error 1:
    When copying files after the PL attributes have been set by deduplication.
    "One or more items can't be copied to "Foler" because you don't have permissions to read them.
    Via the system.log, I am also seeing the following error when accessing these deduplicated file shares. The reparse point tag listed below is "IO_REPARSE_TAG_DEDUP"
    Reported error:
    "smbfs_nget: filename.ext - unknown reparse point tag 0x80000013"

    This is a 'known problem' as discussed on the MacWindows site, see http://www.macwindows.com/More-on-OS-X-conflicts-with-Windows-Server-Deduplicati on.html
    It appears to still affect Mavericks 10.9.5 at least from the lack of any positive reports to the contrary. It is perhaps a bit late but it would have been worth signing up for the public beta of Yosemite and testing that and if needed reporting it as an issue for Yosemite as this will be getting more bug fix attention than Mavericks now.
    I would agree turning off de-duplication is not a desirable solution, however other possibilities to consider are installing the standard Samba software on a Mac and using that instead of Apple's SMBx software. This is done by using the SMBup installer See http://eduo.info/2013/07/13/smbup-faq it does not officially list Mavericks but I did see at least one report that it still worked. A second possibility is to install ExtremeZ-IP which installs an AFP server on to your Windows Server and also gives the bonus of supporting Spotlight searches.
    Note: You should only try SMBup on a test setup first.

  • Outlook 2011 Connection Issue with Proxy Server after 10.8 Upgrade

    Hello,
    After upgrading my MBA to 10.8, my MS Outlook (Outlook Mac 2011) mail connection does not work for an exchange based mail account where a VPN/proxy server combination is involved. This was not an issue at all under 10.7. What's interesting is that it's not an issue with MS Outlook 2010 on my Parallels VM either under 10.8. There are no internet connectivity issues, I am able to connect to the internet using Safari and other browsers. Any help would be appreciated.
    Thanks,
    Manish

    I was having a similar problem using Outlook 2011 running under Mountain Lion (10.8.2) on an MacBook Pro. When at work, behind our proxy server, I could not get Outlook to connect to a client's public Exchange server, but this worked fine without changing any settings when I was connected to our DMZ network or at home (no proxy server in these cases). My MacBook was configured to use "Auto Proxy Configuration", and Safari worked fine in all three locations (as did Apple mail)
    Today, the Microsoft Office auto-updater downloaded an update, and since it was installed, the problem has been fixed and I've been able to connect to our client's external Exchange server event when behind our local proxy server (Outlook now reports that the latest installed update is 14.2.5)
    Steve

  • BAM Cluster setup - issue with whole server migration configuration

    HI,
    We are working on a SOA , BAM , BPM Cluster setup on OEL VMs
    With Admin server running on Host1 and Soa_server1, BAM_server1 , Host2 - Soa_server2 , Bam_server2.
    We were successfully able to setup clustering for Soa without using the webTier utilities in our environment, Just by adding entries in the /etc/hosts file.
    Followed the document - except for web tier setup
    http://www.namredlek.nl/orasoa/InstallSOASuite11gOnCluster_v1.pdf
    1)     Installed Weblogic 11g.
    2)     Soa 11g.
    3)     Domain creation
    4) Configured Node manager
    5) Soa Clustering completed successfully.
    6) Domain up and running with SOA_Cluster up and running.
    7)     Extended the domain with BAM
    The issue revolves when we are doing teh Migration configurations from the console for BAM and we restart BAM server we get an error -
    Apr 14, 2011 2:30:35 AM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'bam_server1'
    java.io.IOException: Command '/oracle/Shared_MWHome/user_projects/domains/SOA_Domain/bin/server_migration/wlsifconfig.sh -addif eth0 192.168.1.6 255.255.255.0 ' returned an unsuccessful exit code '1'. Check NM logs for script output.
    and Bam server goes to Failed Not Restartable state.

    The error is clearly out there
    java.io.IOException: Command '/oracle/Shared_MWHome/user_projects/domains/SOA_Domain/bin/server_migration/wlsifconfig.sh -addif eth0 192.168.1.6 255.255.255.0 ' returned an unsuccessful exit code '1'. Check NM logs for script output.
    This error occurs due to a failure in adding the virtual IP of BAM server to the network interface you have specified in nodemanager.properties.
    You need to check whether you have specified the correct interface and subnet mask in node manager.properties as below :
    The fourth step is to edit the Node Manager's properties file. This file is called nodemanager.properties
    and is located in the ORACLE_BASE/product/osbmw/wlserver_10.3/common/nodemanager directory.
    For server migration to work properly, you need to add the properties listed below:
    Interface=eth0
    NetMask=255.255.255.0
    UseMACBroadcast=true
    · Interface
    This property specifies the interface name for the floating IP (for example, eth0).
    · NetMask
    This property specifies the net mask for the interface for the floating IP. The net mask should the
    same as the net mask on the interface; 255.255.255.0 is used as an example in this document.
    · UseMACBroadcast
    This property specifies whether or not to use a node's MAC address when sending ARP packets,
    that is, whether or not to use the -b flag in the arping command.

  • Weird issue with Windows Server 2008 R2 Print Server

    I have an issue with Windows 2008 R2 (VMWare Hosted) running Windows Print Server. 
    Prior to a small network change, the print server was working well, hosting about 80 different networked printers from various vendors. 
    We made a change (that we ended up rolling back) to the Client's DHCP Scope OPT 006 (DNS Servers). The DNS servers never quite worked right and broke AD authentication to different servers, and was just a mess.
    After rolling back we are not able to keep the printers online. If we ping them from the print server, the printer(s) never wake up, when a print job is submitted. If we ping them from one of the access switches, they work fine (until they fall back asleep),
    to prevent this, if we start a ping on the server AFTER waking them up from the Switch Ping, they stay online and no problems. 
    If we stop the ping, they fall back asleep at some point, and again, won't wake up without intervention/switch side ping. 
    Has anyone experienced anything like this? Any tips on how I could possibly resolve it? 
    Thanks in advance.

    Hi,
    According to your description, the issue seems to be that the printers can't keep online. Sounds like a power managerment issue. Why these printers fall into sleep? Have you consulted this issue with the manufacturer of these printers? Do these printers
    fall into sleep if them lose the contact with printer server? Have you tried to reset the printers?
    >>We made a change (that we ended up rolling back) to the Client's DHCP Scope OPT 006 (DNS Servers).
    DNS client will cache the recently queried records. If the DNS server has replied with a wrong records, communication issues will occur. To clear the DNS cache on a Windows device, please run the command below:
    ipconfig /flushdns
    Best Regards.
    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Maybe you are looking for