Solman_admin password changes results in errors during managed system setup

Hello all,
I am trying to get Solman 4.0 EHP 1 to work, but get numberous problems.
Currently I have 6 messages at SAP, but no solution yet.
Situation:
Solman 4.0
SAP_BASIS     701     0003
SAP_ABA     701     0003
ST-PI     2008_1_700     0000
PI_BASIS     701     0003
SAP_BW     701     0003
CRMUIF     500     0001
SAP_AP     700     0014
BBPCRM     500     0013
CPRXRPM     400     0014
BI_CONT     704     0002
ST     400     0019
ST-A/PI     01L_CRM570     0000
ST-ICO     150_700     0016
ST-SER     701_2008_2     0002
So, it is uptodate.
The problem:
Changing the solman_admin password results in errors during connecting a managed system.
In the inital setup the solman_admin is created with a pasword.
After the basic setup I setup some managed systems.
In the meantime I had to change the password of solman_admin
I am logged in with solman_admin and do solman_setup to setup the managed system.
During the setup a process tries to logon back to the solman using solman_admin and the incorrect password.
This is the logging:
Step SSO Details
Found SID for SSO ACL entry : MSD
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (823 bytes)
A failure occured while connecting to ABAP stack on localhost sys=70 client=300 user=SOLMAN_ADMIN
!! Exception : Password logon no longer possible - too many failed attempts
A failure occured while importing ABAP SSO ticket certificate in ABAP stack
!! Exception : java.lang.NullPointerException
Java SSO ticket certificate of MSD was imported in ABAP PSE of kswv024.mob.local (client 300)
The Java SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=MSD LoginTicketClient=000)
Anyone else has this problem?
gr
Sander

Just for clarification it's Solman 7.0 EHP1 correct?
Also you may want to unlock the following user:
localhost sys=70 client=300 user=SOLMAN_ADMIN
Then if you navigate (in solution manager) to TCode solman_workcenter -> "Root Cause Analysis" tab ->"Agent Administration" menu item on the left -> "Applications Configuration" tab -> under the Agent Applications - Configuration menu on the left select "com.sap.smd.agent.application.global.configuration" -> Change the "Scope" drop down in the frame to the right to the SMD agent that you are using for "localhost sys=70 client=300" -> Click the "edit" button to the right of the Scope drop down box -> now find the entry below that lists "SOLMAN_ADMIN" as the user and find the corresponding password entry and update it with the new password that you changed it to -> click save and try the managed setup again.
Hope this helps, please let me know and we can go from there.

Similar Messages

  • Error during Managed system setup "Wilyhost Agent" type

    Hello All,
    Managed system setup finished with one error. Iam using this for selfmonitoring (solman itself as managed system)
    Error msg as follows.
    0 Wilyhost Agent(s) from host inbbssun02 are connected to the EM.
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (TDCTBI.india.tcs.com:6001) no Wilyhost Agent was detected from host inbbssun02. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
    I checked jvm_SMDAgent.out. and log as follows.
    /06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Introscope Agent Release 8.0.2.0 (Build 470970)
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.4.2_20-rev" from S
    un Microsystems Inc.
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.ag
    entProfile"
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Trying to load file from /usr/sap/SMD/J98/SMDAgent/applications.config/com.sa
    p.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Loaded file from /usr/sap/SMD/J98/SMDAgent/applications.config/com.sap.smd.ag
    ent.application.wilyhost/IntroscopeSapAgent.profile
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval i
    s set to 1800
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to
    500
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is
    set to 3000
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to
    locate the extensions directory.
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] The agent extensions directory /usr/sap/SMD/J98/SMDAgent/applications.config/
    com.sap.smd.agent.application.wilyhost/ext was successfully located
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Introscope Agent startup complete.
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent J98" based on the value of the System Pro
    perty "com.wily.introscope.agent.agentName".
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent J98
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
    1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
    1/06/10 02:55:30 PM IST [INFO] [IntroscopeAgent] Started Error Reporting service
    [p4://inbbssun02:50004] Agent ready.
    1/06/10 02:55:34 PM IST [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise
    Manager at TDCTBI.india.tcs.com:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "inbbssun02", Proce
    ss = "SAP HostAgent Process", Agent Name = "SAP HostAgent J98".
    Is there any seperate setting for wilyhost agent connection to EM ?
    Regards,
    Shyam

    I have restarted the agent at OS level and it appears in the Agent Admin page.
    I then re-ran the Managed System Config for this system and receive the same error.
    I have looked at the jvm_smdagent.out file on the wilyhost and found the following errors
    1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.
    1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] The agent extension property "introscope.agent.extensions.directory" is not set. No extensions will be loaded.
    1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] Introscope Agent startup complete.
    1/19/10 12:34:08 PM CET [WARN] [IntroscopeAgent.IsengardServerConnectionManager] The Introscope Agent is sending data to the Introscope Enterprise Manager too slowly.  Keeping the connection alive.
    The agent on the solution manager box is version 7.0 and the version od the agent on the PI box is 7.11
    Regards
    Stephen

  • No P4 connection could be established to SID during managed systems setup

    Hi,
    I get the following error when executing managed systems setup Create Users request.
    No P4 connection could be established to BJR
    No configuration found for key (BJR/sapj2ee/msgserver/host). DETECTED Self-managing scenario. You need to first adapt the connectivity of Diagnostics Agent used for the Managed system BJR, before you could proceed with this setup. Therefore change the Agent connection type for the BJR relevant Diagnostics Agent to P4 Dispatcher, before you run again this setup. This connection update has to be performed in the Agent Administration under Agent Connectivity. You could access the Agent Administration from the Root Cause Analysis Work Center when logged as Solution Manager Administrator.
    I have deleted and manually recreated SM_ADMIN_SOL, SAPSUPPORT and SM_COLL_SOL users, but still get the same issue.
    Message server ports etc are correct. Screenshot below.
    I have reviewed OSS note 1678469 but not resolved the issue.
    Any ideas will be appreciated.
    Regards
    Tariq

    Hi,
    As stated please review how do you register dia agent in solution manager, you can check in step 4 assign diagnostic agent in solman_setup.
    further review the below doc for dia agent registration via P4 port  Diagnostics Agents - SAP Solution Manager Setup - SCN Wiki
    Thanks
    Jansi

  • 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.

  • Solution Manage Diagnostics - error in the system setup

    Hello,
    I have installed SMD and I installed one system with the Setup Wizard of the SMD. According to the result of the setup, it was successful.
    However, when I do a self check in SMD, I get the five following errors in the Monitored Setup node :
    5 error(s) found:
    No DB agent autoconfig status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
    No JVM startup parameters setting status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
    No Roles assignment status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
    No SSO Setup status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
    No Telnet agent autoconfig status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
    Can anybody help me ?
    Thank you

    If you goto http://server:port/smd >>> Diagnostic Setup >>> Diagnostic System >>> Setup Wizard, do you have a message similar to:
    Last Diagnostics setup wizard execution on Tue Oct 09 13:34:44 2007 :
    - 0 setup steps disabled by user
    - 13 setup steps succesfully executed
    - 0 setup steps executed with warnings
    - 0 setup steps in error
    If you do, your Diagnostic server is correctly setup.
    For Managed system, same thing, http://server:port/smd >>> Diagnostic Setup >>> Managed Systems >>> Setup Wizard, or check setup results to make sure it's completed.

  • Error in Managed System Configuration - Sol Man 7.1

    Dear Experts,
    Whle configuring using solman_setup, I am getting below mentioned error in Managed System Configuaration:
    Cannot retrieve CIM Instances from CIM Class 'SAP_DiagnosticsRelevantSoftwareFeature'!
    Cannot  retrieve all CIM Instances from CIM class name 'SAP_TechnicalScenario' via LMDB Mass Access API!
    Cannot retrieve all CIM Instances from CIM class name 'SAP_DatabaseSystem' via LMDB Mass Access API!
    Any suggestions??
    Regards
    Vivek

    Hi Paul ,
    Thanks for the note that you provided.
    I am reconfiguring the LMDB and conteny Sync... The refresh will take 15-16 hours.. I am just waiting for the
    sync to be finished. Let's see what is in the store for me
    Keeping my fingers crossed untill then.
    Regards
    Vivek

  • Managed System Setup Wizard: which J2EE-Admin-User

    Hello,
    I'm running the managed system setup wizard in the diagnostic.
    In the setup of the parameters, I have to enter the J2EE-Admin-User. But which one?
    I tried:
    SMD_AGT_ADM (Dialog user with admin roles on both stacks)
    SMD_AGT_ADM (Communications user with admin roles on both stacks)
    The user was created by me before the setup. But regardless of the user settings, I get the following error:
    A logon failure occured on frces4139/SM7/00 (192.168.1.139).
    System Setup aborted, to prevent locking the User Account.
    Please check error details, specify a valid User/Password if necessary, and start Setup again
    Any ideas? Which user or user settings have to be maintained?
    Thanks,
    Jan

    Hello,
    I think the user you need to enter here is the j2ee_admin user or another user with SAP_J2EE_ADMIN role.
    Regards,
    Benjamin Rouger

  • Managed System Setup / Configure Diagnostics for Solution Manager itself

    Hello,
    I'm trying to run the "Managed System Setup" for the Solution Manager itself and
    I got a problem in the step 4 (Diagnostics Configuration / Configure Diagnostics):
    In the new opened window is only the ABAP stack displayed and the Java stack
    is missing.
    Does somebody know how to make the java stack visible?
    From my point of view seems the configuration of the SMSY ok. The java stack is also
    as "relevant" set.
    The Solution Manger 7.0 EHP1 is on SP25.
    Thanks in advance for your help!
    Kind regards,
    Joern

    Hi Jorn,
    I dont think its happening just because of your CR Content.
    Still If you want to update it,then go to Administration Tab in SLD->>Import the latest CR Content from there.
    As the latest CR Content is :SAP CR Content Version (sld/active):     SAP_CR 7.6 (produced 11/17/2011)
    And Jorn if you are stucked in the Diagnostic Agent registration then Go to Agent Candidate Administration->>In connection
    Parameters Tab go to->>Custom SLD Connection Parameters->>Apply->>Mark the Diagnostic Agent you want to
    connect->>Attach->>Give the password of the SMD_ADMIN->>Apply->>This way you will connect to the available Diagnostic
    Agent.Hope this will help your problem.
    Thanks & Regards
    Ajitabh
    Edited by: jitu001 on Dec 23, 2011 5:47 PM

  • SMD - MANAGED SYSTEM SETUP WIZARD.

    Hi,
    I'm on Solman SPS 15, trying to setup EWA for portals.
    Ran the managed system setup, got the error.
    Step DataCollect Details
    Initial Data Collect ERROR for host XXXXXXX
    !! Exception : Tue Jun 24 11:03:08 EDT 2008 | storeComponentVersion(...):ComponentVersion ComponentVersion [SAP J2EE ENGINE 7.00][01200314690200004229][N/A][N/A]:Cannot insert/update/delete the component '[IComponent: key=1199734241239977, name=SAP J2EE ENGINE 7.00, internalVersion=7.00   PatchLevel 29172.450, ppmsId=01200314690200004229, date=Tue Jun 24 11:03:06 EDT 2008, status=[N], mod=[M], messageServer=XXXXX:3901, masterComponent=true]'! Please see log for next warning(s).
    com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: Tue Jun 24 11:03:08 EDT 2008 | storeComponentVersion(...):ComponentVersion [SAP J2EE ENGINE 7.00][01200314690200004229][N/A][N/A]:Cannot insert/update/delete the component '[IComponent: key=1199734241239977, name=SAP J2EE ENGINE 7.00, internalVersion=7.00   PatchLevel 29172.450, ppmsId=01200314690200004229, date=Tue Jun 24 11:03:06 EDT 2008, status=[N], mod=[M], messageServer=XXXXXX:3901, masterComponent=true]'! Please see log for next warning(s).
    at com.sap.sup.admin.scheduler.task.remote.AbstractGatherRemoteTask.checkTaskResult(AbstractGatherRemoteTask.java:42)
    at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.parseXml(InitialConfigGatherTask.java:107)
    at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.process(InitialConfigGatherTask.java:68)
    at com.sap.sup.admin.scheduler.config.DataCollect.execute(DataCollect.java:138)
    at com.sap.sup.admin.setup.AppCfgTasks.runInitialDataCollect(AppCfgTasks.java:57)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:305)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:263)
    at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:655)
    at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:28)
    at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:903)
    at java.lang.Thread.run(Thread.java:534).
    Plz advise.
    Thx in advance.

    #1.#00144F17012A00C700000018000066BD0004506CFD4B5C16#1214328943107#/Applications/AdminConsole/ConfigurationChangeReportingUpload#sap.com/tcwddispwda#com.sap.sup.admin.upload.configreport.xml.ConfigurationChangeHandler#J2EE_ADMIN#16932##XXXXX_SID_28888050#J2EE_ADMIN#0964c860421111dd94ec00144f17012a#Thread[Thread-83,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/Applications/AdminConsole/ConfigurationChangeReportingUpload#Plain###[7498] storeComponentVersion(...):ComponentVersion [SAP J2EE ENGINE 7.00][01200314690200004229][N/A][N/A]:Cannot insert/update/delete the component '[IComponent: key=1214257551084558, name=SAP J2EE ENGINE 7.00, internalVersion=7.00   PatchLevel 29172.450, ppmsId=01200314690200004229, date=Tue Jun 24 13:35:42 EDT 2008, status=[N], mod=[M], messageServer=XXXXX:3901, masterComponent=true].
    I found this in application log
    Edited by: Kobby bryant on Jun 24, 2008 7:39 PM

  • Managed System Setup Wizard Status " ? " SPS 15

    Dear All,
    I have a problem with my SMD.
    I have already upgrade the Solution Manager 4.0 from SPS 13 to SPS 15.
    I want to setup E2E Root Cause Analysis for CRM system.
    So I configured SMSY since I didn't configure SLD yet.
    I've already installed SMD Agent in managed system successfully also.
    When I run the Diagnostics Setup -> Managed System -> Setup WIzard,
    in the Setup Parameter Step , it said that " No SMD Agent is currently available (ie not assigned). Please install an agent for jktgrhxsapc1 or unassign an existing agent in Agent Administration  Why is that so ?
    In the Agent Administration ( DIagnostics Administration -> Managed SYstem -> Agent Administration) found that the agent is online.
    Second, In managed system setup wizard - System Selection Step, there's an unknown system with SID '???' and  the status said that 'Some SMD Agent Runnning on host not belonging any successfully published solution' . Where can we find the log if we have an error when publishing solution ?
    Thanks in advance,
    Adhi

    Hi Labinot,
    I have checked the agent log looks like no error,
    id loaded TTL refType
    applications:com.sap.smd.agent.application.global.configuration true 0 strong
    applications:com.sap.smd.agent.application.tracing true 0 strong
    applications:com.sap.smd.agent.application.wilyhost true 0 strong
    applications:com.sap.smd.agent.application.flightrecorderdumpscan true 0 strong
    applications:com.sap.smd.agent.application.telnet true 0 strong
    applications:com.sap.smd.agent.application.filesystem true 0 strong
    applications:com.sap.smd.agent.application.logviewer true 0 strong
    applications:com.sap.smd.agent.application.remotesetup true 0 strong
    applications:com.sap.smd.agent.application.database true 0 strong
    applications:com.sap.smd.agent.application.datacollector true 0 strong
    applications:com.sap.smd.agent.application.runtime true 0 strong
    applications:com.sap.smd.agent.application.connectors true 0 strong
    applications:com.sap.smd.agent.application.wily true 0 strong
    Apr 10, 2008 7:13:07 PM [Thread[SMDAgent connection thread,5,main]] Info       [p4://jktgrhxsapl1:50604] Registration done.
    Apr 10, 2008 7:13:07 PM [Thread[SMDAgent connection thread,5,main]] Info       [p4://jktgrhxsapl1:50604] Agent ready.
    Apr 10, 2008 7:27:25 PM [Thread[Thread-37,5,main]] Info       Returned service object :com.sap.smd.core.runtime.agent.LogService@14cee41f
    Apr 10, 2008 7:27:26 PM [Thread[Thread-34,5,main]] Info       Returned service object :com.sap.smd.core.runtime.agent.LogService@14cee41f
    any other idea?
    -Adhi-

  • RCS Managed system setup

    Hi,
    Do we need to re run managed system setup wizard, each time system stack or EHP is updated ? or even when solman stack is updated ?
    Reason: We recently updated solman to SPS27 after which I dont see any data collection happening specially for User Load for ABAP systems
    and none for java
    BR,
    Shyam

    Hello,
    Run transaction solman_setup and check in the OVERVIEW what are the Open Activities listed in Basic and Initial Configuration.
    All activities there must be redone, grey, red or green.
    In these tasks there will be the Diagnostics Configuration. This step includes setting the Maintenance Mode ON and OFF, which will stop all agents and deploy the new software to them (the so-called agelets that are delivered centrally from Solman LM-SERVICE to the managed system's SMD Agent).
    This is all you must execute after a LM-SERVICE upgrade.
    Therefore there's no reason to rerun the whole setup wizard, as it may cause issues with wrong parameters in the setup wizard. If the managed system is working perfectly and this is only an upgrade, it is not recommended to do the setup wizard again.
    Best regards,
    Guilherme
    Edited by: Guilherme Balbinot on Jul 15, 2011 8:37 AM
    Edited by: Guilherme Balbinot on Jul 15, 2011 8:41 AM

  • 'Check  covered levels OKS'  process results in error during QA checkup

    Hi,
    The following process in QA test, before submiting a service contract results in error.
    'Check covered levels OKS' with the error message
    "Atleast one covered line is required".
    I'm not able to choose any product.
    How to set the covered level as product in service contracts?
    In the service contracts authoring window, under lines tab -->pricing/products-->
    effectivity
    line number
    level- covered product. But the lov in name field doesn't list any value ?
    what could be the possible reason for this?
    Regards,
    Nithya

    Well, I think I can only give some limited info about these questions since I am only a contracts user, not a developer or administrator.
    But here's a few things that might help.
    1 & 2) I have always created contracts from scratch where I work. They can't seem to get OM to create contracts correctly (so I can't help with question 2). I don't use OM except for inqueries.
    When you create such a contract, it should show up in the Install Base (IB) if you look up the IB record with the related Reference Number (which changed to Product Number in the IB when my company switched from 11.5.5 to 11.5.8). In my case it was the Contracts tab in 11.5.5 (Java interface) and the Contracts link in 11.5.8 (HTML interface).
    3) From my experience, the Contract Number is the Sales Order Number in View Transactions if you had the AR Interface checked in the contract.
    If you want to change from not having the AR Interface checked to having it checked, I think this works fine and the contract will bill the next time the Main Billing program is run after you make the change, as long as the Bill On Date (11.5.5) or Invoice Date (11.5.8) is set to the current date or earlier. An Invoice (INV line item with invoice # -99) will show up in the Billing History after the AR to Contracts Interface program is run. The actual invoice # will show up in this Billing History after the Invoicing programs are run.
    In 11.5.5, if our contract started in the future, we not only had to make sure the Bill On Date was current or earlier, but also run the Main Billing program on that contract with a date equal to or later than the end date of the contract we wanted to bill before it would work. Do not do this on all your contracts at once if you have recurring billing on any of them. You must run it on the individual contracts, otherwise the recurring contracts will bill in full. This is supposedly fixed in 11.5.8, since you can use offsets of more than 31 days on the invoice date, but we haven't billed any yet, so I can't say for sure.
    I had problems with billing when trying to change the ammounts in the line items after the billing program had already invoiced a contract in 11.5.5 and haven't tried this in 11.5.8 (it billed incorrect ammounts on the successive invoices).
    Note that we have a highly customized version of Oracle Applications 11i, so your results may differ somewhat.

  • 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

  • Error during a system copy with HANA DB

    Hello,
    I´m doing a system copy in a SAP ERP 6.0 EHP7 with SAP HANA DB.
    During a homogeneous system copy procedure with SWPM, it show me the following error during the phase Database refresh postload-activities.
    I checked some log files:
    -- sapinst.log:
    ERROR 2014-08-24 16:14:01.109
    MSC-04120  Creating a license signature failed:
    ===...could not load SSF library S:\usr\sap\\D00\exe\sapcrypto.dll .
    ERROR 2014-08-24 16:14:01.109
    MSC-04120  Creating a license signature failed: 543 wlikey_sign_for_installer: Couldn't load SAPSECULIB ("S:\usr\sap\\D00\exe\sapcrypto.dll") using function SsfSupInitEx (), rc = 10 (no library).
    ERROR 2014-08-24 16:14:01.109
    MSC-04120  Creating a license signature failed: 542 wlikey_sign_for_installer: At least one more attempt to load the SAPSECULIB will follow.
    INFO 2014-08-24 16:14:01.234
    Switched to user: ASCENDUMCE\ed1adm.
    INFO 2014-08-24 16:14:01.343
    Creating file C:\Program Files\sapinst_instdir\BS2013\BS2013SR1\ERP607SR1\HDB\COPY\SYSTEM\STD\AS-ABAP\REF\saplikey.log.
    INFO 2014-08-24 16:14:01.390
    Switched to user: ASCENDUMCE\ed1adm.
    INFO 2014-08-24 16:14:01.422
    Output of S:\usr\sap\ED1\SYS\exe\uc\NTAMD64\saplikey pf=\\SATDCSAP3\sapmnt\ED1\SYS\profile\ED1_DVEBMGS00_SATDCSAP3 -install_first_temp F1740289712 XXXXXX is written to the logfile saplikey.log.
    WARNING 2014-08-24 16:14:01.640
    Execution of the command "S:\usr\sap\ED1\SYS\exe\uc\NTAMD64\saplikey pf=\\SATDCSAP3\sapmnt\ED1\SYS\profile\ED1_DVEBMGS00_SATDCSAP3 -install_first_temp F1740289712 XXXXXX" finished with return code 2. Output:
    saplikey: failed to connect to the database.
    ERROR 2014-08-24 16:14:01.640
    CJS-30023  Process call 'S:\usr\sap\ED1\SYS\exe\uc\NTAMD64\saplikey pf=\\SATDCSAP3\sapmnt\ED1\SYS\profile\ED1_DVEBMGS00_SATDCSAP3 -install_first_temp F1740289712 XXXXXX' exits with error code 2. For details see log file(s) saplikey.log, dev_slic.
    ERROR 2014-08-24 16:14:01.703
    FCO-00011  The step createTempLicense with step key |NW_ABAP_DB_DBRefresh|ind|ind|ind|ind|0|0|NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_Postload|ind|ind|ind|ind|postload|0|NW_Postload_DBRefresh_ABAP|ind|ind|ind|ind|abap|0|NW_Temp_License_ABAP|ind|ind|ind|ind|lic|0|createTempLicense was executed with status ERROR ( Last error reported by the step: Creating a license signature failed:
    ===...could not load SSF library S:\usr\sap\\D00\exe\sapcrypto.dll .).
    INFO 2014-08-24 16:14:02.31
    Creating file C:\Program Files\sapinst_instdir\BS2013\BS2013SR1\ERP607SR1\HDB\COPY\SYSTEM\STD\AS-ABAP\REF\__instana_tmp.xml.
    INFO 2014-08-24 16:14:02.734
    Removed file C:\Program Files\sapinst_instdir\BS2013\BS2013SR1\ERP607SR1\HDB\COPY\SYSTEM\STD\AS-ABAP\REF\instslana.xml.
    INFO 2014-08-24 16:14:02.734
    Creating file C:\Program Files\sapinst_instdir\BS2013\BS2013SR1\ERP607SR1\HDB\COPY\SYSTEM\STD\AS-ABAP\REF\instslana.xml.
    -- saplikey.log:
    saplikey: failed to connect to the database.
    -- dev_likey:
    -> init()
      STATEMENT_CACHE_SIZE = 1000
    -> init()
    -> loadClientRuntime()
    Loading SQLDBC client runtime ...
    SQLDBC Module  : S:\usr\sap\ED1\hdbclient\libSQLDBCHDB.dll
    SQLDBC Runtime : libSQLDBCHDB 1.00.80.00 Build 0391861-1510
    SQLDBC client runtime is 1.00.80.00.0391861
    -> getNewConnection()
    <- getNewConnection(con_hdl=0)
    -> checkEnvironment(con_hdl=0)
    -> connect(con_info_p=0000000000000000)
    Try to connect via secure store (DEFAULT) on connection 0 ...
    *** ERROR => Connect to database failed, rc=1, rcSQL=10
    [dbhdbsql.cpp 332]
    SQLCODE    : 10
    SQLERRTEXT : invalid username or password:
    -> SetSdbDbslCA(errcode=10)
    -> freeConnection(con_hdl=0)
       close all opened locators of connection 0
    } DbSlHDBConnect(rc=99)
    ***LOG BY2=> sql error 10     performing CON [dblink       559]
    ***LOG BY0=> invalid username or password:  [dblink       559]
    *** ERROR => saplikey: failed to connect to the database. [saplikey.c   830]
    release memory of the SIBU buffers
    release memory of the STATEMENT CACHE
    Can you help me please!? This is very urgent!
    Thank you,
    samid raif

    Hello John Appleby,
    I ran the R3trans -d and this is the output:
    4 ETW000 r3trans version 6.24 (release 741 - 10.06.14 - 20:14:07).
    4 ETW000 unicode enabled version
    4 ETW000 ===============================================
    4 ETW000
    4 ETW000 date&time   : 24.08.2014 - 20:22:19
    4 ETW000 control file: <no ctrlfile>
    4 ETW000 R3trans was called as follows: r3trans -d
    4 ETW000  trace at level 2 opened for a given file pointer
    4 ETW000  [     dev trc,00000]  Sun Aug 24 20:22:19 2014                                                 124  0.000124
    4 ETW000  [     dev trc,00000]  db_con_init called                                                       103  0.000227
    4 ETW000  [     dev trc,00000]  set_use_ext_con_info(): usage of ssfs switched off (rsdb/ssfs_connect=0)
    4 ETW000                                                                                                  94  0.000321
    4 ETW000  [     dev trc,00000]  determine_block_commit: no con_hdl found as blocked for con_name = R/3
    4 ETW000                                                                                                  44  0.000365
    4 ETW000  [     dev trc,00000]  create_con (con_name=R/3)                                                 26  0.000391
    4 ETW000  [     dev trc,00000]  Loading DB library 'dbhdbslib.dll' ...                                    64  0.000455
    4 ETW000  [     dev trc,00000]  DlLoadLib success: LoadLibrary("dbhdbslib.dll"), hdl 0, count 1, addr 000007FEEFE00000
    4 ETW000                                                                                                5889  0.006344
    4 ETW000  [     dev trc,00000]      using "S:\usr\sap\ED1\SYS\exe\uc\NTAMD64\dbhdbslib.dll"               35  0.006379
    4 ETW000  [     dev trc,00000]  Library 'dbhdbslib.dll' loaded                                            36  0.006415
    4 ETW000  [     dev trc,00000]  function DbSlExpFuns loaded from library dbhdbslib.dll                    52  0.006467
    4 ETW000  [     dev trc,00000]  Version of 'dbhdbslib.dll' is "741.10", patchlevel (0.43)                111  0.006578
    4 ETW000  [     dev trc,00000]  function dsql_db_init loaded from library dbhdbslib.dll                   39  0.006617
    4 ETW000  [     dev trc,00000]  function dbdd_exp_funs loaded from library dbhdbslib.dll                  63  0.006680
    4 ETW000  [     dev trc,00000]  } DbSlHDBControl(rc=0)                                                    81  0.006761
    4 ETW000  [     dev trc,00000]  { DbSlHDBControl(con_hdl=-1,command=39,arg_p=0000000000000000)            40  0.006801
    4 ETW000  [     dev trc,00000]  } DbSlHDBControl(rc=0)                                                    29  0.006830
    4 ETW000  [     dev trc,00000]  { DbSlHDBControl(con_hdl=-1,command=10,arg_p=000000000221F280)            34  0.006864
    4 ETW000  [     dev trc,00000]  } DbSlHDBControl(rc=0)                                                    29  0.006893
    4 ETW000  [     dev trc,00000]  New connection 0 created                                                  25  0.006918
    4 ETW000  [     dev trc,00000]  0: name = R/3, con_id = -000000001, state = DISCONNECTED, tx = NO , bc = NO , oc = 000, hc = NO , perm = YES, reco = NO , info = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO , prog = 
    4 ETW000                                                                                                  63  0.006981
    4 ETW000  [     dev trc,00000]  { DbSlHDBControl(con_hdl=-1,command=10,arg_p=0000000141FF5E40)            49  0.007030
    4 ETW000  [     dev trc,00000]  } DbSlHDBControl(rc=0)                                                    30  0.007060
    4 ETW000  [     dev trc,00000]  db_con_connect (con_name=R/3)                                             31  0.007091
    4 ETW000  [     dev trc,00000]  determine_block_commit: no con_hdl found as blocked for con_name = R/3
    4 ETW000                                                                                                  42  0.007133
    4 ETW000  [     dev trc,00000]  find_con_by_name found the following connection:                          28  0.007161
    4 ETW000  [     dev trc,00000]  0: name = R/3, con_id = 000000000, state = DISCONNECTED, tx = NO , bc = NO , oc = 000, hc = NO , perm = YES, reco = NO , info = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO , prog = 
    4 ETW000                                                                                                 124  0.007285
    4 ETW000  [     dev trc,00000]  { DbSlHDBConnect(con_info_p=0000000000000000)                             61  0.007346
    4 ETW000  [     dev trc,00000]  DBHDBSLIB : version 741.10, patch 0.043 (Make PL 0.43)                    65  0.007411
    4 ETW000  [     dev trc,00000]  HDB shared library (dbhdbslib) patchlevels (last 10)                      37  0.007448
    4 ETW000  [     dev trc,00000]    (0.043) R3szchk with partitioned tables (note 2040561)                  32  0.007480
    4 ETW000  [     dev trc,00000]    (0.031) New DBCON syntax for HANA (note 1983389)                        50  0.007530
    4 ETW000  [     dev trc,00000]    (0.028) Bulk insert stop on duplicate, dbsl returncode corrected (note 1996982)
    4 ETW000                                                                                                  51  0.007581
    4 ETW000  [     dev trc,00000]    (0.027) Set DBAREQ class (note 1991383)                                 35  0.007616
    4 ETW000  [     dev trc,00000]    (0.022) Get database version via dbsl call (note 1976918)               36  0.007652
    4 ETW000  [     dev trc,00000]    (0.020) FDA: Core Dump in SELECT ... FOR ALL ENTRIES for tables with strings (note 1970276)
    4 ETW000                                                                                                  53  0.007705
    4 ETW000  [     dev trc,00000]    (0.020) SQL DDL with data aging (note 1897636)                          35  0.007740
    4 ETW000  [     dev trc,00000]    (0.017) Datatype NCLOB missing in tablesize calculation (note 1952609)
    4 ETW000                                                                                                  52  0.007792
    4 ETW000  [     dev trc,00000]    (0.014) Tablesize calculation for HANA optimized (note 1952609)         36  0.007828
    4 ETW000  [     dev trc,00000]    (0.014) Native SQL UPSERT with DataAging (note 1897636)                 32  0.007860
    4 ETW000  [     dev trc,00000]                                                                            22  0.007882
    4 ETW000  [     dev trc,00000]   -> init()                                                                33  0.007915
    4 ETW000  [     dev trc,00000]    STATEMENT_CACHE_SIZE = 1000                                            212  0.008127
    4 ETW000  [     dev trc,00000]   -> init()                                                               615  0.008742
    4 ETW000  [     dev trc,00000]   -> loadClientRuntime()                                                   46  0.008788
    4 ETW000  [     dev trc,00000]  Loading SQLDBC client runtime ...                                         31  0.008819
    4 ETW000  [     dev trc,00000]  SQLDBC Module  : S:\usr\sap\ED1\hdbclient\libSQLDBCHDB.dll              1327  0.010146
    4 ETW000  [     dev trc,00000]  SQLDBC Runtime : libSQLDBCHDB 1.00.80.00 Build 0391861-1510               84  0.010230
    4 ETW000  [     dev trc,00000]  SQLDBC client runtime is 1.00.80.00.0391861                               50  0.010280
    4 ETW000  [     dev trc,00000]   -> getNewConnection()                                                    37  0.010317
    4 ETW000  [     dev trc,00000]   <- getNewConnection(con_hdl=0)                                          100  0.010417
    4 ETW000  [     dev trc,00000]   -> checkEnvironment(con_hdl=0)                                           53  0.010470
    4 ETW000  [     dev trc,00000]   -> connect(con_info_p=0000000000000000)                                  42  0.010512
    4 ETW000  [     dev trc,00000]  Try to connect via secure store (DEFAULT) on connection 0 ...             86  0.010598
    4 ETW000  [dbhdbsql.cpp,00000]  *** ERROR => Connect to database failed, rc=1, rcSQL=10                11122  0.021720
    4 ETW000  [     dev trc,00000]  SQLCODE    : 10                                                           68  0.021788
    4 ETW000  [     dev trc,00000]  SQLERRTEXT : invalid username or password:                                40  0.021828
    4 ETW000  [     dev trc,00000]   -> SetSdbDbslCA(errcode=10)                                              41  0.021869
    4 ETW000  [     dev trc,00000]   -> freeConnection(con_hdl=0)                                             43  0.021912
    4 ETW000  [     dev trc,00000]     close all opened locators of connection 0                              60  0.021972
    4 ETW000  [     dev trc,00000]  } DbSlHDBConnect(rc=99)                                                   65  0.022037
    4 ETW000  [    dblink  ,00000]  ***LOG BY2=>sql error 10     performing CON                               68  0.022105
    4 ETW000  [    dblink  ,00000]  ***LOG BY0=>invalid username or password:                                 35  0.022140
    4 ETW000  [     dev trc,00000]  { DbSlHDBControl(con_hdl=0,command=41,arg_p=0000000140541C48)            107  0.022247
    4 ETW000  [     dev trc,00000]  } DbSlHDBControl(rc=0)                                                    79  0.022326
    4 ETW000  [     dev trc,00000]  { DbSlHDBControl(con_hdl=0,command=14,arg_p=0000000002215998)             38  0.022364
    4 ETW000  [     dev trc,00000]  } DbSlHDBControl(rc=0)                                                    28  0.022392
    4 ETW000  [     dev trc,00000]  { DbSlHDBControl(con_hdl=0,command=50,arg_p=0000000002215990)             33  0.022425
    4 ETW000  [     dev trc,00000]  } DbSlHDBControl(rc=0)                                                    43  0.022468
    4 ETW000  [     dev trc,00000]  { DbSlHDBControl(con_hdl=0,command=13,arg_p=00000000022159B0)             35  0.022503
    4 ETW000  [     dev trc,00000]  } DbSlHDBControl(rc=0)                                                    27  0.022530
    4 ETW000  [     dev trc,00000]  { DbSlHDBControl(con_hdl=0,command=52,arg_p=0000000002215A00)             33  0.022563
    4 ETW000  [     dev trc,00000]  } DbSlHDBControl(rc=0)                                                    28  0.022591
    2EETW169 no connect possible: "DBMS = HDB                              ---  SERVER = '' PORT = ''"
    4 ETW000  [     dev trc,00000]  release memory of the SIBU buffers                                      2900  0.025491
    4 ETW000  [     dev trc,00000]  release memory of the STATEMENT CACHE                                     91  0.025582

  • Error in Managed system configuration.

    Hi Folks,
    In Solman 7.1 i am configuring my Java system in managed system configuration on the last phase of configuration which is "Check Configuration" i got the below error...
    Can any one guide me on this....
    I installed the Diagnostic agent as well as willy inter scope.
    Regards,
    Anil.

    check the note which describes your problem
    1776959 - Solution Manager 7.1 Manged System configuration. Error: Timezone from managed system could not be retrieved: Timezone of J2EE Engine (GMT+01:00) does not match the timezone of the diagnostics agent (Europe/Berlin)
    Resolution
    Open the instance.properties file of the J2EE Engine on the managed system
    Locate the parameter "-Duser.timezone=" and its value
    If the -Duser.timezone is not set the JVM uses GMT
    Set the -Duser.timezone parameter in the JVM of the SMD Agent. If there was no "-Duser.timezone in the J2EE's instance.properties file use the timezone that was indicated in the error message e.g. GMT+01:00 (from the above error message, this might differ on your environment) To do this:
    Locate the smd.properties file (for newer agents the files is called: smdagent.properties)
    The path is: .../usr/sap/<DiagnosticAgentSID>/SMDA<SYSNumber>/SMDAgent/smdagent.properties
    The -Duser.timezone= parameter of the Diagnostics Agent and the SAP J2EE engine need to be set to the same timezone. That means the string needs to be the same for both parameters
    e.g.
    If the -Duser.timezone= parameter of the J2EE engine is set to -Duser.timezone="GMT+01:00"
    set the Diagnostics Agent parameter to:
    smdagent.javaParameters=-DP4ClassLoad=P4Connection -Xmx256m -Xms256m -Duser.timezone="GMT+01:00"
    Restart the Agent
    Re-run the "Configuration Check" in the "Managed System Configuration"
    Please make sure that the time zone configuration is correct according to the SAP recommendations: http://wiki.sdn.sap.com/wiki/display/Basis/Timezone+changes+best+practices

Maybe you are looking for