Daylite Server Admin - Error Code 300

Symptom

When you attempt to launch Daylite Server Admin, you see the error below:

Alt text

Why is this problem occurring

You may be getting this error due to one of the following reasons:

  • The database has been moved to another machine incorrectly
  • The database has been restored from a backup incorrectly
  • The Daylite Server user is missing from Mac OS
  • A server process ID file already exists
  • Permissions changed in the Daylite database environment

Solution

Because this issue can be caused by different scenarios there isn't a single quick fix. This article walks you through steps on how to resolve the issue. This article includes basic troubleshooting steps as well as advanced steps that require the use of terminal.

As a first step you in this case you should always restart the server computer.

You have restored the database using Time Machine or Migration Assistant

If you have restored from Time Machine or Migration assistant prior to this issue starting, follow the steps outlined in the article on how to recover after restoring from Time Machine or Migration Assistant.

The _dayliteserver user is missing from the Mac OS.

The _dayliteserver user is a hidden Mac OS X users which is required for Daylite Server Admin to run correctly. This use can be deleted if you have upgraded your OS and the user didn't migrate or if you have incorrectly moved the database from one machine to another.

To ensure that this user is on the system, reinstall Daylite Server Admin as this will recreate the user. For Daylite 5 users click here and Daylite 4 users click here

Advanced Troubleshooting Steps

This section discusses advanced troubleshooting steps which take advantage of Mac OS's terminal application. Please use caution when performing these commands and only use them if you are confident with terminal.

If you are unsure or uncomfortable, submit a support ticket to continue support.

For these steps you will need to review the output of the DLServerEnv log. To get to this log, follow the steps below:

  1. Open Finder and choose Go > Go to Folder
  2. Copy/Paste the following line and then hit return:
    • /Library/Application Support/Daylite Server 4/Logs
  3. Open the DLServerEnv.log file
  4. Review the output of these logs:

A server process ID file already exists

Alt text

If you are receiving this in your logs the issue is because of a left over PID file in the Daylite Server storage environment. This can occur if there was an improper shutdown of the Mac or power loss while Daylite Server Admin was running.

To resolve this issue do the following:

  1. Copy/Paste the following command in Terminal and then hit return:
    • sudo rm "/Library/Application Support/Daylite Server 4/Storage.dlsdb/Data/9_1/postmaster.pid"
  2. Add your computers admins password
  3. Once the command has been accept restart the Mac
  4. Launch Daylite Server Admin

Permissions changed in the Daylite database environment

Alt text

If you are receiving this in your logs the issue is because of incorrect permissions within the Daylite database environment.

This can occur if you tamper/move around the storage folder or migrate your data from one Mac to another incorrectly. This can also occur if using a 3rd party permissions/cache cleanup program as they can also adjust your permissions.

The change in permissions vary, and you will need to adjust the command depending on the specific error message in the logs.

As an example. In the case above fie folder 9_1 needs to have the permissions changed to 700 (owner can read, write and execute)

To resolve that:

  1. Copy/Paste the following command in Terminal and then hit return:
    • sudo chmod -R 700 "/Library/Application Support/Daylite Server/Storage.dlsdb/Data/9_1/"
  2. Add your computers admins password
  3. Once the command has been accept restart the Mac
  4. Launch Daylite Server Admin

Was this article helpful?


Thanks for your feedback


 please wait...
 

Still can't find what you're looking for?