Device Status/Software Distribution
I am trying to push new software down to few device but these are reporting 'the device has not reported status in 19 or more days'. These devices are not receving the new software. When checking the Device Report the following appears
No events are available. This may be because the client has not yet sent the event or the events have been purged from the server. Refer to %WINDIR%\WindowsUpdate.log on Device2.domain.local for details.
Where is the windowsupdate.log on the device or server?
Previously I was advised to enable alert logger in Status viewer but i can not see this option. I can only see the Menu, Managed programs and managed objects viewer. The connection in Status viewer/MDM connect now is successful.
Answers
I logged a call with Microsoft and they identified orphaned registry keys caused by failed packages, after removing the orphaned key from HKLM\Security\SwMgmt\Download the device made the contact and was downloading software again once i clicked MDM Connect Now.
Hope others can benefit from this.- Marked As Answer byJun1or Saturday, October 31, 2009 1:20 PM
All Replies
Have you had software distribution working previously? Are you using a Web Proxy?
You can enable logging using the Connect Now client. Launch Connect Now -> Menu -> Logging.
Check the MDM console for Last Connected Date rather than the Software Distribution Console. Several people have reported the Software Distribution Console Date doesn't update until new software is pushed out. Use the MDM Console for correct connection times.
Are you sure the software package has been approved and associated with the correct device group?
Check out the Troubleshooting MDM Software Distribution Issues TechNote.
Cheers Wayne
Airloom- Edited byWayne Phillips.MVP, ModeratorWednesday, October 07, 2009 12:20 AMadded link
- Hi Jun1or, This is due to the WSUS software thinking it is regular Windows machines being used as clients, and not Windows Mobile clients. :-)
As Wayne already described best to turn on logging on the device side and try to find a smoking gun.. You can also check out my previous posting on the various logging you can do on a Windows Mobile device here: http://myitforum.com/cs2/blogs/mnielsen/archive/2009/02/03/windows-mobile-troubleshooting-how-to-log-like-an-expert.aspx
|\\arco.. Please see log details below:
There are random devices which are doing this.
Device Update Log: to disable, zero HKLM\System\DeviceUpdate\LogLevel
2009-10-21 12:42:50 omadmclient.exe:CCeBitsStore::GetDbVersion 0x200: hr=0x02009-10-21 12:42:50 omadmclient.exe:CCeBitsStore::GetJobRecordById failed, hr=0x80200001
2009-10-21 12:42:50 omadmclient.exe:Error: DisGetDownloadJobHandle, hr=0x80200001
2009-10-21 15:06:33 services.exe:SvcProc: wakeup for event: 0
2009-10-21 15:06:33 services.exe:+CServiceThread::TryBindSocketToVpnInterface()
2009-10-21 15:06:33 services.exe:+CServiceThread::TearDownOldPort()
2009-10-21 15:06:33 services.exe:-CServiceThread::TearDownOldPort()
2009-10-21 15:06:33 services.exe:CServiceThread::TryBindSocketToVpnInterface: not in a connected state, not binding.
2009-10-21 15:06:33 services.exe:+CServiceThread::TearDownOldPort()
2009-10-21 15:06:33 services.exe:-CServiceThread::TearDownOldPort()
2009-10-21 15:06:33 services.exe:-CServiceThread::TryBindSocketToVpnInterface(), hr = 0
2009-10-21 15:06:33 services.exe:SvcProc: main loop - m_fInterfaceUp = 0, m_sock = ffffffff, weMessageAvailable = 46a02436, hInterfaceChangeEvent = 46b3884e.
2009-10-21 15:06:33 services.exe:SvcProc: wakeup for event: 0
2009-10-21 15:06:33 services.exe:+CServiceThread::TryBindSocketToVpnInterface()
2009-10-21 15:06:33 services.exe:CServiceThread::TryBindSocketToVpnInterface: not in a connected state, not binding.
2009-10-21 15:06:33 services.exe:+CServiceThread::TearDownOldPort()
2009-10-21 15:06:33 services.exe:-CServiceThread::TearDownOldPort()
2009-10-21 15:06:33 services.exe:-CServiceThread::TryBindSocketToVpnInterface(), hr = 0
2009-10-21 15:06:33 services.exe:SvcProc: main loop - m_fInterfaceUp = 0, m_sock = ffffffff, weMessageAvailable = 46a02436, hInterfaceChangeEvent = 46b3884e.
2009-10-21 15:06:33 services.exe:SvcProc: wakeup for event: 0
2009-10-21 15:06:33 services.exe:+CServiceThread::TryBindSocketToVpnInterface()
2009-10-21 15:06:34 services.exe:CServiceThread::TryBindSocketToVpnInterface: not in a connected state, not binding.
2009-10-21 15:06:34 services.exe:+CServiceThread::TearDownOldPort()
2009-10-21 15:06:34 services.exe:-CServiceThread::TearDownOldPort()
2009-10-21 15:06:34 services.exe:-CServiceThread::TryBindSocketToVpnInterface(), hr = 0
2009-10-21 15:06:34 services.exe:SvcProc: main loop - m_fInterfaceUp = 0, m_sock = ffffffff, weMessageAvailable = 46a02436, hInterfaceChangeEvent = 46b3884e.
2009-10-21 15:06:37 services.exe:SvcProc: wakeup for event: 0
2009-10-21 15:06:38 services.exe:+CServiceThread::TryBindSocketToVpnInterface()
2009-10-21 15:06:38 services.exe:CServiceThread::TryBindSocketToVpnInterface: not in a connected state, not binding.
2009-10-21 15:06:38 services.exe:+CServiceThread::TearDownOldPort()
2009-10-21 15:06:38 services.exe:-CServiceThread::TearDownOldPort()
2009-10-21 15:06:38 services.exe:-CServiceThread::TryBindSocketToVpnInterface(), hr = 0
2009-10-21 15:06:38 services.exe:SvcProc: main loop - m_fInterfaceUp = 0, m_sock = ffffffff, weMessageAvailable = 46a02436, hInterfaceChangeEvent = 46b3884e.
2009-10-21 15:06:38 services.exe:SvcProc: wakeup for event: 0
2009-10-21 15:06:38 services.exe:+CServiceThread::TryBindSocketToVpnInterface()
2009-10-21 15:06:38 services.exe:CServiceThread::TryBindSocketToVpnInterface: not in a connected state, not binding.
2009-10-21 15:06:38 services.exe:+CServiceThread::TearDownOldPort()
2009-10-21 15:06:38 services.exe:-CServiceThread::TearDownOldPort()
2009-10-21 15:06:38 services.exe:-CServiceThread::TryBindSocketToVpnInterface(), hr = 0
2009-10-21 15:06:38 services.exe:SvcProc: main loop - m_fInterfaceUp = 0, m_sock = ffffffff, weMessageAvailable = 46a02436, hInterfaceChangeEvent = 46b3884e.
2009-10-21 15:06:38 services.exe:SvcProc: wakeup for event: 0
2009-10-21 15:06:38 services.exe:+CServiceThread::TryBindSocketToVpnInterface()
2009-10-21 15:06:38 services.exe:CServiceThread::TryBindSocketToVpnInterface: not in a connected state, not binding.
2009-10-21 15:06:38 services.exe:+CServiceThread::TearDownOldPort()
2009-10-21 15:06:38 services.exe:-CServiceThread::TearDownOldPort()
2009-10-21 15:06:38 services.exe:-CServiceThread::TryBindSocketToVpnInterface(), hr = 0
2009-10-21 15:06:38 services.exe:SvcProc: main loop - m_fInterfaceUp = 0, m_sock = ffffffff, weMessageAvailable = 46a02436, hInterfaceChangeEvent = 46b3884e.
2009-10-21 15:06:38 services.exe:SvcProc: wakeup for event: 0
2009-10-21 15:06:38 services.exe:+CServiceThread::TryBindSocketToVpnInterface()
2009-10-21 15:06:38 services.exe:CServiceThread::TryBindSocketToVpnInterface: not in a connected state, not binding.
2009-10-21 15:06:38 services.exe:+CServiceThread::TearDownOldPort()
2009-10-21 15:06:38 services.exe:-CServiceThread::TearDownOldPort()
2009-10-21 15:06:39 services.exe:-CServiceThread::TryBindSocketToVpnInterface(), hr = 0
2009-10-21 15:06:39 services.exe:SvcProc: main loop - m_fInterfaceUp = 0, m_sock = ffffffff, weMessageAvailable = 46a02436, hInterfaceChangeEvent = 46b3884e.
2009-10-21 15:06:39 services.exe:SvcProc: wakeup for event: 0
2009-10-21 15:06:39 services.exe:+CServiceThread::TryBindSocketToVpnInterface()
2009-10-21 15:06:39 services.exe:CServiceThread::TryBindSocketToVpnInterface: not in a connected state, not binding.
2009-10-21 15:06:39 services.exe:+CServiceThread::TearDownOldPort()
2009-10-21 15:06:39 services.exe:-CServiceThread::TearDownOldPort()
2009-10-21 15:06:39 services.exe:-CServiceThread::TryBindSocketToVpnInterface(), hr = 0
2009-10-21 15:06:39 services.exe:SvcProc: main loop - m_fInterfaceUp = 0, m_sock = ffffffff, weMessageAvailable = 46a02436, hInterfaceChangeEvent = 46b3884e.
2009-10-21 15:06:39 services.exe:+PSH_IOControl()
2009-10-21 15:06:39 services.exe:-PSH_IOControl()
2009-10-21 15:06:53 services.exe:SvcProc: wakeup for event: 0
2009-10-21 15:06:53 services.exe:+CServiceThread::TryBindSocketToVpnInterface()
2009-10-21 15:06:53 services.exe:CServiceThread::TryBindSocketToVpnInterface: not in a connected state, not binding.
2009-10-21 15:06:53 services.exe:+CServiceThread::TearDownOldPort()
2009-10-21 15:06:53 services.exe:-CServiceThread::TearDownOldPort()
2009-10-21 15:06:53 services.exe:-CServiceThread::TryBindSocketToVpnInterface(), hr = 0
2009-10-21 15:06:53 services.exe:SvcProc: main loop - m_fInterfaceUp = 0, m_sock = ffffffff, weMessageAvailable = 46a02436, hInterfaceChangeEvent = 46b3884e.
2009-10-21 15:06:53 services.exe:SvcProc: wakeup for event: 0
2009-10-21 15:06:53 services.exe:+CServiceThread::TryBindSocketToVpnInterface()
2009-10-21 15:06:53 services.exe:CServiceThread::TryBindSocketToVpnInterface: not in a connected state, not binding.
2009-10-21 15:06:53 services.exe:+CServiceThread::TearDownOldPort()
2009-10-21 15:06:53 services.exe:-CServiceThread::TearDownOldPort()
2009-10-21 15:06:53 services.exe:-CServiceThread::TryBindSocketToVpnInterface(), hr = 0
2009-10-21 15:06:53 services.exe:SvcProc: main loop - m_fInterfaceUp = 0, m_sock = ffffffff, weMessageAvailable = 46a02436, hInterfaceChangeEvent = 46b3884e.
2009-10-21 15:06:54 services.exe:SvcProc: wakeup for event: 0
2009-10-21 15:06:54 services.exe:+CServiceThread::TryBindSocketToVpnInterface()
2009-10-21 15:06:54 services.exe:CServiceThread::TryBindSocketToVpnInterface: binding to interface 10.24.3.238
2009-10-21 15:06:54 services.exe:-CServiceThread::TryBindSocketToVpnInterface(), hr = 0
2009-10-21 15:06:54 services.exe:SvcProc: main loop - m_fInterfaceUp = 1, m_sock = 83, weMessageAvailable = 46a02436, hInterfaceChangeEvent = 46b3884e.
2009-10-21 15:06:54 services.exe:SvcProc: wakeup for event: 2
2009-10-21 15:06:54 services.exe:+CServiceThread::ProcessIncomingUdpTraffic()
2009-10-21 15:06:54 services.exe: Rejecting packet -- too small (or other read error).
2009-10-21 15:06:54 services.exe:-CServiceThread::ProcessIncomingUdpTraffic(), hr = 02009-10-21 15:06:54 services.exe:SvcProc: main loop - m_fInterfaceUp = 1, m_sock = 83, weMessageAvailable = 46a02436, hInterfaceChangeEvent = 46b3884e.
2009-10-21 15:07:01 services.exe:+PSH_IOControl()
2009-10-21 15:07:01 services.exe:-PSH_IOControl()
This is from another Device:
Device Update Log: to disable, zero HKLM\System\DeviceUpdate\LogLevel
2009-10-21 16:27:59 omadmclient.exe:CCeBitsStore::GetDbVersion 0x200: hr=0x02009-10-21 16:27:59 omadmclient.exe:CCeBitsStore::GetJobRecordById failed, hr=0x80200001
2009-10-21 16:28:00 omadmclient.exe:Error: DisGetDownloadJobHandle, hr=0x80200001
2009-10-21 16:29:04 omadmclient.exe:CCeBitsStore::GetDbVersion 0x200: hr=0x0
2009-10-21 16:29:04 omadmclient.exe:CCeBitsStore::GetJobRecordById failed, hr=0x80200001
2009-10-21 16:29:04 omadmclient.exe:Error: DisGetDownloadJobHandle, hr=0x80200001
- This level of troubleshooting should go through the MDM Product team. I suggest logging a case with Microsoft Support.
Cheers Wayne
Airloom Number of the devices which are having issues had certain software manually installed (signed copied on to memory card on the device), could this potentially cause an issue??
When looking in managed programs the manually installed application does not show as installed its not in the remove programs either but i know the software is installed. Is there anyway I can remove this software from the devices??
ThanksI have one device not syncing with the Software Distribution console for days, however it's syncing properly with the Device Manager console. I also manually installed software, rewriting remote installed software (replacing exe files).
I found out that everytime this device connects with the Device Manager server, the following command shows "Failed" on the Device History window:
Description: ./Vendor/MSFT/SwMgmt/Download?list=StructData
Operation: Get
Context: SD.MatchingDataQuery
Other devices syncing properly with the Software Distribution console show Success when executing the same command.
Is there a way to reset the Software Distribution configuration on certain device? I tried to delete the database at \Application Data\MDS because there was some error at the software distribution log referring to it but no luck. There exist some tools for Windows PC such as wuauclt.exe, but what about Windows Mobile?
ThanksI logged a call with Microsoft and they identified orphaned registry keys caused by failed packages, after removing the orphaned key from HKLM\Security\SwMgmt\Download the device made the contact and was downloading software again once i clicked MDM Connect Now.
Hope others can benefit from this.- Marked As Answer byJun1or Saturday, October 31, 2009 1:20 PM
- Thank you very much!!!
I shall apply the fix on the corrupted device and try to sync it with the Software Distribution server. I'll give some feedback later.
