SMD Agent 7.4* and SAPHOSTAGENT

Hi All,
Thanks for looking in to this.
I have installed the latest SMD agent (7.41) on the managed system. I managed to read somewhere that the latest smd agents have an option to update host agents automatically. can some one help me in telling me how this can be done?  i know of the old procedure by keeping the latest host agent in $DIR_EXECUTABLE. But I assume there is a new procedure in updating host agents with SMD. i couldnt find sap notes on this. Could anyone help me on this?
thanks in advance..

Hi Jim,
Below notes may be helpful for queries ,
1365123 - Installation of Diagnostics Agents( check the attachment )
Diagnostics Agent Release Characteristics - pg 22
1473974 - Using the SAP Host Agent Auto Upgrade Feature( check the attachment )
https://websmp204.sap-ag.de/~sapidb/012003146900000135752013E/SAP_Host_Agent_129.pdf
Rg,
Karthik

Similar Messages

  • Failed to connect to server - Please make sure SMD Agent is up and Running

    Hi All
    I am getting this message in SMD when trying to set up the SMD agent on one of our JAV servers - this is possibly a really simple problem to solve but I have no idea how to start  the SDM Agent.
    Can anyone give me instructions on how to do this (Windows / SQL)?
    Thanks in advance
    Phil

    Hi Phil,
    The SMD Agent gets installed as an instance & can be started/stopped via the SAP MMC.
    Have a great day,
    -S.

  • SMD Agent doesn't work

    Hello,
    I have been trying to install SMD Agent in my BI system but Solution Manager can't check it, this is the message in Solman_setup
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (sapl917.intra.banesco.com:6001) no Wilyhost Agent was detected from host svs978. 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.
    Step Wilyhost Agent Details
    Created destination QBB|svs978_QBB_01
    Created action QBB - QBB AbapSystem
    Created action QBB|svs978_QBB_01 - QBB|svs978_QBB_01 AbapInstance
    Created 2 action(s).
    0 Wilyhost Agent(s) from host svs978 are connected to the EM.
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (sapl917.intra.banesco.com:6001) no Wilyhost Agent was detected from host svs978. 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.
    do you know something??? i restarted the agent but nothing happens
    Thanks!!!!

    Hello...
    For JAVA
    Software Components 
    Vendor  Name  Version  Provider  Location  Applied 
    sap.com  ADSSAP  7.01 SP4 (1000.7.01.4.0.20090417021200)  SAP AG  SAP AG  20091103161136 
    sap.com  BASETABLES  7.01 SP4 (1000.7.01.4.0.20090417015900)  SAP AG  SAP AG  20091103153957 
    sap.com  BI_MMR  7.01 SP4 (1000.7.01.4.0.20090417021807)  SAP AG  SAP AG  20091103161215 
    sap.com  BI_UDI  7.01 SP4 (1000.7.01.4.0.20090416221700)  SAP AG  SAP AG  20091103162333 
    sap.com  CAF  7.01 SP4 (1000.7.01.4.0.20090417194106)  SAP AG  MAIN_NW701P04_C  20091103163937 
    sap.com  CAF-UM  7.01 SP4 (1000.7.01.4.0.20090417194111)  SAP AG  MAIN_NW701P04_C  20091103161325 
    sap.com  CORE-TOOLS  7.01 SP4 (1000.7.01.4.0.20090417021948)  SAP AG  SAP AG  20091103154019 
    sap.com  ISAGENT  8.1 SP0 (8.1.0.0.20090605095817)  SAP AG  SAP AG  20091210142716 
    sap.com  JLOGVIEW  7.01 SP4 (1000.7.01.4.0.20090417020000)  SAP AG  SAP AG  20091103154104 
    sap.com  JSPM  7.01 SP4 (1000.7.01.4.2.20090918151100)  SAP AG  SAP AG  20091201201543 
    sap.com  KM-KW_JIKS  7.01 SP4 (1000.7.01.4.0.20090514115300)  SAP AG  SAP AG  20091103161349 
    sap.com  LM-SERVICE  7.01 SP5 (1000.7.01.5.2.20091211060559)  SAP AG  SAP AG  20091224192630 
    sap.com  LM-TOOLS  7.01 SP5 (1000.7.01.5.3.20091208123420)  SAP AG  MAIN_NW701P05_C  20091228135344 
    sap.com  SAP-JEE  7.01 SP4 (1000.7.01.4.1.20090612152648)  SAP AG  SAP AG  20091103154150 
    sap.com  SAP-JEECOR  7.01 SP4 (1000.7.01.4.0.20090417015900)  SAP AG  SAP AG  20091103154414 
    sap.com  SAP_JTECHF  7.01 SP4 (1000.7.01.4.2.20090612144700)  SAP AG  SAP AG  20091103154520 
    sap.com  SAP_JTECHS  7.01 SP4 (1000.7.01.4.2.20090612152905)  SAP AG  SAP AG  20091103162132 
    sap.com  SWLIFECYCL  7.01 SP4 (1000.7.01.4.0.20090511115334)  SAP AG  MAIN_NW701P04_C  20091103151458 
    sap.com  UMEADMIN  7.01 SP4 (1000.7.01.4.0.20090417195012)  SAP AG  MAIN_NW701P04_C  20091103165828 
    For ABAP
    SAP_BASIS     701     0004     SAPKB70104
    SAP_ABA     701     0004     SAPKA70104
    ST-PI     2008_1_700     0001     SAPKITLRD1
    PI_BASIS     701     0004     SAPK-70104INPIBASIS
    CRMUIF     500     0003     SAPK-50003INCRMUIF
    SAP_BW     701     0004     SAPKW70104
    SAP_AP     700     0016     SAPKNA7016
    BBPCRM     500     0015     SAPKU50015
    CPRXRPM     400     0015     SAPK-40015INCPRXRPM
    ST     400     0021     SAPKITL431
    BI_CONT     704     0004     SAPK-70404INBICONT
    ST-A/PI     01L_CRM570     0000          -
    ST-ICO     150_700     0022     SAPK-1507MINSTPL
    ST-SER     701_2008_2     0005     SAPKITLOQ5
    LM Components were updated for EHP1 SPS21, I installed SMD Agents in DEV and some QA servers and they work, but this one specially works as a fail over for a PRD cluster enviroment, and for that reason I'm using logical name, in SMSY it is configure with the same name, do you have any ideas?
    Thanks!!!

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

  • Standalone SMD Agent for EEM won't connect to SLD

    I have installed a standalone SMD agent, which was configured properly (logs verify this) and starts up successfully, but I don't ever see it register in the SLD. Does anyone know of a guide which tells how to manage a standalone SMD agent? I want to get it connected to the SLD in Solution Manager so that I can use it as an EEM robot, but the connectivity so far is not working.
    For instance, if there is a way to get something like SM59 in an ABAP system on my SMD agent to change and test connectivity parameters, this may help.
    Cheers,
    David.

    OK, thanks for the reference to the troubleshooting guide, I had not seen that before. Using it, I found the following procedure:
    How to check if the Diagnostics agent is registered in SLD?
    ␣ Go in SLD with the url: http://sldhostname:port/sld
    ␣ Logon with a J2EE user having the role SAP_SLD_ADMINISTRATOR
    ␣ Go in the section u2018Administrationu2019
    ␣ Click on link u2018Content Maintenanceu2019
    ␣ Select the subset u2018All with Instances and class u2018Diagnostics Agent Instanceu2019
    If the class u2018Diagnostics Agent Instanceu2019 does not appear in drop down list, No Diagnostics agent is registered
    ␣ In column Name of table, check if the Diagnostics agent is present.
    This procedure verified that my diagnostics agent is in fact in contact with the SLD, but for some reason, the agent does not show up in the SLD when I go to Home > Technical Systems, nor does it show up when I go to the EEM Administration screen > Robots > Check Agents.
    So I'll have to keep researching.
    Cheers,
    David.

  • The SMD Agent 'server' hasn't been found

    I've seen this question posted, but no answer provided. I'm trying to install Wily Introscope on a Java-only (Netweaver 7) system. The SMD software is installed and the agent is running. I can see in the log files that the Wily agent  has connected to the management console.
    I'm running EHP1 on the Solution Manager server.
    When I go to Introscope Agent - Detailed Selection   and select this server this message is displayed "Failed to connect to server: "server" - Please make sure SMD Agent is up and running"
    When I attempt to run the Diagnostic Setup Wizard. I get the following message "the SMD Agent "server" hasn't been found" 
    1.) I've stopped and started the SMD agent on the client serveral times - Does not fix the problem
    2.) I've restarted Solution Manager - does not fix problem
    Any idea how to trouble shoot this issue?

    Thanks for pointing me in the right direction - here are the steps to resolve this issue.
    In my case the problem was caused by dual entries  in smsy for the server. I had the hostname and a DNS u2013 cname u2013 for the server in smsy. This was confusing Solution Manager.
    1. Use SOLMAN_WORKCENTER
    2. GoTo      ROOT CAUSE ANALYSIS  COMMON TASKS  ADMINISTRATION  AGENT ADMINISTRATION
        a. Right-click on the server with the problem and select  u201CRESET SERVER NAMEu201D
            i. The SMD agent will be disassociated with the server.  Restart the SMD agent on the server.
    3. Steps to reassign the server name
        a. Use SOLMAN_WORKCENTER
        b. GoTo     ROOT CAUSE ANALYSIS  COMMON TASKS SETUP and CHECK  DIAGNOSTIC SETUP  DIAGNOSTIC SYSTEMS  UPGRADER
            i. Select the UPGRADE NOW button
        c. Once the UPGRADER tasks completes
        d. GoTo     ROOT CAUSE ANALYSIS  COMMON TASKS SETUP and CHECK  DIAGNOSTIC SETUP MANAGED SYSTEMS  SETUP WIZARD
            i. Select the server
            ii. Reassign the SMD agent to this server
               1. The SMD agent will restart with the correct server name

  • SMD Agents for Dialog Instances and Distributed Systems

    Hi,
    We are planning to install SMD agents in our landscape.
    Is it sufficient if we install SMD agent on the central instance Host to monitor all the instances ( CI + Dialog Instances)
                                       or
    Do we need to install SMD agents individually for all the Instances each for CI and Dialog Instances.
    Also , If we have CI and DB on a separate host (Distributed Environment),  Do we need to install SMD Agent on DB host also.
    Thanks,
    Tanuj

    Hello Tanuj,
    Please refer to note 1365123 - Installation of Diagnostics Agents and check the attachments (AgentInstallationStrategy.zip) for this note.
    BR,
    SAPFan

  • SMD and SMD-agent - network load

    We have a SolMan with SMD, monitoring a portal (with SMD agent).
    The network people tell us there is a lot of communications going on between the 2 servers - approx. 10 GB/day.
    Could this possibly be the communication between SMD agent and SMD?
    (Or the comminication between the Introscope agent and the Introscope EM?)
    If so, could it be reduced by configuration of the agent (configuring the level of detail of the information it sends across)?
    Where can I find the documentation? The documentation I have found so far is about set-up - making it work - not about fine-tuning.

    Thank you for your reply.
    Are you sure that those 2 servers are dealing with this much # of data?
    That's what the network people see in their tool.
    Basically, how come you can arrive at a decision that SMD agents is using this much load..there can be any other processes too, which are causing this traffic of data...
    The reasoning is, that this is the only functional relationship. The only application on server A that has a need to communicate with anything on server B is SMD. This assumes that the application manager has not overlooked any interactions.
    On the other hand, we are now looking at port numbers and checking what's listening on those port numbers.

  • Connection between SMD Agent and SMD server via SAProuter

    In our scenario, we have to setup the connection between SMD agent and SMD server(solution manager server) via saprouter. But during the installation of SMD agent, we can only specify the hostname of the managing system, we have no place to add saprouter string(/H/..../H/). I I am not sure if we could connect the agent and server via saprouter, if so how to do it?
    Hope someone can give us your precious advices on this issue.
    Karl

    Perfect; and thanks for your response. I found this help page for developers to implement P4 support over SAP router: http://help.sap.com/saphelp_nw73/helpdata/en/48/2992d7ad8758d7e10000000a421937/content.htm
    But in the SM Diagnostics Setup options I can set up only a direct HTTP adresses and have no options to set up connections over a sap router to P4 ports directly. I can at the moment only solve my problems with NAT or firewall rules.
    And also the diagnostic agent setup has no options to config a proxy or sap router. I found yesterday a blog on sdn side with screenshots of the setup with all available connection opetions to SLD... sry I can not post this link today.
    This is an official statment of SAP from the current version of SMD guide; it is also possible but why not from the beginning???:
    In some network conficurations, the Diagnostics agent has to connect to the Managing system though a SAP router.
    This feature will be fully supported in Solution Manager 7 Ehp2 (7.02).
    In order to enable this feature in Ehp1, please contact the Diagnostics Agent support team to get information on how to
    setup the agent and on which patch level you can perform the installation.
    This thread were a long time not answared; proxy and routing connections are mostly stepmotherly handled by SAP; this is also a problem by set up of automatic RFC generations in SMSY; why there are in the setup assitents no options to set up the router string.
    I have absolutly no comprehension for this in year 2011. All this technics are good known and long time tested.
    In this case the f**k has provoked an answare to this thread and this is what I expected; but sorry for my style You are right I could also writh why the heck
    FAQ:
    SMD root side on SDN: http://service.sap.com/diagnostics
    SM FAQ: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/4e49dbea-0c01-0010-91bd-f0b61388c9ae
    SM Setup Home: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Home
    SM Diagnostic Troubleshooting Guide: https://websmp201.sap-ag.de/~sapdownload/002007974700000409092009E/DiagAgent_TroubleShooting.pdf
    SMD Candidate Setup: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents

  • H E A P   C O R R U P T E D - and smd agent shows not running

    Hello Gurus,
    My SMD agent is goes down every day when i check the status:
    I found the heap corroupted everyday with the below warnings:
    nbcsaplpa018:nedadm 19> tail hs_err_pid1888352.log
      H E A P   C H E C K  -
    Suspension of other threads succeeded.
    Heap corruption found in object at address 0x070000004ac38268. Class of object is not in the reserved heap memory area (0x002e006e006f0072).
      H E A P   C O R R U P T E D  -
    Please suggest
    Regards,
    Munish

    Please fine the file SMDAgentApplication.0.log for logs again : other file in next reply.
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[SMDAgentAppLog]/>
    <!PATTERN[SMDAgentApplication.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%t] %10s %m)]/>
    <!ENCODING[ISO8859_1]/>
    <!FILESET[0, 10, 1000000]/>
    <!PREVIOUSFILE[SMDAgentApplication.9.log]/>
    <!NEXTFILE[SMDAgentApplication.1.log]/>
    <!LOGHEADER[END]/>
    Mar 24, 2010 1:53:17 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Mar 29, 2010 10:57:12 AM [Thread[Thread-174,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Mar 30, 2010 12:18:05 PM [Thread[Thread-229,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Apr 1, 2010 1:59:00 PM [Thread[Thread-311,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Apr 1, 2010 2:00:32 PM [Thread[Thread-340,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Apr 9, 2010 5:41:47 PM [Thread[Thread-546,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    May 28, 2010 5:44:24 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    May 29, 2010 3:26:39 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    May 29, 2010 9:09:56 AM [Thread[Thread-6,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    May 30, 2010 10:13:43 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    May 31, 2010 4:00:07 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Jun 1, 2010 3:04:42 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Jun 2, 2010 4:09:21 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Jun 2, 2010 9:02:55 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Jul 20, 2010 3:07:02 PM [Thread[Thread-6,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Jul 21, 2010 5:32:08 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Jul 22, 2010 12:46:11 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Jul 22, 2010 8:28:13 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Jul 22, 2010 3:30:13 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Jul 22, 2010 9:15:34 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Jul 26, 2010 7:00:11 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Jul 26, 2010 2:56:56 PM [Thread[Thread-6,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
    Jul 26, 2010 11:25:29 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found

  • SMD agent not starting correctly FAIL: NIECONN_REFUSED (Connection refused)

    I am getting the following message when I start the agent.  I don't see any errors except for this, and when I try to connect it in agent_adminstration, it never connects.  Just eventually times out after 30 mins.
    FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
    cat jvm_SMDAgent.out
    LoadBalanceRestricted=no
    P4ClassLoad=P4Connection
    SAPDBHOST=
    SAPINFO=SMD_98_server
    SAPMYNAME=ssmsap_SMD_98
    SAPSTARTUP=1
    SAPSYSTEM=98
    SAPSYSTEMNAME=SMD
    application.home=/usr/sap/SMD/exe
    com.ibm.cpu.endian=little
    com.ibm.oti.configuration=scar
    com.ibm.oti.jcl.build=20080922_1143
    com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    com.ibm.oti.vm.library.version=23
    com.ibm.util.extralibs.properties=
    com.ibm.vm.bitmode=64
    file.encoding=UTF-8
    file.separator=/
    ibm.signalhandling.rs=false
    ibm.signalhandling.sigchain=true
    ibm.signalhandling.sigint=true
    ibm.system.encoding=UTF-8
    j2ee.dbhost=
    java.assistive=ON
    java.awt.fonts=
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    java.class.version=48.0
    java.compiler=j9jit23
    java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
    java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.home=/opt/IBMJava2-amd64-142/jre
    java.io.tmpdir=/tmp
    java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version=2.3
    java.specification.name=Java Platform API Specification
    java.specification.vendor=Sun Microsystems Inc.
    java.specification.version=1.4
    java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
    java.vendor=IBM Corporation
    java.vendor.url=http://www.ibm.com/
    java.version=1.4.2
    java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.vm.name=IBM J9 VM
    java.vm.specification.name=Java Virtual Machine Specification
    java.vm.specification.vendor=Sun Microsystems Inc.
    java.vm.specification.version=1.0
    java.vm.vendor=IBM Corporation
    java.vm.version=2.3
    jstartup.debuggable=yes
    jstartup.mode=JCONTROL
    jstartup.ownHardwareId=F2143454721
    jstartup.ownProcessId=17393
    jstartup.whoami=server
    jxe.current.romimage.version=9
    jxe.lowest.romimage.version=9
    line.separator=
    memory.manager=256M
    os.arch=amd64
    os.name=Linux
    os.version=2.6.9-89.ELsmp
    path.separator=:
    sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
    sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    sun.io.unicode.encoding=UnicodeLittle
    sun.java2d.fontpath=
    sys.global.dir=/usr/sap/SMD/SYS/global
    user.country=US
    user.dir=/usr/sap/SMD/J98/SMDAgent
    user.home=/home/smdadm
    user.language=en
    user.name=smdadm
    user.timezone=
    user.variant=
    Running SMD Agent ...
    [p4://ssmsap:50004] Agent ready.
    Initialization done.
    cat jvm_SMDAgent.out
    LoadBalanceRestricted=no
    P4ClassLoad=P4Connection
    SAPDBHOST=
    SAPINFO=SMD_98_server
    SAPMYNAME=ssmsap_SMD_98
    SAPSTARTUP=1
    SAPSYSTEM=98
    SAPSYSTEMNAME=SMD
    application.home=/usr/sap/SMD/exe
    com.ibm.cpu.endian=little
    com.ibm.oti.configuration=scar
    com.ibm.oti.jcl.build=20080922_1143
    com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    com.ibm.oti.vm.library.version=23
    com.ibm.util.extralibs.properties=
    com.ibm.vm.bitmode=64
    file.encoding=UTF-8
    file.separator=/
    ibm.signalhandling.rs=false
    ibm.signalhandling.sigchain=true
    ibm.signalhandling.sigint=true
    ibm.system.encoding=UTF-8
    j2ee.dbhost=
    java.assistive=ON
    java.awt.fonts=
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    java.class.version=48.0
    java.compiler=j9jit23
    java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
    java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.home=/opt/IBMJava2-amd64-142/jre
    java.io.tmpdir=/tmp
    java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version=2.3
    java.specification.name=Java Platform API Specification
    java.specification.vendor=Sun Microsystems Inc.
    java.specification.version=1.4
    java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
    java.vendor=IBM Corporation
    java.vendor.url=http://www.ibm.com/
    java.version=1.4.2
    java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.vm.name=IBM J9 VM
    java.vm.specification.name=Java Virtual Machine Specification
    java.vm.specification.vendor=Sun Microsystems Inc.
    java.vm.specification.version=1.0
    java.vm.vendor=IBM Corporation
    java.vm.version=2.3
    jstartup.debuggable=yes
    jstartup.mode=JCONTROL
    jstartup.ownHardwareId=F2143454721
    jstartup.ownProcessId=17393
    jstartup.whoami=server
    jxe.current.romimage.version=9
    jxe.lowest.romimage.version=9
    line.separator=
    memory.manager=256M
    os.arch=amd64
    os.name=Linux
    os.version=2.6.9-89.ELsmp
    path.separator=:
    sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
    sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    sun.io.unicode.encoding=UnicodeLittle
    sun.java2d.fontpath=
    sys.global.dir=/usr/sap/SMD/SYS/global
    user.country=US
    user.dir=/usr/sap/SMD/J98/SMDAgent
    user.home=/home/smdadm
    user.language=en
    user.name=smdadm
    user.timezone=
    user.variant=
    Running SMD Agent ...
    [p4://ssmsap:50004] Agent ready.
    Initialization done.

    cat dev_SMDAgent
    trc file: "/usr/sap/SMD/J98/work/dev_SMDAgent", trc level: 1, release: "701"
    node name   : smdagent
    pid         : 17393
    system name : SMD
    system nr.  : 98
    started at  : Wed Oct  7 08:56:32 2009
    arguments         :
              arg[00] : /usr/sap/SMD/J98/../exe/jlaunch
              arg[01] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
              arg[02] : -DSAPINFO=SMD_98_server
              arg[03] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
    JStartupReadInstanceProperties: read instance properties [/usr/sap/SMD/J98/profile/smd.properties]
    -> ms host    :
    -> ms port    : 36
    -> OS libs    : /usr/sap/SMD/exe
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/SMD/J98/profile/smd.properties
    Instance properties
    -> ms host    :
    -> ms port    : 36
    -> os libs    : /usr/sap/SMD/exe
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    Worker nodes
    -> [00] smdagent             : /usr/sap/SMD/J98/profile/smd.properties
    [Thr 182894174624] Wed Oct  7 08:56:32 2009
    [Thr 182894174624] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 182894174624] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
    [Thr 1085282656] WaitSyncSemThread: Thread 1085282656 started as semaphore monitor thread.
    [Thr 182894174624] SigISetDefaultAction : default handling for signal 17
    [Thr 182894174624] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 182894174624] CPIC (version=701.2009.01.26)
    [Thr 182894174624] [Node: SMDAgent] java home is set by profile parameter
            Java Home: /opt/IBMJava2-amd64-142
    [Thr 182894174624] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SMD/J98/../exe/jvmx.jar
    JStartupIReadSection: read node properties [smdagent]
    -> node name          : SMDAgent
    -> node type          : server
    -> node id            : 1
    -> node execute       : yes
    -> java path          : /opt/IBMJava2-amd64-142
    -> java parameters    : -DP4ClassLoad=P4Connection -Xj9 -Xmn50m -Xgcpolicy:gencon
    -> java vm version    : J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    -> java vm vendor     : IBM J9 VM (IBM Corporation)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 256M
    -> init heap size     : 256M
    -> root path          : ../SMDAgent
    -> class path         : ../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    -> OS libs path       : /usr/sap/SMD/exe
    -> main class         : com.sap.smd.agent.launcher.SMDAgentLauncher
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar
    -> parameters         : run jcontrol
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 58981
    -> shutdown timeout   : 20000
    [Thr 182894174624] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1086335328] JLaunchIStartFunc: Thread 1086335328 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [SMDAgent]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -DP4ClassLoad=P4Connection
    -> arg[  4]: -Xj9
    -> arg[  5]: -Xmn50m
    -> arg[  6]: -Xgcpolicy:gencon
    -> arg[  7]: -Dsys.global.dir=/usr/sap/SMD/SYS/global
    -> arg[  8]: -Dapplication.home=/usr/sap/SMD/exe
    -> arg[  9]: -Djava.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    -> arg[ 10]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    -> arg[ 11]: -Dmemory.manager=256M
    -> arg[ 12]: -Xmx256M
    -> arg[ 13]: -Xms256M
    -> arg[ 14]: -DLoadBalanceRestricted=no
    -> arg[ 15]: -Djstartup.mode=JCONTROL
    -> arg[ 16]: -Djstartup.ownProcessId=17393
    -> arg[ 17]: -Djstartup.ownHardwareId=F2143454721
    -> arg[ 18]: -Djstartup.whoami=server
    -> arg[ 19]: -Djstartup.debuggable=yes
    -> arg[ 20]: -DSAPINFO=SMD_98_server
    -> arg[ 21]: -DSAPSTARTUP=1
    -> arg[ 22]: -DSAPSYSTEM=98
    -> arg[ 23]: -DSAPSYSTEMNAME=SMD
    -> arg[ 24]: -DSAPMYNAME=ssmsap_SMD_98
    -> arg[ 25]: -DSAPDBHOST=
    -> arg[ 26]: -Dj2ee.dbhost=
    [Thr 1086335328] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [SMDAgent]
    -> arg[  0]: run
    -> arg[  1]: jcontrol
    [Thr 1086335328] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1086335328] Wed Oct  7 08:56:35 2009
    [Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Initial (0)]
    [Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 1086335328] Wed Oct  7 08:56:38 2009
    [Thr 1086335328] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 1086335328] JLaunchISetState: change state from [Starting (2)] to [Running (3)]
    [Thr 1101334880] Wed Oct  7 08:56:43 2009
    [Thr 1101334880] JLaunchISetState: change state from [Running (3)] to [Starting applications (10)]
    [Thr 1101334880] Wed Oct  7 08:56:48 2009
    [Thr 1101334880] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]

  • SMD Agent 7.00 or Diagnostics Agent 7.11

    Hello,
    Our managed systems are running on NetWeaver 7.00.
    We are currently implementing SAP Solution Manager Diagnostics using SOLMAN_SETUP guided procedure.
    In https://service.sap.com/swdc -
    Support Packages and Patches - Entry by Application Group" SAP Technology Components" SAP SOLUTION MANAGER" SAP SOLUTION MANAGER 7.0 EHP 1" Entry by Component" Agents for managed
    there are 2 kinds of Diagnostcis Agents :
    1. SMD Agent 7.00
    2. Diagnostics Agent 7.11
    Question :
    Can we install a Diagnostic Agent 7.11 on our managed systems running on NetWeaver 7.00 or must we install SMD Agent 7.00 ?
    Are Diagnostics Agent 7.11 supported for managed systems running on NW 7.00 ?
    Best regards
    PC

    Hi
    To avoid libraries conflicts it is highly recommended to install a Diagnostics agent which has the same kernel release
    that the SAP systems already installed on the host.
    Refer the doc in this [link|https://websmp205.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_HIER_KEY=701100035871000526434&_OBJECT=002007974700000409092009E&_SCENARIO=01100035870000000112&]  Section 2.3 Managed system page no:8
    Hope this helps you
    regards
    Naveen

  • Diagnostics Agent 7.11 vs SMD Agent 7.00

    Hello,
    In our SAP System environment, most of managed systems are running under SAP NW 7.0 platform.
    We are currently installing SMD Agent 7.00. The installation is not finished and I was wondering if we can install Diagnostics Agent 7.11 on managed systems running on SAP NW 7.0 ?
    In other terms :
    SMD Agent 7.00 have to be installed only on SAP NW 7.00
    Diagnostics Agents 7.11 have to be installed only on SAP NW 7.11 or also on SAP NW 7.00 ?
    Thanks in advance for your feedback
    Best regards
    P. Cuennet

    Yes you can install diagnostics agent 7.11 for a managed system 7.00
    It's even possible for a managed system 6.40
    Prerequisite is that your Solution Manager stack verison is 20 or higher (EHP1)
    You can find the details in the installation guide for diagnostics agent 7.11 on SAP service marketplace:
    [https://service.sap.com/diagnostics]

  • Start of SMD agent fails!

    Hi!
    After the installation of SMD AGENT 7.00 SP09 we've got some problems starting the agent.
    The errorlog says: (/usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log)
    Oct 11, 2006 2:11:26 PM [Thread[SMDAgent connection thread,5,main]] Error      Exception ID: 1160572286256
    Registering agent on server myhost.de:50004failed:
    com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
            java.lang.reflect.InvocationTargetException
    java.lang.reflect.InvocationTargetException
    However, the manual setup of the agent succeeds:
    ./smdsetup.sh /usr/java14_64 myhost.de 50004 j2ee_admin PASSWORD
    SAP Solution Manager Diagnostic - SMD Agent Setup - Copyright (c) 2005 SAP AG
    SMD Agent Setup is in process ...
    - STEP 1: checking JDK location
    JDK location is consistent: /usr/java14_64/bin
    - STEP 2: checking JDK Version
    JDK Version is correct: 1.4.2
    - STEP 3: checking Connection to SMD Server
    SMD Server check completed successfully
    - STEP 4: generating Runtime Properties
    runtime.properties has been created.
    - STEP 5: generating Launcher
    smdagent.bat has been created.
    smdagent.sh has been created.
    - STEP 6: generating SecStore
    secstore.properties: has been created.
    secstore.properties: user has been set.
    secstore.properties generation completed successfully.
    - STEP 7: checking P4 Connection and SMD Agent Registration
    SMD Agent Registration succeeded
    SMD Agent Setup completed successfully
    During the start process of the agent, the agent appears in the agent administration tab in SMD/admin, but it disappears after the erroneous shutdown.
    What can we do?
    Thanks for all hints solving our problem!
    Greetz,
    André Richter

    Hi Rahul,
    please try SMD Agent 7.00 SP10! We had no problems with this version!
    Also make sure that the OSUser has enough privileges. We use the "sidadm" to start the agent.
    Regards
    André

  • Install SMD agent on EP6 fails

    Hi,
    I get an error when installing SDM agent on EP6 (HP-UX):
    STEP 7: checking P4 Connection and SMD Agent Registration
    External Command Executed:
    /opt/java1.4/bin/java -DP4ClassLoad=P4Connection -Dsap.p4.remote_classloading=false -cp ":/usr/sap/SMD/J97/SMDAgent/lib/sapxmltoolkit.jar:/usr/sap/SMD/J97/SMDAgent/lib/smdagent.jar:/usr/sap/SMD/J97/SMDAgent/lib/tc_sec_secstorefs.jar:/usr/sap/SMD/J97/SMDAgent/lib/iaik_jce_export.jar:/usr/sap/SMD/J97/SMDAgent/lib/launcher/logging.jar:/usr/sap/SMD/J97/SMDAgent/lib/smdserver.jar:/usr/sap/SMD/J97/SMDAgent/lib/exception.jar:/usr/sap/SMD/J97/SMDAgent/lib/sapj2eeclient.jar:/usr/sap/SMD/J97/SMDAgent/lib/launcher/smdagentlauncher.jar:" com.sap.smd.setup.Setup /p4connection
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    P4 Connection succeeded but SMD Agent Registration failed
    Root exception is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of smdserver.
    I couldn't find anything on SAP Market Place but a similar thread here advised to check if SDM servers is not in maintenance mode.
    Well, it's not.
    Can someone please help?
    Thx
    Bert

    Hi,
    Did you connect to smd server http://host:port/smd and desactivate maintenance mode in Agent Administration page?
    This should solve your issue.
    Regards,
    Frederic

Maybe you are looking for

  • IMac no longer boots up to windows partition?

    Hi, I have a problem where my I installed Windows 7 on my iMac and set it to automatically boot up to the Windows partitionwhen turning on the computer. Suddenly, it's not doing that anymore. It boots up to the Apple partition and when I want to choo

  • How to restore contacts on my iphone

    Hi, I have been syncing my phone with itunes from 3 days as I have bought a new macbook pro. Suddenly yesterday due to some change of settings or I dont know what all my contacts got deleted. I tried to restore back up by right clicking the iphone op

  • [HELP] Reading PNG Problem?

    Hello, I got a PNG image in my game: http://img211.imageshack.us/img211/4742/effectquestgate10sb3.png When it is rendered in java, it appears like this: http://img381.imageshack.us/img381/6696/glitcheddb3.jpg Why is that? It also looks like that in p

  • Strange issue on newly installed 5510

    Hi all, A couple issues came up after installing our new 5510, a couple sites that uses the same ISP as our's had issues, one where we can email them but their incoming to us wasn't working, and another site we couldn't browse on the web. This all wo

  • Install error on XP laptop installing C410 software

    Bought a new HP C410 for home.  Have 4 laptops (3 Win 7 and one XPPro) and 2 Desktops, both XP Home.  Almost new D-Link DIR-628 router running WPA shared.  Every install of HP software and connection to printer through wireless went flawlessly, excep