Critical problem after update OS X Server 3.0,anyone can help me?

Question

first of all,forgive me using the "critical problem".... corz I am totally crazy now...Before I update,OS X server 2.2 working on OS X 10.8,and everything works fine.
After I upgrade to OS X 10.9 Mavericks, the old server app shows "can not work". Ok.... I download the OS X Server 3.0 and upgrade with it.
After it,the server app going crazy....
Original Toggle On Services include:
Time Machine,VPN,wiki,Message,File sharing,Calendar,Address Book,Mail
DHCP,DNS,Open Directory
Now working ok Services include:
DHCP,DNS
Now Toggle On but got problems Services include:
Open Directory,File Sharing
Problem with service:
Open Directorory
     Toggle as on in server app,but seems my local network account was crash.
     any existing user login to server,the server ask them to change password,but the chage not worked. It was stuck on the "change password".When I directly changing the password in server app, its also no response.
     If I create a new accout,the mail adrees will not be auto fill,and when I click "Create", a error windows showed "existing connection is not authenticated: password change denied", and the server app go crash. Re open it , new account shows "not allowed" in the list.
Time Machine,Calendar,Address Book
     Can't Login.... seems because Open Directory
File Sharing
     Using a server local account was ok.Can not login as a "network account",if I using Open Directory account, it stucks on change password window.
Mail
     Just after I upgrade the server app , it shows "ON",but when I telnet port 110 or 25, no response. I guess maybe the devocot didn't Starting up. So I toggle it to off and on again, the status showing "stating...." and got no response...
I am totally crazy... seems the Open Directorory was crash,also the mail server was crash...
Can anybody help me solve these problem?

Answer 1

Here's what I discovered just a few hours ago.
I had created a new Mavericks Server install, done the migration wizard from 10.6.8 and got the same errors. "Existing connection is not authenticated. Password chage denied". Performed sudo touch /var/db/openldap/migration/.rekerberize, yada yada. Then I ran through the whole gamut of trouble shooting and norrowed it down to this:
Before starting, make an archive of your previous OD (SL or Lion). After doing the migration your users may not be there and you have to reimport the LDAP again, sometimes after step 2 below.
1. Double check your DNS service on the server you're building. Make sure any test DNS names and real DNS names have correct corresponding IP addresses. I used two so I could switch back and forth from names and IPs. Set your local DNS in the network control panel to 127.0.0.1 so its referrencing itself while you build.
2. Double check your host name under 'fileserver' and correct any errors. The local and domain have to match. example: fileserver.local, fileserver.my.domain.com. Verify all hostnames and IP address and make sure they match in DNS service. Use changeip command in terminal if you wish, but under 'Fileserver' in the 'Server.app' menu it works fine. After this you may need to re-import from your original server's LDAP archive.
3. Run the "touch" commands listed above.
4. Reboot.
5. Archive your directory again and name it for referrence. Save it to a flash drive so you can use it again if you need to rebuild later (you probably won't)
5. (here's the kicker) Turn off OD and look at your certificates in Server.app. Generate a new self-signed certificate and assign everything to that. You might need to stop OD to change its cert. Delete any expired or unused certificates. Rerun the touch commands and reboot (to be sure).
6. reimport from the LDAP archive you just saved.
6. Go through your users and edit server access. (trick, hold down the option key to turn them all on per user with a single click.s I was able to add users, edit users and connect on AFP and SMB.
After I did this it all worked, even adding users. I even did a fresh build of Mavericks server and was able to just import from the new LDAP archive with no issues.