Bookshelf Home | Contents | Index | Search | PDF

Security Guide for Siebel eBusiness Applications > Troubleshooting Security Issues >

User Registration Issues

---

This section describes problems that may occur when registering users.

Workflows do not appear in the Workflow 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 list param lang to verify. If the language code is incorrect, you can run change parameter lang=language_code, where language_code is your three-letter database language code. Restart the server.

When I click New User, either nothing happens or an error appears

Possible causes include:

One or more of the necessary User Registration workflows have not been activated.
The language of your 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 Activating Workflow Processes.
Using Server Manager, connect to the server and run list param lang to verify. If the language code is incorrect, you can run change parameter lang=language_code, where language_code is your three-letter database language code. Restart the server.

When I click Finish, an "Error updating business component at step `Insert New User'" message appears

The problem is often that the user being created already exists in the LDAP directory server. The LDAP directory server is not refreshed and is shared by everyone. The user you are trying to create may be new to the database but may already exist 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 the user exists in the directory. Connect to the LDAP server, but instead of creating a new user, right-click on People and select Search.

After I click Finish, the "View not accessible" message appears

The user was successfully created and was able to log in. However, the user that was created did not receive the appropriate responsibility and 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 have not been activated; or if they are, the server needs to be restarted.

In the Server Administration screen, restart only the necessary Application Object Managers. Restarting the server will also work.

When I click Next in a User Registration view, nothing happens

There may be another workflow that is being triggered and is disrupting the User Registration workflow. It is also possible that not all necessary workflows have been activated. You must activate all the necessary workflows.

To deactivate a disruptive workflow:

In the Runtime Events Administration screen, click the Events view.
Query for Object Name is null. Aside from some application type events, there should be nothing else. In particular, be wary of any records whose Action Set Name begins with "Workflow." Such a record indicates that the workflow is triggered every time the event specified in the Event field happens. This can be particularly disruptive if the event is common, such as ShowApplet or WriteRecord. The Object Name normally constrains the actions to trigger only when the specified event occurs within the context of the object; for example, a specific business component or applet.
If there is a suspicious Event, drill down on the Action Set Name and note the ID following the string ProcessId in the Business Service Context field. Query against the database to find the suspect workflow: select NAME from S_WF_STEP where ROW_ID='xxx', where xxx is the previously noted ID.

That workflow is the disruptive one. Deactivate it.

When I click Finish, an error is returned

Possible causes include:

The SecExternalUserAdministration system preference is not set to FALSE.
The SecThickClientExtAuthent system preference is not set to TRUE.
The server has not been restarted since setting the system preferences. For information about the system preferences related to user authentication, see System Preferences.

Check to see if the user exists in the Person view in the User Administration screen. If the user exists but was not given an entry in the LDAP server, then that user would not be able to 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, try to log in as that person.

Bookshelf Home | Contents | Index | Search | PDF