EM Agent is not starting -

Hi DBAs,
I have installed the Oracle Grid Control Grid Control 10.2.0.5.0 on RHEL 5.4 (64 bit) and repository DB is 11.1.0.7. I installed the agent 10.2.0.5.0 on the Database server sucessfully but it is giving me the following error while starting.
[oracle@myhost bin]$ ./emctl start agent
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Starting agent ...... failed.
The agentTZRegion value in /u01/app/oracle/db/tech_st/10.2.0/agent10g/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute 'emctl resetTZ agent' and also execute the script mgmt_target.set_agent_tzrgn(<agent_name>, <new_tz_rgn>) to get the value propagated to repository.
Consult the log files in: /u01/app/oracle/db/tech_st/10.2.0/agent10g/sysman/log
I searched over this forum and found the following fix:
$export TZ=US/Eastern
$export ORACLE_HOME=/u01/app/oracle/db/tech_st/10.2.0/agent10g
$EMDROOT=$ORACLE_HOME
$EMSTATE=$ORACLE_HOME
$export EMDROOT EMSTATE
$emdctl validateTZ agent US/Eastern
but I am getting same error while starting. I am trying the emctl resetTZ agent but getting following error
$export TZ=US/Eastern
$./emctl resetTZ agent
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Updating /u01/app/oracle/db/tech_st/10.2.0/agent10g/sysman/config/emd.properties...
----- Thu Jul 8 01:18:17 2010::tzOffset for US/Eastern is 0(min), but agent is runnning with tzOffset -240(min)
----- Thu Jul 8 01:18:17 2010::trying again after waiting for 1 sec to account for daylight transition
----- Thu Jul 8 01:18:17 2010::tzOffset for US/Eastern is 0(min), but agent is runnning with tzOffset -240(min)
resetTZ failed.
I verified the agent is not running. Please help to resolve the issue.
Thanks
Shashi

You are hitting a Time Zone issue
Please check Startup Agent: Agent fails to start due to TZ issues [ID 403018.1]
On support.oracle.com
https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(bmDocDsrc=KB&bmDocType=PROBLEM&bmDocID=403018.1&viewingMode=1143&from=BOOKMARK&bmDocTitle=Startup%20Agent:%20Agent%20fails%20to%20start%20due%20to%20TZ%20issues))
Regards
Rob
http:/oemgc.wordpress.com

Similar Messages

  • OracleHome92 agent service not started

    hai All,
    I renamed my windows 2003 server machine. After rebooting the server a message appears that oracle intellegent agent exectable encountered a problem and needed to close. After that I noticeed that The oracleHome92 agent service not started. I cannot able to start that service.some eror occurs.... need any extra change?
    Please help?
    Shiju

    You wrote: "Some error occurs"
    Let me rephrase that for you: "My car won't start tell me why."
    No one can help you if you don't post relevant information.
    My advice ... Stop doing things when you don't know the implications. That is why testing environments exist. Rename the server back to its original name and then learn what to do, and test it, before doing it again.

  • CTI toolkit Agent desktop not starting

    Hi
    I have recently installed a CTI toolkit agent desktop in my PC but it is not starting and is giving error
    "Cisco Desktop client has stpped working"
    This is the first time i installed this application in my computer running windows7 64 bit.
    the version of cti toolkit is 8.0.1
    what should i look for ??

    Two things come to mind.  First make sure you have the latest version, 8.0.1 doesn't sound like the latest one.  Next, make sure you install it as administrator.
    david

  • 9i agent will not start on windows

    We have 3 servers. Oracle 9i was installed via same user with same
    rights in all cases.
    Server 1 -
    - no existing Oracle install
    - installed 9.2.0.5 and agent starts
    Server 2 -
    - old Oracle Apps 11i server
    - installed 9.2.0.5
    - agent ran from roughly map to August. Since August it refuses to
    start. This was not discovered until December so nobody knows what if
    anything happened to break it.
    Server 3 -
    - Oracle Apps 11i dev servers
    - installed 9.2.0.6
    - agent fails to start
    In both cases where the 9i agent fails to start, the 8i agent runs
    great.
    There are NOT two nic cards.
    Trace indicates agent is trying to talk to 0.0.0.0. Oracle had us
    remove a tns_admin entry in the registry but same result.
    Looking for anything to try next.

    We have 3 servers. Oracle 9i was installed via same user with same
    rights in all cases.
    Server 1 -
    - no existing Oracle install
    - installed 9.2.0.5 and agent starts
    Server 2 -
    - old Oracle Apps 11i server
    - installed 9.2.0.5
    - agent ran from roughly map to August. Since August it refuses to
    start. This was not discovered until December so nobody knows what if
    anything happened to break it.
    Server 3 -
    - Oracle Apps 11i dev servers
    - installed 9.2.0.6
    - agent fails to start
    In both cases where the 9i agent fails to start, the 8i agent runs
    great.
    There are NOT two nic cards.
    Trace indicates agent is trying to talk to 0.0.0.0. Oracle had us
    remove a tns_admin entry in the registry but same result.
    Looking for anything to try next.

  • Wily Introscope Agent does not start

    Hi,
    i am installing Solution Manager Diagnostics on a Solution Manger 7.0 System. At the moment i am on the point to install the Wily Introscop Agent and i have following problem:
    At first i tried the automatic setup and deployed the agent with JSPM and it seemed to work. I see "ISAGENT" on the System Information -> All Compontents over http://0/smd/admin and there is no log directory in the wily directory?
    Does anybody has an idea whats wrong?
    Best Regards,
    Stefan
    Edited by: Stefan on Feb 17, 2009 8:57 AM
    Edited by: Stefan on Feb 17, 2009 9:31 AM

    Hello Stephan,
    1. Wily IS Agent (2 agents) is installed ONLY in SOLMAN system.
    2. Then, with SOLMAN_SETUP Guided procedure, in third phase (Managed System Configuration),
        you deploy the Wily IS Agent to your managed system.
    To summarize :
    1. Install the ISAGENTxxx.SCA in SOLMAN only !
    2. Start the SOLMAN_SETUP guided procedure
    3. Phase I - Initial Configuration
        Phase II - Basis Configuration
        Phase III - Managed System Configuration.
    In Phase III, there are 6 steps :
    1.     Connect Managed system
    2.     Check Prerequisites
    3.     Manual Configuration
    4.     Diagnostics Configuration
    5.     Wily Introscope Configuration
    6.     Create Logical Components
    The Wily IS Agent (2 agents : IS Agent wich monitored JAVA instance and Wily Host-level Agent which a sub-process of the SMD Agent) is configured and STARTED here.
    So, you cannot start / stop by any OS command the Wily IS Agent.
    You start it from SMD.
    Hope it help you.
    Best regards
    Pascal Cuennet

  • OEM Agent will not Start

    Hello,
    We have a OMS 11.1.0.1.0 environment running on Linux.
    We have performed a Fresh Install (using OEM) of a 10.2.0.5.0 Agent to a HPUX server. We have tried 'emctl stop', 'emctl start' and 'emctl secure' commands. They all fail. We have performed a new discovery on that agent. We have removed the agent and performed a 2nd and 3rd Fresh Install. Nothing works.
    We have a 15+ server environment that is working great.
    Any ideas on why this agent won't start?
    Thanks,
    Bob Larsen

    It didn't product a .trc file, need to adjust options in emd.properties
    Do you see any problems below ?? Thanks ...
    emctl.log
    13849 :: Tue Feb 7 14:32:43 2012::AgentLifeCycle.pm: Processing start agent
    13849 :: Tue Feb 7 14:32:43 2012::AgentLifeCycle.pm: EMHOME is /oemagenthome/agent10g
    13849 :: Tue Feb 7 14:32:43 2012::AgentLifeCycle.pm: service name is
    13849 :: Tue Feb 7 14:32:43 2012::AgentLifeCycle.pm:status agent returned with retCode=0
    13849 :: Tue Feb 7 14:32:51 2012::AgentLifeCycle.pm:Watch dog processs id: 13856 exited with an exit code of 0
    13849 :: Tue Feb 7 14:34:46 2012::AgentLifeCycle.pm: Exited loop with retCode=0
    emagent.nohup
    EMHOME ================== /oemagenthome/agent10g
    --- Standalone agent
    ### Tue Feb 7 14:32:48 2012::agentTZRegion already exists in /oemagenthome/agent10g/sysman/config/emd.properties. ###
    ### Tue Feb 7 14:32:48 2012::agentTZRegion successfully validated. ###
    ----- Tue Feb 7 14:32:48 2012::Agent Launched with PID 13874 at time Tue Feb 7 14:32:48 2012 -----
    ----- Tue Feb 7 14:32:48 2012::Time elapsed between Launch of Watchdog process and execing EMAgent is 5 secs -----
    --EMAGENT_MEMCHECK_HOURS=1
    --EMAGENT_RECYCLE_DAYS=0
    --EMAGENT_TIMESCALE=1
    --EMAGENT_RECYCLE_MAXMEMORY=512
    --EMAGENT_MAXMEM_INCREASE=1
    ### Tue Feb 7 14:32:48 2012::EMWD. Monitoring 1 Components. ###
    ### Tue Feb 7 14:32:48 2012::Env changes prior to agent launch recorded in /tmp/emctl.env.13837.diff2 ###
    ### Tue Feb 7 14:32:51 2012::EMWD Checking component processes... 1 ###
    ### Tue Feb 7 14:32:51 2012::EMWD. Checking Status for EMAgent 13874 ###
    ### Tue Feb 7 14:32:51 2012::waitpid(13874) reaped=13874, processStatus=0 ###
    ### Tue Feb 7 14:32:51 2012::reapChild pid=13874, status = 1, 0
    ### Tue Feb 7 14:32:51 2012::Status for 13874 : (1, 0), 99 ###
    ----- Tue Feb 7 14:32:51 2012::Checking status of EMAgent : 13874 -----
    ----- Tue Feb 7 14:32:51 2012::EMAgent exited at Tue Feb 7 14:32:51 2012 with return value 0. -----
    ----- Tue Feb 7 14:32:51 2012::EMAgent was shutdown normally. -----
    ----- Tue Feb 7 14:32:51 2012::Exiting watchdog loop

  • CA agent is not starting uo.

    I am facing below issue while i m starting the agent in CA.
    ERROR main EMF_CATEGORY - Error: Internal Exception: - Error registering peer
    ERROR main EMF_CATEGORY - Error while connecting to server - retrying attempt 6
    ERROR main EMF_CATEGORY - Error while connecting to 'http://pacr-srv-utweb33.cvt
    y.com:8855/PSEMHUB/hub'.
    ERROR main EMF_CATEGORY - Error: Internal Exception: - Error registering peer
    ERROR main EMF_CATEGORY - Error while connecting to server - retrying attempt 7
    I check on net, n i have updated GUID in psoption table. Bounce the webserver and app server, but no luck.

    it's working fine.
    Thanks,
    Vishal

  • Oracle Intelligent Agent does not started on RH9

    Hi Sir
    I have installed Red Hat 9 and Oracle 9i Release 2 ....But When I would like to start Intelligent Agent ,I encounter with
    error => ( error in loading shared libraries : libvppdc.so No such file or directory) ..
    Anyway I am sure that my environment setting like LD_LIBRARY_PATH is correct and this .so file is existed in this path
    (Again same of your condition).
    It will be my pleasure to help me at earliest convenience.
    Regards
    Shervin

    Open up a console and login as oracle user. Execute these lines:
    $ cd $ORACLE_HOME/network/lib
    $ make -f ins_net_client.mk install
    Then edit the $ORACLE_HOME/ctx/lib/ins_ctx.mk file so that lines 13-14 change from:
    ctxhx: $(CTXHXOBJ)
    $(LINK) $(CTXHXOBJ) $(INSO_LINK)
    to
    ctxhx: $(CTXHXOBJ)
    $(LINK) -ldl $(CTXHXOBJ) $(INSO_LINK)
    Then do
    $ make -f $ORACLE_HOME/ctx/lib/ins_ctx.mk install
    Now you should be able to start your agents with
    $agentctl start

  • SQL Data Sync Agent can not start - Debug error in windows 7 x86

    Log file as per below
    LocalAgentHost 1/3/2013 11:55:31 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:Main,
    message:Microsoft SQL Data Sync Windows service is starting as a Windows Service.
    LocalAgentHost 1/3/2013 11:55:31 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:OnStart,
    message:Microsoft SQL Data Sync Windows service starting.
    LocalAgentHost 1/3/2013 11:55:31 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:OnStart,
    message:Starting a service worker thread.
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:OnStart,
    message:Started a service worker thread.
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:OnStart,
    message:Microsoft SQL Data Sync Windows service started successfully.
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:StartUxWcfService,
    message: Namedpipe bd54233d-16ce-46d3-8858-5e564732b21c, BaseAddress net.pipe://localhost/bd54233d-16ce-46d3-8858-5e564732b21c
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:StartUxWcfService,
    message: Opened WCF Host
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:StartServiceThread,
    message: GetEntryAssembly().Location: C:\Program Files (x86)\Microsoft SQL Data Sync\bin\LocalAgentHost.exe, GetExecutingAssembly().Location: C:\Program Files (x86)\Microsoft SQL Data Sync\bin\LocalAgentHost.exe, Process.GetCurrentProcess().StartInfo.WorkingDirectory:
    LocalAgentHost 1/3/2013 11:55:37 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:AgentConfigDataManager.DownloadAndCacheServiceUrisFromLocator,
    message:Scale unit found
    AgentCore 1/3/2013 11:55:40 AM  id:AgentCore_InstanceStarted, rId:, sId:65915150-1284-4a17-9c13-d58e2830fcd9, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0
    ThreadId:40. Dispatcher started. Waiting
    ThreadId:43. GetRequest started.
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:46. GetRequest started.
    ThreadId:41. GetRequest started.
    ThreadId:48. GetRequest started.
    ThreadId:45. GetRequest started.
    ThreadId:42. GetRequest started.
    ThreadId:47. GetRequest started.
    ThreadId:44. GetRequest started.
    ThreadId:49. GetRequest started.
    ThreadId:50. GetRequest started.
    ThreadId:51. GetRequest started.
    ThreadId:52. GetRequest started.
    ThreadId:53. GetRequest started.
    ThreadId:54. GetRequest started.
    ThreadId:55. GetRequest started.
    ThreadId:56. GetRequest started.
    ThreadId:57. GetRequest started.
    ThreadId:58. GetRequest started.
    ThreadId:59. GetRequest started.
    ThreadId:60. GetRequest started.
    ThreadId:61. GetRequest started.
    ThreadId:62. GetRequest started.
    ThreadId:63. GetRequest started.
    ThreadId:64. GetRequest started.
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest

    Hi,
    I believe that your issue is resolved by now. Please try this step is the issue still persists.
    its security issues and re-install the data sync with domainname\Myaccount user and give the user as adminitsrator privileges and change the time of your system.
    http://social.technet.microsoft.com/wiki/contents/articles/2655.sql-azure-data-sync-troubleshooting-guide.aspx
    Girish Prajwal

  • Server Intelligence Agent is not starting in BOXI R3.1 with FP 1.3

    Hi All,
    Iam trying to start the SIA ,but it is started then stopped.
    It is installed on Windows 2003 SP2 and Oracle 11g database.
    can i have any workaround solution.
    Any help would be appreciated.
    Edited by: mahesh ch on Apr 21, 2009 10:26 AM
    Edited by: mahesh ch on Apr 21, 2009 10:27 AM

    Hi,
    please look in the <bobj installation folder>\BusinesObjects Enterprise 12.5\logging folder for newly created log files (after trying to restart the SIA). Please scan these files for error messages regarding the start of SIA.
    Regards,
    Stratos

  • Agent service on Windows does not start

    Ok:
    Grid Control 10.2.0.1, repository 10.1.0.4, Linux Red hat 4
    Target node is a windows 2003 server (kinda, its on VMWare) with no service pack installed (don't ask). There is no oracle software on the target node except an oracle 10.2.0.3 agent. We just monitor the host up/down.
    Ok this was working until the windows server crashed. It was restarted but then the agent would not start. It complained about not being able to load files and after three attempts it crashed. I removed it from grid, deinstalled the agent then reinstalled it with no errors. The same thing then happened, start the agent ok, then try an upload and it would fail and crash the agent:
    2007-04-12 14:22:14 Thread-1820 ERROR upload: Failed to upload file A0000001.xml, ret =
    -6
    2007-04-12 14:22:14 Thread-1820 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
    2007-04-12 14:22:14 Thread-1820 ERROR upload: Error in uploadXMLFiles. Trying again in 72.00 seconds or earlier.
    2007-04-12 14:22:16 Thread-2360 WARN upload: FxferSend: received fatal error in header from
    repository: https://<grid_host>:1159/em/upload
    FATAL_ERROR::500|ORA-20206: Target does not exist: Agent does not exist for
    https://<target_host.com>:3872/emd/main/
    ORA-06512: at "SYSMAN.EMD_LOADER", line 1700
    ORA-06512: at line 1
    2007-04-12 14:22:16 Thread-2360 ERROR upload: number of fatal error exceeds the limit 3
    2007-04-12 14:22:16 Thread-2360 ERROR upload: agent will shutdown now
    2007-04-12 14:22:16 Thread-2360 ERROR : Signalled to Exit with status 55
    2007-04-12 14:22:16 Thread-3776 ERROR main: EMAgent abnormal terminating
    Rebooted the box (its windows after all!!) but now its worse!
    The agent service refuses to start at all, when I try to start it via the services panel I get straightaway 'Error 1053 The service did not respond in a timely fashion'. An emctl start agent from the command prompt produces a 'The service is not responding to the control
    function'.
    In the logs:
    2007-04-13 09:03:32 Thread-1872 WARN http: snmehl_connect: connect failed to (<target_host.com>:3872): No connection could be made
    because the target machine actively refused it.
    (error = 10061)
    2007-04-13 09:03:32 Thread-1872 ERROR main: nmectla_agentctl: Error connecting to
    https://<target_host.com>:3872/emd/main/. Returning status code 1
    But nothing is grabbing the 3872 port on the target host for the agent. The target host can 'see' the grid control server. There is no firewall in between.
    I have an SR open, oracle are pointing the finger at a dodgy agent install (I've sent them the install logs to verify) or a firewall issue, but the target host certaintly does not have one.
    I'm a bit of a loss now to be honest, any thoughts anyone? Not really used the agent on windows much.

    If I clean out the logs and do:
    emctl start agent
    emctl status agent
    The only logs produced are emctl.log:
    4064 :: Fri Apr 13 09:38:28 2007::AgentLifeCycle.pm: Processing start agent
    4064 :: Fri Apr 13 09:38:28 2007::AgentLifeCycle.pm: EMHOME is c:\app\ora\product\agent\agent10g
    4064 :: Fri Apr 13 09:38:28 2007::AgentLifeCycle.pm:Exiting with 2
    3972 :: Fri Apr 13 09:39:03 2007::AgentLifeCycle.pm: Processing status agent
    3972 :: Fri Apr 13 09:39:03 2007::AgentStatus.pm:Processing status agent
    3972 :: Fri Apr 13 09:39:05 2007::AgentStatus.pm:emdctl status returned 1
    emdctl.log which is blank and emdctl.trc which is the output I posted earlier. Not very much to go on at all

  • "Could not start Agent" with SunMC 3.6.1 on Red Hat Enterprise release 4

    Hi everyone,
    I'm trying to install the Linux agent from the SunMC 3.6.1 installation dvd on a RedHat system (kernel 2.6). The installation seems to go fine, but while seting up the agent I recieve the following eror:
    /opt/SUNWsymon/base/sbin/xget: error while loading shared libraries: libxcfg.so.1.0: cannot open shared object file: No such file or directory
    /opt/SUNWsymon/base/sbin/xput: error while loading shared libraries: libxcfg.so.1.0: cannot open shared object file: No such file or directory
    Naturally, in the end you get the message "Could not start Agent"...
    Has anybody experienced this with a RedHat system or any other Linux system?
    Best Regards,
    Emerald

    Hi!
    I am trying to install SunMC 4.0 agent in a Red Hat Enterprise Linux AS release 4 (whith a SunMC server installed in a Solaris 10 platform).
    I had installed the agent in the Red Hat, but the agent did not start.
    I got this messages from the agent.log ( the same messages that Emerald)
    [00000000 0046 ]info May 14 10:19:25 agent Channel already exists: syslog......................
    [00000001 0048 ]info May 14 10:19:25 agent using ip mode for URL addressing....................
    [00000002 003b ]info May 14 10:19:25 agent enabling timed jobs.................................
    [00000003 004d ]info May 14 10:19:25 agent subagent registry successfully loaded...............
    [00000004 005a ]info May 14 10:19:25 agent loading trap actions: subagent-manager-trap-action..
    [00000005 0040 ]info May 14 10:19:25 agent startLegacySubagents: <>............................
    [00000006 003e ]info May 14 10:19:25 agent activating MIB objects..............................
    [00000007 0047 ]info May 14 10:19:25 agent *** shutting down subagents ***.....................
    [00000008 005d ]error May 14 10:19:25 agent stopemd: action command script em-daemon.sh not found.
    [00000009 007b ]error May 14 10:19:25 agent invalid dictionary entry: internal outBoundTrap in b
    ase-agent.x(221) at token '???'............................................................................
    [0000000a 0042 ]error May 14 10:19:25 agent *** aborting execution ***..........................
    [0000000b 0046 ]info May 14 10:20:29 agent Channel already exists: syslog......................
    [0000000c 0048 ]info May 14 10:20:29 agent using ip mode for URL addressing....................
    [0000000d 003b ]info May 14 10:20:29 agent enabling timed jobs.................................
    [0000000e 004d ]info May 14 10:20:29 agent subagent registry successfully loaded...............
    [0000000f 005a ]info May 14 10:20:29 agent loading trap actions: subagent-manager-trap-action..
    [00000010 0040 ]info May 14 10:20:29 agent startLegacySubagents: <>............................
    [00000011 003e ]info May 14 10:20:29 agent activating MIB objects..............................
    [00000012 0047 ]info May 14 10:20:29 agent *** shutting down subagents ***.....................
    [00000013 005d ]error May 14 10:20:29 agent stopemd: action command script em-daemon.sh not found
    Had anyone resolve this isue?? or had any ideas to resolve it??
    Thanks in advance.
    maza

  • Coldfusion 9  ODBC Agent & ODBC Server not starting

    Hello !
    I currently have Coldfusion 9 Enterprise Edition 64 bit installed on a Windows 2008 R2 64 bit server.  I did not notice this before but on this server, both the Coldfusion 9 ODBC Agent & Server services will not start.  I have tried starting them but they start for a second and then stop.  A dialog box then gets displayed which says "The Coldfusion 9 ODBC Agent service on Local Computer started and then stopped.  Some services stop automatically if they are not in use by other services or programs".  I have checked the event viewer on the server and I am seeing the following messages on the enterprise edition server.
    The description for Event ID 0 from source ColdFusion 9 ODBC Agent cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    ColdFusion 9 ODBC Agent@LOCALHOST,ErrorCode=430,ErrorMessage=Failed to open event trace file because the file version is not recognised.
    The description for Event ID 0 from source ColdFusion 9 ODBC Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    ColdFusion 9 ODBC Server@LOCALHOST,ErrorCode=430,ErrorMessage=Failed to open event trace file because the file version is not recognised.
    The strange this is that I have Coldfusion 9 Standard Edition 64 bit also installed on another Windows 2008 R2 64 bit server and both of the ODBC services on that machine are starting fine.  I have checked the account these services are running under on both servers and both services on both machines are running under the local system account so I am not sure if it is permission related or not.
    I would appreciate it if some could assist me in getting these services started and what I need to do.
    Thank you.
    Ed

    Has anyone bothered to file a bug report for this issue (I just searched the bug tracker and couldn't see one that applied to this issue)?  I see this has bit several people already, but unless you file an official bug report, Adobe won't know.  They don't monitor these forums with an eye to identifying bugs.
    -Carl V.

  • Could not start agent

    Hi, I've managed to install SMC3.6 agent on a Solaris 8 platform but I was unable to start my agent. I get "Could not start agent" whenever i invoked the ./es-start -a command.
    I've removed SMC3.6 agent and installed with 3.5 and it works. But I still prefer to use 3.6.
    Do I require any patches for SMC3.6 agents?

    I've tried "sh -x" like you asked me to and I get:
    # sh -x
    # ./es-start -aOops, I meant "sh -x es-start -a". "sh -x" should
    show you every line of the startup shell script as
    it's being run. But it looks like you found the
    problem anyways...
    couldn't load file "pkgsymon.so": ld.so.1: esd:
    fatal: relocation error: file
    /opt/SUNWsymon/base/lib/sparc-sun-solaris2.8/
    liblaccess.so.1.0: symbol free_proflist:referenced
    symbol not found
    invalid command name "unordered_slice" while
    executing "unordered_slice internal value"
    invoked from within "source toe-basic.toe"
    invoked from within "source base-$file.tcl"I'm no expert with Solaris libraries, but it looks
    like the files "pkgsymon.so" or "liblaccess.so.1.0"
    can't be found. You said that you had other Solaris 8
    systems that run 3.6 fine: can you see where they
    have those files:
    find /opt/SUNWsymon -name pkgsymon.so
    find /opt/SUNWsymon -name liblaccess.so.1.0
    ...then if they are in the right place (or exist at
    all) on the problem box? And does it have a
    /opt/SUNWsymon/base/lib/sparc-sun-solaris2.8
    directory?
    Maybe SunMC detected the wrong version of Solaris on
    install or something, and either didn't install the
    proper libraries, or put them in sparc-sun-solaris2.7
    or sparc-sun-solaris2.9?
    Does you root user have different environment
    variables set (i.e. LD_LIBRARY_PATH) on the problem
    box than on the ones that work?
    At this point i'm just guessing: 3.6 is so new I
    haven't had a lot of debugging time with it. Worst
    case you can call Sun support and yell at them...
    (just kidding, please don't do that :) )
    Regards,
    [email protected]
    Hi Mike,
    Found the 2 files in the /opt/SUNsymon. Checked and confirmed /opt/SUNWsymon/base/lib/sparc-sun-solaris2.8 is there. Will try touse sunchecktool to see if i need any patch fer that fella.
    Anyway, about yelling at the Sun guys. That's a good one! :)
    Thanks!

  • Sql Server Agent not starting automatically in failover in a clustered environment.

    Hi,
    We are running Sql Server 2008 R2 as a 2 node cluster in Windows 2008 R2
    server. In the Sql Server Configuration manager we find that service of
    the Sql Server(database engine) as got a start mode as manual being
    an instance in the 2 node cluster. When the node in which the service is
    running fails the the Sql Server service gets started in the other node. However
    we find that the  Sql Server Agent service(whose start mode is also in manual)
    does not get started automatically in the other node along with the Sql Server
    service.Why does the cluster service do not start Sql Server agent service as well.
    Should we make the Sql Server agent service start mode to be automatic
    instead of being manual as it is now? Thanking you in advance
    Binny Mathew

    Folks - the startup type of all clustered services should be set to manual - when you virtualize SQL Services, they are put in manual startup mode and this should not be changed. It is the cluster manager which starts the SQL and SQLAgent when a
    failover happens (SQL does not start SQLAgent). If your SQLAgent doesn't start after a cluster failover, check the SQLAgent logs to see what the root cause of the problem is and rectify it. You should not change the startup type to "Automatic" -
    leave it as manual
    Satish Kartan www.sqlfood.com
    I suspect that your clustered SQLAgent resource is currently NOT dependent on SQL resource. If not, make SQLAgent dependent on SQL resource, which will coerce SQLAgent to wait for the SQL resource to come online before it brings itselft (SQLAgent) resource
    online, when a failover happens.
    Satish Kartan www.sqlfood.com

Maybe you are looking for

  • How can I get icloud to back up my computer?

    I am set up with icloud and had the icloud icon on my desktop, which worked without problems for several months. Now the icloud icon is gone, and the only way to retrieve the saved documents is in a file entitled "previous local idisks". I looked und

  • RABAX_STATE error in SOLMAN_SETUP step 6.6

    Hi all, I'm doing the Solman_setup, step "System Preparation" for a new Solution Manager 7.1 sp 14. As I try to get into the task 6.6 "Connect Diagnostics" the system generates a short dump : Category               ABAP Programming Error Runtime Erro

  • Incomplete import from OE in XP. Not all folders imported, and no messages imported.

    I have OE installed in WindowsXP. Installed Tbird. Tried import tool to import everything from OE. Only a few of the folders showed up, and no messages were imported. Tried uninstall and re-install of TBird...no help. Any assistance will be greatly a

  • Accidentally trashed iPhoto Library - how to remake

    Hi, I have a user who accidentally trashed her iPhoto Library and emptied the bin. With the tool Photorec I am in the progress of finding all jpg on the disk system - it takes a lot of time and it is not finished yet. So far more that 85.000 files wi

  • Recently ran out of space on c:

    I used the preferences to change my iTunes library location from my c: drive to my j: drive where I had a lot more space. Unfortunately, now my iTunes can not location any of the purchased music, tv shows or movies I previously purchased. How do I ge