Diagnostics Setup - Warning on Step "SSO"

Hi All
After getting rid of one issue with this setup I have managed to com across another which I am finding difficult to solve.
I am getting the following issues with SSO:
Step SSO Details
The SSO ticket Certificate <OU=J2EE,CN=SMP> has been successfully imported into ticket Keystore
The Login Modules for validating SSO tickets were already installed
The ticket ACL already contained : sys=SMP,169 iss=OU=J2EE,CN=SMP dn=OU=J2EE,CN=SMP
The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
The Authentication template for component sap.com/tcmonitoringsysteminfo*sap_monitoring was already set to ticket
The Authentication template for component sap.com/tcwddispwda*webdynpro_dispatcher was already set to ticket
The Authentication template for component sap.com/tcwddispwda*webdynpro_welcome was already set to ticket
SSO Abap Ticket certificate of Diagnostics system not available : can not perform SSO setup. Please make sure ABAP PSE is not empty and not locked by transaction STRUSTSSO2 on Diagnostics system
The Login Modules for validating SSO tickets were already installed
SSO certificate data not available : Ticket login module can not be updated
SSO setup failed : error while updating login modules : SSO certificate data not available : Ticket login module can not be updated.
SMD Agent Log:
Apr 7, 2010 11:58:34 AM [Thread[SapStartSrv_perth_EPD_04,5,main]] Warning    com.sap.smd.wily.hostagent.sapcontrol.SapControlAction - doRun:
[EXCEPTION]
javax.xml.rpc.soap.SOAPFaultException: JCMON_ShmAdminOpen failed
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:747)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:870)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1451)
     at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.j2EEGetProcessList(SAPControlStub.java:2247)
     at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.j2EEGetProcessList(SAPControlStub.java:2262)
     at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.getJ2EEProcessList(SapControlAction.java:498)
     at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.doRun(SapControlAction.java:957)
     at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)
     at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
     at java.lang.Thread.run(Thread.java:664)
Apr 7, 2010 11:58:34 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Apr 7, 2010 11:59:34 AM [Thread[SapStartSrv_perth_EPD_04,5,main]] Warning    com.sap.smd.wily.hostagent.sapcontrol.SapControlAction - doRun:
[EXCEPTION]
javax.xml.rpc.soap.SOAPFaultException: JCMON_ShmAdminOpen failed
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:747)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:870)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1451)
     at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.j2EEGetProcessList(SAPControlStub.java:2247)
     at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.j2EEGetProcessList(SAPControlStub.java:2262)
     at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.getJ2EEProcessList(SapControlAction.java:498)
     at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.doRun(SapControlAction.java:957)
     at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)
     at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
     at java.lang.Thread.run(Thread.java:664)
Apr 7, 2010 12:00:30 PM [Thread[Thread-3,5,main]] Error      [Setup]No ABAP SSO ticket certificate file received. Please check Monitoring host logs and look for SSO ticket cert read failure
Apr 7, 2010 12:00:30 PM [Thread[Thread-3,5,main]] Warning    [Setup]No SSO Cert loaded => Options of EvaluateTicketLoginModule will *not* be updated properly
Apr 7, 2010 12:00:30 PM [Thread[Thread-3,5,main]] Error      [Setup]SSO setup failed : error while updating login modules
[EXCEPTION]
java.lang.IllegalArgumentException: SSO certificate data not available : Ticket login module can not be updated
     at com.sap.smd.agent.plugins.remotesetup.SecurityContextAdapter.updateTicketModules(SecurityContextAdapter.java:100)
     at com.sap.smd.agent.plugins.remotesetup.SetupManager.updateLoginMonitoredModules(SetupManager.java:319)
     at com.sap.smd.agent.plugins.remotesetup.RemoteSetupStep.setupSSO(RemoteSetupStep.java:239)
     at com.sap.smd.agent.plugins.remotesetup.RemoteSetupStep.setupSSO(RemoteSetupStep.java:195)
     at com.sap.smd.agent.plugins.remotesetup.RemoteSetupStep.execute(RemoteSetupStep.java:116)
     at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:549)
     at com.sap.smd.agent.plugins.remotesetup.RemoteSetupService._setup(RemoteSetupService.java:159)
     at com.sap.smd.agent.plugins.remotesetup.RemoteSetupService.setup(RemoteSetupService.java:86)
     at com.sap.smd.agent.plugins.remotesetup.RemoteSetupServicep4_Skel.dispatch(RemoteSetupServicep4_Skel.java:112)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
     at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
     at java.lang.Thread.run(Thread.java:664)
Apr 7, 2010 12:00:34 PM [Thread[SapStartSrv_perth_EPD_04,5,main]] Warning    com.sap.smd.wily.hostagent.sapcontrol.SapControlAction - doRun:
[EXCEPTION]
javax.xml.rpc.soap.SOAPFaultException: JCMON_ShmAdminOpen failed
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:747)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:870)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1451)
     at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.j2EEGetProcessList(SAPControlStub.java:2247)
     at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.j2EEGetProcessList(SAPControlStub.java:2262)
     at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.getJ2EEProcessList(SapControlAction.java:498)
     at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.doRun(SapControlAction.java:957)
     at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)
     at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
     at java.lang.Thread.run(Thread.java:664)
I have check STRUSTsso2 in Solution Manager and all seems to be fine (Status Green), it does not appear to be locked and I am now unsure what else to try.
Any ideas?

Thanks for your response.
Our current LM-TOOLS version is below:
sap.com LM-TOOLS 7.01 SP5 (1000.7.01.5.2.20091119080143) SAP AG MAIN_NW701P05_C 20100323084604
I have been through both of the notes and the issue appears to be with Solution Manager as we get the same error for ALL systems.

Similar Messages

Diagnostics Setup - Warning on Step "Wilyhost Agent Details"

Hi All
I am having a bit of dificulty configuring the Wily Agent via Solution Manager diagnostics.
I am currently getting the following errors when trying to set up the Wilyhost Agent when I run the setup wizard I am getting the following results:
Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager(solman:6001).
Step Wilyhost Agent Details
Created destination EPT_JC01_server0
Created destination SapStartSrv_nwportal_EPD_04
Created destination EPD_JC04_server0
Created destination SapStartSrv_nwportal_EPT_01
Created action SAP GC|EPT_JC01_server0 - SAP GC|EPT_JC01_server0
Created action EPD|perth_EPD_04 - SapStartSrv_nwportal_EPD_04
Created action SAP GC|EPD_JC04_server0 - SAP GC|EPD_JC04_server0
Created action EPT|perth_EPT_01 - SapStartSrv_nwportal_EPT_01
Created 4 action(s).
1 Wilyhost Agent(s) from host perth is connected to the EM.
90 seconds after restarting the WilyHostAgent the data of the following action is still missing in EM: SAP OsCol - null
Please check SMDAgentApplication log files for warnings and errors.
Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager(solman:6001).
The Diagnostics agent log is:
Apr 6, 2010 4:56:35 PM [Thread[SAPOsCol,5,main]] Error      com.sap.smd.wily.hostagent.action.SapOsColAction - processXml(): Error processing saposcol output: saposcol -xml
AdjustTokenPrivileges failed with 1300
<?xml version="1.0" encoding="utf-8" ?>
<saposcol version="COLL 20.95 700 - 20.65 NT 08/02/06" date="1270569346" status="running">

<OperatingSystem>
        <property name="OpSysRelease">
          <value>Windows NT</value>
          
        </property>
        <property name="OpSysReleaseName">
          <value>Windows NT 5.2</value>
          
        </property>
        <property name="OpSysCategory">
          <value>Windows NT</value>
          
        </property>
</OperatingSystem>
[EXCEPTION]
com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 73, 61, 70(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 73, 61, 70(:main:, row:1, col:3)
     at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787)
     at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832)
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
     at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
     at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
     at com.sap.smd.wily.hostagent.action.SapOsColAction.processXml(SapOsColAction.java:146)
     at com.sap.smd.wily.hostagent.action.SapOsColAction.doRun(SapOsColAction.java:420)
     at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)
     at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
     at java.lang.Thread.run(Thread.java:664)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
     at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
     at com.sap.smd.wily.hostagent.action.SapOsColAction.processXml(SapOsColAction.java:146)
     at com.sap.smd.wily.hostagent.action.SapOsColAction.doRun(SapOsColAction.java:420)
     at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)
     at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
     at java.lang.Thread.run(Thread.java:664)
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 73, 61, 70(:main:, row:1, col:3)
     at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787)
     at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832)
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
     at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
     ... 6 more

Hi,
This seems to be a bug and please install the saposcol version 710 as saposcol 710 is downward compatible with release 700 and this issue must be resolved.

Diagnostics Setup - remembers old settings

Hi,
have a strange problem and it's really giving me a headache. We did set up solution manager diagnostics earlier ago and it worked fine. Recently I logged on again to the SolMan Diagnostics page and got the message that Diagnostics was not running because the WEBADMIN connection did not work.
I checked in Visual Admin (JCo RFC Provider) and it was really down. The reason was the user which was entered for the connection did not exist anymore. So I changed it to something else and it was started up fine.
But I also had to re-run a Diagnostics Setup -> Diagnostics System -> Setup Wizard due to upgrade we made.
Magically this again changed the old connection parameters back in Visual Admin's WEBADMIN connection. On the very first page of the diagnostics wizard you can maintain the connection parameters to the ABAP system and I also changed that to the new user but when the setup proceeds it always fails at the ABAP connection step saying the user ID and password is not correct (and stating the old user which really surprises me).
So it seems whatever data you gave for the very first time the wizard just can't forget it and brings them up even you already changed the connection parameters...and it also overrides the WEBADMIN connection parameters back to the obsolete parameters.
Anybody has an idea how can I overcome this issue? Is it somewhere buffered and I need to empty the buffer?
Our solman is a 7.0 at SPS17
Cheers

Hi, thanks for the reply - the problem is not in the ABAP stack. It's on the java side when you try to open the http://hostname:port/smd link and try to do a diagnostics setup wizards.
On this first page there are some parameters you need to provide like:
Support User
Please enter the UserId of the SMD Support User. If not yet existing, the User will be created with password set in advanced setup (default : 'init1234')
ABAP Connection
Please enter the settings of the Solution Manager Backend ISM
ABAP Client
ABAP Admin User Id
ABAP Admin Password
ITS port
Is BW installed in a separate... Client ? System ?
J2EE Administrator
Please enter admin User Id and password of the SAP J2EE administrator of Solution Manager
J2EE Admin User Id
J2EE Admin Password
Etc etc...
my problem is that at the very first time I populated the ABAP connection parameters using a user ID called e.g. SMD_RFC_XYZ.
Now when I change this to e.g. SMD_COMMUINICATION user and run the setup wizard with the changed parameters in the error log I still see SMD_RFC_XYZ user id for some reason I don't know where the system gets it from.

I didn't setup a two step verification for my apple Id , and then when i login into my account on the browser it prompt to enter my verification code !!! HOW COME

i didn't setup a two step verification for my apple Id , and then when i login into my account on the browser it prompt to enter my verification code !!! HOW COME
please help because all my data are stored in the cloud

- See if it is listed here for downloading. If it is then redownload it..
Downloading past purchases from the App Store, iBookstore, and iTunes Store
- If not there then contact iTunes.
Contact iTunes

2 apple IDs how do I setup a 2 step verification?

I have 2 apple IDs 1 for itunes store,app store and Mac app store and another for iCloud how do I setup a 2 step verification?

I can't. When I connect my iPhone to my computer either my iPhone or the computer "knows" about my old id and tries to use it. I don't know the password for my old id and I'm not using, and don't have access to, the email for my old id. I can't find my old id in my phone or computer to get rid of it.
Thoughts?
Thanks.

Solman Setup 7.1SP04 - Step 2.5 Setup Data Upgrade failed

Hi Everyone!
For a few days I've been trying to fix an issue with solution manager setup, but no luck. It occurs on the 2.5 step (Solution Manager Internal Connectivity) during the 'Run Java Upgrader' substep.
Notes 1633725 - SAP Solution Manager 7.1 SP4 - basic functions, as well as 1659101 (as it was suggested in the similar threat SolMan 7.1 SP4: Diagnostics data upgrader ended with errors ) have been implemented, but nothing changed.
Before performing above step I've also upgraded SLD to the most recent version:
Please find attached the failed step error log. The 'dev_icm' file contains no errors, only 5 warnings.
I will be very grateful for any help you can provide!
Tomasz Sobkowiak

Hi,
I finally managed to resolve this issue. The thing was that I had to execute a oracle statistics update using BRConnect:
brconnect -u / -c -f stats -t all
After that this step has been finished in about 10 seconds.
I hope this information will be useful for someone.
Best regards,
Tomasz Sobkowiak

A failure occured while calling Diagnostics Setup web service

Hi Guys.
When performing the Automatic Activities of the Solution Manager 7.1 Basic Configuration, on one step you can execute the Diagnostics Configuration.
When clicking on the details it shows the following message.
SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 401 : Unauthorized")
Error when processing Web service call
I tried running the configuration a user having SAP_ALL, also j2ee_admin, so no clue where is the authorization fault.
Any ideas what is causing this Authorization Error?
I also tried to access SMD manually on saphost:8000/SMD but it says Root Cause Analysis Setup has been moved and Call transaction SOLMAN_SETUP from the SAP GUI to configure SAP Solution Manager.
Is there any url to access to SMD directlty without going thru SOLMAN_SETUP since i dont see where is the url.
Thanks!

Please make sure that your solman box meet the software prerequisit as per this note below
1483508 : Solution Manager 7.1: Root Cause Analysis pre-requisites
This will solve that ptoblem .
Best Regards
Jai Wardhan

Solution Manger Diagnostics setup (SMD Agent)

Hi All
I have managed to setup Solution Manager Diagnostics and Deploy on of the agents to out DEV BI Server (JAVA), however I keep getting the message:
     "Failed to connect to server: bidevdb - Please make sure SMD Agent is up and running"
Now I can see in the SAPMSC that the SMD agent is running - so I am not sure why this is the case. Does SMD require SAPCCMS setup as a windoes service on the BI Server?
Or what else can I check to find out what the issue might be?
Thanks all in advance (will award points for helpfull answers)

SMDSystem.x.log
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[SMDSystemLog]/>
<!PATTERN[SMDSystem.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%t] %10s %m)]/>
<!ENCODING[Cp1252]/>
<!FILESET[0, 10, 1000000]/>
<!PREVIOUSFILE[SMDSystem.9.log]/>
<!NEXTFILE[SMDSystem.1.log]/>
<!LOGHEADER[END]/>
Mar 25, 2010 2:23:08 PM [Thread[main,5,main]] Info       Starting SMDAgent ...
Mar 25, 2010 2:23:09 PM [Thread[main,5,main]] Info       ===> Establishing connection to server '[host is empty]' on port [port is empty]
Mar 25, 2010 2:23:11 PM [Thread[Connector,5,main]] Info       Smd connector is disabled because no SLD association and no credentials found.
Mar 25, 2010 2:23:11 PM [Thread[Connector,5,main]] Info       Smd connector is disabled because no SLD association and no credentials found.
Mar 25, 2010 2:23:12 PM [Thread[SLD-Registration,1,main]] Error      Cannot retrieve saposcol hardware info for SLD data instance.
[EXCEPTION]
java.io.IOException: CreateProcess: ..\..\exe\saposcol -b error=2
     at java.lang.ProcessImpl.create(Native Method)
     at java.lang.ProcessImpl.<init>(ProcessImpl.java:85)
     at java.lang.ProcessImpl.start(ProcessImpl.java:30)
     at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
     at java.lang.Runtime.exec(Runtime.java:591)
     at java.lang.Runtime.exec(Runtime.java:429)
     at java.lang.Runtime.exec(Runtime.java:326)
     at com.sap.smd.agent.util.RunExec.exec(RunExec.java:78)
     at com.sap.smd.agent.util.RunExec.exec(RunExec.java:55)
     at com.sap.smd.agent.util.RunExec.execAndWaitFor(RunExec.java:158)
     at com.sap.smd.agent.util.RunExec.execAndWaitFor(RunExec.java:148)
     at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.getSAPOSColHostInfo(SLDAgentDataBuilder.java:254)
     at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.addAgentHostMember(SLDAgentDataBuilder.java:195)
     at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.addGroupAgentInstance(SLDAgentDataBuilder.java:132)
     at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.addSLDInfoNodeForAgentRegistration(SLDAgentDataBuilder.java:498)
     at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.writeAgentInstanceData(SLDAgentDataBuilder.java:597)
     at com.sap.smd.agent.connection.sld.SLDQueryBuilder.registerAgentInstanceData(SLDQueryBuilder.java:604)
     at com.sap.smd.agent.connection.sld.process.SLDReg.run(SLDReg.java:68)
     at java.lang.Thread.run(Thread.java:664)
Mar 25, 2010 2:23:12 PM [Thread[SLD-Registration,1,main]] Info       [SLDReg] Next try to push instance data in SLD is Fri Mar 26 02:23:12 GMT 2010
Could not find the SMDAgentApplication.X.log
Does that help?

QM SetUp Tables Filling Steps

Hi Gurus,
I am trying to fill the setup tables for the QM Module (05).
Even after waiting for a few hours its not filling any records to the Data Sources.
Can you please let me know if i need to do anything else like any other settings before filling the QM Set Up tables.
When I checked the NPRT T-Code ... It shows that the finish date and time along with 0 Number of Documents .
Can someone please let me know the exact steps for filling the QM set up tables .
Regards
Vikram....

Hi Jorge,
I have a live BW 3.5 system connected to this live R/3 system and now we are Re-Implementing the same into BI 7.0 System.
The delta Loads are getting loaded everyday to the existing BW 3.5 System, so I cannot delet the initialization request and i dont see any reason for doing that to fill the setup tables.
I have to do a Full load to the new BI 7.0 System till 2007 Fiscal year and are planning to load the current fiscal year data during cut over period.
So,I need to fill the Setup tables to load the Historical Data till 2007 Fiscal Year. Can you please help me out with this issue....
Regards
Vikram...

Managed system diagnostics setup problem

Hi
I am trying to configure managed system setup for NW 7.2 ce java system. I passed check prereq and manual configuration.
However I got stuck at phase "configure diagnotsics". I am getting the "None of the instances making-up this system was selected for setupPlease select at least one instance" message. The managed products : SAP NETWEAVER AS JAVA 7.2 and the product instance :Application Server Java.
the smsy configuration is configured to transfer data from solman sld.
Do you have any idea of Why this message appears? which part should I check?
Thanks....
Edited by: Turgay SAMDANLI on Apr 4, 2011 10:08 AM
Edited by: Turgay SAMDANLI on Apr 4, 2011 10:09 AM

Hi Turgay,
Fisrtly, you should have Solman at least on SP23 in order to configure a CE 7.2 for diagnostics. Before this version the
CE 7.2 is not supported.
Also, check the relevant instances in SMSY definition for the Netweaver CE 7.2.
Kind Regards,
Allam Drebes

Setup Windows TS step changes boot partition from C to D

Greetings,
I have a build and capture task sequence. In the Winpe phase I create one single partition (no bde). During the WinPE phase, diskpart says this drive is C and I can copy stuff to the C drive no problem. Once the "Setup Windows and configmgr"
step starts and reboots into the OS, the OS in "my computer" says its on the D drive. How can I make sure that the reboot into the OS keeps the C drive for the boot partition?
Thanks
David Z

I generally set OSDPreserveDriveLetter also and it works fine however there is a lengthy support blog for times when even it doesn't work:
http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2014/04/28/how-to-ensure-that-windows-installs-on-c-during-a-system-center-2012-configuration-manager-osd-task-sequence.aspx
Jason | http://blog.configmgrftw.com

Setup of Xwindows - step by step guide for SLES 11.3 reqd

Hi
I have used Unix before but I am new to SLES and I need to run a gui based installer on a new AWS image of SUSE 11.3.
I wanted to remove Putty/SSH complications from the equation so for now, to check if XWindows is working I directly connected to the SLES desktop using xRDP as ec2-user, and from xterm I issued the following commands:
su - root
export TERM=xterm
export DISPLAY=localhost:0.0
After checking the variables, I launched xclock but it fails making me conclude that Xwindows is not correctly configured or running.
Can anyone point me towards a step by step guide on how to setup XWindows, or given my dated knowledge, is there a better way to run a gui-based program?
Regards
Ratna

A couple thoughts:
1. If this is just SLES (and not Open Enterprise Server (OES) then you
may want to post in the SUSE forums (https://forums.suse.com/) using the
same credentials that you used to access this site.
2. It sounds like you have X working already since you were able to acess
the system using xRDP. Is there a reason you cannot just start the
installer from there? Alt+F2 to run things usually, I think. If you are
using Gnome, I think 'gksu' or 'gksudo' will start things as a privileged
user from the current non-root user after sufficient credentials are
entered; from the KDE side of things I use 'kdesu' all of the time for the
same thing. This avoids loading a shell, changing to root, forwarding X,
etc. as you are trying to do.
3. Going back to your attempt, I do not see you allowing access to your X
session anywhere so that 'root' can connect with its new process. Before
you change to root, you need to instruct your current X session to allow
other users to throw things onto your desktop (usually not a good thing).
The easy way is to just run 'xhost +' from a shell, maybe before running
'su'; note that if other users are on the system they can now send shells
your way forever, and that may not be fun.
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

Annoying email setup warning during roaming on 580...

Guys,
Does anyone know how to disable the message that pops up from the Email Setup program when the network changes (e.g.. During roaming) on the Nokia 5800 (FW version 50.0.005) saying "allow phone to use network to send and receive data".
Basically if you go abroad and have roaming enabled you will often find the phone changes network, e.g.. I was just in Italy and it regularly roamed from Vodafone IT to I Wind and TIM. Each time it swapped network I got the email setup program displayed and it said "can it use the network" which required a response. Why?? No other application needs this constant interaction!
It was especially annoying as I would be using the sat nav (so cool) but then while driving it would change network, then this message would be displayed which takes the focus from Ovi Maps so the screen blacks out, and locks (which seemed to stop the navigation instructions being read out even!).
Please fix this Nokia!!!

Any update on this from Nokia?
I recently updated my 5800xm and I have the same problem now; in fact I wouldn'st say roaming changes anything, it happens all the time.
I really like all the updates we get on the 5800; I think it adds a lot of credibility to the Nokia offering.
But this bug should be resolved now. The only solution I have is to remove the mail setup application; not really a solution is it?
Or I could disable it. Any idea how to disable an app on NOkia 5800?

Setup and Configure Steps?

I have tried to find documentation on how to set up and configure to use LCDS but I can't find anything. I am new to LC products and I don't think the Adobe installation doc is of much help.
Does anyone have any docs or steps they would like to pass on? We have it installed but aren't using it and I have heard it's a pain to set up but once you do it's an awesome product.
Thanks,
John

Hopefully this link will help:
http://blogs.adobe.com/flexdoc/2007/06/livecycle_data_services_docume.html
Have you already seen the developer guide?
- Mike Peterson

Setup Cache Connect Step by Step on RedHat AS3.0

1.     Install TimesTen with Cache Connect option and access control
2.     Install Oracle Client
3.     Setup environment variable:
export ORACLE_HOME=/ora/product/10.2.0/db_1
export ORACLE_SID=orcl
export TT_HOME=/ora/TimesTen/tt60
export PATH=$PATH:$ORACLE_HOME/bin:$TT_HOME/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib:$TT_HOME/lib
export SHLIB_PATH=$SHLIB_PATH:$ORACLE_HOME/lib:$TT_HOME/lib
4.     Setup Oracle Name Service to connect to oracle server.
5.     Create required Oracle accounts
CREATE USER testuser IDENTIFIED BY welcome1;
GRANT connect, resource, create any trigger TO testuser;
COMMIT;
6.     Copy $TT_HOME/info/sys.odbc.ini to user home path and rename it to .odbc.ini
7.     Create an account on TimesTen by connecting to TimesTen using the TT_tt60 DSN
ttIsql TT_tt60
CREATE USER testuser IDENTIFIED BY 'welcome1';
GRANT ADMIN, DDL TO testuser;
8.     Create a TimesTen DSN named cgDSN
cgDSN =TimesTen 6.0 Driver
[cgDSN]
Datastore=/temp/cgds
PermSize=16
TempSize=16
UID=testuser
OracleId=system1
OraclePwd=mypsswrd
9.     Create an Oracle table
sqlplus testuser/welcome1@orcl
CREATE TABLE readtab (a NUMBER(10,0) NOT NULL PRIMARY KEY,b CHAR(31));
INSERT INTO readtab VALUES (1, 'hello');
INSERT INTO readtab VALUES (2, 'world');
COMMIT;
10.     Create the cache group
ttIsql cgDSN
call ttCacheUidPwdSet('testuser','welcome1');
call ttCacheStart();
CREATE READONLY CACHE GROUP readcache AUTOREFRESH INTERVAL 5 SECONDS FROM readtab (a INT NOT NULL PRIMARY KEY, b CHAR(31));
11.     Load the cache group
LOAD CACHE GROUP readcache COMMIT EVERY 30 ROWS;
12.     Check the result and the result should be 2 records.
SELECT * FROM readtab;
13.     Insert one more record from database and check the result from TimesTen, the result should be 3 recourd;
sqlplus testuser/welcome1@orcl
INSERT INTO readtab VALUES (3, ‘!’);
Commit;
ttIsql cgDSN
SELECT * FROM readtab;

A couple thoughts:
1. If this is just SLES (and not Open Enterprise Server (OES) then you
may want to post in the SUSE forums (https://forums.suse.com/) using the
same credentials that you used to access this site.
2. It sounds like you have X working already since you were able to acess
the system using xRDP. Is there a reason you cannot just start the
installer from there? Alt+F2 to run things usually, I think. If you are
using Gnome, I think 'gksu' or 'gksudo' will start things as a privileged
user from the current non-root user after sufficient credentials are
entered; from the KDE side of things I use 'kdesu' all of the time for the
same thing. This avoids loading a shell, changing to root, forwarding X,
etc. as you are trying to do.
3. Going back to your attempt, I do not see you allowing access to your X
session anywhere so that 'root' can connect with its new process. Before
you change to root, you need to instruct your current X session to allow
other users to throw things onto your desktop (usually not a good thing).
The easy way is to just run 'xhost +' from a shell, maybe before running
'su'; note that if other users are on the system they can now send shells
your way forever, and that may not be fun.
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

Diagnostics Setup - Warning on Step "SSO"

Similar Messages

Maybe you are looking for