10.8.2 ML and 2.1 OS X Server.app Update

May be carefull: I've installed the Server.app update after updating ML from 10.8.1 to 10.8.2. After then, a dialog told me that the Server.app was replaced in the folder "Applications", the service was stopped and the service files were saved.

Starting the new Server.app let me gave no chance except to configure the server by ground with the configuration wizzard. Obviously after that, all the previous settings are lost.

Somebody else with this behavior? I encountered it with two 10.8.1 ML-servers (German-GUI), exactly the same way.

Thanks & Regards, Yann

I got the dialog as well. In my case all text was placed oddly and in wrong fontsizes. After entering my AppleID for push notifications the server.app is stuck on "Configuring services".

Did your wizard finish at all?

Hope there is a fix for this.

Hi MaartenP,

Good to know that I'm not the only one... I found nothing concerning this issue but read a couple of posts concerning the new server app. So it could be running.

Yes, my wizard finished after a couple of minutes, it maybe takes a few time to erase the configured services ;-\

Thanks, Yann

Message was edited by: apfelpom -- misspelled the name

Same here 😠

I had to manually start services that were active before the update (DNS, Mail, Calendar etc.). My SSL certificate was invalid for some reason. Also the server won't access the Internet anymore, although DNS is active, and other client can resolve addresses via this server.

Everytime there is an update on the server side, you need to hold your breath for the concequences. Very frustrating Apple!

Edit: forgot to mention:

1. when starting the Server.app an error occurs while reading the "servermgr_jabber service".

2. I am using 10.8.1 (didn't upgrade yet).

3. Server resolves names as well, but cannot open webpages, or enter the App Store.app (message: Cannot connect to the App Store).

Update:

I removed the server.app form my server and did a fresh install from the AppStore. The lay-out of the wizard was ok again. I walked trough the steps and the services turned up the way I left them before the update.

There must be something wrong in the replacement of the app during the update. The logs filled up with NIB files missing from Server.app.

Whish these update were less painful.

Make sure you walk through the network settings as well (if using DNS on the Server). The DNS Server field was empty in my case, causing some of my problems. It did not point to itself anymore for resolving (and forwarding) addresses.

In addition to all the issues noted above, my netinstall setup is broken and my old bootp settings for controlling dhcp are gone. Moreover, when I try to turn those services on to reconfigure I get errors about problems with settings files. I'm going to do a clean install. This is ridiculous.

I have the solution after this disaster...Happily i have a clone.

1- i add 8.8.8.8 (google dns) into the network panel dns (like this i don't loose Internet connection)

2- i stopped all the service before i updated to 2.1 and unchecked push certificates and stopped the certificates for all services.

3- don' t open the server app before a reboot

4- and now do the migration, it's worked for me

No issues here after applying the update.

After the update completed I restarted my Mac Mini, started Server and it began configuration as if it was a first time install. After configuration completed all previous services started except VPN. I manually started that service which added a duplicate VPN port mapping to my AEBS. Opened Airport Utility, removed the dup VPN port mapping and all is working like before.

I applied the update, and now nothing works. At first glance it behaves as though you've got the wrong password when you open server.app, but upon further investigation the server daemon won't start.

$ sudo /Library/PrivilegedHelperTools/com.apple.serverd

2012-09-21 08:07:53.849 com.apple.serverd[410:1d03] unexpected connection error: Connection invalid

Not helping. All of the above have been tried including restarts, and there are other posts from past versions on the daemons not starting, none of those helped either.

We are going to stop using the server for everything but open directory. Its a toy. One of the bugs this fixes is that the slider bar for configuring anti-spam was "backwards", in other words you had to set it to 35 to get it to use a spam score of 5.

I'm at the same point. This server will be removed from use. I'm done.

no, you don't have to do that ! that's normal your dns point to yourself !!

I use the dns from google just to initialize 2.1, after i removed it and I stay with the correct DNS that's pointing to itself...

I had a similar experience. My server was set to only have one dns resolve: 127.0.0.1. I noticed certain services didn't start and the attempt to renew the Apple Push Notification Certificate kept failing. Lo and behold, when I looked at Network Settings, there were NO DNS servers present. I returned 127.0.0.1, did a restart, renewed certs and all seems well now.