If you can't access the administration page with a web browser other than Safari, try with Safari. If you can't access it with Safari, try the following troubleshooting steps.

Check your DNS server

DNS settings are important when you're managing a Profile Manager deployment. If Profile Manager doesn't open, make sure your server points to a reliable DNS server.

If you can't push profiles or apps to clients

If you experience issues when you push profiles or apps to client systems, check the system log file in Console. If it reports that your server can't reach Apple's APNs servers, check your network's configuration. Make sure that all needed ports are open.

For more information, turn on APNS debug logging with these Terminal commands:

If you get other issues with Profile Manager

Profile Manager logs can help you fix issues with Profile Manager. You can find a symbolic link named "devicemgr" at /var/log. This file points to /Library/Logs/ProfileManager, where you can find these logs:

devicemgrd.log

Provides the status of querying and syncing Open Directory and Active Directory users and groups.

About transaction "failures"

Some of these logs might list transaction "failures" or retries. Most of these entries are expected and don't indicate an issue. These logged events are conflicts between attempts to modify the underlying PostgreSQL database at the same time. These kinds of failures retry until they succeed.

You can identify transaction conflicts when you see any of these notes in your log files:

Canceled on conflict out to pivot

could not serialize access due to concurrent update

@@@ Retry #X

@@@ Retry X

Use verbose logging to find more info

More information on how to fix an issue is sometimes available if you increase the log level. To gather the information you need, reproduce the issue after you increase the logging level.

When you're finished, revert to the original logging level. If you leave the logging level at a higher setting, it decreases the available space on your startup drive.

Turn on verbose logging

To increase the level of logging, use this Terminal command:

sudo debugDeviceMgr 4

This automatically restarts Profile Manager Service.

Turn off verbose logging

To revert the logging level back to its original setting, use this Terminal command: