RME not running inventory collection/polling

LMS 3.2 RME 4.2.0
Server suddenly stopped polling inventory and won't run credential verification jobs. The devices are never attempted and job stays in running state till deamons are stopped.
Logs for all failing jobs show this error:
[ Thu Oct 15 06:46:02 BST 2009 ],ERROR,[main],No resource is associated with key "POLLERJOB015".
[ Thu Oct 15 06:46:02 BST 2009 ],ERROR,[main],POLLERJOB015
javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection refused: connect
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:33)
at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:271)
at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:211)
at org.apache.activemq.ActiveMQConnectionFactory.createTopicConnection(ActiveMQConnectionFactory.java:188)
at com.cisco.nm.cmf.jms.TopicConnectionFactoryImp.createTopicConnection(TopicConnectionFactoryImp.java:74)
at com.cisco.nm.rmeng.inventory.ics.util.JobEventListener.start(JobEventListener.java:43)
at com.cisco.nm.rmeng.inventory.ics.util.Job.startEventListener(Job.java:95)

I don't know that a service request was opened for this, but if the originator does not reply, you can start a new thread for this issue. If the symptoms are the same, a service request may be required to figure out why ESS is either not starting completely, or dying after it starts.
One thing we have seen since this thread was first posted was some ESS problems that are caused by corrupt data stores. Moving the contents of NMSROOT/objects/ess/data to a backup location then restarting Daemon Manager has been known to help with that.

Similar Messages

RME 4.3, Inventory Collection doesn't work for 6500

I have a issue with Inventory collection for 6500 devices running IOS 12.2.33 SXI1, fails with a message, "device collection failed"
From IC_Server log i could see SNMP Request timeout exception, so increased SNMP timeout to 10 under device attributes for the device but still it fails.
attacehd is the extract from IC_Server log.
Could anybody help me on this? Thanks

You have not increased the timeout properly. You need to go to RME > Devices > Device Management > RME Devices, and edit the attributes for the required device. Select the device from the list in the left-hand pane to pre-populate the current attributes. Then increase the SNMP timeout to 10, and save the changes. On the previous screen, you will need to APPLY those changes before the 10 second timeout will take effect.

RME 3.2 Inventory Collection Failure with error

Hi,
Inventory collection fails with error is "Timed out. Make sure that ICServer is runningâ. But the ICServer process is running. I enabled debug on could see the following in the IC_Server.log which I'm not sure if it indicates any issues.
I can find the devices in DCR and the devices are classified as Normal in RME.
Series of following message for all the devices
DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.Request,115,Removing device 181from request 1255347128972
DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,163,Removing, 175
DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,171,got device, 175
DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.Device,51,Removing request 1255347128972 for device 175
DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,177,Removed2 dev, 175from Priority of the ENUM is : 0
then,
DEBUG,[Thread-25],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,89,Adding Device :175
DEBUG,[Thread-25],com.cisco.nm.rmeng.inventory.ics.core.Device,46,Adding request 1255347128973 for device 175
DEBUG,[Thread-25],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,142,Found dup device in queue: 175
DEBUG,[Thread-25],com.cisco.nm.rmeng.inventory.ics.core.Request,75,Adding device 175 to request 1255347128973
and then the below messages
DEBUG,[Timer-0],com.cisco.nm.rmeng.inventory.ics.threadpool.ThreadPool,69, Timer Tasks Run method is called.
DEBUG,[Timer-0],com.cisco.nm.rmeng.inventory.ics.threadpool.ThreadPool,69, Timer Tasks Run method is called.
DEBUG,[Timer-0],com.cisco.nm.rmeng.inventory.ics.threadpool.ThreadPool,69, Timer Tasks Run method is called
I highly appreciate any help on this. Thanks

The ICServer process could have locked up which means a full thread dump will be required to see why this is happening. Open a TAC service request, and they can walk you through getting this.

RME 4.31 inventory collection failed on 122-33SXI3

Hi
I have the same issue with IOS 122-33 SXI3 running on 6513.
RME unable to collect the inventory details eventhough updated to LMS 3.2 .
RME version : 4.3.1
Is any workaround to solve this issue on LMS 3.2
Regards
Dileep

Hi Clarke,
I am also facing the similar issue with IOS 12.2(33) SXI1, the Core Switches are in VSS mode. Inventiry collection shows failed for these devices. I am using LMS 3.1 with the following submodule versions:
Name
Version
License Status
Size
CiscoWorks Common Services
3.2.0
Licensed
Not applicable
Campus Manager
5.1.0
Purchased
5000
CiscoView
6.1.8
Licensed
Not applicable
CiscoWorks Assistant
1.1.0
Licensed
Not applicable
Device Fault Manager
3.1.0
Purchased
5000
Internetwork Performance Monitor
4.1.0
Purchased
5000
Integration Utility
1.8.0
Licensed
Not applicable
LMS Portal
1.1.0
Licensed
Not applicable
Resource Manager Essentials
4.2.0
Purchased
5000

LMS 3.0.1, RME 4.1.1 - Inventory Collection Status displays too many device

Running LMS 3.0.1 with RME 4.1.1 on a Windows box. On the Inventory Collection Status screen I see the following:
Inventory Collection Status No. of Devices
Inventory Collected: 1246
Inventory Never Collected: 0
Inventory Recently Failed: 34
Total 1246
The problem with this is that I only have 668 devices. Is this just a cosmetic issue?

Assuming you're not integrated with ACS, then yes. If integrated with ACS, some of the devices may not be authorized. You will need to check your ACS configuration to make sure all devices in LMS are known to ACS and that your user (and the System Identity User) is authorized to manage them.

LMS 3.2 Inventory collection - Job timeouts after ~5h, all devices "Not attempted"

Hello All,
We have a strange problem with LMS 3.2 regarding Inventory Collection.
This problem started immediatelly after the LMS installation/upgrade (LMS 3.2 was installed on a new server, and LMS 2.6 database migrated to it).
All Jobs finish as failed, with all devices "not attempted".
Job hangs for a five and a half hours and then reports failed status.
The symptoms are the same for scheduled jobs and manually created jobs.
I also have opened a TAC case, but it seems that nothing relevant can be found in the IC_Server.log.
Also, according to a packet capture, it seems that LMS does collect SNMP data from devices after a job is started...
We tried to upgrade RME 4.3.0 to 4.3.1.
One Job immediately after the upgrade was succesful (Inventory was collected for manually selected device), but the next day all Inventory Jobs were failing again with the same symptoms...
Does anyone have a sugestion where to look for a problem trace?
Thanks in advance!
Ragards,
Jasmina

Hi Jasmina ,
Please chech the Existing MDF pacakge :
go to common service > software center > device update >>> check the checkbox for Cisco works common service and click on check for updates
--if there is an Update , please upgarde the MDF version..
--Similarly look for any Available Device Pacakges update for RME , if there are Upgarde all the Device Pacakages ....
--After all of the above Task is done , Now re-run the Job and it still fails then share the IC_server.log again..
Thanks--
Afroj

LMS 3.2 RME 4.3.1 Inventory collection failing for switches

I have 6 switches that inventory is failing for. They do run the 12.2(33)SXI3 software but I have the CSCtb16925-1.0 patch installed. I've tried to increase the SNMP timeout for the devices but they still fail.
Ideas?
Chris Jasztrab

You did not properly increase the SNMP timeout. Go to RME > Devices > Device Management > RME Devices, and edit the attributes of the device in question. Perform an inline edit. Click on the device name, then change the existing SNMP timeout value to 10. Then save your changes, and apply them on the previous screen. Then inventory collection should work.

RME 4.3.1 - No inventory collection of some 65xx devices

Hi all,
my problem is, that LMS3.2 with RME 4.3.1 does not make an inventory of some 65xx devices. What I've tried so far to correct this problem:
# read the other incidents regarding this problem
# increased the RME device attribute "SNMP timeout" from 2s to 10s -> no success
# increased SNMP timeout for one device (192.168.90.7) from 10 to 20s and the retries from 2 to 3 -> no success
What I've observed:
# no credential problem (I can backup the configs)
# no SNMP problem (I can snmpwalk through the device)
# Inventory collection takes always only app. 10s until the above error unless I've increased SNMP timeout and retries
# IC_Server.log generates always following error:
[ Tue Dec 15 12:22:59 CET 2009 ],ERROR,[Thread-21],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,729,Exception for device 192.168.90.7 is
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:719)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NumberFormatException: EPLOYMENT RELEASE SOFTWARE (fc1)
TAC Support: http://www.cisco.com/tac
Seems if RME has a problem with this special IOS version.
Enclosed you will find the complete IC_Server.log and the screenshot from the inventory collection of 192.168.90.7.
Thank you in advance for help.
Kind regards
Alfred Brunner

This is CSCtb16925. A patch is available from TAC to correct the problem.

LMS 3.2 - RME 4.3.1 Inventory Collection never stops (Job Result = pending)

Hello all,
with our LMS-System running on Solaris 10 we have the following problem:
- Inventory Collection never stops after starting
- This can be seen with all devices or 1 device selected
- Config-Mgmt is working
- After re-init of RME-DB the problem persists
In Logfile (IC_Server.log) no problems are shown.
In Job-Logfile only the collection request is shown.
Any help is appreciated
Thanks for your feedback
Lothar

Hi Joe,
with further troubleshooting this problem I discoverd the following.
- Having problems with inventoring certain Cat4000 we requested patch for Bug-ID CSCtb16925 (LibInventory.zip-File).
- Replacing this file with the old one or installing the newest IDU for RME the problem was solved.
It seems that the LibInventory.zip file given with Bug-ID CSCtb16925 is somewhat buggy (maybe in context with device-number) greater
than 1000.
Thanks for your support.
Lothar

RME 4.3.1 Inventory collection failing for cisco 3925

Hi,
I've a customer having LMS 3.2 and RME 4.3.1. He has 14 Cisco 3925 routers out of which inventory collection for 2 fails.
Router IOS is: c3900-universalk9-mz.SPA.150-1.M.bin".
Can someone suggest what might be going wrong? Attached is the IC_Server log file for reference.
Thanks in advance,
inner_silence

Hi,
Here are the exception found from the log :-
[ Fri Mar 18 16:28:24 EDT 2011 ],ERROR,[Thread-17],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,729,Exception for device 10.103.251.12 is
java.lang.reflect.InvocationTargetException
    at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:719)
    at java.lang.Thread.run(Thread.java:595)
Caused by: com.cisco.nm.xms.xdi.ags.system.CollectionFailed: java.lang.StringIndexOutOfBoundsException: String index out of range: 2
    at com.cisco.nm.xms.xdi.pkgs.LibInventory.EnergyWise_HelperMethods.getDeviceEnergyWise(EnergyWise_HelperMethods.java:72)
    at com.cisco.nm.xms.xdi.pkgs.SharedInventoryCatIOS.EnergyWiseAGI_ENERGYWISE_Mib.g$eval(EnergyWiseAGI_ENERGYWISE_Mib.java:51)
    at com.cisco.nm.xms.xdi.ags.EnergyWiseAGI.g$eval(EnergyWiseAGI.java:21)
    at com.cisco.nm.xms.xdi.SdiEngine.initAndEvalAGIs(SdiEngine.java:383)
    at com.cisco.nm.xms.xdi.SdiEngine.request(SdiEngine.java:309)
    at com.cisco.nm.xms.xdi.SdiEngine.getDevRepr(SdiEngine.java:302)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:539)
    ... 1 more
[ Fri Mar 18 16:28:24 EDT 2011 ],ERROR,[Thread-17],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,761, Collection failed for the device : 63
com.cisco.nm.xms.xdi.ags.system.CollectionFailed: java.lang.StringIndexOutOfBoundsException: String index out of range: 2
Kindly check if the your device is running the required IOS on the device as per the device supported list :-
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/device_support/table/lms32sdt.html
There are two 3925 listed with different versions :-
Cisco 3925 Integrated Services Router   --> 1.3.6.1.4.1.9.1.1042 --> 15.0(1)M [RME]. if this is your device then upgrade to
3925 to 150-1.M2
and
Cisco 3925E Integrated Services Router --> 1.3.6.1.4.1.9.1.1144 --> 15.1(1)T
Thanks,
Gaganjeet
If this post answers your question, please click the "Correct Answer" button

Prime Infrastructure 2.2- problems: Wired Detailed Device Inventory report not running / Cisco 5500 WLCs no listed in subgroup

New installation of Prime Infrastructure 2.2.0 (PI-VA-2.2.0.0.158.ova)
installed fixes/software/device packs:
PI 2.2.1 Poodle Fix (installed)
PI 2.2.1 Maintenance Release (installed,ncs stopped,rebooted)
Prime Infrastrucutre 2.2 Device Pack 3 (installed,ncs stopped,rebooted)
Licences installed (ncs stopped,rebooted)
Added all devices via Bulk Import (Inventory>Device Management>Network Devices)
Problem 1:
The Cisco 5500 WLCs are not listed in Inventory>Device Management>Network Devices (see screen shot) but listed under "All Devices"!
The Cisco 4400 WLCs and the 8500 WLCs are listed within their subgroup.
Devices are in "Managed State"
Problem 2: fixed! (Browser issue)
Problem 3:
Unable to run "Wired Detailed Device Inventory" report because I get the error message: Failed to run report: Unable to retrieve data for: Chassis Information (if Chassis Information is selected, if System Information is selected I get the error message with ...retrieve data for:System Information)
All devices do have an "Admin Status = Managed" and the Last Inventory Collections Status = Completed.
Has anyone the same issues or a tip for me?
Another topic, the "User Defined Fileds" are not exported when with running a "Device Export" (Inventory > Device Management > Network Devices). ;-(
BR
Bastian

Hallo Bastian,
I think you still have browser issue, Using IE is still the best with Prime.
I have exactly same prime 2.2 and installed fixes/software/device packs.
I have no problem I can see all views. I use now IE 11, with Chrome 42.0.2311.90 and firefox 37.01 I have problems too with lots of views. You have not tell what browser + version you have.
Since you have same prime 2.2 as me. I have other problems, can you check yours?
Can you see a functional CLI template page at Configuration > Templates > Features & Technologies:
https://supportforums.cisco.com/discussion/12481691/can-cisco-prime-22-still-do-simple-ad-hoc-deployment-job-cli-over-all-switches
Do you have SNMP Connectivity Failed while Verify Credentials has no errors all green and checked.
https://supportforums.cisco.com/discussion/12494786/snmp-request-exceeds-internal-data-buffer-512-bytes-prime-22-asa-5545

SW Inventory not running

I have about 100+ plus machines that are no longer running their software inventory.       They all seem to have the same data in InventoryAgent.log.    I don't know why it is saying VirtualServer when these
are physical workstations.   Any help would be great.
Collection: Namespace = \\localhost\root\vm\VirtualServer; Query = SELECT __CLASS, __PATH, __RELPATH, Name FROM VirtualMachine; Timeout = 600 secs. InventoryAgent 12/29/2014 11:31:38 AM 648
(0x0288)
Failed to get IWbemService Ptr for
\\localhost\root\vm\VirtualServer Namespace: 8004100E InventoryAgent 12/29/2014 11:31:39 AM 648 (0x0288)
Failed to enumerate instances of VirtualMachine: 8004100E InventoryAgent 12/29/2014 11:31:39 AM 648 (0x0288)
Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, Description, DeviceID, DisplayType, MonitorManufacturer, MonitorType, Name, PixelsPerXLogicalInch, PixelsPerYLogicalInch, ScreenHeight, ScreenWidth
FROM Win32_DesktopMonitor; Timeout = 600 secs. InventoryAgent 12/29/2014 11:31:39 AM 648 (0x0288)
Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, Name, TotalPageFileSpace, TotalPhysicalMemory, TotalVirtualMemory FROM CCM_LogicalMemoryConfiguration; Timeout = 600 secs. InventoryAgent 12/29/2014
11:31:39 AM 648 (0x0288)
Collection: Namespace =
\\localhost\root\Microsoft\appvirt\client; Query = SELECT __CLASS, __PATH, __RELPATH, CachedLaunchSize, CachedPercentage, CachedSize, LaunchSize, Name, PackageGUID, TotalSize, Version, VersionGUID FROM Package; Timeout = 600 secs. InventoryAgent 12/29/2014
11:31:39 AM 648 (0x0288)
Failed to get IWbemService Ptr for
\\localhost\root\Microsoft\appvirt\client Namespace: 8004100E InventoryAgent 12/29/2014 11:31:39 AM 648 (0x0288)
Failed to enumerate instances of Package: 8004100E InventoryAgent 12/29/2014 11:31:39 AM 648 (0x0288)
Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, Availability, Description, DeviceID, Manufacturer, Name, Status FROM Win32_IDEController; Timeout = 600 secs. InventoryAgent 12/29/2014
11:31:39 AM 648 (0x0288)
Collection: Namespace = \\.\root\cimv2\sms; Query = SELECT __CLASS, __PATH, __RELPATH, Availability, Compressed, Description, DeviceID, DriveType, FileSystem, Name, Size, SystemName, VolumeName, VolumeSerialNumber FROM
SMS_LogicalDisk; Timeout = 600 secs. InventoryAgent 12/29/2014 11:31:39 AM 648 (0x0288)
Skipping Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, InstanceKey, PhysicalHostName, PhysicalHostNameFullyQualified FROM Win32Reg_SMSGuestVirtualMachine64, we're running on a 32-bit platform
and attempting to force enumerating 64-bit data. InventoryAgent 12/29/2014 11:31:39 AM 648 (0x0288)
Collection: Namespace = \\.\root\CCM\powermanagementagent; Query = SELECT __CLASS, __PATH, __RELPATH, Requester, RequesterInfo, RequesterType, RequestType, Time, UnknownRequester FROM CCM_PwrMgmtLastSuspendError;
Timeout = 600 secs. InventoryAgent 12/29/2014 11:31:39 AM 648 (0x0288)
Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, Description, Manufacturer, Name, Status FROM Win32_NetworkClient; Timeout = 600 secs. InventoryAgent 12/29/2014 11:31:39 AM 648
(0x0288)
Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT __CLASS, __PATH, __RELPATH, Name, SMSID, Domain, SystemRole, SystemType, LocalDateTime FROM CCM_System; Timeout = 600 secs. InventoryAgent 12/29/2014
11:31:39 AM 648 (0x0288)
Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, Availability, Caption, Description, DeviceID, Drive, Manufacturer, MediaType, Name, SCSITargetId, SystemName, VolumeName FROM Win32_CDROMDrive;
Timeout = 600 secs. InventoryAgent 12/29/2014 11:31:39 AM 648 (0x0288)
Collection: 47/60 inventory data items successfully inventoried. InventoryAgent 12/29/2014 11:31:39 AM 648 (0x0288)
Inventory: Collection Task completed in 69.326 seconds InventoryAgent 12/29/2014 11:31:39 AM 648 (0x0288)
Inventory: 13 Collection Task(s) failed. InventoryAgent 12/29/2014 11:31:40 AM 648 (0x0288)
Inventory: Temp report = C:\WINDOWS\CCM\Inventory\Temp\de862af3-01c5-4cd9-92c3-e49cc1693e60.xml InventoryAgent 12/29/2014 11:31:40 AM 648 (0x0288)
Inventory: Starting reporting task. InventoryAgent 12/29/2014 11:31:40 AM 1060 (0x0424)
Reporting: 31 report entries created. InventoryAgent 12/29/2014 11:31:40 AM 1060 (0x0424)
Inventory: Reporting Task completed in 0.780 seconds InventoryAgent 12/29/2014 11:31:40 AM 1060 (0x0424)
Inventory: Successfully sent report. Destination:mp:MP_HinvEndpoint, ID: {0CCC3339-4D74-4764-A591-97815CDAD35F}, Timeout: 80640 minutes MsgMode: Signed, Not Encrypted InventoryAgent 12/29/2014 11:31:40 AM 1060 (0x0424)
Inventory: Cycle completed in 85.005 seconds InventoryAgent 12/29/2014 11:31:49 AM 1060 (0x0424)
Inventory: Action completed. InventoryAgent 12/29/2014 11:31:49 AM 1060 (0x0424)
Inventory: ************************ End of message processing. ************************ InventoryAgent 12/29/2014 11:31:49 AM 1060 (0x0424)
Inventory: *********************** Start of message processing. *********************** InventoryAgent 12/30/2014 9:37:24 AM 2424 (0x0978)
Inventory: Message type is InventoryAction InventoryAgent 12/30/2014 9:37:24 AM 2424 (0x0978)
Inventory: Temp directory = C:\WINDOWS\CCM\Inventory\Temp\ InventoryAgent 12/30/2014 9:37:24 AM 2424 (0x0978)
Inventory: Clearing old collected files. InventoryAgent 12/30/2014 9:37:24 AM 2424 (0x0978)
Inventory: Opening store for action {00000000-0000-0000-0000-000000000003} ... InventoryAgent 12/30/2014 9:37:24 AM 2424 (0x0978)
Inventory: Action=Discovery, ReportType=Full, MajorVersion=145, MinorVersion=0 InventoryAgent 12/30/2014 9:37:24 AM 2424 (0x0978)
Inventory: Initialization completed in 0.390 seconds InventoryAgent 12/30/2014 9:37:24 AM 2424 (0x0978)
Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT __CLASS, __PATH, __RELPATH, PlatformID FROM CCM_DiscoveryData; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:24 AM 1900 (0x076C)
Collection: Signing turned off. Skipping query SELECT __CLASS, __PATH, __RELPATH, EncodedSigningPublicKey FROM CCM_ClientSecurityInformation; InventoryAgent 12/30/2014 9:37:24 AM 1900 (0x076C)
Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT __CLASS, __PATH, __RELPATH, FQDN FROM CCM_ExtNetworkAdapterConfiguration; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:24 AM 1900 (0x076C)
Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT __CLASS, __PATH, __RELPATH, SystemOUName FROM CCM_SystemOU; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:24 AM 1900 (0x076C)
Collection: Namespace = \\.\root\ccm; Query = SELECT __CLASS, __PATH, __RELPATH, ClientIdChangeDate, PreviousClientId FROM CCM_Client; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:24 AM 1900 (0x076C)
Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT __CLASS, __PATH, __RELPATH, ADSiteName FROM CCM_ADSiteInfo; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:24 AM 1900 (0x076C)
Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, IPAddress, MACAddress FROM Win32_NetworkAdapterConfiguration WHERE IPEnabled=TRUE; Timeout = 600 secs. InventoryAgent 12/30/2014
9:37:25 AM 1900 (0x076C)
Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, UserName FROM Win32_ComputerSystem; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:25 AM 1900 (0x076C)
Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT __CLASS, __PATH, __RELPATH, IPv6Address FROM CCM_IPv6NetworkAdapterConfiguration; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:25 AM 1900
(0x076C)
Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT __CLASS, __PATH, __RELPATH, IPSubnet FROM CCM_NetworkAdapterConfiguration; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:25 AM 1900 (0x076C)
Collection: Namespace = \\.\root\ccm; Query = SELECT __CLASS, __PATH, __RELPATH, Name FROM SMS_Authority; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:25 AM 1900 (0x076C)
Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT __CLASS, __PATH, __RELPATH, IsWriteFilterCapable, IsPortableOS, AgentEdition, IsAOACCapable FROM CCM_OperatingSystem; Timeout = 600 secs. InventoryAgent 12/30/2014
9:37:25 AM 1900 (0x076C)
Collection: Namespace = \\.\root\ccmvdi; Query = SELECT __CLASS, __PATH, __RELPATH, IsAssignedToUser, IsMachineChangesPersisted, IsVirtual, HostIdentifier FROM CCM_DesktopMachine; Timeout = 600 secs. InventoryAgent 12/30/2014
9:37:25 AM 1900 (0x076C)
Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT __CLASS, __PATH, __RELPATH, IPv6Prefix FROM CCM_IPv6PrefixNetworkAdapterConfiguration; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:25 AM 1900
(0x076C)
Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, UUID FROM Win32_ComputerSystemProduct; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:25 AM 1900 (0x076C)
Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT __CLASS, __PATH, __RELPATH, Domain FROM CCM_ComputerSystem; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:25 AM 1900 (0x076C)
Collection: Namespace = \\.\root\ccm; Query = SELECT __CLASS, __PATH, __RELPATH, HardwareID1 FROM CCM_ClientIdentificationInformation; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:25 AM 1900 (0x076C)
Collection: Namespace = \\.\root\cimv2\sms; Query = SELECT __CLASS, __PATH, __RELPATH, Description FROM SMS_Processor; Timeout = 600 secs. InventoryAgent 12/30/2014 9:37:25 AM 1900 (0x076C)
Collection: 17/18 inventory data items successfully inventoried. InventoryAgent 12/30/2014 9:37:26 AM 1900 (0x076C)
Inventory: Collection Task completed in 2.293 seconds InventoryAgent 12/30/2014 9:37:26 AM 1900 (0x076C)
Inventory: 1 Collection Task(s) failed. InventoryAgent 12/30/2014 9:37:26 AM 1900 (0x076C)
Inventory: Temp report = C:\WINDOWS\CCM\Inventory\Temp\c87baeb7-ec5b-4efc-a31b-a4ec237d335c.xml InventoryAgent 12/30/2014 9:37:26 AM 1900 (0x076C)
Inventory: Starting reporting task. InventoryAgent 12/30/2014 9:37:26 AM 2424 (0x0978)
Reporting: 16 report entries created. InventoryAgent 12/30/2014 9:37:27 AM 2424 (0x0978)
Inventory: Reporting Task completed in 0.094 seconds InventoryAgent 12/30/2014 9:37:27 AM 2424 (0x0978)
Inventory: Successfully sent report. Destination:mp:MP_DdrEndpoint, ID: {C464BB78-8B5E-4B50-98CB-20F9998CEF45}, Timeout: 80640 minutes MsgMode: Signed, Not Encrypted InventoryAgent 12/30/2014 9:37:27 AM 2424 (0x0978)
Inventory: Cycle completed in 3.213 seconds InventoryAgent 12/30/2014 9:37:27 AM 2424 (0x0978)
Inventory: Action completed. InventoryAgent 12/30/2014 9:37:27 AM 2424 (0x0978)
Inventory: ************************ End of message processing. ************************ InventoryAgent 12/30/2014 9:37:27 AM 2424 (0x0978)
mqh7

What leads you to believe that software inventory is not working?
I setup SW inventory to run every 7 days. I then ran a SQL query that showed me all machines that have not run a SW inventory in 8 days or more.   I had 95 machines.   I then started the Resource Explorer on a handful of these
machines and it too showed the SW inventory had not run for far more than 7 days.   All of these machines appear in the Collection has healthy which is what is throwing me off. What also throws me off is in c:\windows\ccm\logs I
see 15+ log files that have been written too "today". I have not gone through all of them yet.
Am I chasing a red herring or do I have something to worry about based on the SQL query and Resource Explorer? Note, all of these machines are desktop and are "usually" left on.
Thanks.
mqh7

After ZEN 7 HP3 agent upgrade, inventory not running?

I didn't notice this until now, but after upgrading the agents on the
workstations from 6.5 SP1b, to 7.0 HP3, I'm not getting inventory scans
anymore.
Inventory IS running and working on the server end (I believe the back-
end is 7.0 SP1). I just don't see the ZEN 7 "workstations" as being
scanned.
I looked in the scheduler task and I see it's reading my USER policy,
but does not appear to be reading my WORKSTATION policy for some strange
reason.
AT least I used to see workstation inventory in there and now I do not.
I've not changed any of the associations or policies for workstations.
Any ideas?

In article <sPqSi.16628$[email protected]>,
[email protected] says...
> m_jonis,
>
> It appears that in the past few days you have not received a response to your posting. That concerns us, and has triggered this automated reply.
>
> Has your problem been resolved? If not, you might try one of the following options:
>
> - Visit http://support.novell.com/ to search the knowledgebase and check the other support options available on that page under "Self Support" and "Support Programs".
> - You could also try posting your message again. Make sure it is posted in the correct newsgroup. (http://support.novell.com/forums)
>
> If this is a reply to a duplicate posting, please ignore and accept our apologies and rest assured we will issue a stern reprimand to our posting bot.
>
> Good luck!
>
> Your Novell Product Support Forums Team
> http://support.novell.com/forums/
>
>
For some reason that agent doesn't like the ZEN 7 SP1 policies (even
created from scratch), so I had to create new ones from scratch with the
updated snapins.
Weird.

Inventory Collection problem for RME 4.3.1 LMS 3.2

I recently upgraded from LMS 3.1 to LMS 3.2 and RME v 4.3.1. I have problems with the inventory collection. It will start scanning, but stops after approximately 10 devices. The rest of them will have a pending state. If I stop the collection job and start it again none (0) devices will be scanned. If I restart the ICServer it will result in the first option. That is, it will scan only 10 devices and then stop. I have extended the SNMP timeout to 30 secs and zero retries. Any suggestion would be appreciated

I have read through the dump and cant find anything in particular. Another discovery I've made is that the SNMP walk of an unsuccessful device takes 10 times longer than a successful device. An inventory job on a unsuccessful device only goes into pending and the job never starts.

RME 4 - Inventory Collection Failure

I am getting the following RME inventory collection error on 4 devices. These 4 devices were recently added to the network and were all attached to a new radius server. I have tested AAA to the 4 switches and am confident that radius is working as intended.
The devices are a mix of 2950 and 3550 switches.
Here is the error.
RICS0001:Internal Error,unable to process the collected data from the device.
Thanks in advance.

In that case, this is probably CSCsk65355 which should be fixed in 4.1.1. However, 4.1.1 suffers from CSCsm97530. So I would suggest to first upgrade to RME 4.1.1. If you continue to see this, then you can contact TAC and apply patch for CSCsm97530 over 4.1.1.

RME not running inventory collection/polling

Similar Messages

Maybe you are looking for