1 2 3 4 Previous Next 57 Replies Latest reply: Apr 17, 2013 6:06 AM by rvschenck
sjolshag Level 1 Level 1 (0 points)

Hi,

 

After upgrading to ML, my calendar service didn't want to start.

 

There is a "Error reading settings" message in the Server window when selecting "Calendar". Additionally, when clicking the "on" button, I get the following error:

 

The error occurred while processing a command of type 'getLocationList' in plug-in 'servermgr_calendar'.

Where do I start troubleshooting this issue?

  • 1. Re: Calendar won't start after upgrade to Mountain Lion
    CeesBerrens Level 1 Level 1 (0 points)

    I've the same issue. Also contact server and imessage server are not starting.

  • 2. Re: Calendar won't start after upgrade to Mountain Lion
    noben Level 1 Level 1 (0 points)

    Same error here! And I didnt even use contact/imessage server in 10.7.4 :-( The migration assistent gave me an error to) Profilemanager, filecharing and OpenDirectory looks OK.

  • 3. Re: Calendar won't start after upgrade to Mountain Lion
    ~morgen Level 1 Level 1 (105 points)

    Look in /var/log/caldavd/servermgr_calendar.log for "getLocationList" to see if there are any errors.  A successful operation would look something like:

     

    [cal] 7/25/12 3:11:35 PM PDT : calendarServerOperationWithRequest

    [cal] 7/25/12 3:11:35 PM PDT : Sending to utility

    <?xml version="1.0" encoding="UTF-8"?>

    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

    <plist version="1.0">

    <dict>

            <key>command</key>

            <string>getLocationList</string>

    </dict>

    </plist>

     

     

    [cal] 7/25/12 3:11:36 PM PDT : returned from utility

    <?xml version="1.0" encoding="UTF-8"?>

    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

    <plist version="1.0">

    <dict>

            <key>command</key>

            <string>getLocationList</string>

            <key>result</key>

            <array>

                    <dict>

                            <key>AutoSchedule</key>

                            <false/>

                            <key>GeneratedUID</key>

                            <string>1119F7D2-21DA-4453-81F7-54E803F092FC</string>

                            <key>RealName</key>

                            <string>Morgen's test location</string>

                            <key>RecordName</key>

                            <array>

                                    <string>1119F7D2-21DA-4453-81F7-54E803F092FC</string>

                            </array>

                    </dict>

            </array>

    </dict>

    </plist>

     

     

    [cal] 7/25/12 3:11:36 PM PDT : No error from plist parser

    [cal] 7/25/12 3:11:36 PM PDT : Resulting dictionary

    {

        command = getLocationList;

        result =     (

                    {

                AutoSchedule = 0;

                GeneratedUID = "1119F7D2-21DA-4453-81F7-54E803F092FC";

                RealName = "Morgen's test location";

                RecordName =             (

                    "1119F7D2-21DA-4453-81F7-54E803F092FC"

                );

            }

        );

    }

     

     

    Possible problems could include not being able to read /Library/Server/Calendar and Contacts/Data/resources.xml or augments.xml, which is the source of information for the locations/resources list within Server.app.

     

    In a terminal window you could also try using the "calendarserver_manage_principals" utility to list locations, e.g.:

     

    % sudo calendarserver_manage_principals --list-principals locations

    Full name              Record name       UUID

    ---------              -----------       ----

    Morgen's test location 1119F7D2-21DA-4453-81F7-54E803F092FC 1119F7D2-21DA-4453-81F7-54E803F092FC

     

     

    Did you have any resources or locations defined for calendar server within Server.app prior to upgrading?

  • 4. Re: Calendar won't start after upgrade to Mountain Lion
    CeesBerrens Level 1 Level 1 (0 points)

    Yes, resources and locations were assigned to calendar.

  • 5. Re: Calendar won't start after upgrade to Mountain Lion
    CeesBerrens Level 1 Level 1 (0 points)

    And they were assigned prior to the upgrade.

  • 6. Re: Calendar won't start after upgrade to Mountain Lion
    ~morgen Level 1 Level 1 (105 points)

    What were the migration errors?

  • 7. Re: Calendar won't start after upgrade to Mountain Lion
    ~morgen Level 1 Level 1 (105 points)

    Look in /Library/Logs/Migration/calendarmigrator.log for calendar server specific migration messages.

  • 8. Re: Calendar won't start after upgrade to Mountain Lion
    noben Level 1 Level 1 (0 points)

    The only logfile in the Library/Logs/Migration/ folder:

     

     

    -------------------------------------------------------------

    Begin Mail Migration: Wed Jul 25 22:09:51 2012

    -------------------------------------------------------------

    purge: 0

    sourceRoot: /Library/Server/Previous

    sourceType: System

    sourceVersion: 10.7.4

    targetRoot: /

    language: sv

    Did not supply a valid language for the --language parameter, needs to be one of [en|fr|de|ja]

     

    Cant remember the message that the server.app displayed. Just something about not able to complete the migration.

  • 9. Re: Calendar won't start after upgrade to Mountain Lion
    ~morgen Level 1 Level 1 (105 points)

    Hmm, it sounds like migration exited prior to the calendar script running.  There should be an overall migration log in the /Library/Logs directory called ServerSetup.log I believe.  See if there are any errors there.

  • 10. Re: Calendar won't start after upgrade to Mountain Lion
    noben Level 1 Level 1 (0 points)

    true!

     

    It has lot of "Setup extra succeeded"....., but the file ends with:

     

    22:11:08.912 Setup extra succeeded:

    path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/CommonE xtras/smbsetup.sh

    RESULT CODE: 0

    STDOUT:

    STDERR:

     

     

    22:11:09.251 Setup extra succeeded:

    path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/CommonE xtras/webCommonSetup

    RESULT CODE: 0

    STDOUT:

    STDERR:

     

     

    22:11:09.267 Setup extra failed with code 1 at path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Migrati onExtras/001-migrationExtraServerRestore.pl

    22:11:18.604 touching SetupRegComplete

    22:11:18.604 touching ServerSetupDone

    22:11:18.604 touching PromotionDone

  • 11. Re: Calendar won't start after upgrade to Mountain Lion
    ~morgen Level 1 Level 1 (105 points)

    Looks like that failed script writes log output to /Library/Logs/Setup.log.  Any errors in there?

  • 12. Re: Calendar won't start after upgrade to Mountain Lion
    noben Level 1 Level 1 (0 points)

    Hm, sorry. I found more errors!

     

    22:09:14.233 Setup extra failed:

    path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Migrati onExtras/30-afctlmigrator.pl

    RESULT CODE: 1

    STDOUT: Did not supply a valid language for the --language parameter, needs to be one of [en|fr|de|ja]

     

     

    22:09:14.306 Setup extra failed:

    path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Migrati onExtras/30-ftpconfigmigrator.pl

    RESULT CODE: 1

    STDOUT: Did not supply a valid language for the --language parameter, needs to be one of [en|fr|de|ja]

     

    22:09:14.457 Setup extra failed:

    path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Migrati onExtras/30-natconfigmigrator.pl

    RESULT CODE: 1

    STDOUT: --targetRoot is the key for value /

    --sourceRoot is the key for value /Library/Server/Previous

    --purge is the key for value 1

    --sourceVersion is the key for value 10.7.4

    --sourceType is the key for value System

    --language is the key for value sv

     

     

    22:09:14.571 Setup extra failed:

    path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Migrati onExtras/30-serverperflogconfigmigrator.pl

    RESULT CODE: 1

    STDOUT: Did not supply a valid language for the --language parameter, needs to be one of [en|fr|de|ja]

     

    22:09:14.692 Setup extra failed:

    path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Migrati onExtras/30-snmpconfigmigrator.pl

    RESULT CODE: 1

    STDOUT: Did not supply a valid language for the --language parameter, needs to be one of [en|fr|de|ja]

     

    22:09:14.763 Setup extra failed:

    path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Migrati onExtras/30-xsannotificationsmigrator.pl

    RESULT CODE: 1

    STDOUT: --targetRoot is the key for value /

    --sourceRoot is the key for value /Library/Server/Previous

    --purge is the key for value 1

    --sourceVersion is the key for value 10.7.4

    --sourceType is the key for value System

    --language is the key for value sv

    sourceVersion := 10.7.4

    Did not supply a valid language for the --language parameter, needs to be one of [en|fr|de|ja]

     

     

    22:09:14.836 Setup extra failed:

    path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Migrati onExtras/50-vpnconfigmigrator.pl

    RESULT CODE: 1

    STDOUT: Did not supply a valid language for the --language parameter, needs to be one of [en|fr|de|ja]

     

     

    22:09:14.910 Setup extra failed:

    path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Migrati onExtras/58_jabbermigrator.pl

    RESULT CODE: 1

    STDOUT: Did not supply a valid language for the --language parameter, needs to be one of [en|fr|de|ja]

     

    22:09:51.870 Setup extra failed:

    path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Migrati onExtras/65_mail_migrator.pl

    RESULT CODE: 1

    STDOUT: Did not supply a valid language for the --language parameter, needs to be one of [en|fr|de|ja]

     

    22:09:53.035 Setup extra failed:

    path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Migrati onExtras/70_calendarmigrator.py

    RESULT CODE: 2

    STDOUT:

    STDERR: Usage: 70_calendarmigrator.py [options]

     

    70_calendarmigrator.py: error: option --language: invalid choice: 'sv' (choose from 'en', 'fr', 'de', 'ja')

     

     

    Everyone with: Did not supply a valid language for the --language parameter, needs to be one of [en|fr|de|ja]

    I use Swedish as my language in finder.....

     

    Message was edited by: noben

  • 13. Re: Calendar won't start after upgrade to Mountain Lion
    sjolshag Level 1 Level 1 (0 points)

    However, I use en as my language and the only error I found was

     

    Setup extra failed with code 1 at path: /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Migrati onExtras/70_calendarmigrator.py

     

    Only error in /Libaray/Logs/Migration/calendarmigrator.log is:

    calendarmigrator: Jul 25 15:43:58 Can't find previous carddavd plist at /Library/Server/Previous/private/etc/carddavd/carddavd.plist

     

    No relevant errors found in /Library/Logs/Setup.log

  • 14. Re: Calendar won't start after upgrade to Mountain Lion
    ~morgen Level 1 Level 1 (105 points)

    This isn't technically an error, just information:

     

    calendarmigrator: Jul 25 15:43:58 Can't find previous carddavd plist at /Library/Server/Previous/private/etc/carddavd/carddavd.plist

     

    What else is in /Libaray/Logs/Migration/calendarmigrator.log ?

1 2 3 4 Previous Next