‎2009 Sep 07 1:31 PM
Hello All,
When one of the user in CRM Sandbox system, tries to execute a report in the backkground, he gets the error -
"No Authorization for Printer LP01"
When i ran SU53 in another session it showed error for object S_SPO_DEV, authorization field SPODEVICE - LP01
User comparison was done for the roles assigned to the user.
But this did not help.
I checked in SU01, Printer defaults are maintained for the user. [default printer as LP01]
Any suggestions as to what else can be checked and how to resolve ?
Regards
Shubhra
‎2009 Sep 08 7:41 AM
Pls check the below mention 3 auth.objects and field name field values
S_SPO_ACT
S_SPO_DEV
S_SPO_PAGE
before checking the above check the local Pc printer driver are properly installed and whether he can able to take print out locally if user can, then go to su01 spool control output device enter LOCL this should be already configured through SPAD
‎2009 Sep 07 1:34 PM
User comparison was done for the roles assigned to the user.
But this did not help.
That would not help if the value does not exist in the authorization object. You need to add LP01 to S_SPO_DEV in on an appropiete role assigned to the user.
Regards
Juan
‎2009 Sep 07 1:46 PM
Hi Juan,
That is already there. I checked, the role has the object with value LP01.
‎2009 Sep 07 2:39 PM
‎2009 Sep 07 2:53 PM
Maybe the role's profile isn't up to date? You'd see that as a yellow traffic light on the authorizations tab in PFCG.
Have you tried reading the user buffer for htis user (SU56) to see the actual values for this object?
‎2009 Sep 07 3:17 PM
‎2009 Sep 08 6:22 AM
‎2009 Sep 08 7:41 AM
Pls check the below mention 3 auth.objects and field name field values
S_SPO_ACT
S_SPO_DEV
S_SPO_PAGE
before checking the above check the local Pc printer driver are properly installed and whether he can able to take print out locally if user can, then go to su01 spool control output device enter LOCL this should be already configured through SPAD
‎2009 Sep 15 7:03 AM
Thanks all of you.
All the authorization object values were maintained correctly.
We just removed and added the roles again and saved it. Now it works fine for the user.