on 10-04-2005 6:14 AM
Hi,
I have created some iViews using .Net PDK for SAP.
I have added these iViews to a page. Then the page is added to workset. I have created a new role and assigned this workset to the new Role. Then I have created a new User and associated this user with the newly created Role.
Now the problem is whenever I login to portal using new user name and password I am able to see the workset as well as page and iViews. But these iViews are throwing following exception.
An Error occurred while processing one of the iViews on this page in the .NET server.
More information:
1. Default Trace
.
Exception id: 10:37_04/10/05_0037_6409650
However these iViews are running properly when I preview them from admin login.
What are possible causes/solutions for the above mentioned behavior?
Thanks for suggestions
Regards,
Vikas Khandpur
Hi Vikas,
You can find the exception details in the log file. The log file can be viewed from the System Admin>>Support.
Or try out this link
http://help.sap.com/saphelp_erp2004/helpdata/en/9d/9f173f5ff48443e10000000a114084/frameset.htm
Regards
gEorgE
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vikas
In the properties of the iview change the authentication to 'anonymous'. Then the iview will be accessible to all logins.
Regards
Geogi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Geogi,
Thanks for prompt reply.
Changing the authentication to 'anonymous' doesn't solve my problem. Still exceptions are coming.
However I am not sure the cause of exception is non admin login or not.
I have two user one is default - admin and other one which I have created.
The exception is coming whenever I am trying to see iView from new User's Login.
Regards,
Vikas Khandpur
Hi Vikas
Add the iview to the role of admin and check it is coming instead of taking preview.If this is working properly then the problem is with the permissions of the new user.The new user is not having required permissions for the iview content.You check for the required permissions in the system admin->permissions. Can you please explain the content of the iview..whether there is any other systems accessed from this iview..or any user based functionalities depending on logon..
Regards
Geogi
Hi Geogi,
I have added iView to role of admin. It is working properly.
So there may be some issue of permissions with new user.
Can you please tell me what kind of permissions need to given to new user?
My iViews are communicating with Web Service to display data based on user login.
Regards,
Vikas Khandpur
Hi Vikas,
All objects in the Portal Content Directory (PCD) contain a number of permission settings and levels, which determine their availability in the portal administrative environment (design time) and the end user environment (runtime). Role objects have an additional permission setting for defining which portal administrators are authorized role assigners.
Check out this link for more details
http://help.sap.com/saphelp_nw04/helpdata/en/f6/2604e505fd11d7b84200047582c9f7/frameset.htm
Regards
gEorgE
Hi Vikas
If your iView is based on a system object defined in your system landscape, you must assign end user permission for the relevant user, group, or role to the system object, as well. End user permission assigned to a system permits the iView to retrieve data from the respective back-end application through the system object at runtime.
On one hand, iViews automatically inherit their permissions from the role to which they are used. On the other hand, portal components and services inherit their permissions from the security zone or safety level to which they are assigned. Most generic portal applications intended for standard users in an organization should apply to either the no safety or low safety levels, and no additional role-specific permissions need to be assigned to their security zones.
Set the <b>SafetyLevel</b> in the portalapp.xml file of your application to <b>No_Safety</b> or <b>Low_Safety</b> and check again.
Hope that was helpful
Warm Regards
Priya
Hi Priya
Thanks for the response.
I have defined a system in System Landscape.
Can you please provide me the steps how can I assign end user permission to the relevant groups , role etc.?
One more thing when I add the new user to admin role I donot get any exceptions for iViews.
Can you please tell me what kind of permissions need to be given to new user?
Regards,
Vikas Khandpur
Hi Vikas
You should use the Permission Editor to assign user, group and role permissions to portal objects.
You can launch the Permission Editor in two ways:
1. Using the central Permission Editor
2. Using the object-specific Permission Editor
a. Launch the relevant administration tool or editor in the portal.
b. In the Portal Catalog, locate the object or folder to want to set or edit permissions for. Then, do one of the following:
i. Right-click the object and choose Open ® Permissions from the context menu.
ii. Open the object in the editor, and from the Display menu or drop-down list, choose Permissions.
To know how to set permissions in the permission editor, please refer to the following thread.
http://help.sap.com/saphelp_nw04/helpdata/en/f6/2604db05fd11d7b84200047582c9f7/content.htm
As for your doubt on why you are able to view the iViews from an administrator's login,it is because The standard super administer role is assigned maximum access to the entire set of portal initial content. The Super Administrator role is assigned by default to the Administrators group. Therefore, initially all standard administrator users have super administrator permissions in the portal.
Hope that helped.
Best Regards
Priya
Hi Vikas
Please follow this link.
http://help.sap.com/saphelp_nw04/helpdata/en/ab/a954036e164c7eaeca840144f267dd/content.htm
You can see all the default permissions there.
Hope that helped
Best Regards
Priya
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.