Managed System Configuration Super User Issue

Hi folks ,
I have a strange error in Solman SP8 Managed System Config .
In Step 5 : "Enter System Parameters" , for entering super user , it throws an error even though the user credentials are valid.
This happens for some of the managed systems only . The error says : " Issue with connection to system <SID> <Client>".
It does not seem to be using the right RFC and I feel it is checking for the user in 000 client , regardless of which client we give . Because if we give 000 credentials it works.
Please help . As without this I cannot save any of the system parameters like Load Balancer URL etc.
Thanks,
Shaswat

I have seen this exact issue when my IE cached the page and was stuck with the client 000 RFC's selected on step 3.  I just exit managed sys config and clear my cache and start solman_setup again. To avoid this all together I set my IE to check for newer versions of stored pages every time I visit page. (under internet options -> general -> browsing history -> tempory internet files)
Then
In step 3 create the user to avoid security issues or auditor problems later on.  This way the SM_ADMIN_XXX will have the proper roles required. Please note (The user is not authorized to use a Trusted RFC (authorization object S_RFCACL). To authorize the user, assign the role SAP_SM_S_RFCACL manually).
Confirm there is no error and hit next.  For an explicit save. 
Now go to step 5 and select the client that the RFC's were created on and hit test credentials.
  This should solve your issue. 

Similar Messages

  • Managed system configuration step 8: No Admin User Id provided for TS SID

    Hello experts,
    I face the following problem in step 8 of managed system configuration (Configure automatically, SolMan 7.1 SPS 3):
    All Activities fail (except Activate services) with the following Details message:
    No Admin User Id provided for TS <SID> (ABAP)
    Any hint?
    Thanks and best regards, Basti

    Hi Sunny,
    I don't find anything where I can provide the user information. It just uses the actual user (SOLMAN_ADMIN). Can you tell me where to provide the user for this step?
    Managed system configuration -> step 8 Configure automatically -> SSO Setup
    Thank you, Basti

  • Managed system Configuration Diagnostics Prerequisites check fail

    Dear All,
      My solman_setup initial configuration part and basic configuration part all passed without error. And  when I do the managed system configuration part , first I choose the solution manager itself and the client 001 to config , and then the maintain connection passed OK , but in the next step , check Prerequisites, it fails. The Navigation Button just open a link to the SAP Service Market Place, and the IMG documentation just let me to see the note 1010428. The deatl part of the execuation result of the Prerequisites open a page but with error statement as below :
    Service cannot be reached
    What has happened?
    URL https://sapsolmgr.centurydsp.com:8000/webdynpro/dispatcher/sap.com/tcsmdnavigation/StandaloneApp call was terminated because the corresponding service is not available.
    Note
    The termination occurred in system SM2 with error code 404 and for the reason Not found.
    The selected virtual host was 0 .
    What can I do?
    Please select a valid URL.
    If you do not yet have a user ID, contact your system administrator.
    ErrorCode:ICF-NF-https-c:000-u:SAPSYS-l:E-i:SAPSOLMGR_SM2_00-v:0-s:404-r:Notfound
    HTTP 404 - Not found
    Your SAP Internet Communication Framework Team
    Any comment will be appreciated.
    Enddy.

    Hello Enddy,
    This sounds as if you have yet to configure the HTTP services in SPRO or have misconfigured them.  Please review your configuration for the HTTP Services as it should resolve your issue.
    Please review the diagnostics URL to see if it helps you out:
    http://service.sap.com/diagnostics
    Also, please review the following SAP Notes which will also guide you through diagnostics and solution manager setup/installation:
    1010428 End-to-End Diagnostics
    1145779 SAP Solution Manager 7.0 Installation
    1163836 Solution Manager Diagnostics required for troubleshooting
    Also pay attention to the relevant notes listed on the bottom of these. If you follow these documents, I'm sure you will have your issue resolved.
    Hope this helps you out!
    Thanks,
    Mark

  • SOLMAN_SETUP - Managed System Configuration - DBA_COCKPIT

    Dear SAP Colleagues,
    I am currently implementing SMD in my Solution Manager system. I use the guided procedure SOLMAN_SETUP. The first 2 phases - Initial and Basic Configuration are completed.
    I have starting the 3rd one - Managed System Configuration - Manual Configuration.
    I have started the "Configure DBA Cockpit".
    I have no problem with most of my managed systems (ERP, BI, EP)..
    But when I want to configure the DBA cockpit for my PI systems, I get error.
    Even if I personnaly there is nothing to do with the SAP Product, I get an error when I want to configure my all 3 PI system in DBA Cockpit.
    1. I select the Managed System in my list
    . The DB Host Name is automatically filled out.
    . The DB Name is automatically filled out.
    . The Schema Name (Optional) is also automatically filled out.
    2. Then I click on Next button and I get this error :
    The DB connection is no successfully tested.
    Please make sure the parameters below are correct and hit ....
    Database Name : XDS
    Datbase host : xdsci
    TNS Name : ???
    User Name : SAPXDS
    Password : ???
    Question :
    1. From where (SLD or SMSY) these information (Database Name, Database Host, TNS Name ...)
        related to managed system XDS are uploaded ?
        In other terms, where are these technical information pre-configured ? In SLD ? In SMSY ?
    2. How may I fix this issue ? I did not configure the other managed system and it perfectly works.
    Thanks in advance for your help
    Best regards
    CP

    Hi,
    I found this OSS Note : 1265070
    You can also connect directly to this link :
    https://websmp207.sap-ag.de/~sapidb/011000358700000074392009E
    Best regards
    CP

  • Change Management System configuration

    Dear Experts.
    I have some problem with Change Management System configuration, probably it hasn't installed properly,
    but I cannot tell certain description of the problem to the BASIS administrator.
    The problem is the following:
    At first, then I logon into CMS by the first time, in the tab Domain Data obligatory input fields CMS User and CMS Password are the empty. Whitch username anew password values I should input in those input fields?
    The other problem is then I'm trying to create the new Track: in the tab Track Data input Id and Name of the Track,
    and pushing the Save Button, in the left table it doesn't appear. And then I trying to add Software Components to the Track, pushing the button Add SC, but the component list is empty.
    Edited by: Sergey Tuzov on Apr 25, 2008 11:28 AM

    We has found the problem issue by our self.
    The user account for CMS has no role with permission to SLD component access.
    Therefore, there was no access to SLD resources: software component and others.
    Thanks' for you attention to my topic.

  • Link SAP PI 7.3 to SolMan 7.1 - error during managed system configuration

    All,
    I installed my diagnostics agent twice with different options:
    - Direct P4 connection via Java EE Dispatcher Node with port 5xx04
    - P4 connection via SCS message server with port 81xx
    In both cases I get an error during the managed system configuration of SAP PI 7.3: Remote error : Connection to P4 port of managed system failed.
    I'm a bit confused with the step Enter System Parameters. In the Java parameters section, I can only enter port 39xx. if not, I get an error.
    Also, I marked and unmarked the option concerning the ABAP user store, but the error persists.
    Please advice.
    Thanks a lot.

    Hi Allam,
    I checked the KBA and I think now, I have the correct HTTP port.
    The error I now get is S:CL_DIAGSTP_MESSAGE:483
    When I take the next step, Configure Automatically, I get this error during the Byte Code Adapter Installation phase when I open the Java URL stated in the navigation column:
    DIAG_WILY_MSG:157:S - com.sap.smdagent.vmmanager.VMManagerP4Exception: com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException: Access is denied to SAP System sid: check the connection credentials.More details about the error in agent 'sappi' log file (SMDAgentApplication.X.log).; nested exception is:
    com.sap.engine.services.security.exceptions.BaseLoginException: Error during authentication. For more information see the remote server traces.
    Any idea?
    Thanks.

  • Configuration Check Error in Managed System Configuration

    Hi dear experts,
    I come across a problem as the screenshot shows blew:
    I check some relevant information, but no issues found:
    1.
    DEWDFLSSC5062:/usr/sap/hostctrl/exe # ./saphostexec -status
    saphostexec running (pid = 7094)
    sapstartsrv running (pid = 7097)
    10:46:34 24.06.2014     LOG: Using PerfDir (DIR_PERF) = /usr/sap/tmp
    saposcol running (pid = 7130)
    DEWDFLSSC5062:/usr/sap/hostctrl/exe # cat host_profile
    SAPSYSTEMNAME = SAP
    SAPSYSTEM = 99
    service/porttypes = SAPHostControl SAPOscol SAPCCMS
    DIR_LIBRARY = /usr/sap/hostctrl/exe
    DIR_EXECUTABLE = /usr/sap/hostctrl/exe
    DIR_PROFILE = /usr/sap/hostctrl/exe
    DIR_GLOBAL = /usr/sap/hostctrl/exe
    DIR_INSTANCE = /usr/sap/hostctrl/exe
    DIR_HOME = /usr/sap/hostctrl/work
    service/admin_users = daaadm
    service/logfile_000 = /tmp/s
    service/logfile_001 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace*.trc
    service/logfile_002 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.*.trc
    service/logfile_003 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.trc
    And the version of hostagent is up-to-date.
    2.The URL
    - http://<SMDhost>:1128/SAPOscol/?wsdl
    - http://<SMDhost>:1128/SAPHostControl/?wsdl
    can be accessed.
    3.The step 3 in managed systems configuration is executed successfully.
    4.I have even uninstalled and re-installed the SMD and hostagent, and change the alert_timeout parameter in T-code DMD, but the issue insisted.
    5.Only a few SMDs in my landscape, so I think the parameter MaxThreadCount, InitialThreadCount, MinThreadCount should be no problem.
    Now I have no idea how to proceed, please give me some advice, thank you in advance.
    Best Regards,
    Pany Pan

    Hi Pany
    Kindly check the below two sapnote
    1935653 - Error "A timeout occured during the execution of the OS Command Console" when performing a Managed System Configuration - Solution Manager 7.1
    1865122 - Solution Manager 7.10 Configuration Check errors : "A timeout occured during the execution of the OS Command Console" "An unexpected error occured"
    Moreover , you need to check/verify/maintain the parameter in configtool
    ThreadManager -> MaxThreadCount
    Total number of Diagnostics Agents * 2 + 50
    1250
    ThreadManager -> InitialThreadCount
    Total number of Diagnostics Agents * 1.5
    900
    ThreadManager -> MinThreadCount
    Total number of Diagnostics Agents
    600
    ConnectionManipulator -> maxSoTimeOutConnections
    Total number of Diagnostics Agents * 1.35
    810
    ConnectionManipulator -> MaxParallelUsers
    Total number of Diagnostics Agents + 50
    650
    In Diagnostics Agent Troubleshooting - SAP Solution Manager Setup - SCN Wiki 
    guide check the section Required Solution Manager Java Stack Settings (Scalability)
    I face the same issue , which got resolved by maintaining the above parameters, maxthreadCount,
    minthreadcount , maxSoTimeOutConnections.
    With Regards
    Ashutosh Chaturvedi

  • Software Prerequisites in managed system configuration are not fulfilled

    Hello dear Forum,
    I'm facing a problem when I configure a PI system in managed system configuration. I register the  Netweaver PI AS ABAP technical system to solman's SLD directly(run RZ70), and collect the information of the Netweaver PI AS JAVA from the PI's sld. I don't know whether it matters.
    The following error occurs when I Check Prerequisites:
                   J2EE-FRMW does not fulfill the prerequisites (installed: 7.11 SP0, expected: 7.11 SP001)
    But I don't know how to find J2EE-FRMW 7.11 SP001 and do some update, please give me some advice.
    Best regards and thanks for your help,
    Pany

    Hi Pany,
    Steps to follow
    - Rename the J2EEFRMW01_5-20002637.zip file to J2EEFRMW01_5-20002637.SCA.
    -telnet localhost 5$$08
    -logon with the user administrator
    - deploy /software/j2eefrmwpatch/J2EEFRMW01_5-20002637.SCA version_rule=all
    - Once it is done , then trigger the data to the SLD
    - Checked the software component in SLD
    - Resync the LMDB with SLD
    - Then performed the activity of manage system Configuration.
    With Regards
    Ashutosh Chaturvedi

  • Managed system configuration: Some required roles have not been granted

    Hi experts,
    I face a strange problem in my SolMan 7.1 SPS 4:
    In the configuration of managed system everything is green except the last step "Check configuration" => "Configuration Check".
    The error is:
    Some required roles have not been granted to user SAPSUPPORT  (ID: MANAGED.DUAL.SAPSUPPORT)
    Action: Execute step Managed System Configurationn / Create Users
    Check Context: Managed systems users/roles | Managed users/roles | SYSTEM =LSM~ABAP
    and the same for SMDAGENT_xyz (ID: MANAGED.ABAP.WILYAGT).
    The funny thing is that the step no. 7 (Create users) is done successfully. I have also deleted SAPSUPPORT manually and have reexecuted step 7 but no success.
    Any ideas? Thanks and best regards, Basti

    Hello,
    Just a thought... it could be due to a UME role that is not assigned to the user. Have you checked the security guide?? There are a couple of steps to do in Visual Admin for this use as per the guide.
    Cheers,
    Diego.

  • Managed System Configuration step Assign Diagnostics Agent

    Dear Experts,
    We've newly instaled solution manager system 7.0 Ehp1 via latest sp stack 25 on aix 6.1, we've completed initial and basic configuraiton successfully via solman_setup, and instaled wily introscpe on same host with solution manager system,
    Now i am trying to managed system configuration for solution manager system via solman_setup step Assign Diagnostics Agent as demo link below
    https://service.sap.com/~sapidb/011000358700001735062008E
    I opend http://>SOLMANHOST>:<SOLMANPORT>/smd/go/ADMIN_AGENT
    >> Agent Candidates Management
    >>  Connection Parameters
    >> Custom SLD Parameters > Aply and the selected the SMD instance then trying to attached via password SMD_ADMIN
    But agent registration is waiting, SMD_ADMIN user is creating when i execute intial configuration, after i change the intial password, password is correct, so why the agent state is waitng status, i also push sld Setting for all from SMD view tab,
    I've also try to restart SMD agent, /usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log file after restart
    Oct 28, 2010 11:07:25 AM [Thread[main,5,main]] Info       Starting SMDAgent ...
    Oct 28, 2010 11:07:25 AM [Thread[main,5,main]] Info       ===> Establishing connection to server 'ms://ccisolman:8101/P4
    Oct 28, 2010 11:07:28 AM [Thread[Connector,5,main]] Info       Smd connector is disabled because no SLD association and no credentials found.
    Oct 28, 2010 11:07:32 AM [Thread[SLD-Registration,1,main]] Info       [SLDReg] Next try to push instance data in SLD is  Thu Oct 28 23:07:32 EEST 2010     
    Best Regards

    hi
    pls chk again your sld parameters and check the correct user name, password entered in agent connection management under CUSTOM SLD(in agent candidates management)
    jansi

  • Managed System Configuration ! The table does not contain any data !

    Hi,
    In Sol Man Setup , Managed System Configuration, in phase 6 - Create Logical Componets -
    There is no Product Version and Product Instance Available.
    The message is :  " The table does not contain any data "
    How can correct this problem ?
    Thanks

    Hi,
    while creating new Logical Component via SMSY , you need to specify Product first.
    e.g. if you managed system is ERP 6.0 , select Product as SAP ERP
    once you select Product , it automatically fetches information for product Version and Main Instance depending upon Product field input.
    Please check and let us know if issue still persits.
    Thanks,
    Rupali

  • Managed system Configuration : The JMX metrics of this Host / Byte Code Adapter are missing

    Hi Friends
    While Configuring EP system with SOLMAN 7.1 SP12 it is giving below message in self Diagnosis Phase.
    1. Solman system is already having ISAGENT version 8 and 9 installed (but Managed system is having 8)
    2. I have followed the automatic Process as below
    ==========================================
    Automated Installation of the Introscope Agent via SMD
    The Solution Manager provides an application that performs the setup of the Introscope
    byte code agent for Java automatically. This section explains the steps to run the setup.
    Before you can run the Introscope agent setup, the setup wizard for the managed system
    must have been executed.
    1.
    2.
    3.
    4. Launch the Introscope Setup application: SAP Solution Manager Configuration 
    Managed Systems Configuration  Step 7 Configure Automatically  Automatic
    Activity “Byte Code Adapter Installation”  “Open Java URL” (only available in edit
    mode). Your screen will look similar to the image below:
    5. Check the Enterprise Manager Settings at the top of the screen. These are the
    connection parameters that will be used by the agent to connect to the Enterprise
    Manager.
    6. In the pane Introscope Agent Setttings, select the system that you want to instrument
    with the agent. Check “select all” and click “Retrieve Current Settings”. This will display
    the current status of the agent setup.
    7. To initially setup or update the agents, click Setup Introscope Agent …. This will open
    the setup dialog as shown below. Select the desired agent version (by default only one
    available) and choose the profile. Next, check the desired instrumentation areas, and,
    in the case of AIX, review the AIX settings to match your environment (J9 or classic
    mode).
    8. Finally, hit Apply to perform the necessary changes in the agent configuration. Agent
    config files will be adapted and the Java VM parameters will be set as required for the
    managed system.
    ================================================================
    3. Restarted SAP but error still present.
    Please help to resolve the issue.
    Thanks

    Found the solution :
    1819577 - Workload Analysis data missing for Java systems when using ISAGENT 8.2.4.0
    Cause
    l This issue has been identified as product defect and documented in note 1273028
    Resolution
    l As mentioned in note 1273028, update to ISAGENT 8.2.4 Patch 1 timestamp: 2012-06-26, please proceed as described below)
    1. Enable the Maintenance Mode in the Agent Administration UI (http://solmanserver:port/smd/AgentAdmin)
    2. Deploy the file to the Solution Manager JAVA stack using the Software Deployment Manager (SDM)
    3. Disable the Maintenance Mode in the Agent Administration
    4. Execute again the activity 'Byte Code Adapter Installation' of the step 'Configure Automatically' in the 'Managed System Configuration' for the
    affected systems. This activity will deploy the new version of the
    Introscope JAVA agent in the managed system servers and reconfigure the JVM parameters to use the new version of Introscope JAVA
    Agent;
    5. Check from Introscope Agent Admin if "IS Agent State" contains value "Running but needs restart"
    6. Restart the affected managed system(s)
    Finally Solution is update your SOLMAN system patch ISAGENT 8.2.4.0 from patch 0 to 1 via SDM.
    Thanks
    Mukesh

  • Managed System Configuration - Software version and OS is not accepting

    Dear
    When i try to setup the PI system in solman 7.1 - Managed system configuration, below the error msg.
    Please help to sort it the problem
    Regards
    Jay

    Hi Pany,
    Steps to follow
    - Rename the J2EEFRMW01_5-20002637.zip file to J2EEFRMW01_5-20002637.SCA.
    -telnet localhost 5$$08
    -logon with the user administrator
    - deploy /software/j2eefrmwpatch/J2EEFRMW01_5-20002637.SCA version_rule=all
    - Once it is done , then trigger the data to the SLD
    - Checked the software component in SLD
    - Resync the LMDB with SLD
    - Then performed the activity of manage system Configuration.
    With Regards
    Ashutosh Chaturvedi

  • Managed System Configuration: SSO setup failed for Solution Manager 7.1 sp11

    Hi Folks,
    While doing Managed System Configuration for Soman system i am getting error in SSO Setup
    Currently I am in
    8. Configure Automatically :Single Sign On Setup
    This is i am going for managed System (Solution Manager System Itself)
    Below is error log..
    SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
    Screen shot attached.
    Found SID for SSO ACL entry : SMP
    Found login.ticket_client for SSO ACL entry : 000
    The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
    The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
    The SSO ticket Certificate <OU=J2EE,CN=SMP> has been successfully imported into ticket Keystore
    SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
    SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
    java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
    at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    The SSO ticket Certificate <CN=SMP> has been successfully imported into ticket Keystore
    SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
    SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
    java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
    at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Exception
    java.rmi.RemoteException: Caller not authorized.; nested exception is:
    java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
    at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:160)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
    at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    at com.sap.engine.services.security.exceptions.BaseSecurityException.writeReplace(BaseSecurityException.java:349)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:331)
    at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:910)
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1024)
    at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1344)
    at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1316)
    at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1260)
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1065)
    at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:282)
    at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:147)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:338)
    ... 8 more
    Regards,
    San

    Hi Sandeep,
    It seems authorization issue. Please check the below SAP Note :
    1988642 - Warning 'caller not authorized' in Step 'Single Sign On Setup'
    Hope this helps.
    Thanks & Regards,
    Nisha

  • Managed System configuration for SAP NW Java system in Solution Manager 7.1 SP10

    Hi All,
    I am doing Managed system configuration for my SAP NW 7.01 Java system and getting below error in step 6 create users SAPSUPPORT & SM_COLL_SID.
    "An unexpected error occured. An error occured while processing the UME command READ_USER from agent <hostname> : Server returned: 302 Found "
    I have checked my DAA as well as host agents are up and running fine. My Solution Manager is 7.1SP10.
    Please suggest.
    Regards,
    Manish

    Manish,
    Which UME you are using? portal/ABAP/LDAP
    Are you using the SOLMAN_ADMIN user while configuring.
    Also check the below forum.
    https://scn.sap.com/thread/1167282
    Regards,
    Raja. G

Maybe you are looking for

  • Change all icons of a file type in Yosemite?

    Hello, I just upgraded from a early 2011 MBP running Mavericks to a new Retina MBP running Yosemite. I did not use Migration Assistant as I wanted a fresh start and instead have copied over all of my data from a clone manually. I use Parallels 10 to

  • IWeb 3.0.2 will not open

    I'm on a MacBook 2.2 GHz Core 2 with OSX 10.5.8 and using iWeb 3.0.2 (is this the right forum?). Had begun a fairly large project, ran out of disk space, deleted / moved some extraneous files, rebooted, and iWeb will suddenly not start. Every time I

  • WBS Settlement error

    Hi, We have a negative balance in area 02 of AuC. We cannot settle that to asset as no negative values are allowed to fixed assets and we cannot change that setting too. Now we posted a manual correction entry to WBS and settled it to AuC to nullify

  • Best option to save data populated from a web service?

    I have manage to made a windows form that uses a web service to populate the data into a DataGridView. Then I have a column for adding comments next to each row. So a user could add some comments about this data for each row. Also I have a drop down

  • How does one use bluetooth to send and recive on t...

    sending and reciving via bluetooth using nokia lumia 610