Troubleshooting User Registration Issues

This topic describes problems that can occur when users are registered. To resolve the problem, look for it in the list of Symptoms or Error messages in Table 10-2.

Table 10-2 Troubleshooting User Registration Issues

Symptom or Error Message	Diagnostic Steps or Cause	Solution
Workflows do not appear in the Business Process Administration screen.	Your server or application is probably running on a different language from the database. For example, a DEU installation is running against an ENU database.	Check your setup. Using Server Manager, connect to the server and run the following command to verify the language: list param lang If the language code is incorrect, then run the following command: change param lang=LANGUAGE where LANGUAGE is your three-letter database language code. Restart the server.
When I click New User, either nothing happens or an error message appears.	Possible causes include: One or more of the necessary User Registration workflows have not been activated. The language of the application setup does not match the language of the database. The workflow is not activated properly.	To correct this problem: Activate the workflow processes described in "About Activating Workflow Processes for Self-Registration". Using Server Manager, connect to the server and run the following command to verify the language: list param lang If the language code is incorrect, then run the following command: change param lang=LANGUAGE where LANGUAGE is your three-letter database language code. Restart the server.
When I click finish, the following message appears: Error updating business component at step Insert New User	The problem can occur if the user being created already exists in the LDAP directory. This problem commonly occurs if the directory is not refreshed after deployment testing.	Try to create another user or use the LDAP console to check whether or not the user exists in the directory. Connect to the LDAP directory, but instead of creating a new user, right-click on People and select Search.
After I click Finish, the following message appears: View not accessible	The user was successfully created and could log in. However, the user did not receive the appropriate responsibility and so cannot access the view.	Change the New Responsibility field for the Anonymous User of the application to one that contains the necessary views.
When I click the New User link, nothing happens.	Most likely, some or all of the User Registration workflow processes are not activated; or if they are, the server needs to be restarted.	In the Administration - Server Management screen, restart only the necessary Application Object Managers. Restarting the server also works.
When I click Next in a User Registration view, nothing happens.	There might be another workflow that is being triggered which is disrupting the User Registration workflow. It is also possible that not all necessary workflows have been activated.	Activate all necessary workflows and deactivate any disruptive workflows. For information on these tasks, see: "About Activating Workflow Processes for Self-Registration" "Identifying Disruptive Workflows"
When I click Finish, an error is returned.	Possible causes include: The SecThickClientExtAuthent system preference is not set to TRUE. For information about this system preference, see "Setting a System Preference for Developer Web Clients". The Siebel Server has not been restarted since setting the system preferences.	Check to see if the user exists in the Person view in the Administration - User screen. If the user exists but was not given an entry in the LDAP directory, then that user cannot log in. You can also verify this by trying to create a user in the User view. If you can set the user ID and password, then try to log in as that person.