Problem:
You have created a database user e.g. SIE_USR that is going to be used for anonymous login to perform various tasks. All the proper roles and privileges have been assigned to it but still it is not working.
Solution:
Whenever you create a database user you have to create corresponding user profile to it. Every user that has to login through Object Manager needs to have its user profile created in Siebel. If user profile for that database user doesn’t exist that user will not be able to login to Siebel through object manager.
You can create user profile by going to
Administration User ==> Employees View
In next post I will present a case study where we had to create database user and faced the problem mentioned above after forgetting the user profile creation of that user.
Read more!
Sunday, October 21, 2007
Siebel Database User not abel to Login
Posted by Neel 0 comments
Labels: Problem-Solutions
Tuesday, October 16, 2007
Drill Downs - Common mistakes made.
- We configure a drill down and we test it. It works fine and it takes us to the destination view that we have provided. Another user logs in for him the drill down disappear. It is just plain text field.
- When we click on the drill down it gives us an error
“You do not have permission to view this record or this record has been deleted” - Drill down is working for some users and some users are facing error while using that drill down.
The reason behind the problems mentioned above is Responsibilities. Yes, It is as simple as that.
Posted by Neel 2 comments
Labels: Problem-Solutions
Thursday, October 4, 2007
Siebel Dedicated Client - Executing Workflows!
Problem Statement :
Whenever we try execute a functionality in siebel dedicated client involving workflows we get an error message!
Problem Description:
Ever tried executing functionality that involved workflows from dedicated client. If you have then you must be familiar from this problem. Whenever you try to execute functionality in siebel which involves execution of workflows with the default CFG file you will get an error message. (Will update the post with exact error message)
Solution/Answer:
If you go through the CFG file you will see a section [InfraObjMgr] which contains a parameter:
RequestServerName = CHANGE_ME
Just update the value CHANGE_ME to the name of your workflow server, save your CFG and your problem is solved. Example given
RequestServerName = server2 (server2 will be the server where workflow manager resides)
Hope this post Helps you.If yes, Do post your comments!!!!
Read more!
Posted by Neel 0 comments
Labels: Problem-Solutions