SCOM Agent on Linux Server Fail

Dears,
I am new to this topic of deploying SCOM Agent to Linux Server...
In my deployment, I want to push SCOM Agent to Linux Ubuntu, I have confirmed below:
Ubuntu distribution is supported
I am using root account with no SSH certificate
On Linux Server firewall for IPv4 and IPv6 is off
I can telnet to linux port 22
root account have privilege to access 22
WHen I try push installation, I am able to:
Discover the servers
Push the agent and deploy it (I can see the service scom agent service started and I can telnet to Linux Server port 1270)
when scom push agent wizard try to sign the certificate it fail with below error:
Task invocation failed with error code -2130771918. Error message was: The SCXCertWriteAction module encountered a DoProcess exception. The workflow "Microsoft.Unix.Agent.GetCert.Task"
has been unloaded.
Module: SCXCertWriteAction
Location: DoProcess
Exception type: ScxCertLibExceptionTask invocation failed with error code -2130771918. Error message was: The SCXCertWriteAction module encountered a DoProcess exception. The workflow "Microsoft.Unix.Agent.GetCert.Task"
has been unloaded.
Module: SCXCertWriteAction
Location: DoProcess
Exception type: ScxCertLibException
Exception message: Unable to open root store; {Access is denied.}
Additional data: Sudo path: /etc/opt/microsoft/scx/conf/sudodir/
-----BEGIN CERTIFICATE-----
MIIDETCCAfkCAQEwDQYJKoZIhvcNAQEFBQAwQjEfMB0GA1UEAxMWZnRwLnRlbGVj
b20ubW9pLmdvdi5xYTEfMB0GA1UEAxMWZnRwLnRlbGVjb20ubW9pLmdvdi5xYTAe
Fw0xMzA0MTcwNjEyMThaFw0zNDA0MTIwNjEyMThaMEIxHzAdBgNVBAMTFmZ0cC50
ZWxlY29tLm1vaS5nb3YucWExHzAdBgNVBAMTFmZ0cC50ZWxlY29tLm1vaS5nb3Yu
cWEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC+d2oX2lK20nSDGmcD
whe1sy2WJ9mXGTtZm7VLidh12vN1yImkzi6Ds/mJPA2cKfBlWc8PJX/Uje7m647F
SBaqDfORsWGhW3XQUkj44lWKsqiq2AFe2ZJIXw0peWIIZzvGzo0vfNc66ECFv3G8
RFaF1M9KppJE0SExR9DGAkgrOym9xsYce6mBqdmli4Imr7eBWsr8bkQob1OCem4E
N70tPW4al4N0un2G6p5CVDNOiNCKvE11QdBugQ8uFCpksoB9IFPggxsF3qg+BpPx
Q+N0p3/sjpiGqwRHXUNIPBzCok3C2mi9hNgsTlBU6BPJEaTgDIvJJvcm6Isvn+zo
vdFDAgMBAAGjFzAVMBMGA1UdJQQMMAoGCCsGAQUFBwMBMA0GCSqGSIb3DQEBBQUA
A4IBAQAqCjyyqVjdcxU3AWKNCzs7g7Gc6nQlNIaurHsV6Wks8Qo24PED6eLdhCDL
SSOxp/pi3jxpq1LWcYyjy0dCDlUceQVaGVgu/wwqqkvvZcukYbG3DSp/m+kAwyDu
0zr4S8Iq1sjmHm7CqCrinQcdXN5OrW8EYd3yzBalZ33WNPbBQJADK0ZENDkfSatZ
vjMoyFgrFmMM+sG52ZeILohfwU/DJow6SYe45VhHUB6oimFgPRpTy+Ir4FM+Xo0W
JhJPtYD80nYX7fKtLFbLzF21yF96o5gCvoLoqyL0rJOvakF9qVaCIy9s/jrt1Axh
W8lSYN+wCCDAnTpmHMPS37KL2zHV
-----END CERTIFICATE-----
Management group: OMMS
Workflow name: Microsoft.Unix.Agent.GetCert.Task
Object name: Unix Linux Monitoring Resource Pool
Object ID: {76C1B3F5-866D-0AFC-3E98-4EBC36647765}
I have tried to:
I tried to add FQDN Name of Linux Server with IP address to host file (but again it fail)
I have tried sudo account , it also fail with same error
Please help on this.

Jean,
It looks like this is most likely your issues. Please give it a try and see if it resolves the problem.
Possible Causes
The Management Servers default action account does not have the necessary privileges (administrator) to open the root certificate store.
Resolutions
Set the Action Account for the Manage Server(s) as a local administrator account
Configure a local administrator account in the Run As Profile: Certificate Signing Profile
If the Certificate Signing Profile is configured, the action account associated in that profile will be used. If not, it will fall back to the default Action Account
Regards,
-Steve

Similar Messages

Move SCOM agent between gateway server and management server ?

Dear all,
IN SCOM 2012 R2 is it possible to move SCOM agent between gateway server and management server ? I mean if one agent is reporting to Gateway server , in case if i want to shutdown that Gateway server , can i move to another Management server and
Vice versa ?
Thanks,
Sengo

Hi,
http://blogs.catapultsystems.com/cfuller/archive/2012/06/05/how-does-the-failover-process-work-in-opsmgr-2012-scom-sysctr.aspx
and links at the bottom of
the article

Problem upgrading from SCOM 2012 SP1 to R2 (near impossible to uninstall SCOM agent from Management Server)

I'm trying to upgrade our SCOM 2012 SP1 environment to R2, but I have a heck of a problem getting there.
We currently have an test installation with SCOM 2012 SP1 with Management Server and Console on a single 2012 Standard server. The database are located on a remote server. The R2 setup stopped mid way through the setup, because the SCOM 2012 SP1 agent is
installed. And I could NOT remove it my any normal means. I've tried "misexec.exe /x productcode", the setup, powershell uninstall and so on. Nothing works, because the management server installation is blocking the uninstall. The uninstall says
I have to remove the management installation first. And that's not gonna happen.
I had to follow this guide to finally getting through the setup: http://www.opsman.co.za/forcibly-removing-a-scom-agent-that-cannot-be-uninstalled-by-normal-means/
In addition to searching for the agent msi install key in registry, and deleting everything. After I did this, the setup is working, and the SCOM management server, console and DB are up to date. However, the Microsoft Monitoring Agent are STILL there in
Control Panel. And this can NOT be the most healthy way of getting through the setup.
I'm about to upgrade to R2 in our production environment with 3 management servers, and I would hate to go through this sketchy process there as well. Just for the record, I have no idea why the agents are installed on our management servers.
Any of you have tips as to how I can get rid of the agents more gracefully?

Hi
Thanks for the replay guys!
None of those links touch my problem I'm afraid. I have followed the Upgrade guides you pointed to, step by step. But the setup does not Complete. There's problems during the actual software Upgrade of the management servers (3'rd step in the Upgrade page).
I've dived into the Application logs and installation logs, and as far as I can tell, it stops because it has trouble upgrading while the server has the 2012 SP1 Agent installed. I do not remember the actual error text right now, but I can get it in a few
days.
Anyhow, the setup DID move on once I removed most of the registry information of the agent installation. So. that leaves me to the conclusion that the agent IS in fact stopping the setup. Either the agent are malfunctioning, or the setup do not expect the
agent to be present on the management servers. I suspect the latter to be the the most plausible. At least until Yan Li told me this was normal.
So, I'm not sure what to think. I'm pretty much forced to remove this agents, as this is the only thing allowing me to continue the setup. At least untill I'm told otherwise. But I hate to do it this way. It's so dirty. The registry is pretty much cleaned,
but there's still Application files present, and the agent is still in the Control panel and can be started. It's not something I would like to do in our prodution environment.

SCOM agent communicating with server?

Dear all,
After SCOM agent installation how that agent will start communicating with server? Is there any flowchart (like first how the communication will start , then when the MP will get download ..etc..)
Thnaks,
Sengottuvel M

Hi,
The System Center Management Health service on each monitored agent collects performance data, executes tasks, and so on. Even when the service is unable to communicate with the management server it reports to, the service continues to run and queues the
collected data and events on the disk of the monitored computer. When the connection is restored, the System Center Management Health service sends collected data and events to the management server.
Regards, Yan Li

Siebel 8.1.1 on linux - server fails to connect to gateway after stop/start

I have a very stubborn symptom in my environment, with Siebel SIA 8.1.1 [21111] on OEL 5 2.6.18.
Everything will be working fine after initial install, then I stop the Siebel Server and Gateway, start the services again and the Siebel Server fails to start. The NameServer.log complains that the server cannot connect to the gateway configuration store, and that the login password is incorrect. However it was just working minutes prior. Once it fails like that I can fiddle with it all day and still the Siebel Server will not start.
I have tried a number of suggestions found, verifying the odbcsql command works, verifying the memory files *.shm is not still in the admin directory, making sure all approp. processes are closed after stopping the siebel server, recreating the gateway and siebel server services, rebooting the vm.
The symptom and log messages never change. Once in a while for no apparent reason the siebel server will start again but sure enough if I stop it, it won't come back up.
I have a couple of environments that I have worked with and tried things but both experience the same symptom.

Good one. For reference its detailed in
[Siebel CRM 8.1.1 DataDirect License file IVSE.LIC is missing from Gateway Name Server (Doc ID 751784.1)|https://metalink3.oracle.com/od/faces/secure/km/DocumentDisplay.jspx?id=751784.1&h=Y]

Schedulling an agent in obiee 11g on Linux server

Hi,
I am trying to schedule an agent on Linux server. I know its possible on windows server, but did anyone try it on Linux, if so please provide instructions on how to do this? Thanks,

Hi,
How to schedule an agent? just set the when it must run and the frequency in the agent itself.
OBIEE has his own scheduler process, so scheduling an agent on Windows or Linux is the same work, everything happen inside OBIEE.
Of course I assume your OBIEE is installed correctly and all the components are started...

SCOM agent install on Unix/Linux

Hi, trying to install agent on RHEL. Here is the case:
- Hosts file added with FQDN name on Linux server
- IPtables off for IPv4 & IPv6(I've a doubt here. Even turned off, do they need exception entry in iptables for both v4 & v6)
- Replying for ping from both SCOM management servers by hostname and IP address.
- nslookup pointing to same IP & server
- DNS resolution ok (both forward & reverse)
- WinRM qc showing WinRM already set to listen.
- Getting discovered while agent install, failing at certificate signing validation - the last step.
- Sudoer file modified perfectly
- Port 1270 is open over network (confirmed by n/w team)
Still receive below error :(
- Agent verification failed.
Error detail: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination,
most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". When verifying winrm, it is already configured to receive requests.
-Thanks, Satya

Certificate does not include the FQDN so it fails. You can do a few things here to fix it.
Run the following on the Linux agent and try discovery again. This will overwrite the old certificate and create a new one with the FQDN.
/opt/microsoft/scx/bin/tools/scxsslconfig -h <Linux hostname> -d <domain name> -f -v
Update the /etc/hosts file on the Linux computer and add the FQDN:
x.x.x.x myLinux.mydomain.com myLinux
or update the /etc/resolv.conf:
domain mydomain.com
If you do either of the last 2 you will want to delete everything under
/etc/opt/microsoft/scx/ssl and then re-run discovery as it will still try to use the old certificate if it exists.
-Steve

SCOM agent install fails Error 80070035 - the network path was not found

I have deployed SCOM 2012 agents to most servers (2008, 2008 R2, 2012, 2012R2) in our estate but some either fail to install or are not monitored. I assume the two problems are related, but for now I am concentrating on the servers that fail completely.
Installation is from the Discovery Wizard and I have about 20 servers that fail of various server versions.
So looking at one specific server that is failing to install the agent - a 2008 standard service pack 2
The firewall in on and file and printer sharing is enabled for domain, remote administration is enabled for domain
I added a specific rule to allow TCP 5723 and 5724
DCOM is enabled
I can Ping the target server from the SCOM server by both name and FQDN - both return the same IP and our DNS server has only one entry for this server
I can browse to the admin share \\server\C$ from the SCOM Server, using the same account that I specify for the agent install that is a domain admin with rights on this server (and on the other servers the agent
did install to) and the server has plenty of disk space available
I am not sure what else to look at so would welcome any ideas
Thanks

Hi Petro,
I have a Agent installation failure cheat sheet, For your error 80070035 it is said to perform a manual installation.
So i would like to understand which version of SCOM is this ? 2007 R2 or 2012 or 2012 r2 ?
Also check if your agents have the WMI service started and enabled ?
Also if yours is a SCOM 2007 R2 do you have a RMS & MS in your management group ? If yes then Pushing the agent installation from MS may cause such issue. So would suggest you push the installation from RMS.
Also check if your Network connectivity meets the minimum requirement as recommended by SCOM. Below is applicable for Both SCOM 2007 R2 & SCOM 2012 & 2012 R2.
Component A
Component B
Minimum Requirement
Root management server or management server
Agent
64 Kbps
Root management server or management server
Agentless
1024 Kbps
Root management server or management server
Database
256 Kbps
Also check if you have any Anti virus / Firewall which is blocking the install / communication. If yes disabe or add the "Monitoringhost.exe to the safe list or what your feature is.
Check if you have another IP assigned to the NIC card and remove it tempraurly andchecl.
Also post the event logs of the Agents which are in not monitored state for analysis.
SCOM Agent installation failure error codes
Error
Error Code(s)
Remediation Steps
The MOM Server could not execute WMI Query "Select * from Win32_Environment where
NAME='PROCESSOR_ARCHITECTURE'" on computer server.domain.com
Operation: Agent Install
Install account: domain\account
Error Code: 80004005
Error Description: Unspecified error
80004005
1. Check the PATH environment variable. If the PATH statement is very long, due to lots of installed third party software - this can
fail. Reduce the path by converting any long filename destinations to 8.3, and remove any path statements that are not necessary.
2. The cause
could be corrupted Performance Counters on the target Agent.
To rebuild all Performance counters including extensible and third party counters in Windows Server 2003, type the following commands at a command
prompt. Press ENTER after each command.
cd
\windows\system32
lodctr /R
Note /R is uppercase.
Windows Server 2003 rebuilds all the counters because it reads all the .ini files in the C:\Windows\inf\009 folder for the English operating system.
How to manually rebuild Performance Counter Library values
http://support.microsoft.com/kb/300956
3. Manual agent install.
The MOM Server could not execute WMI Query "Select * from Win32_OperatingSystem" on
computer “servername.domain.com”
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.
8004100A
800706BA
1. Ensure agent push account has local admin rights
2. Firewall is blocking NetBIOS access
3. Inspect WMI health and rebuild repository if necessary
4. Firewall is blocking ICMP (Live OneCare)
5. DNS incorrect
The MOM Server failed to open service control manager on computer "servername.domain.com". Access is Denied
Operation: Agent Install
Install account: DomainName\User Account
Error Code: 80070005
Error Description: Access is denied.
80070005
80041002
1. Verify SCOM agent push account is in Local Administrators group on target computer.
2. On Domain controllers will have to work with AD team to install agent manually if agent push account is not a domain admin.
Disable McAfee antivirus during push
The MOM Server failed to open service control manager on computer "servername.domain.com".
Therefore, the MOM Server cannot complete configuration of agent on the computer.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.
800706BA
1. Firewall blocking NetBIOS ports
2. DNS resolution issue. Make sure the agent can ping the MS by NetBIOS and FQDN. Make sure the MS can ping the agent by NetBIOS
and FQDN
3. Firewall blocking ICMP
4. RPC services stopped.
The MOM Server failed to acquire lock to remote computer servername.domain.com. This means there is already an agent management operation proceeding
on this computer, please retry the Push Agent operation after some time.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 80072971
Error description: Unknown error 0x80072971
80072971
This problem occurs if the LockFileTime.txt file is located in the following folder on the remote computer:
%windir%\422C3AB1-32E0-4411-BF66-A84FEEFCC8E2
When you install or remove a management agent, the Operations Manager 2007 management server copies temporary files to the remote computer. One
of these files is named LockFileTime.txt. This lock file is intended to prevent another management server from performing a management agent installation at the same time as the current installation. If the management agent installation is unsuccessful and
if the management server loses connectivity with the remote computer, the temporary files may not be removed. Therefore, the LockFileTime.txt may remain in the folder on the remote computer. When the management server next tries to perform an agent installation,
the management server detects the lock file. Therefore, the management agent installation is unsuccessful.
http://support.microsoft.com/kb/934760/en-us
The MOM Server detected that the following services on computer "(null);NetLogon" are not running. These services are required for push
agent installation. To complete this operation, either start the required services on the computer or install the MOM agent manually by using MOMAgent.msi located on the product CD.
Operation: Agent Install
Remote Computer Name: servername.domain.com Install account: DOMAIN\account
Error Code: C000296E
Error Description: Unknown error 0xC000296E
C000296E
1. Netlogon service is not running. It must be set to auto/started
The MOM Server detected that the following services on computer
"winmgmt;(null)" are not running
C000296E
1. WMI services not running or WMI corrupt
The MOM Server detected that the Windows Installer service (MSIServer) is disabled on computer "servername.domain.com". This service is
required for push agent installation. To complete this operation on the computer, either set the MSIServer startup type to "Manual" or "Automatic", or install the MOM agent manually by using MOMAgent.msi located on the product CD.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: C0002976
Error Description: Unknown error 0xC0002976
C0002976
1. Windows Installer service is not running or set to disabled – set this to manual or auto and start it.
The Agent Management Operation Agent Install failed for remote computer servername.domain.com.
Install account: DOMAIN\account
Error Code: 80070643
Error Description: Fatal error during installation.
Microsoft Installer Error Description:
For more information, see Windows Installer log file "C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\servernameAgentInstall.LOG
C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\servernameMOMAgentMgmt.log" on the Management Server.
80070643
1. Enable the automatic Updates service…. Install the agent – then disable the auto-updates service if desired.
Call was canceled by the message filter
80010002
Install latest SP and retry. One server that failed did not have Service pack installed
The MOM Server could not find directory \\I.P.\C$\WINDOWS\. Agent will not be installed on computer "name". Please verify the required
share exists.
80070006
1. Manual agent install
Possible locking on registry?
http://www.sysadmintales.com/category/operations-manager/
Try manual install.
Verified share does not exist.
The network path was not found.
80070035
1. Manual agent install
The Agent Management Operation Agent Install failed for remote computer "name". There is not enough space on the disk.
80070070
1. Free space on install disk
The MOM Server failed to perform specified operation on computer "name". The semaphore timeout period has expired.
80070079
NSlookup failed on server. Possible DNS resolution issue.
Try adding dnsname to dnssuffix search list.
The MOM Server could not start the MOMAgentInstaller service on computer "name" in the time.
8007041D
80070102
NSlookup failed on server. Possible DNS resolution issue.
Verify domain is in suffix search list on management servers.
The Agent Management Operation Agent Install failed for remote computer "name"
80070643
1. Ensure automatic updates service is started
2. Rebuild WMI repository
3. DNS resolution issue
The Agent Management Operation Agent Install failed for remote computer "name". Another installation is already in progress.
80070652
Verify not in pending management. If yes, remove and then attempt installation again.
The MOM Server detected that computer "name" has an unsupported operating system or service pack version
80072977
Install latest SP and verify you are installing to Windows system.
Not discovered
Agent machine is not a member of domain
Ping fails
1. Server is down
2. Server is blocked by firewall
3. DNS resolving to wrong IP.
Fail to resolve machine
1. DNS issue
The MOM Server failed to perform specified operation on computer "name". Not enough server storage…
8007046A
1. This is typically a memory error caused by the remote OS that the agent is being installed on.
There are currently no logon servers available to service the logon request.
8007051F
1. Possible DNS issue
This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version
of the Windows Installer service.
8007064D
1. Install Windows Installer 3.1
The network address is invalid
800706AB
Possible DNS name resolution issue.
Tried nslookup on server name and did not get response.
Verify domain is in suffix search list on management servers.
The MOM Server failed to perform specified operation on computer servername.domain.com
80070040
1. Ensure agent push account has local admin rights
The MOM Server detected that the actual NetBIOS name SERVERNAME is not same as the given NetBIOS name provide for remote computer SERVERNAME.domain.com.
80072979
1. Correct DNS/WINS issue.
2. Try pushing to NetBIOS name
Gautam.75801

SCOM 2012 R2 # Windows Server agents remain in pending management

Hi,
First I installed one SCOM 2012 R2 Ops Manager. On same SCOM ops manager I added 3 windows server agents to monitor as below..
one 2008 R2 AD server
one Lync 2013 FE server
one Exchange server 2013
Now due to some technical issues later I had to completely remove/uninstall SCOM 2012 R2 setup. But I forgot to uninstall/remove 3 agents first before uninstalling SCOM 2012 R2 ops manager :( However I did manual uninstall of Microsoft monitoring agent setup
from all 3 monitored agent servers.
Now I setup new SCOM 2012 R2 ops manager once again. FQDN of new SCOM has been changed now, though server is in same domain as old one. Problem I am facing here is " I cannot able to add those 3 agents back into new SCOM ops manager. When I install
agent back onto those 3 servers (by agent discovery or manual setup) , servers remains in pending management. I used power shell command to approve all 3 but even after approval servers are not being monitored. Health status always showing not monitored. A
blank green circle.
I think I didn't properly removed old agent setup, & somehow those 3 agents still bound to old SCOM ops manager.
Could you please help me how I can remove remaining components of old agent setup from windows agent servers and monitor them with new SCOM?
BR,
Ajit

Ensure that the following registry keys are deleted:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService
Reboot the agent machine (if possible)
Delete the agent from Agent Managed in the OpsMgr console.
Then try to discovery and push agent from console if failed. Try to install it manual and then from pending management click approved.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

SCOM 2012 R2 Agent Issue: Error 25211.Failed to install performance counters.. Error Code: -2147024809

Hi All,
I'm trying to deploy SCOM 2012 R2 agent onto a domain controller and I get the following error "Product: Microsoft Monitoring Agent -- Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.)."
I've installed the agent successfully onto 4 other domain controllers with out any issues.</p><p>The domain controllers are all VM's running on VMWare and are Windows Server 2012 R2.
I've rebuilt the Perfmon Counters based on this article: https://support.microsoft.com/en-us/kb/2554336?a=wsignin1.0
I've also enabled verbose logging on the msi installation:
InstallHSPerfCounters: Custom Action Data. C:\Program Files\Microsoft Monitoring Agent\Agent\
InstallHSPerfCounters: Installing agent perf counters.
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft Monitoring Agent\Agent\HealthServiceCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft Monitoring Agent\Agent\MOMConnectorCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
Any help on this would be great.

Hi Stefan,
I've successfully installed the agent. The server needed a reboot after fixing the corrupt perfmon counters.
I know have a issue with the agent on the domain controller. It kkeeps on greying out and have used hslockdown to allow the local system access by using the following command.
HSLockdown.exe "ManagementGroupName" /A "NT AUTHORITY\Authenticated Users"
Further digging into the issue I see in the SCOM Management Server the following error "The entity servername is not heartbeating"
Written a SQL query to gather more information. SQL query I used is:
SELECT
ME.FullName,
HSO.StartDateTime AS OutageStartDateTime,
DATEDIFF (DD, hso.StartDateTime, GETDATE()) AS OutageDays,
HSO.ReasonCode,
DS.Name AS ReasonString
FROM vManagedEntity AS ME
INNER JOIN vHealthServiceOutage AS HSO ON HSO.ManagedEntityRowId = ME.ManagedEntityRowId
INNER JOIN vStringResource AS SR ON HSO.ReasonCode =
REPLACE(LEFT(SR.StringResourceSystemName, LEN(SR.StringResourceSystemName)
– CHARINDEX(‘.’, REVERSE(SR.StringResourceSystemName))), ‘System.Availability.StateData.Reasons.’, ”)
INNER JOIN vDisplayString AS DS ON DS.ElementGuid = SR.StringResourceGuid
WHERE (SR.StringResourceSystemName LIKE ‘System.Availability.StateData.Reasons.[0-9]%’)
AND DS.LanguageCode = ‘ENU’
AND ME.FullName like ‘%SERVER NAME%’ –Change name here or leave %% for ALL SERVERS
ORDER BY OutageStartDateTime
This gives me the following reason behind the failure : "The heartbeat from System Center Management Service is missing."
Have I missed anything? The agent is running fine, however SCOM is reporting that the heartbeat is missing.
Any help on this would be great.

Execution timed out error when running opcagt command on linux server with agent 11.12.009 installed

Hi,
Can anyone help me in the below issue.
we have a Linux server with agent version 11.12.009 installed on it. when I try running opcragt command on it through are management server it gives the output that all agent components are running.
but when I check the agent status or version through opcagt command on it it gives below error:
ERROR: (depl-86) Unable to execute command 'opcagt' on node
(depl-176) Message returned from host
(xpl-117) Timeout occurred while waiting for data.
Below are the error lines that I got from system.txt file of the server:
0: ERR: Fri Dec 19 09:09:38 2014: ovconfd (3708/140429034952480): (conf-180) Could not create messenger for configuration server 'ovconfd' and register its methods with the messenger object.
1: ERR: Fri Dec 19 09:09:38 2014: ovconfd (3708/140429034952480): (xpl-89) write(11)[012C5430] failed.
2: ERR: Fri Dec 19 09:09:38 2014: ovconfd (3708/140429034952480): (RTL-28) No space left on device
Could anyone please let me know what can be the issue in this.
Thanks,
Akansha

ORA-00600: internal error code, arguments: [kzxcInitLoadLocal-7], [942],
[ORA-00942: table or view does not exist
ORA-01403: no data found
ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 252
ORA-06512: at line 36
ORA-01403: no data foundWhat does this query return?
SQL> SELECT HOST, ACL
FROM DBA_NETWORK_ACLS;Please see (Redefining a Network Access Control List Fails with ORA-1403 [ID 854083.1]).
Thanks,
Hussein

Scom agent failed to send perf data to scom

Hi all,
Been seeing this from one of our exchange mailbox servers once a day,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Alert: Scom agent failed to send perf data to SCOM. Issues may be occurring that are not being properly reported.
Source: Server - XXXX- XXXX
Path: XXX.XX.XX.XXX;<server name> - XXXX
Last modified by: System
Last modified time: 11/5/2014 (MM/DD/YY)
Alert Description: In PerfDataSource, querying for Global Snapshot failed with error 'The size limit for this request was exceeded.
One or more workflows were affected by this.
Workflow name: _cc4f2e1a_817c_44d9_b527_4216676b3bfd_
Instance name: Database Copy (log) Logical Disk Space (F:) - Server (Mailbox)
instance ID: {2FB68006-BD4A-A39C-5D40-0588077643F7}
EventSourceName: Health Service Modules.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I've checked my event logs, it seems to be taking global snapshot quite ok frequently each day but one would fail and cause this error.
I am wondering what would cause this and if anyone has experienced this before and resolved it.
regards,

For this issue, You can refer below link
http://technet.microsoft.com/en-us/library/hh361436%28v=exchg.140%29.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Dicovering Intelligent Agent on Linux fails with VD-4565

I try to discover an Intelligent Agent 8.1.5 running on a Linux server with an Oracle 8.1.5 DB from an Oracle Enterprise Management Server 2.1. We just upgraded from OEM 2.0.4 to 2.1 and I had no problem with the Linux agent under 2.0.4.
After starting the Agent on the Linux server the SERVICES.ORA and SNMP_RO.ORA files contain the information about the services running on the server. When I start the Discovery Wizard it fails with the error 'Discovery Failed:VD-4565:The agent of the node is already being deleted'.
Then I stoped the agent and all service on the Linux server and did the following. I removed the SID_LIST entry from the LISTENER.ORA file and used the LOCAL_LISTENER init.ora parameter for the database. I know that the agent needs the SID_LIST to discover the database services, but I just wanted to give it a try. After restarting the database, listener and agent the SERVICE.ORA and SNMP_RO.ORA files did not contain any service information as expected. I tried to discover the agent again from the OEM 2.1 console and everything seemed to work fine. No errors this time. The Linux node was added to Nodes folder in the Navigator tree, but for sure no database or listener.
Therefore I put the SID_LIST back into the listener.ora file and restarted the listener and agent. The service information were included in SERVICES.ORA and SNMP_RO.ORA file again. So I tried a Refresh Node from the OEM console and the error VD-4565 showed up again.
Does anyone have any idea what's going on an how I can manage a Linux database from an OEM 2.1 console?
Any help is appreciated.
Thanks
Peter
null

Hello Peter,
I, alas do not have the answer for you. But... your symptom is EXACTLY LIKE MINE!!I was running OEM 2.0.4 and Oracle on a linux box (unfortunately, today I did something wrong and blew the database away!!!, I do not want to tell you how many hours I spend getting the database up, connected and communitcating with Windows NT box running OEM!) I made the switch from 2.0.4 to 2.1, and everything quit. More or less. I fixed my tnsnames.ora file on the NT side. That allowed me to connect. I got the Agent (sortof) running on the linux box and then I could discover the linux host computer name and domain, but it would not find ANY database. Although I could connect from the linux box, the nt box using oem (direct to db), sqlplus, and Access odbc!!! All listeners were there, etc. I did check the snmp*.ora files, and they would not discover anything (linux side) even though the LISTENER was listening, and tnsnames were naming and instances were instancing. My guess is yet another bug.
Sorry for long reply. Now I will RELOAD THE ENTIRE DATABASE AND APP AGAIN!! I so far have been totally unable to run on the liux side, net assist and net easy config, but I could sucessfully bypass those apps by correctly using and configuring initSID.ora, etc and the other *.ora files.
Eric
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Peter C:
I try to discover an Intelligent Agent 8.1.5 running on a Linux server with an Oracle 8.1.5 DB from an Oracle Enterprise Management Server 2.1. We just upgraded from OEM 2.0.4 to 2.1 and I had no problem with the Linux agent under 2.0.4.
After starting the Agent on the Linux server the SERVICES.ORA and SNMP_RO.ORA files contain the information about the services running on the server. When I start the Discovery Wizard it fails with the error 'Discovery Failed:VD-4565:The agent of the node is already being deleted'.
Then I stoped the agent and all service on the Linux server and did the following. I removed the SID_LIST entry from the LISTENER.ORA file and used the LOCAL_LISTENER init.ora parameter for the database. I know that the agent needs the SID_LIST to discover the database services, but I just wanted to give it a try. After restarting the database, listener and agent the SERVICE.ORA and SNMP_RO.ORA files did not contain any service information as expected. I tried to discover the agent again from the OEM 2.1 console and everything seemed to work fine. No errors this time. The Linux node was added to Nodes folder in the Navigator tree, but for sure no database or listener.
Therefore I put the SID_LIST back into the listener.ora file and restarted the listener and agent. The service information were included in SERVICES.ORA and SNMP_RO.ORA file again. So I tried a Refresh Node from the OEM console and the error VD-4565 showed up again.
Does anyone have any idea what's going on an how I can manage a Linux database from an OEM 2.1 console?
Any help is appreciated.
Thanks
Peter<HR></BLOCKQUOTE>
null

SCOM 2012 Unix/linux agents authentication method

Hi everybody
We have an environment including SCOM 2012 SP1, 10 windows server, 40 linux servers and 10 HP-UX servers. all of them are joined a trusted domain. I know the authentication method between windows agents and management server is kerberos. but about linux
and HP-UX servers? I have read :
"UNIX and Linux agent monitoring in Operations Manager requires certificates to secure the SSL communication channel between the Management Servers and agents. The
Operations Manager UNIX/Linux agent is a very lightweight agent implementation, comprising a CIM Object Manager (OpenPegasus) and CIM Providers. There are two
protocols involved in the communication between the Management Server and the UNIX/Linux agent: ssh and WS-Management."
Now I want to secure the Unix/Linux agents authentication and communication to RMS. some questions:
1- how much secure and credible is current authentication method? and in a high secure environment can I trust SCOM self signed Certificates?
2- Considering this point that Unix/linux computers are joined to active directory domain and are using Kerberos to authenticate, can I use this authentication method between RMS and linux Agents?
3- if I make a decision to use certificates should I use gateway server? (considering all servers and RMS are in same trusted domain)
any other suggestion?
Thanks in advance

Hi Ghasem,
Some helpful links for your questions:
http://technet.microsoft.com/en-us/library/hh487288.aspx
http://blogs.technet.com/b/kevinholman/archive/2012/03/18/deploying-unix-linux-agents-using-opsmgr-2012.aspx
Natalya

SCOM Agent windows server issue

Hi,
Here the agent machine is Windows server 2012 64 bit. Its a workgroup machine. These workgroup servers are getting communicating with SCOM management servers through Root CA Server certificate.
*Am able to telnet to 5723 & 5724
*Certificate imported succesfully
Below is the error message am getting in Operations event logs from the agent server;
"Failed to initialize security context for target MSOMHSvc/Hostname. The error returned is 0x80090311(No authority could be contacted for authentication.). This error can apply to either the Kerberos or the SChannel package."
Please assist..
Regards, Rajeev Parambil

Please check the following
1) whether the trust root certificate is installed on both agent machines and Management server
2) You should obtain certificates for both management server and agent machine
3) certificates subject name should be agent FQDN name and management server name respectively
4) make sure that the management server and agent machine can be communicate using FQDN
5) The "Review new manual agent installations in pending management" setting should be selected
For detail on how to monitor no-domain computer using SCOM, pls. refer to the following:
Monitoring non-domain members with OM 2012
http://blogs.technet.com/b/stefan_stranger/archive/2012/04/17/monitoring-non-domain-members-with-om
2012.aspx
Monitoring non-domain servers using SCOM
http://blogs.technet.com/b/quenguyen/archive/2011/07/13/monitoring-non-domain-servers-using-scom.aspx
Roger

SCOM Agent on Linux Server Fail

Similar Messages

Maybe you are looking for