Agent service management

I have several agents that are registered to an older ZLM 7.1 server. I want to move them to a new server running 7.2ir2. They way I moved a few was to issue the command rug sd <https://old server URL> then rug sa <https://new server URL>. Is there an easier way to do accomplish this or is using the rug sd and sa commands the way to go. I have several more agents I need to move over to this new server and wanted to use the most effective means. I couldn't find any mention of this in the ZLM 7.2 Admin guide so I thought I would see what answers I could find from this board.

Well, that didn't work. It looks like the agent is registered to both ZLM servers when I look in the Control Center. I can refresh and reboot a client from either ZLM server.
Another question I had is what is the proper procedure to update the agent? When I run a rug ping I get:
ZMD 7.2.0, Copyright (C) 2007 Novell, Inc.
Started at 3/9/2009 1:10:43 PM (uptime: 0 days, 1 hours, 18 minutes)
RSS size: 171544
Network Connected: Yes
Running on Mono 1.2.2
OS Target: SUSE Linux Enterprise Server 10 (x86_64)
Module Name | Description
-------------------+-------------------------------------------------
Image Agent Module | Novell ZENWorks Imaging Agent
Policy Manager | Manages policy enforcement on the device
Settings | Handles Settings refresh events.
TessModule | Tess Module
Inventory | Software and Hardware inventory module for Linux
NetworkManager | NetworkManager support
Package Management | Package Management module for Linux
RMModule | Remote Management module
ZENworks Server | SOAP methods used by a ZENworks server
Scheduled Actions | Scheduled Actions module for ZMD
XML-RPC interface | Export ZMD public interfaces over XML-RPC
This is on a SLES 10sp1 64 bit machine. I would like to upgrade it to
ZMD 7.2.2, Copyright (C) 2008 Novell, Inc.
ZLM Hot Patch Level - 3
Started at 2/4/2009 9:51:43 AM (uptime: 33 days, 3 hours, 52 minutes)
RSS size: 124168
Network Connected: Yes
Running on Mono 1.2.2
OS Target: SUSE Linux Enterprise Server 10 (x86_64)
Module Name | Description
-------------------+-------------------------------------------------
Image Agent Module | Novell ZENWorks Imaging Agent
Policy Manager | Manages policy enforcement on the device
Settings | Handles Settings refresh events.
TessModule | Tess Module
Inventory | Software and Hardware inventory module for Linux
NetworkManager | NetworkManager support
Package Management | Package Management module for Linux
RMModule | Remote Management module
ZENworks Server | SOAP methods used by a ZENworks server
Scheduled Actions | Scheduled Actions module for ZMD
XML-RPC interface | Export ZMD public interfaces over XML-R
I am having a time trying to figure out the best course of action to update the client and move the client to a different ZLM server to control updates, etc.

Similar Messages

  • Why SCOM 2012 R2 Agent version for Service Manager servers is 6.1.7221.49, why not 7.1.10184.

    Hi ,
    In SCOM 2012 R2 console  if i look at all of my agent managed servers have agent builds of 7.1.10184 but my two service manager  servers have agent builds of 6.1.7221.49
    Can anyone let me know is this known issue or how can we upgrade the agent to correct version.
    Thanks in advance
    Bharath

    Hi,
    SCOM and SCSM are built on the same structure, Management Servers and DAta Warehouse etc. This means that when you install the SCSM Management Server, the Microsoft Monitoring Agent is also installed. When
    you want to monitor Service Manager and the server it´s installed on, you need to configure the SCOM parameters from the control panel at the SCSM management server.
    If you were to try and install the SCOM agent at the SCSM server, it would fail and tell you that you can´t install the agent on a server where Service Manager is installed. The agent will be upgraded when
    you upgrade Service Manager so this is all expected and It´s as it should be :)
    Regards,
    Daniel
    IT Consultant at Viridis IT

  • Microsoft Monitoring Agent Service on Management Servers - 2012R2

    Hi,
    Is the Microsoft Monitoring Agent Service supposed to be running on Management Servers?
    I can't remember if I have added an agent by accident, or if this is part of the install.
    Thx,
    John Bradshaw

    When you install Management server, SCOM will automatic install Microsoft Monitoring Agent service. However, Microsoft Monitoring Agent service default installation path in Management server, c:\program files\Microsoft system Center 2012 R2\Operations
    Manager\Server\health Service state, is different to ordinary agent machine which installation path is c:\program Files\Microsoft Monitoring Agent\Agent. Moreover, SCOM 2012 R2 uses Microsoft Monitoring Agent to collect and monitor server status and performance
    whether they are SCOM agent or Management server.
    Roger

  • Management Agent service not created with 10gR2 RAC DB install on Win2003?

    Our 10gR2 RAC installation on Win2003 platform didn't create management agent service. After installing and setting up current release of OEM with Grid Control (10.1) and installing Management Agent from 10.1 OEM distribution (install additional management agents option), agent service is up and running. However, there is one small problem:
    All target configuration xml files are created under 10.2 Oracle home, and agent running from 10.1 home does not see them - which means database, listener, etc are not registered in OEM.
    Is this a known problem, and is there solution for it?
    thanks,
    Dejan Bogojevic
    ps. message posted on metalink also

    GlobalBank.ESB application will be created only when you run DynamicResolution
    Setup.
     run \Source\Samples\DynamicResolution\Install\Scripts\setup_bin.cmd to install GlobalBank.ESB application
    on BizTalk Server.
    thanks Rachit.

  • Unable to start SQL server agent service

    hi,
    We have 2 Node SQL Cluster that was working fine. Then We migrated the Linux DNS to Windows DNS successfully.Now restarted the SQL Server after it when we try to start the SQL Server Agent service its says the below msg while machine name and cluster
    entries are in windows dns and resolving the IP to name and name to IP
    Error msg: The MSSQLSERVER service on Local Computer started and then stopped.  Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service." error message.
    But whenever we set the Linux DNS Server ip in SQL Servers then it successfully starts the service. Now i want to know why its happening and what are the requirements or DNS entries/SPN which we missing when we migrated the linux DNS to windows
    dns
    Sagar

    I was experiencing this issue or one just like it on one of our SQL clusters (SQL Server 2008 R2, two node).
    The fix for us was the database Security Login for: NT SERVICE\SQLAgent$<instancename>  was missing.  The actual service account assigned to the SQL Agent service was a valid domain account and we had the credentials correct in the service
    configuration, so no changes were needed there.
    Using SQL Server Management Studio we manually added this BUILT IN account ( NT SERVICE\SQLAgent$<instancename> ) to the instance, and then assigned it user role = sysadmin (to go along with the default role = public).
    Once this was done, we tried to restart the clustered SQL Agent service and it started and remained started.
    Hope this helps someone, we spent over a day pouring over the installation trying to find the cause.
    This worked for me, thanks:-)

  • SQL server agent job running as Agent Service Account whose service account does not have r/w access but is still able to write?

    Hi. I am newer to SQL server security and am reviewing some of our SQL server's configuration to make sure the services are running under accounts with least privilege.  I have a SQL server 2012 instance whose Agent service is configured to run
    under an AD user account named 'SQLServices'.  The jobs on this server are configured to run as 'SQL server agent service account', which means they should execute as user 'SQLServices'.  The jobs are set up to execute SSIS packages which read and
    write to a database on the same server where the agent job is scheduled and SSIS package installed (all on same server).  The jobs are currently executing without error and are reading writing data correctly.  Upon close examination, it turns out the
    SQLServices account is not assigned to the 'sysadmin' role and had no users mapped to any databases on this server.  How are these jobs working?  I verified in profiler that the login name indeed is 'SqlServices'.  I also verified
    that SQLServices login has no database access by remote-ing onto the server and trying to log into the DB, and access was denied as expected.  According to the literature, the Agent service needs to be a member of 'sysadmin role' but I am reading
    some cases where that is not necessarily the case.  So this is not so concerning.  What is concerning is that the login 'SQLServices' had no access to the databases on that server yet it is reading and writing to the databases as if it does. 
    The only thing I can think of is maybe jobs run as 'SQL server agent service account' on the same server as the databases it r/w to somehow has some kind of default access.  What am I missing here?  Any input would be helpful.

    After 2 days on this forum I found the answer to my own question.  In retrospect, I should have posted this under 'SQL Server Security', but I didn't know it existed.
    The 2 threads below explain that Sql agent actually runs using SID (service) NT SERVICE\SQLSERVERAGENT if you chose that when you installed.  This will automatically create an associated login NT SERVICE\SQLSERVERAGENT in SQL server with sqladmin
    role.  This is the login that Agent uses to connect to the local instance of SQL server.  If you changed to domain account to run the service during install or after using config manager, basically NT SERVICE\SQLSERVERAGENT is still
    used to connect to your local instance behind the scenes (even though you will still see your domain user as account), and the domain account is used to reach outside the server. 
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9e6bb2de-8fd0-45de-ab02-d59bbe05f72e/servicedatabase-accounts-nt-servicemssqlserver-nt-servicesqlserveragent-what-are-they-for
    https://social.technet.microsoft.com/Forums/sqlserver/en-US/b83a52fd-fe11-4c28-a27b-88be8ae79f2a/how-do-i-change-sql-server-agent-service-account-to-nt-servicesqlserveragent?forum=sqlsecurity

  • Service Manager data warehouse management server Installation fails

    Hi there,
    In Virtual Machine Windows Server 2012 R2 Standard with my user being a Local Admin and SQL Admin. I tried to do a Service Manager data warehouse management server
    first installation I am facing the following image as error:
    In the event viewer I get the following error:
    "Microsoft System Center 2012 R2 Service Manager -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 25211
    The arguments are: -2147024809, The parameter is incorrect."
    In the Setup log, some of the errors are:
    WixRemoveFoldersEx:  Entering WixRemoveFoldersEx in C:\Windows\Installer\MSI35E.tmp, version 3.7.1224.0
    WixRemoveFoldersEx:  Error 0x80070057: Missing folder property: PSCONFIGFOLDER.A591E3B4_D228_431D_BF89_99D52C8FFB76 for row: wrf4582BC4C5CC47B1D2380408CD7A752DC.A591E3B4_D228_431D_BF89_99D52C8FFB76
    CustomAction WixRemoveFoldersEx.A591E3B4_D228_431D_BF89_99D52C8FFB76 returned actual error code 1603 but will be translated to success due to continue marking
    CAStartServices: CAStartServices was passed . OMCFG
    CAStartServices: Checking if service already started. OMCFG
    CAStartServices: Attempting to start service. OMCFG
    CAStartServices: StartService failed. Error Code: 0x8007042D.
    ConfigureSDKConfigService: CAStartServices failed, trying again.... Error Code: 0x8007042D. OMCFG
    Action start 17:47:05: _SetHealthServiceConfig.80B659D9_F758_4E7D_B4FA_E53FC737DCC9.
    GetMsiFeatureState: Failed to get feature state. Error Code: 0x80070646. MOMServer
    MSI (s) (EC!4C) [17:47:05:483]: Note: 1: 2711 2: MOMGateway
    SetHealthServiceConfig: Failed to get Feature State.. Error Code: 0x80070646. MOMServer
    GetMsiFeatureState: Failed to get feature state. Error Code: 0x80070646. MOMGateway
    I have checked the following post but it did not help me:
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/c42bb04d-a51e-4037-a8a3-37d714d6faac/scsm-management-server-installation-fails?forum=systemcenterservicemanager
    Could you please help me with this issue?
    Thanks a lot,
    M

    Hi,
    Sorry I cannot post the full log. I have found also these errors in the log:
    Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.RegisterSdkSCP
    RegisterSdkSCP: There is no previous serviceConnectionPoint
    RegisterSdkSCP: Creating New serviceConnectionPoint
    RegisterSdkSCP: Adding ACL for current user: DOMAIN\InstallationAccount
    RegisterSdkSCP: Adding ACL for SM Admini: DOMAIN\SCSMDWadmins
    RegisterSdkSCP: Error: Access is denied.
    InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "D:\Program Files\Microsoft System Center 2012 R2\Service Manager\MOMConnectorCounters.ini"
    InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
    InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
    InstallPerfCountersLib: Retry Count : .
    InstallHSPerfCounters: Failed to install agent perf counters. Error Code: 0x80070057.
    Thanks for your reply.

  • Report Subscription by email error - The SQL Agent service is not running

    Hello All,
    This may be an easy answer, so please excuse my ignorance if I am overlooking something simple. I a simply trying to setup Report Subscriptions to be emailed to me. We currently have essentially 3 servers in use in our environment - a CAS, a Site server
    and a SQL 2012.
    I have configured the email settings in Reporting Services Configuration Manager on the Site server and was finally able to see the email option in the Create Subscription Wizard, but it errors out with:
    System.Web.Services.Protocols.SoapException: The SQL Agent service is not running. This operation requires the SQL Agent service. ---> Microsoft.ReportingServices.Diagnostics.Utilities.SchedulerNotRespondingException: The SQL Agent service is not running.
    This operation requires the SQL Agent service.   at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateSubscription(String Report, ExtensionSettings ExtensionSettings, Boolean isDataDriven, DataRetrievalPlan DataRetrievalPlan, String
    Description, String EventType, String MatchData, ParameterValueOrFieldReference[] Parameters, Guid batchId, String& SubscriptionID)   at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateSubscription(String Report, ExtensionSettings
    ExtensionSettings, String Description, String EventType, String MatchData, ParameterValue[] Parameters, String& SubscriptionID)
    We do not have SQL installed locally, therefore it makes sense that the Agent service is not running. How do I subscribe to alerts in SCCM without a local installation of SQL?
    -Brad

    I am positive - see screenshots below of services on the SQL server:
    Yes, reports work perfectly otherwise... Just cannot subscribe.
    -Brad

  • Unable to start the Agent service in EPM

    Hello Experts,
    I have installed HFM,FDQM,HFR Version 11.1.1.3 in 2003 os with Oracle database.I have the following questions
    1.During the Configuration Financial management I have given 'Administrator' as a DCOM user instead of 'admin' what I have created as a DCOM user.If i give 'admin' as a Dcom user it is throwing error like Dcom configuration failure. So i given 'Administrator'for successful configuration.is it correct ?
    2.After that i can't able to login in windows client to create application but i can able to login in to shared services and can create a user.With that user i can able to create application in Windows client which has application creator right with shared services.
    3.I am not able to launch the workspace page i.e..I am not able to launch the 'index.jsp' page
    4.Finally when I want to stop the 'Agent service' it is showing 'Start' status.
    I want to know the exact solutions for my errors and regarding DCOM user.
    Please give me clear explanations regarding this thread and thanks in advance.

    Hello Experts,
    I have installed HFM,FDQM,HFR Version 11.1.1.3 in 2003 os with Oracle database.I have the following questions
    1.During the Configuration Financial management I have given 'Administrator' as a DCOM user instead of 'admin' what I have created as a DCOM user.If i give 'admin' as a Dcom user it is throwing error like Dcom configuration failure. So i given 'Administrator'for successful configuration.is it correct ?
    2.After that i can't able to login in windows client to create application but i can able to login in to shared services and can create a user.With that user i can able to create application in Windows client which has application creator right with shared services.
    3.I am not able to launch the workspace page i.e..I am not able to launch the 'index.jsp' page
    4.Finally when I want to stop the 'Agent service' it is showing 'Start' status.
    I want to know the exact solutions for my errors and regarding DCOM user.
    Please give me clear explanations regarding this thread and thanks in advance.

  • High Watermark issue with monitoring Service Manager 2012 R2

    Hi,
    Our customer has a Service Manager / Operations Manager 2012 R2 environment where SCOM will regularly generate an alarm related to High Watermark monitoring on the Service Manager data warehouse - not every day though. The alarm looks like this:
    Value of 3559 is not higher than 3559
    This value hasn't changed for weeks.
    Having done a lot of searching we have found nothing but reference to the same recurring flow of information where people keep mentioning different values but there is no conclusion of what this might be caused by and how to solve it. The solutions
    have become outdated anyway. Here is one example:
    http://social.technet.microsoft.com/forums/systemcenter/en-US/889af8f3-cdf8-4d88-ae99-5dbe18d529ef/service-manager-2012-data-warehouse-high-watermark-monitor
    The Service Manager Database Account in SCOM is our service account that has sysadmin in SQL. Basically, with regards to the security configuration, our customer should be covered.
    To my knowledge agent-based and agentless monitoring have both been supported since SCSM 2012 SP1. Also, we have the latest management pack for Service Manager monitoring in SCOM, at the moment this should be
    7.5.3079.0.
    As mentioned above the value has not been changing for quite some time and nor has it in the database.
    My questions are the following:
    - Is there anyone that has found a solution in the meantime, especially with regards to R2?
    - What is the purpose of High Watermark monitoring for the data warehouse? Why does this need to be monitored?
    - We would like to understand the nature of this value better. Should it be higher each day compared to the day before?
    - Could it just be overriden in SCOM?
    Many thanks in advance!

    Rather unexpectedly, the SCOM alarm disappeared overnight and when checking the workflow in the incident that was generated from the alarm, the incident got a Resolved status right before midnight at 23:59:58. We have a ConfigMgr connector that is scheduled
    to run at 23:00 which we had disabled a day ago to check something else. But I don't think it had anything to do with this. As the alarm has disappeared from the SCOM console, we have also checked the registry values. Now, instead of "3559 3559 3559"
    it says "3559 3559 3585". We have had the 3559 value since 18th July, and out of a sudden something must have been triggered, causing the value to increase. What was triggered and how, no idea... Not sure either what it means that only one of the
    Three numbers have been updated with a new value. When talking about the DW jobs, using the SMlets we can see every day that, MPSync, DWMaintenance and the ETL jobs are working well. What we have had though for a longer time is that the cube processing
    tends to have issues once a week, where processing won't finish and the cubes get hanging in a running state. We can fix that manually every time and often we don't even have to touch DWMaintenance or the ETL jobs, we don't need to go beyond manually
    working with the cube processing jobs themselves. So it might not have an impact on the ETL jobs themselves. Occasionally we do find ourselves in a situation where we we need to play around in the SQL database and manually set the required value (can't
    recall if it's 3, 6 or 7) cause we get an error in the DWMaintenance batch, but even though that's an occasional issue it's not constant and also something we can solve, and furthermore it's another known issue outside of the high watermark issue. So
    we are a bit uncertain but can at least see that something works sometimes that sometimes increases the high watermark value :). In our case.

  • Exception while accessing web service secure through web services Manager

    Hi All,
    I deployed sime Hello World web service on JWSDP1.6 and secure it through web service manager(gateway) using Certificate based security.But when I try to access this web service using JWSDP client,I got the following Error while monitoring the soap messages through TCP-Monitor:
    /////////////////////////////////Request///////////////////////////////////////////////////////////////
    POST /gateway/services/SID0003009 HTTP/1.1
    Content-Type: text/xml; charset=utf-8
    Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
    Content-Length: 5631
    SOAPAction: ""
    User-Agent: Java/1.5.0_05
    Host: ivy.cs.ucl.ac.uk:8082
    Connection: keep-alive
    <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://hello.org/wsdl" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Header>
    <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" env:mustUnderstand="1"><xenc:EncryptedKey xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"><xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/><ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
    <wsse:SecurityTokenReference>
    <wsse:KeyIdentifier EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier">eN9famBBWzHNUIwWRhMPktcM+VQ=</wsse:KeyIdentifier>
    </wsse:SecurityTokenReference>
    </ds:KeyInfo><xenc:CipherData><xenc:CipherValue>MHjtgA4wOtvI1B+SuRVEmD07yE+jl6axd4XbJ0nvQ3EzSuVVoST9vHzURh+B47yj41187s8T+yjt
    Bmpk9OB278Jghonkacv6r+q+LVlxRrQDudNGir7plzFeM6bUadMxf+FLgn5O0a44vU/tvy6V9+zi
    yqFdhTvS21No/aW62No=</xenc:CipherValue></xenc:CipherData><xenc:ReferenceList><xenc:DataReference URI="#XWSSGID-1155126003241-1198323932"/></xenc:ReferenceList></xenc:EncryptedKey><wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="XWSSGID-11551260018331598979688">MIIC3TCCAkagAwIBAgIBATANBgkqhkiG9w0BAQQFADBJMQswCQYDVQQGEwJVUzEMMAoGA1UECBMD
    U0NBMQwwCgYDVQQKEwNTVU4xHjAcBgNVBAMTFWNlcnRpZmljYXRlLWF1dGhvcml0eTAeFw0wNjAz
    MTkxMzQ5MDJaFw0xNjAzMTYxMzQ5MDJaMEcxCzAJBgNVBAYTAlVTMQwwCgYDVQQIEwNTQ0ExDDAK
    BgNVBAoTA1NVTjEcMBoGA1UEAxMTeHdzLXNlY3VyaXR5LWNsaWVudDCBnzANBgkqhkiG9w0BAQEF
    AAOBjQAwgYkCgYEAzNDPKUz1MhUH1LsrLqXKxciOKSWeTrdoe/SVwe/4uy5eobAWSsSTposaOYFy
    uxf3cGCCIs7u0jMAXLQ9jzobDbt9XQ4tXPoBzKKzS+yU6hDk2TcOCkioeT9A9db5LF8yevhwXKB4
    AJ1Eh//Dp/djoonXCCxsxupQZp3ueRJrR98CAwEAAaOB1jCB0zAJBgNVHRMEAjAAMCwGCWCGSAGG
    +EIBDQQfFh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUECH05VC3/WGW
    H4AGD6tnH0h+kFUweQYDVR0jBHIwcIAUdry1wGRZ2fyJSKisVSxpMEmIiaahTaRLMEkxCzAJBgNV
    BAYTAlVTMQwwCgYDVQQIEwNTQ0ExDDAKBgNVBAoTA1NVTjEeMBwGA1UEAxMVY2VydGlmaWNhdGUt
    YXV0aG9yaXR5ggkA4HaEvd6hq8YwDQYJKoZIhvcNAQEEBQADgYEA0RhOk67pCrO6MgZZGqrmAMW6
    76fZowBxTKlFq88nrf8v1MUxV8H9wgbTDrwR0HtxY3TGpDFw2tNAww2pyDX/pQ2Wt46ichluGxjf
    aEV53loKTOM7syAmlicWqViGzBfgzriIl918TzFaX9BD/Y55bKZQk057maBCSkUuFfF453s=</wsse:BinarySecurityToken><ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"><ds:SignedInfo><ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"><InclusiveNamespaces xmlns="http://www.w3.org/2001/10/xml-exc-c14n#" PrefixList="wsse enc env ns0 xsd xsi"/></ds:CanonicalizationMethod><ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/><ds:Reference URI="#XWSSGID-1155126002593447652186"><ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><ds:DigestValue>UJ1kuwI+WuF/RkrQpZrj1GvraLI=</ds:DigestValue></ds:Reference><ds:Reference URI="#XWSSGID-1155126002602761294100"><ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><ds:DigestValue>sKG/z5OIGgqJ2nw7JtpXyJzr8pY=</ds:DigestValue></ds:Reference></ds:SignedInfo><ds:SignatureValue>SBc65VTG1xpEkRUTz70H0fVGIgoBJ0QnNad0k07RMSfw4vG1WHJdt19R05pO2AvU5aoYuBSaguJe
    ZGEjmWzw8mnSWKBi+zeDMeJiwgqwW6HHHX9P7JDslxuTIqoJIVUbSjUTSVz6ww8siIK65quXdkMT
    ZzLfp7Cd0gBuA3EEZpg=</ds:SignatureValue><ds:KeyInfo><wsse:SecurityTokenReference xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="XWSSGID-11551260025411896275738">
    <wsse:Reference URI="#XWSSGID-11551260018331598979688" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/>
    </wsse:SecurityTokenReference></ds:KeyInfo></ds:Signature><wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="XWSSGID-1155126002602761294100"><wsu:Created>2006-08-09T12:20:02Z</wsu:Created><wsu:Expires>2006-08-09T12:20:07Z</wsu:Expires></wsu:Timestamp></wsse:Security></env:Header><env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="XWSSGID-1155126002593447652186"><xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Id="XWSSGID-1155126003241-1198323932" Type="http://www.w3.org/2001/04/xmlenc#Content"><xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/><xenc:CipherData><xenc:CipherValue>XNqEzHNp47ILtOagAUNCXYkxOCWv4CjHqmZ7j6VKN/NO96ce4BsNSL6lKzqa9dPxHB1sTVGZQ8KA
    COQ6DGwyWCP8ip+CU2hor3uUAml7nzHTx1LUw3Db+0p31VAT3EqKJA3aFy38GQrBTr9ojMOUA6tm
    Cj71yucN3UCKRUl3RpE8qU68y7AwNxPsyAZeSa2AVm2cmWvSDZlxgMsx+JCEZaf3+D0o1zMp0Fxb
    MSISPt/JrEolt1H5UM1AoFGU4QkckWrQNLPyEF9oxEgZ8oCE5U8v/YJwZIAHFrx67XfaLwQLjzXw
    VPigsH9gLkfbP2BU8Vp31GsPwBZtUeNz9S35+CZPD7EiqoAB1QuAxZkJV7n00VChYH+scT64tNja
    c81bcD8tf4sAr7toCMNDAU6+74+Qy0EyPqgwLtotDxErn4kF8e72cONMMQBQ91tQs+iI+D6C1I6+
    f9UiSfgtm/MTuKQK1CRqarEtI9N6lpqVH8k7ulUwH/jFstihxmhMJ3aZY+qQgSwSs3pwSSim+e18
    eR7dOEq4vG8ivKuGvTDO4sSV2RP/nL/3eXr0y7eM0kMFKwTUA4JqL4Y/l8Bo/rie/ZXkkbF6hwEu
    dX1QmB0gf5k=</xenc:CipherValue></xenc:CipherData></xenc:EncryptedData></env:Body></env:Envelope>
    ////////////////////////////////Response///////////////////////////////////////////////////////////////
    HTTP/1.1 100 Continue
    Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.0)
    Date: Wed, 09 Aug 2006 12:28:47 GMT
    HTTP/1.1 500 Internal Server Error
    Date: Wed, 09 Aug 2006 12:28:47 GMT
    Server: Oracle Application Server Containers for J2EE 10g (10.1.2.0.0)
    Connection: Keep-Alive
    Keep-Alive: timeout=15, max=100
    Content-Type: text/xml
    Transfer-Encoding: chunked
    157
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode xmlns:p="http://schemas.oblix.com/ws/2003/08/Faults">c</faultcode><faultstring>Step execution failed with an exception</faultstring><detail></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
    0
    So basically, what I am doing here as follows:
    HelloClient(using JWSPD1.6)->gateway(web service manager for securing the web service using message level security through certificate )->helloservice(deployed using JWSDP1.6)
    I would appreciate if someone could tell me the cause of this errror.Thanks.
    Kashif

    time to look into the gateway logs as stated by the fault ..
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode xmlns:p="http://schemas.oblix.com/ws/2003/08/Faults">c</faultcode><faultstring>Step execution failed with an exception</faultstring><detail></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
    looks like the cipher step might have failed

  • Service Manager 2012 Agentless Monitoring and SQL Servers More secure distribution

    Having both SCSM 2012 and 2012 in my network, I want to monitor the all using a single account which is securely distributed. The problem is agentless monitored servers does not appear in the "more secure" list.
    My Scenario:
    I have scsm 2012 installed with the following condition:
    SCSM Main DB -> Monitored with Agent (not a management server)
    SCSM Data Warehouse -> Agentless monitored
    SCSM Workflow and other Management Servers -> Agentless Monitored
    Some Test SCSM 2012 Servers with SQL on the same machine -> Agentless Monitored
    Some Test and Operational SCSM 2012 Servers -> Agentless Monitored
    I want to use a single account to monitor them all, I have set the "Service Manager Database Account" profile (yet to understand why Service Manager Database
    Account is actually a Profile!) and in the underlying account set the distribution to "more secure" . As stated above, I have many servers with the SQL running on the management serves and I cannot
    configure them in the SQL account.
    Is my scenario wrong?
    Thanks
    YSobhdel

    It seems the SQL MP is monitoring the database on agentless managed computers without my permission!
    All my agentless managed computers are using the default action account to monitor the SQL!
    Any explanation why is that so?
    Thanks
    YSobhdel

  • The SQL Agent service is not running. This operation requires the SQL Agent service. (rsSchedulerNotResponding)

    Hi,
    I have started sql agent service on the SQL server but I still cannot subscribe. I have followed few instructions but no joy.
    Can you please help?
    Thanks,

    Hi Mo,
    According to your description, you want to subscribe a report with E-mail delivery extension, right?
    In Reporting Services, since the E-mail delivery extension is not configured by default, if we want to subscribe reports with E-mail delivery extension, we should specify E-mail settings in Reporting Services Configuration Manager. Besides, we should specify
    advanced settings in rsReportServer.config file. In your scenario, please make sure you have configured the E-mail delivery extension correctly. For more information, please refer to this article:
    Configure a Report Server for E-Mail Delivery (SSRS Configuration Manager).
    If you have any question, please feel free to ask.
    Best regards,
    Qiuyun Yu
    Qiuyun Yu
    TechNet Community Support

  • Automatically start SQL Agent service after SQL Server service fails and starts.

    Hi! 
    I have SQL Server 2008 R2 with two main services - SQL Server and SQL Agent.
    I'll try to describe my situation. It happens very occasionally, but sometimes SQL Server service terminates unexpectedly. It's my log:
    09/13/2013 10:46:21,Service Control Manager,Error,The SQL Server (MSSQLSERVER) service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 120000 milliseconds: Restart the service.
    09/13/2013 10:46:21,,Error,[359] The local host server is not running,,,,
    09/13/2013 10:46:22,MSSQLSERVER,Error,The MSSQLSERVER service terminated unexpectedly.,Server,1073760843,,
    09/13/2013 10:46:22,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #1)...,,,,
    09/13/2013 10:46:27,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #2)...,,,,
    09/13/2013 10:46:32,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #3)...,,,,
    09/13/2013 10:46:32,,Error,[140] AutoRestart: The MSSQLSERVER service could not be restarted after 3 attempts,,,,
    09/13/2013 10:46:32,,Warning,[360] SQLServerAgent initiating shutdown following MSSQLSERVER shutdown,,,,
    As you can see, SQL Server service  terminates unexpectedly. Then SQL Agent service tries to start SQL Server service. After unsuccessfully attempts to start SQL Server service, SQL Agent service stops itself. I have the option setting in SQL Server
    service to start itself after unexpectedly stop within 2 minutes and it is works well. But I have to start my SQL Agent service after this manually. Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly and in this case I just want
    to make the settings to start both of my services SQL Server and SQL Agent automatically after this.  How can I set up this? How can I make my SQL Agent service starts after SQL Server service?

    Hello,
    SQL server agent service depends on SQL server service so unless SQL server service comes online agent will not come online so agent is depended on SQL server not the other wise.
    Now is your server 2008 R2 patched to latest service pack (SP2).If not please upgrade it to latest SP.Some fixes are there in Sp which will subside this issue.Can you paste output of
    select @@version
    >>Then SQL Agent service tries to start SQL Server service.No this is not the case
    >>Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly
    Did you checked sql server errorlog and windows event log completely.Please do so and paste if you find some more info
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Starting SQL Server Agent service

    I have a brand new 64-bit laptop and have installed both SQL Server 2014 and SQL Server 2012sp1, but neither instance is able to start its SQL Sever Agent Service.  The error is 1053:  'The service did not respond to the start or control request
    in a timely fashion'. Googling that message does not seem to give helpful step by step solutions. Please help.
    Dave Juergens
    [email protected]
    Dave Juergens

    could you tell us your sql server edition - if it is EXPRESS edition - it does not comes with SQL Server agent. you will sql server agent service in configuration manager but it does not start because the feature is not available.
    you can find the sql edition using. select @@version
    and post the output here
    if it is not Express edition, could you please check the error log or event viewer and if there is more detailed information on the error.
    Hope it Helps!!

Maybe you are looking for