Rocky Pope
Level 1 (120 points)
Mac OS X

Q: Server 3.2.1 Installation Failure

I had an install failure of Server 3.2.1.  The exact error was "Error enabling server management.  A problem was detected with Server.  Please redownload Server from the Apple Store."

 

I did a Time Machine restore to version 3.1.2 and I receive the same error upon reinstallation.

 

Does anyone have any suggestions?

 

Apple said to remove the Server app, reboot and then reinstall from the newest version from the Apple Store.  What was the solution that was found to work the best.?

 

 

Thanks,

 

Rocky

Server 3.2.1, OS X Server, Mac Pro 5,1, 20 GB RAM

Posted on Sep 20, 2014 12:45 AM

by MrHoffman,Solvedanswer
MrHoffman MrHoffman
Level 6 (15,637 points)
Mac OS X
A:

Please read through the logs from the installation, looking for some information on what might be failing — that error seems to be a catch-all error, with various possible triggers.

 

As a near-last-resort and if you don't have much customization (as this'll clobber what you have), then the other option is to delete the existing settings and start over again.  (This reset sequence is the closest I've encountered in the official documentation.)

Posted on Sep 20, 2014 12:27 PM

Close
Rocky Pope

Q: Server 3.2.1 Installation Failure

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Sep 20, 2014 11:35 AM in response to Rocky Pope
    Level 10 (208,037 points)
    Applications
    Sep 20, 2014 11:35 AM in response to Rocky Pope

    Please read this whole message before doing anything.

    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.

    Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

    The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

    Test while in safe mode. Same problem?

    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

  • by MrHoffman,Solvedanswer

    MrHoffman MrHoffman Sep 20, 2014 12:27 PM in response to Rocky Pope
    Level 6 (15,637 points)
    Mac OS X
    Sep 20, 2014 12:27 PM in response to Rocky Pope

    Please read through the logs from the installation, looking for some information on what might be failing — that error seems to be a catch-all error, with various possible triggers.

     

    As a near-last-resort and if you don't have much customization (as this'll clobber what you have), then the other option is to delete the existing settings and start over again.  (This reset sequence is the closest I've encountered in the official documentation.)

  • by Rocky Pope,

    Rocky Pope Rocky Pope Sep 20, 2014 4:56 PM in response to Linc Davis
    Level 1 (120 points)
    Mac OS X
    Sep 20, 2014 4:56 PM in response to Linc Davis

    Thanks for the update.  I'll give it a try once I get the chance...

     

     

    Regards,

     

    Rocky

  • by Rocky Pope,

    Rocky Pope Rocky Pope Sep 20, 2014 5:00 PM in response to MrHoffman
    Level 1 (120 points)
    Mac OS X
    Sep 20, 2014 5:00 PM in response to MrHoffman

    Thanks for the provided "nuke" command.  Hoppefully I won;t need it.

     

     

    Regards,

     

    Rocky

  • by Rocky Pope,

    Rocky Pope Rocky Pope Sep 21, 2014 12:14 AM in response to MrHoffman
    Level 1 (120 points)
    Mac OS X
    Sep 21, 2014 12:14 AM in response to MrHoffman

    Here is some log data.  I haven'' had to time to actually do anything yet.

     

    Thanks,

     

    Rocky

     

     

    Process:         com.apple.serverd [24599]

    Path:            /Library/PrivilegedHelperTools/com.apple.serverd

    Identifier:      com.apple.serverd

    Version:         ???

    Code Type:       X86-64 (Native)

    Parent Process:  launchd [1]

    Responsible:     com.apple.serverd [24599]

    User ID:         0

     

     

    Date/Time:       2014-09-21 03:12:27.532 -0400

    OS Version:      Mac OS X 10.9.5 (13F34)

    Report Version:  11

    Anonymous UUID:  FFE8DC3F-C175-B932-CD4C-300B1698E4F0

     

     

     

     

    Crashed Thread:  0

     

     

    Exception Type:  EXC_BAD_ACCESS (Code Signature Invalid)

    Exception Codes: 0x0000000000000032, 0x000000010b978010

     

     

    kernel messages:

    -0 sec           CODESIGNING: rejected new signature for architecture 16777223 of file /Library/PrivilegedHelperTools/com.apple.serverd

    -0 sec           CODE SIGNING: cs_invalid_page(0x10b978000): p=24599[com.apple.server] final status 0x1000200, denying page sending SIGKILL

    -0 sec           CODE SIGNING: process 24599[com.apple.server]: rejecting invalid page at address 0x10b978000 from offset 0x0 in file "/Library/PrivilegedHelperTools/com.apple.serverd" (cs_mtime:1400622294.0 != mtime:1411116349.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:0)

    -10 sec           CODESIGNING: rejected new signature for architecture 16777223 of file /Library/PrivilegedHelperTools/com.apple.serverd

    -10 sec           CODE SIGNING: cs_invalid_page(0x109bc7000): p=24578[com.apple.server] final status 0x1000200, denying page sending SIGKILL

    -10 sec           CODE SIGNING: process 24578[com.apple.server]: rejecting invalid page at address 0x109bc7000 from offset 0x0 in file "/Library/PrivilegedHelperTools/com.apple.serverd" (cs_mtime:1400622294.0 != mtime:1411116349.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:0)

    -20 sec           CODESIGNING: rejected new signature for architecture 16777223 of file /Library/PrivilegedHelperTools/com.apple.serverd

    -20 sec           CODE SIGNING: cs_invalid_page(0x1014c9000): p=24554[com.apple.server] final status 0x1000200, denying page sending SIGKILL

    -20 sec           CODE SIGNING: process 24554[com.apple.server]: rejecting invalid page at address 0x1014c9000 from offset 0x0 in file "/Library/PrivilegedHelperTools/com.apple.serverd" (cs_mtime:1400622294.0 != mtime:1411116349.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:0)

    -30 sec           CODESIGNING: rejected new signature for architecture 16777223 of file /Library/PrivilegedHelperTools/com.apple.serverd

     

     

    VM Regions Near 0x10b978010:

    --> mapped file            000000010b978000-000000010b984000 [   48K] r-x/rwx SM=COW  /Library/PrivilegedHelperTools/*.serverd

        mapped file            000000010b984000-000000010b989000 [   20K] rw-/rwx SM=COW  /Library/PrivilegedHelperTools/*.serverd

     

     

    Thread 0 Crashed:

    0   dyld                           0x00007fff6cfff20f dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) + 369

    1   dyld                           0x00007fff6cfff05e _dyld_start + 54

     

     

    Thread 0 crashed with X86 Thread State (64-bit):

      rax: 0x0000000000000000  rbx: 0x00007fff54287eb0  rcx: 0xd500e194bd69bc81  rdx: 0x0000000000000001

      rdi: 0x000000010b978000  rsi: 0x00007fff6d02589c  rbp: 0x00007fff54287e50  rsp: 0x00007fff54287df0

       r8: 0x000000000000003d   r9: 0x0000000000000d80  r10: 0x00007fff6d032030  r11: 0x0000000000000202

      r12: 0x00007fff6cffe248  r13: 0x00007fff6cffe6b0  r14: 0x000000000000000e  r15: 0x00007fff6cffe4c0

      rip: 0x00007fff6cfff20f  rfl: 0x0000000000010202  cr2: 0x000000010b978010

     

    Logical CPU:     6

    Error Code:      0x00000004

    Trap Number:     14

     

     

     

     

    Binary Images:

        0x7fff6cffe000 -     0x7fff6d031817  dyld (239.4) <7AD43B9B-5CEA-3C7E-9836-A06909F9CA56> /usr/lib/dyld

     

     

    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: 11439429

        thread_create: 9

        thread_set_state: 6

     

     

    VM Region Summary:

    ReadOnly portion of Libraries: Total=288K resident=280K(97%) swapped_out_or_unallocated=8K(3%)

    Writable regions: Total=8448K written=8K(0%) resident=24K(0%) swapped_out=0K(0%) unallocated=8424K(100%)

     

    REGION TYPE                      VIRTUAL

    ===========                      =======

    STACK GUARD                        56.0M

    Stack                              8192K

    VM_ALLOCATE                           8K

    __DATA                              252K

    __LINKEDIT                           80K

    __TEXT                              208K

    mapped file                          88K

    shared memory                         4K

    ===========                      =======

    TOTAL                              64.6M

  • by Linc Davis,

    Linc Davis Linc Davis Sep 21, 2014 10:25 AM in response to Rocky Pope
    Level 10 (208,037 points)
    Applications
    Sep 21, 2014 10:25 AM in response to Rocky Pope

    Restart the computer in safe mode. Certain caches maintained by the system will be rebuilt.

    Safe mode is much slower to start up than normal. The next normal startup may also be somewhat slow.

    When the login screen appears, restart as usual (not in safe mode) and test. There's no need to log in while in safe mode.

    Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a software RAID, you can’t start in safe mode. In that case, ask for instructions.

  • by Rocky Pope,

    Rocky Pope Rocky Pope Sep 22, 2014 12:20 PM in response to Linc Davis
    Level 1 (120 points)
    Mac OS X
    Sep 22, 2014 12:20 PM in response to Linc Davis

    Thanks for the safe mode suggestion.  Now that I have some time available, I'll do the safe mode boot.  It take a lot longer, but at least it isn't as annoying as in previous version, such as 10.5, where you had to hold the key until you saw the safe mode prompt on the screen...

     

     

    Regards,

     

    Rocky

  • by Rocky Pope,

    Rocky Pope Rocky Pope Sep 23, 2014 12:59 AM in response to MrHoffman
    Level 1 (120 points)
    Mac OS X
    Sep 23, 2014 12:59 AM in response to MrHoffman

    Hi,

     

    I could tell once I launched the Server app (after booting in/out of Safe Mode), as it immediately went into the console (after I chose the applicable computer), and didn't ask to apply the update.  Thanks for the pointer.  I'd normally have thought of that, but I guess at 3:30 AM when I applied the update, I didn't feel like messing around for the solution.

     

    And worse yet, sorry Linc, as I mistakenly gave the credit for the solution to the other poster....

     

     

    Regards,

     

    Rocky