Server 10.8 Profile Manager error

I hope some one just help me out here:
Last week, shortly after the 2.2 update came out, I installed the update. Unfortunately, doing so made our NetInstall service run very badly. We rolled back the Server.app from a Time Machine backup. That caused out Profile Manager process to not be able to find it's info. I suspect it was updated with the first 2. update and rolling back the server.app confused it. So, we reapplied the update to 2.2. That allowed Profile Manager to work, and we have been living with the poorly working NetImage. Now, we seem to have an error with Profile Mamager not being able to start due to errors. I would like to restore the database from Time machine and perhaps even the postgreSQL and DeviceManager process to get it working, but I can't figure out which folders I need to restore. I've spent the better aprt of the day surfing for answers to a non functional Profile Manager, but nothing works.
What is the proper location for the Profile Manager database ?
How can I tell that postgreSQL is looking in the right place ?
Can I reindex the database to repair it ?

Similar Messages

Profile Manager Error Reading Settings code:-1

Hello,
I receive this error when I am going into Profile Manager tab on server. Any ideas?
Profile Manager Error Reading Settings code:-1

Did you ever find a resolution? If not then this might help Server: An error with code -1 occurred while setting up Device Management

PKCS12 certificate payloads in OS X Server 10.9 Profile Manager

Hi all,
I'm unable to successfully push .p12 packaged certificate identities to devices managed by OS X Server 10.9 Profile Manager. The problem is that while the file is pushed to the device, it doesn't get unpacked and hence is unable to be used.
I've identified the problem as Profile Manager setting the payload type incorrectly to "com.apple.security.pkcs1" in the profile rather than "com.apple.security.pkcs12". If I strip the profile signing data and edit it, the profile works perfectly when manually installed.
So the questions I have:
1) What's the best way of getting Apple's attention for someone to fix this bug, or is this possibly a browser JavaScript issue incorrectly identifying the payload type (using latest Safari though)?
2) Does anyone know of a workaround to allow this to still be automatically pushed out without having to manually edit and install on each device?
(SCEP is out at the moment due to another issue base64 decoding the SCEP request from Mac OS X devices that I'm taking up with the SCEP server vendor - but iOS works fine)
Thanks!
Al

I'm new to OS X Server and Radius, and have just spent way too many hours trying to figure out what I was doing wrong. I could connect to our enterprise wifi perfectly fine when selecting the certificate from the keychain, but I just couldn't get it to work when I uploaded the .p12 file and used it as the WiFi identity. I tried so many combinations of passphrase, no passphrase, pem format, pkcs12 format, resetting Radius server, resetting whole PKI... But I'd always see Certificate: ?Error_-25257? in the Settings window while I was trying to install the profile, and I couldn't see anything useful in the Radius logs when I tried to connect.
But it turns out, all I needed to do was:
sed -i '' -e '1s/pkcs1/pkcs12/;t' -e '1,/pkcs1/s//pkcs12/' wifi_profile.mobileconfig
(changes the first instance of pkcs1 to pkcs12 - don't change both! I was wondering why it was asking me for a password for our public certificate.)
Will try to update and see if that fixes the problem.

Push config files made in Server app with Profile manager

As I understand the manual you can distribuate configuration files with Profile manager.
A bit confused now when I want to use Profile manager to distribuate a configuration file I´ve made in Server app.
I saved a VPN configuration file and want to distribuate it with Profile manager but how do I import or add that file into the settings pane for my devices in profile manager?

Hi,
I have the same issue, very frustrating. Using a Win 2003 AD and 10.8.2 server and clients. If i use WGM I can see all users and groups correctly, but Server.app and Profile Manager does not show them correct.
Strange that we see issues like this since Profile Manager has been around for a while, really interested to hear other peoples experiences.
PS I see a similar thing here: https://discussions.apple.com/thread/4417085?start=0&tstart=0

Change Server URL in Profile Manager Enrollment Process?

It appears devices learn the IP or URL of their MDM server during the Profile Manager enrollment process. It must be part of the configuration profile sent to the device. It also appears this is based on the machine's host name. Is there anyway to change that URL - as when the host name of the server changes? If so, where are the files located on the server.
I believe in the previous iPhone Configuration Utility there was a "server URL" and "Check in URL" that could be set. We can't seem to find any parameters in Profile Manger to control the same. Thanks for any help.

Hi Jonathan,
I stumbled on your responses because I was looking for an answer to my own issues.
I am like most just a lay user, although wth 20 years Mac experience.
The issue is as folllows:
I set up Lion Server and I host a Wiki page and I try to run Profile Manager.
I do not have a registered host name. The hostname is server.name.private.
In order to reach the server from the Internet my clients use a DynDNS hostname such as "name.dyndns.org".
My clients can access the Wiki pages with no problems and Safari shows https://name.dyndns.org in the address line.
However, if they want to connect to Profile manager, the server re-directs https://name.dyndns.org/profilemanager https://server.name.private/auth?redirect=https://server.name.private/devicemana gement/api/authentication/callback
which the client's browser cannot resolve because the internal hostname is unknown to public DNS servers.
Why does Profile Manager redirect in the first place ?
Can this issue be resolved without obtaining an "officially registered" hostname ?
Thank you for helping.
Regards,
Twistan

Print server, AD, and Profile Manager

Having a number of issues that I can resolve regarding printing--I am trying to set up profiles in the Profile Manager, but printers are not available or visable. However they are visable in the workgroup manager. The printers reside on Windows print server (2008 R2). Further I can add the printers to my server, but they are not visable in the "Printer Sharing" section of "sharing". So with that, I have a few questions:
1. Do I need to turn on Kerberos in CUPS? User's don't authenticate to our printers via Kerberos, but via the Account manager of the individual printers.
2. Why do settings in Workgroup manager not apply? I can add the printers via LDAP the the new groups I have added, but when I open profile manager the changes or printers are not implemented.
3. How do I make printers visible in Profile Manager?
I have scoured the net and several manuals, but I can seem to stumble upon the correct answer.

Hi,
I have the same issue, very frustrating. Using a Win 2003 AD and 10.8.2 server and clients. If i use WGM I can see all users and groups correctly, but Server.app and Profile Manager does not show them correct.
Strange that we see issues like this since Profile Manager has been around for a while, really interested to hear other peoples experiences.
PS I see a similar thing here: https://discussions.apple.com/thread/4417085?start=0&tstart=0

Lion Server Profile Management error reading settings

After starting up Lion Server the profile management pane showed an error. It is also not possible to login via de browser to the profile manager. How can I fix this? Using the default httpd.conf file did not help.
This is one of the many problems I have with Lion server that does not work as expected. So if someone has a solution to remove all profile settings from my client MBP than I can try to revert back to Lion on my server also.
I hope this question is also read by someone of apple as this is not the quality I expected from apple. It lacks decent documentation and the setup of Portable Home Users is not possible. I thought apple product were self explaining and intuitive. This reminds me of the old Windows days: sitting days to figure it out and use a lot of terminal commands.

Did you ever find a resolution? If not then this might help Server: An error with code -1 occurred while setting up Device Management

Mountain Lion Server: Wiki and Profile Manager return 'Error Reading Settings'

Hi,
Have recently installed Mountain Lion Server (clean install) when I open the Server App I am constantly receiving the following error messages on various services inc. Wiki and the Profile Manager Service
After clicking on various other services that error message evolves into
Any help would be greatly appreciated.

Nvm, I managed to resolve this issue to a degree. The errors seem to occur if I copied and installed the Server.app from a windows network location where I had it stored. However if I downloaded and installed the Server.app from the App store the errors dod not occur.

Mountain Lion Server Profile Manager error

I recently setup a Mountain Lion server (10.8.2) to manage multiple ipads and Macs with Profile Manager in a PC oriented Active Directory environment.
I setup an SSL certificate and bound to the organization's active directory (with Directory Utility) and that all works fine.
We are now simply trying to assign the rights to individual users to use Profile Manager and running into trouble.
Using the Server app, we click on a user (or group) and then go to assign rights (with the gear menu).
The list of items to assign is supposed to come up.
Instead the list never comes up.
Can anyone shed any light on what we have to do?

What are you trying to do
Assign what users can use the profile managers web interface
or restrict what users can and can't have devices registered to their name in profile manager

Server 4.1 Profile Manager - Something Went Wrong

Hi,
I just updated my Mac Mini Server from 10.10.2 to 10.10.3, updating to Server 4.1.
It seemed to go okay, but now Profile Manager is messed up. When users try to log in, they get the message:
We're sorry, but something went wrong.
We've been notified about this issue and we'll take a look at it shortly.
(If you're the administrator of this website, then please read the log file "profilemanager.log" to find out what went wrong.)
When I look through the logs I find this:
[2015/04/09 23:15:47.194] F: ActiveRecord::StatementInvalid (PG::Error: ERROR: relation "view_all_user_groups_users_flat" does not exist
[2015/04/09 23:15:47.195] I: Rendering /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/public /500.html (500 Internal Server Error)
Any suggestions?
Thanks!
Frederick

mscott_mdm wrote:
Frederick,
Can you look at the /Library/Logs/ProfileManager/migration_tool.log file and paste in the last 50 or so lines?
Thanks for the help!
Here is the entire migration_tool.log file from updating:
[20723] [2015/04/09 17:13:17.136] -[SULogFileCollection setGlobalLogLevelPrefix:]: YES
0:: [20723] [2015/04/09 17:13:17.138]
    migration_tool-886.204 (PID:20723, OS:14D131, SERVER:14S1092, ARCH:x86_64) starting
    LA: migration_tool
0:: [20723] [2015/04/09 17:13:17.203] Waiting for postgres to startup....
0:: [20723] [2015/04/09 17:13:17.624] +[PGConnection reloadPreferences]: DBDebug = NO, DBLogNotices = NO, DBLogSQL = NO, DBMonitor = NO
0:: [20723] [2015/04/09 17:13:19.409] +[PGConnection reloadPreferences]: DBDebug = NO, DBLogNotices = NO, DBLogSQL = NO, DBMonitor = NO
0:: [20723] [2015/04/09 17:13:20.476] Dropping views...
0:: [20723] [2015/04/09 17:13:21.427] Dropping trigger functions...
0:: [20723] [2015/04/09 17:13:22.172] Dropping remaining non-dependent functions...
0:: [20723] [2015/04/09 17:13:23.810] MIGRATE_00885.001 completed successfully
0:: [20723] [2015/04/09 17:13:23.949] MIGRATE_00885.003 completed successfully
0:: [20723] [2015/04/09 17:13:24.566] EXCEPTION: Postgres <-[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-886.204/Compiled/Fr amework-Models/Postgres/PGConnection.m:339): "Postgres error 2BP01 (ERROR: cannot drop function dm_current_timestamp() because other objects depend on it
    DETAIL: default for table devices column last_update_info_time depends on function dm_current_timestamp()
    HINT: Use DROP ... CASCADE to drop the dependent objects too.
    )">
    USERINFO: {
        SQLSTATE = 2BP01;
        errorMessage = "ERROR: cannot drop function dm_current_timestamp() because other objects depend on it\nDETAIL: default for table devices column last_update_info_time depends on function dm_current_timestamp()\nHINT: Use DROP ... CASCADE to drop the dependent objects too.\n";
0:: [20723] [2015/04/09 17:13:24.566] SQL Module failed at statement:
    DROP FUNCTION dm_current_timestamp();
    -[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-886.204/Compiled/Fr amework-Models/Postgres/PGConnection.m:339): "Postgres error 2BP01 (ERROR: cannot drop function dm_current_timestamp() because other objects depend on it
    DETAIL: default for table devices column last_update_info_time depends on function dm_current_timestamp()
    HINT: Use DROP ... CASCADE to drop the dependent objects too.
0:: [20723] [2015/04/09 17:13:24.567] Caught unhandled exception -[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-886.204/Compiled/Fr amework-Models/Postgres/PGConnection.m:339): "Postgres error 2BP01 (ERROR: cannot drop function dm_current_timestamp() because other objects depend on it
    DETAIL: default for table devices column last_update_info_time depends on function dm_current_timestamp()
    HINT: Use DROP ... CASCADE to drop the dependent objects too.
0:: [20723] [2015/04/09 17:13:24.567] Migration failed at MIGRATE_00885.004 (final step is MIGRATE_00886.204)
0:: [20723] [2015/04/09 17:13:24.764] +[PGConnection reloadPreferences]: DBDebug = NO, DBLogNotices = NO, DBLogSQL = NO, DBMonitor = NO
0:: [20723] [2015/04/09 17:13:24.769] ShutdownMigrator: 2015-04-10 00:13:24 +0000
0:: [20723] [2015/04/09 17:13:24.770] BYE
[22210] [2015/04/09 22:45:34.642] -[SULogFileCollection setGlobalLogLevelPrefix:]: YES
0:: [22210] [2015/04/09 22:45:34.657]
    migration_tool-886.204 (PID:22210, OS:14D131, SERVER:14S1092, ARCH:x86_64) starting
    LA: migration_tool
0:: [22210] [2015/04/09 22:45:34.799] +[PGConnection reloadPreferences]: DBDebug = NO, DBLogNotices = NO, DBLogSQL = NO, DBMonitor = NO
0:: [22210] [2015/04/09 22:45:35.010] +[PGConnection reloadPreferences]: DBDebug = NO, DBLogNotices = NO, DBLogSQL = NO, DBMonitor = NO
0:: [22210] [2015/04/09 22:45:35.637] Dropping views...
0:: [22210] [2015/04/09 22:45:35.638] Dropping trigger functions...
0:: [22210] [2015/04/09 22:45:35.683] Dropping remaining non-dependent functions...
0:: [22210] [2015/04/09 22:45:36.515] EXCEPTION: Postgres <-[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-886.204/Compiled/Fr amework-Models/Postgres/PGConnection.m:339): "Postgres error 2BP01 (ERROR: cannot drop function dm_current_timestamp() because other objects depend on it
    DETAIL: default for table devices column last_update_info_time depends on function dm_current_timestamp()
    HINT: Use DROP ... CASCADE to drop the dependent objects too.
    )">
    USERINFO: {
        SQLSTATE = 2BP01;
        errorMessage = "ERROR: cannot drop function dm_current_timestamp() because other objects depend on it\nDETAIL: default for table devices column last_update_info_time depends on function dm_current_timestamp()\nHINT: Use DROP ... CASCADE to drop the dependent objects too.\n";
0:: [22210] [2015/04/09 22:45:36.548] SQL Module failed at statement:
    DROP FUNCTION dm_current_timestamp();
    -[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-886.204/Compiled/Fr amework-Models/Postgres/PGConnection.m:339): "Postgres error 2BP01 (ERROR: cannot drop function dm_current_timestamp() because other objects depend on it
    DETAIL: default for table devices column last_update_info_time depends on function dm_current_timestamp()
    HINT: Use DROP ... CASCADE to drop the dependent objects too.
0:: [22210] [2015/04/09 22:45:36.548] Caught unhandled exception -[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-886.204/Compiled/Fr amework-Models/Postgres/PGConnection.m:339): "Postgres error 2BP01 (ERROR: cannot drop function dm_current_timestamp() because other objects depend on it
    DETAIL: default for table devices column last_update_info_time depends on function dm_current_timestamp()
    HINT: Use DROP ... CASCADE to drop the dependent objects too.
0:: [22210] [2015/04/09 22:45:36.548] Migration failed at MIGRATE_00885.004 (final step is MIGRATE_00886.204)
0:: [22210] [2015/04/09 22:45:36.842] +[PGConnection reloadPreferences]: DBDebug = NO, DBLogNotices = NO, DBLogSQL = NO, DBMonitor = NO
0:: [22210] [2015/04/09 22:45:36.847] ShutdownMigrator: 2015-04-10 05:45:36 +0000
0:: [22210] [2015/04/09 22:45:36.848] BYE

Profile Manager "Error Reading Settings"

If you get the above error in the PM you may check the profilemanager.log for the entry "ServermgrDevicemgr: Exception caught No such file or directory - file_store/......". If so, it seems that the "Everyone Profile" is corrupt. In my case it was cause by a certificate. After I removed the certificate the PM seetings could be read again. I placed the certificate into another profile (device group) where it caused no trouble.
The certificate itself is valide and works well. I am not sure if this behaviour is a common bug in the PM or only related to my certifiacte.

I think what happened was that I tried to restart the Profile Manager from Server.app to see if that would clear up the error but it wouldn't start up again. However It turns out that I could start it from the command line with:
sudo serveradmin start devicemgr
Once I could get to the web UI and remove the certificate from Settings for Everyone, everything is working fine again. Thanks.

Help profile manager error

when I open profile manager gives me the following error:

this is what appears:
postgres:dataDirHasBeenInitialized = yes
postgres:PG_VERSION = "9.0.4"
postgres:dataDir = "/Volumes/BACKUP/Library/Server/PostgreSQL/Data"
postgres:postgresIsResponding = yes
postgres:dataDirIsDirectory = yes
postgres:PGserverVersion = 90004
postgres:dataDirExists = yes
postgres:setStateVersion = 1
postgres:state = "RUNNING"
macserver:~ admin$

Is there a way to have separate permissions between Server app and Profile manager?

I'm running OS X 10.10.1 (Yosemite) with Server app 4.0 installed.
I am a System Administrator for a University. I want to give our college techs the ability to manage Profile Manager, but if I grant them Admin rights on the Apple server they will also have access to the Server app, if they have the server app installed on their computer.
Is there a way to limit access to the Server app, but allow certain individuals admin right to Profile Manager?

This provides instructions:
How to use multiple iPods, iPads, or iPhones with one computer

Can I use OS X Server 4.0 Profile Manager to distribute iOS apps with iOS Developer Enterprise Program (iDEP)?

We are developing an iOS and complementary Mac OS X app for in house use by about 1500 users. I need to manage the devices and distribute the in-house app to these users.
We have an iOS Developer Enterprise Program (iDEP) licence.
Can I combine OSX Server and iDEP to distribute and manage the app? Or do I nee dot move to something like Air Watch?

You should not have to do anything the user/group import should be automatic and you should not have to manually create any accounts and it does onging syncs automatically but I do not know how often.
Once you are install and connect to profile manager all the accounts should show up just by clinking on users or the groups icons and they will work with that. You should not need to mess with them in the actual server application Although I would assume the other services all ink into the OD directory I don't know exactly how services like email, file sharing or VPN work as we have other more full featured better scaling services for that like MS Exchange for email/calendar and Cisco VPN.
We are only using OD, Profile Manager and Software Update.
Just a note I am using Server 3.2 on OS 10.9.5 if you are using Server 4.X your mileage will probably vary slightly as I am not sure what the areas of major change are.

OS X Server 10.7 Profile Manager - Force User Pin

Hi.
My company has hit a show stopper with OS X Server 10.7 and its Profile Manager. We would like to use OS X as a mobile device manager for iOS but we cannot find the option to force a PIN lock and deny the user the ability to remove the PIN lock. The iPhone configuration utility does have this option however. The user cannot remove the PIN without a master password that we define in the iPhone Config Utility.
The omission of this feature seriously undermines the usefulness of the Profile Manager.
Is this a known bug? Can a PIN lock be applied and not removed by the user in the latest OS X server 10.8?
Thanks for your help.
James

I'm new to OS X Server and Radius, and have just spent way too many hours trying to figure out what I was doing wrong. I could connect to our enterprise wifi perfectly fine when selecting the certificate from the keychain, but I just couldn't get it to work when I uploaded the .p12 file and used it as the WiFi identity. I tried so many combinations of passphrase, no passphrase, pem format, pkcs12 format, resetting Radius server, resetting whole PKI... But I'd always see Certificate: ?Error_-25257? in the Settings window while I was trying to install the profile, and I couldn't see anything useful in the Radius logs when I tried to connect.
But it turns out, all I needed to do was:
sed -i '' -e '1s/pkcs1/pkcs12/;t' -e '1,/pkcs1/s//pkcs12/' wifi_profile.mobileconfig
(changes the first instance of pkcs1 to pkcs12 - don't change both! I was wondering why it was asking me for a password for our public certificate.)
Will try to update and see if that fixes the problem.

Server 10.8 Profile Manager error

Similar Messages

Maybe you are looking for