Search the Community

Having an issue with my single primary site/Management point, case is currently opened with Microsoft. It starts like this... Recently I noticed clients have not been reporting in to the site. This include hardware, software inventories, etc. BITS crashed my console and threw errors, the documented fix was to uninstall BITS, reboot and re-install on the server- done. Then noticed ALL SQL logins have been removed with the exception of a SMSremoteusers read only account!! Microsoft suggested re installing db. - done. A side note is we have a SCCM 2012 VM Test environment - segregated from our production environment by VLAN and ACOLS. Test environment has own DC, etc. But I don't see any type of interference. Hope someone can help! PROD Server SQL 2008 IIS 7 SCCM R3 Management Point Reporting Point Distribution Point Deployment Service Windows Server Standard SP2 64bit - Physicial Box 8GB RAM 2 Processors 2.66GHz MPcontrol.log Successfully performed Management Point availability check against local computer. SMS_MP_CONTROL_MANAGER 11/3/2012 10:27:20 AM 5288 (0x14A8) Call to HttpSendRequestSync failed for port 80 with status code 404, text: Not Found SMS_MP_CONTROL_MANAGER 11/3/2012 10:32:20 AM 5288 (0x14A8) Http test request failed, status code is 404, 'Not Found'. SMS_MP_CONTROL_MANAGER 11/3/2012 10:32:20 AM 5288 (0x14A8) MP_Status.log Mp Status: processing event: SMS_PolicyAgent_BitsPolicyDownloadFailed, for machine: machinename MP_StatusManager 11/3/2012 11:02:04 AM 9492 (0x2514) MP Status: SVF file written successfully to "E:\Program Files (x86)\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs\KQODD45Q.SVF" MP_StatusManager 11/3/2012 11:02:04 AM 9492 (0x2514) MP_Policy.log CPolicyManagerHandler::HandleMessage(): SetComplete(DISCARD) called. MP_PolicyManager 11/2/2012 9:56:52 PM 8592 (0x2190) CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005 MP_PolicyManager 11/2/2012 9:56:54 PM 8592 (0x2190) ======================================= MP_PolicyManager 11/2/2012 9:56:54 PM 8592 (0x2190) MPDB ERROR - CONNECTION PARAMETERS SQL Server Name : SERVER SQL Database Name : SMS NAME Integrated Auth : True MPDB ERROR - EXTENDED INFORMATION MPDB Method : Init() MPDB Method HRESULT : 0x80004005 Error Description : Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Server is in single user mode. Only one administrator can connect at this time. OLEDB IID : {} ProgID : Microsoft OLE DB Provider for SQL Server MPDB ERROR - INFORMATION FROM DRIVER SQL Server Name : SERVER Native Error no. : 18461 Error State : 1 Class (Severity) : 14 Line number in SP : 1 MP_PolicyManager 11/2/2012 9:56:54 PM 8592 (0x2190) ======================================= MP_PolicyManager 11/2/2012 9:56:54 PM 8592 (0x2190) MP_Location.log MPDB ERROR - CONNECTION PARAMETERS SQL Server Name : SERVER SQL Database Name : SMS Integrated Auth : True MPDB ERROR - EXTENDED INFORMATION MPDB Method : Init() MPDB Method HRESULT : 0x80004005 Error Description : Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Server is in single user mode. Only one administrator can connect at this time. OLEDB IID : {} ProgID : Microsoft OLE DB Provider for SQL Server MPDB ERROR - INFORMATION FROM DRIVER SQL Server Name : SERVER Native Error no. : 18461 Error State : 1 Class (Severity) : 14 Line number in SP : 1 MP_LocationManager 11/2/2012 9:56:53 PM 8592 (0x2190) ======================================= MP_LocationManager 11/2/2012 9:56:53 PM 8592 (0x2190) CHandleLocationRequest::CreateReply failed with error (80004005). MP_LocationManager 11/2/2012 9:56:53 PM 8592 (0x2190) MP LM: Message discarded MP_LocationManager 11/2/2012 9:56:53 PM 8592 (0x2190) CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005 MP_LocationManager 11/2/2012 9:56:53 PM 8592 (0x2190) ======================================= MP_LocationManager 11/2/2012 9:56:53 PM 8592 (0x2190) IIS W3SVC1/uex121103.log 2012-11-03 16:16:18 10.x.xx.x CCM_POST /ccm_system/request - 80 - 10.x.xx.xxx ccmhttp 200 0 0 3 2012-11-03 16:16:18 10.x.xx.xx BITS_POST /CCM_Incoming/{9F78C7C0-35E7-40F8-9A07-5EF9A8767F31} (bits_error:,501,0x80070005) 80 - xx.xx.xx.xxx Microsoft+BITS/7.5 501 0 0 3 2012-11-03 16:16:18 10.x.xx.xx BITS_POST /CCM_Incoming/{22206B66-F87F-45DE-B174-CD3DC447E3CD} (bits_error:,501,0x80070005) 80 - 10.1.xx.xxx Microsoft+BITS/6.7 501 0 0 1 2012-11-03 16:16:18 10.x.xx.xx HEAD /SMS_MP/.sms_pol {45b5690e-6732-4c9e-8930-85dd3fdd85c0}.14_00 80 - 10.x.xx.xx Microsoft+BITS/7.5 404 0 2 208 2012-11-03 16:16:18 10.x.xx.xx CCM_POST /ccm_system/request - 80 - 10.x.xx.xx ccmhttp 200 0 0 3

Hi All, I want to use powermanagement. I have installed SCCM R3. When I right click on the site and go to properties, it shows: R3 Installed: Yes Build number: 6487 When I click help -> About System Center Configuration Manager the version number is Version: 4.00.6487.2000 I have reporting services installed also. I have an SCCM server and a reporting server with MS SQL Server 2008 R2 installed. I believe I have followed all of the instructions to enable power management from this page: http://blogs.technet.com/b/ptsblog/archive/2011/03/08/configure-power-management-with-sccm-2007-r3.aspx However the following issues occur: When I right click on a computer and run resource explorer I see Power Capabilities and Power Settings, but I do not see Power Management Day or Power Management Month. If I run the powervwr.exe on the machine (or connect to it remotely) I see data in Power Config and Power Events but I do net see any graph under Day Activity. When I run power reports they show as having "no data". I have a test machine where I completly removed and reinstalled the SCCM client, then re applied the R3 client hotfix. When I launch Configuration manager from control panel, and look under components I see: ConfigMgr Power Management Agent version: 4.0.6487.2157, but the issue is still occuring. The strange thing is the production servers which don't have the R3 client patch installed are reporting daily and monthly power activity, show the graphs and the correct entries in resource explorer. Old clients also reported this data correctly up until they where patched. As I understand it, it shouldn't work at all until it is patched ? I have checked the following: Power management options are set in SMS_def.mof Power management client agent is enabled Hardware inventory client agent is enabled and scheduled to run The test collection that the test client belongs to has power management enabled I have installed hotfix KB977384 and KB2536089 on the server I have rebooted both servers In the server inventory records, we can see the following entries: Pragma delete found in inventory group MICROSOFT|POWER_MANAGEMENT_ACT_DAY|1.0. Deleting group... SMS_INVENTORY_DATA_LOADER 8/15/2012 10:37:23 PM 9168 (0x23D0) Pragma delete found in inventory group MICROSOFT|POWER_MANAGEMENT_ACT_DAY|1.0. Deleting group... SMS_INVENTORY_DATA_LOADER 8/15/2012 10:37:23 PM 9168 (0x23D0) Pragma delete found in inventory group MICROSOFT|POWER_MANAGEMENT_ACT_DAY|1.0. Deleting group... SMS_INVENTORY_DATA_LOADER 8/15/2012 10:37:23 PM 9168 (0x23D0) Begin transaction: Machine=SRVDDV044(GUID:E8775B85-0DAE-429B-A7F5-EA3431051759) SMS_INVENTORY_DATA_LOADER 8/15/2012 10:37:23 PM 9168 (0x23D0) I also tried re-downloading the SCCM R3 client patch from microsoft, completly removed the client from my test machine and re-installed it, then installed the R3 client patch but still the same result. Microsoft are recommending that I delete and re-create the SCCM database indexes. Can anyone help ?