This chapter covers typical problems in PeopleSync Agent. Listed below are some of the reasons and solutions to common problems.
Login to PeopleSync Console fails
Symptoms:
-
Error message “The application cannot connect to the specified database, because the latter doesn't exist, or its version is older than that of the application. (…)” after login.
Cause:
-
The Windows domain user has no sufficient permissions.
Resolution:
-
Check that the user is a member of the PeopleSync Admins group.
-
Check that the PeopleSync Admins group has Datareader and Datawriter permissions in the PeopleSync Database.
-
Check that the PeopleSync Admins group has Mbodify permissions for the file <PeopleSync Directory>\Console\LogonParameters.
PeopleSync is not licensed
Symptoms:
-
The PeopleSync log shows “Error” events of category “Licensing”.
-
The PeopleSync Service is stopped.
Cause:
-
PeopleSync is not licensed, license keys have not been copied to the proper directory or license keys have expired.
Resolution:
-
Make sure license keys have been copied to “Licensekeys” folder in the PeopleSync Agents’ installation directory (e.g. C:\Program Files\messageconcept GmbH\PeopleSync\Agent)
-
Verify that license keys are still valid by opening the license file in a text editor or reading the PeopleSync log entries.
-
Restart the PeopleSync Service.
PeopleSync Service stopped: Invalid user, insufficient rights
Symptoms:
-
The PeopleSync Service is stopped.
-
System event log shows errors with source “Service Control Manager” for service “PeopleSync Agent”
Cause:
-
The service user account password is invalid
-
The service user does not have sufficient privileges to run a service
Resolution:
-
Check that the service user account password is correct.
-
Make sure the service user account is an administrator on the local server.
PeopleSync Service fails to start: Database problem
Symptoms:
-
The PeopleSync Service is stopped.
-
Application event log shows errors with source “PeopleSync_Agent” and event text contains “System.Data.SqlClient.SqlException” and “DevExpress.ExpressApp.Updating.CompatibilityException”.
Cause:
-
SQL Server is unreachable
-
The database connection is wrong
Resolution:
-
Make sure the database is running and the service account running PeopleSync Service has sufficient rights in the database.
-
Search for “ConnectionString” in the agent.exe.config file located in the PeopleSync Agents’ installation directory (e.g. C:\Program Files\messageconcept GmbH\PeopleSync\Agent). Make sure the connection string is still correct.
Exchange GAL Agent fails to connect to WinRM server
Symptoms:
-
Error message 20900 in the event log: “Connecting to remote server ps.outlook.com failed with the following error message: WinRM cannot complete the operation.”
-
If you are using an Exchange Server on premise instead of Office 365, the server name might differ from ps.outlook.com.
Cause:
-
Agent connection to the remote server has been blocked by a local firewall or network firewall.
-
Problem with forwarding the traffic by a proxy server to the remote server.
-
The agent caused too many requests and run in Throttling state.
Resolution:
-
Check that the agent can communicate with the remote server.
-
Check the Throttling configuration in Exchange Server or Office 365.
-
Let the Exchange GAL Agent run less often.
Agent does not load data
Symptoms:
-
A PeopleSync Agent does not load data or is not running.
Cause:
-
Agent or address list may be disabled
-
Schedule is invalid
-
Agent configuration is invalid
Resolution:
-
Check that the agent and the corresponding address book are both enabled.
-
Check the validity of the Schedule. For example, a cron expression that contains the same number twice (e.g. 0,5,10,5) is invalid.
-
Check the PeopleSync log for errors regarding this agent. Verify that the agent’s configuration parameters are correct.