![]() RegTask: Failed to send registration request. RegTask: Failed to send registration request message. CCMEXEC 12:25:56 PM 1832 (0x0728)ĬlientIDManagerStartup.log keeps repeating this: HandleRemoteSyncSend failed (0x80040231). ![]() HTTP ERROR: URL=, Port=80, Protocol=http, SSLOptions=0, Code=12002, Text=ERROR_WINHTTP_TIMEOUT CCMEXEC I've run that batch file that I see on most of the websites where it runs a for loop and reregisters all the DLLs in WBEM and runs mofcomp on all the MOFs and MFLs.įailed in WinHttpSendRequest API, ErrorCode = 0x2ee2 CCMEXEC 12:25:56 Once the client was uninstalled and reinstalled the errors below started. In the log files and at least one I know for sure was patching just fine, but kept showing on reports as missing a lot of patches so that tells me it wasn't able to report its status. The clients that weren't getting windows updates didn't appear to have any issues being logged ![]() Our site layout is like this: Main Server and Primary MP at our corporate site, we have a secondary MP at our site.Ĭlients register with the Primary MP and then automatically are directed to our local MP and I think all the clients with this issue are running Windows 7 SP1. We are running SCCM 2007 R2 in mixed mode but are not going to R3, a new 2012 site is being built. Our SCCM admins say they think it is still WMI related.Īll other computers at our site are working fine. Most ended up being a problem on the MP not having a FQDN back to the main server, but it is not the case here. I've tried everything I could in about the first 10 links or so on this issue on google. The first computer I saw this issue on was getting patched but not reporting it so I uninstalled and reinstalled the client and it started doing this (see logs below names of servers, sites and domains changed of course). ![]() WMI repairs were done as well as renaming and recreating the repository.Īlso worth noting there are only 2 actions in SCCM, Machine Policy and User Policy and only 10 log files so it can’t get policies. On all of the computers I’ve done uninstall and reinstall of the client. Most of the things I’ve googled with similar errors point to a problem with the PC communicating with the management point, or certificate issue. I’ve spent several hours looking at this myself and have had nothing that seems to resolve it. Microsoft 365, Office 2019, or Office 2016 (Follow the steps to select a specific bit version, such as 64-bit if that's the version you need.)įor overall guidance about which version to install, see Choose the 32-bit or 64-bit version of Office.I’ve found this month about 5 or 6 computers that weren’t getting patched but have since found another computer which isn’t in SCCM that is having this issue. ![]() Select your version below and follow the installation steps. Install the 32-bit or 64-bit version of Office Go to Uninstall Office from a PC and follow the steps to uninstall the version of Office (or stand-alone Office application, such as Visio or Project) you don't want. To fix this error and switch from 32-bit to 64-bit (or vice-versa), you must do the following in this order. This occurs because you can't mix 64-bit and 32-bit versions of Office. If you tried to install a 64-bit or 32-bit version of the Office suite, or a standalone application such as Visio on a computer that already has either the 32-bit or 64-bit version of Office, you could see an error message similar to the one below. ![]()
0 Comments
Leave a Reply. |