I have 4 servers where we Sent our Image (Boot Image X86) ... If I check the Package Status it says "Installed"... but it won't work... We installed it September last year but until now i'm having the opportunity to test it... If I go to the logs I noticed that there are four logs that had a lot of errors in those days: (Seems there was an SQL issue), but I need some advise... because it says Image is installed but it doesn't work and logs from those days have errors. MP_Hinv Hinv Retry: ******************* Start of Task ********************* MP_HinvEndpoint 1/22/2010 4:07:35 PM 6068 (0x17B4) CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005 MP_HinvEndpoint 1/22/2010 4:07:35 PM 6068 (0x17B4) ======================================= MP_HinvEndpoint 1/22/2010 4:07:35 PM 6068 (0x17B4) MPDB ERROR - CONNECTION PARAMETERS SQL Server Name : GRUMASCCM SQL Database Name : SMS_G00 Integrated Auth : True MPDB ERROR - EXTENDED INFORMATION MPDB Method : Init() MPDB Method HRESULT : 0x80004005 Error Description : null OLEDB IID : null ProgID : null MPDB ERROR - INFORMATION FROM DRIVER null MP_HinvEndpoint 1/22/2010 4:07:35 PM 6068 (0x17B4) ======================================= MP_HinvEndpoint 1/22/2010 4:07:35 PM 6068 (0x17B4) Hinv: IMPDBConnection::Init() for class failed. MP_HinvEndpoint 1/22/2010 4:07:35 PM 6068 (0x17B4) Hinv: Error loading Inventory Mapping Table from the SQL data base! MP_HinvEndpoint 1/22/2010 4:07:35 PM 6068 (0x17B4) Raising event: [SMS_CodePage(437), SMS_LocaleID(1033)] instance of MpEvent_CannotLoadHinvMap { ClientID = "GUID:17290A3A-5C45-4FAE-ABE4-4F1C9F66AFD0"; DateTime = "20100123000735.670000+000"; MachineName = "MEXICALI00"; ProcessID = 4380; ProcessingType = "Hardware inventory"; SiteCode = "G18"; ThreadID = 6068; Win32ErrorCode = 0; }; MP_HinvEndpoint 1/22/2010 4:07:35 PM 6068 (0x17B4) Hinv Task: Translate report attachment to file "Default.HTMP" returned 80004005 MP_HinvEndpoint 1/22/2010 4:07:35 PM 6068 (0x17B4) Hinv Retry: ******************* End of Task ********************* MP_HinvEndpoint 1/22/2010 4:07:35 PM 6068 (0x17B4) Inv-Hinv: calling SetComplete with with CCM_SETCOMPLETE_ABORT_REDELIVER MP_HinvEndpoint 1/22/2010 4:07:35 PM 6068 (0x17B4) Inv-Hinv: task not completed (flag=8) due to error 80004005 MP_HinvEndpoint 1/22/2010 4:07:35 PM 6068 (0x17B4) ClientAuth Error verifying message from client 'GUID:51042637-F718-4671-9EAF-CA46BE82C5CA' (0x80040241). ClientAuth 9/28/2010 9:32:14 PM 588 (0x024C) Error verifying message from client 'GUID:F433FAE5-E7C1-4138-8406-D67929048BC2' (0x80040241). ClientAuth 9/28/2010 9:32:23 PM 588 (0x024C) Error verifying message from client 'GUID:0457B68D-67AA-442C-A5F7-B187F7E0E3D7' (0x80040241). ClientAuth 9/28/2010 9:32:53 PM 588 (0x024C) Error verifying message from client 'GUID:51042637-F718-4671-9EAF-CA46BE82C5CA' (0x80040241). ClientAuth 9/28/2010 9:33:14 PM 588 (0x024C) Error verifying message from client 'GUID:F433FAE5-E7C1-4138-8406-D67929048BC2' (0x80040241). ClientAuth 9/28/2010 9:33:23 PM 588 (0x024C) Error verifying message from client 'GUID:0457B68D-67AA-442C-A5F7-B187F7E0E3D7' (0x80040241). ClientAuth 9/28/2010 9:33:53 PM 588 (0x024C) Error verifying message from client 'GUID:51042637-F718-4671-9EAF-CA46BE82C5CA' (0x80040241). ClientAuth 9/28/2010 9:34:14 PM 8964 (0x2304) Error verifying message from client 'GUID:F433FAE5-E7C1-4138-8406-D67929048BC2' (0x80040241). ClientAuth 9/28/2010 9:34:23 PM 8964 (0x2304) Error verifying message from client 'GUID:0457B68D-67AA-442C-A5F7-B187F7E0E3D7' (0x80040241). ClientAuth 9/28/2010 9:34:53 PM 8964 (0x2304) Error verifying message from client 'GUID:51042637-F718-4671-9EAF-CA46BE82C5CA' (0x80040241). ClientAuth 9/28/2010 9:35:14 PM 8964 (0x2304) Error verifying message from client 'GUID:F433FAE5-E7C1-4138-8406-D67929048BC2' (0x80040241). ClientAuth 9/28/2010 9:35:23 PM 8964 (0x2304) Error verifying message from client 'GUID:0457B68D-67AA-442C-A5F7-B187F7E0E3D7' (0x80040241). ClientAuth 9/28/2010 9:35:53 PM 8964 (0x2304) Error verifying message from client 'GUID:51042637-F718-4671-9EAF-CA46BE82C5CA' (0x80040241). ClientAuth 9/28/2010 9:36:14 PM 8964 (0x2304) MP_GetPolicy CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80040E4D MP_GetPolicy_ISAPI 9/29/2010 5:02:26 AM 6344 (0x18C8) ======================================= MP_GetPolicy_ISAPI 9/29/2010 5:02:26 AM 6344 (0x18C8) MPDB ERROR - CONNECTION PARAMETERS SQL Server Name : GRUMASCCM SQL Database Name : SMS_G00 Integrated Auth : True MPDB ERROR - EXTENDED INFORMATION MPDB Method : Init() MPDB Method HRESULT : 0x80040E4D Error Description : Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. OLEDB IID : {0C733A8B-2A1C-11CE-ADE5-00AA0044773D} ProgID : Microsoft OLE DB Provider for SQL Server MPDB ERROR - INFORMATION FROM DRIVER SQL Server Name : GRUMASCCM Native Error no. : 18456 Error State : 1 Class (Severity) : 14 Line number in SP : 1 MP_GetPolicy_ISAPI 9/29/2010 5:02:26 AM 6344 (0x18C8) ======================================= MP_GetPolicy_ISAPI 9/29/2010 5:02:26 AM 6344 (0x18C8) CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005 MP_GetPolicy_ISAPI 9/29/2010 5:03:03 AM 6344 (0x18C8) ======================================= MP_GetPolicy_ISAPI 9/29/2010 5:03:03 AM 6344 (0x18C8) MPDB ERROR - CONNECTION PARAMETERS SQL Server Name : GRUMASCCM SQL Database Name : SMS_G00 Integrated Auth : True MPDB ERROR - EXTENDED INFORMATION MPDB Method : Init() MPDB Method HRESULT : 0x80004005 Error Description : null OLEDB IID : null ProgID : null MPDB ERROR - INFORMATION FROM DRIVER null MP_GetPolicy_ISAPI 9/29/2010 5:03:03 AM 6344 (0x18C8) ======================================= MP_GetPolicy_ISAPI 9/29/2010 5:03:03 AM 6344 (0x18C8) CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005 MP_GetPolicy_ISAPI 9/29/2010 5:03:20 AM 1212 (0x04BC) ======================================= MP_GetPolicy_ISAPI 9/29/2010 5:03:20 AM 1212 (0x04BC) MP_Framework CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005 MpFramework 9/29/2010 5:35:13 AM 9180 (0x23DC) ======================================= MpFramework 9/29/2010 5:35:13 AM 9180 (0x23DC) MPDB ERROR - CONNECTION PARAMETERS SQL Server Name : GRUMASCCM SQL Database Name : SMS_G00 Integrated Auth : True MPDB ERROR - EXTENDED INFORMATION MPDB Method : Init() MPDB Method HRESULT : 0x80004005 Error Description : null OLEDB IID : null ProgID : null MPDB ERROR - INFORMATION FROM DRIVER null MpFramework 9/29/2010 5:35:13 AM 9180 (0x23DC) ======================================= MpFramework 9/29/2010 5:35:13 AM 9180 (0x23DC) CMpDatabase::GetClientPublicKeyEx(ClientID='GUID:0457B68D-67AA-442C-A5F7-B187F7E0E3D7') failed (0x80040241). MpFramework 9/29/2010 5:35:13 AM 9180 (0x23DC) CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005 MpFramework 9/29/2010 5:35:33 AM 9180 (0x23DC) ======================================= MpFramework 9/29/2010 5:35:33 AM 9180 (0x23DC) MPDB ERROR - CONNECTION PARAMETERS SQL Server Name : GRUMASCCM SQL Database Name : SMS_G00 Integrated Auth : True MPDB ERROR - EXTENDED INFORMATION MPDB Method : Init() MPDB Method HRESULT : 0x80004005 Error Description : null OLEDB IID : null ProgID : null MPDB ERROR - INFORMATION FROM DRIVER null MpFramework 9/29/2010 5:35:33 AM 9180 (0x23DC) ======================================= MpFramework 9/29/2010 5:35:33 AM 9180 (0x23DC) CMpDatabase::GetClientPublicKeyEx(ClientID='GUID:51042637-F718-4671-9EAF-CA46BE82C5CA') failed (0x80040241). MpFramework 9/29/2010 5:35:33 AM 9180 (0x23DC) CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005 MpFramework 9/29/2010 5:35:44 AM 9180 (0x23DC) ======================================= MpFramework 9/29/2010 5:35:44 AM 9180 (0x23DC) MPDB ERROR - CONNECTION PARAMETERS SQL Server Name : GRUMASCCM SQL Database Name : SMS_G00 Integrated Auth : True MPDB ERROR - EXTENDED INFORMATION MPDB Method : Init() MPDB Method HRESULT : 0x80004005 Error Description : null OLEDB IID : null ProgID : null MPDB ERROR - INFORMATION FROM DRIVER null MpFramework 9/29/2010 5:35:44 AM 9180 (0x23DC)

Do you also have a distribution point set up for that boot image? another thing to check is the site boundaries. You want to make sure the IP address of the client trying to access a given server is included in the IP range for that server. If you have VLANs setup, you may need to have the client and the server on the same VLAN unless you have an IP helper set up to pass traffic across the VLANs.

Isn't that the same problem as described in: http://social.technet.microsoft.com/Forums/en-US/configmgrsdk/thread/74f439bf-9934-4f32-8a31-ac972225d641/#d08ec368-5440-4fd6-bc32-878000fcdf45Torsten Meringer | http://www.mssccmfaq.de

Hello Torsten... No, it is not the same problem... The one from the Management Point is a recent problem and it just stopped working This one, the Management Point is working and we can send packages, but the Boot Image Package doesnt work... We sent PXE service and Image on September 2010... And the package showes it was installed but does not work and logs have information that I showed you up above.

Have you verfied your drivers that you require are loaded into the boot image? To check, right click on the boot image in the console and choose properties. Click the WindowsPE tab and check the drivers box to make sure you have your drivers in there, including the appropriate network and storage drivers most of all What machine are you trying to load this on (IE Dell Optiplex 745 or whatever)? Anything worth doing is worth doing right.

I dont think it's drivers since we use the same Image in all servers and it's working in the others. There are just four of them which are not working. The machines are HP...

The models are all exactly the same?Anything worth doing is worth doing right.

Ok, I feel really sorry but since this was a partner's issue that I want to help him with... Actually the images was never installed (in the first post of this topic I said the image was installed but did not work)... well the real thing is that in our Secondary Sites with the issue the images got stuck in "Install Pending" (even though we are able to send other packages but the image)... What are the logs I should check today that we send the image again?

Ok, I checked the logs and I found that distmgr.log shows following constantly, so that could be reason why my image is not installing in some servers (G00000E0 is my image pckg name). Package G00000E0 requires a newer version (1) of source files and the new compressed files haven't arrived yet, current version is 0, skip e:\sccm\inboxes\distmgr.box\INCOMING\7A6NTQ5Q.PKG SMS_DISTRIBUTION_MANAGER 4/28/2011 10:30:24 AM 7088 (0x1BB0)

Did you try refreshing the distribution point? That'll re-copy the files into the distribution point and give it a new version number.

Did you try refreshing the distribution point? That'll re-copy the files into the distribution point and give it a new version number. "Updating" a package will increase the version number, not "refresh": http://technet.microsoft.com/en-us/library/bb892806.aspxTorsten Meringer | http://www.mssccmfaq.de

Is it possible to update the image package but only for ONE of our Secondary Sites (Distribution Points)... because we have the image working for most of them.. There are just 4 which have this issue... Problem with updating the package (which actual version is 1), is that we're talking about a complete image of more than 4GB and it'll affect all of our Network and all of our Secondary Sites, that'll be really difficult and bring some problems... Is there a way to update only for specific packages or what would you recommend?.

Did you try refreshing the distribution point? That'll re-copy the files into the distribution point and give it a new version number. "Updating" a package will increase the version number, not "refresh": http://technet.microsoft.com/en-us/library/bb892806.aspx Torsten Meringer | http://www.mssccmfaq.de I stand corrected, thanks for the link. I didn't realize the differences.

Is it possible to update the image package but only for ONE of our Secondary Sites (Distribution Points)... because we have the image working for most of them.. There are just 4 which have this issue... Problem with updating the package (which actual version is 1), is that we're talking about a complete image of more than 4GB and it'll affect all of our Network and all of our Secondary Sites, that'll be really difficult and bring some problems... Is there a way to update only for specific packages or what would you recommend?. Looks like you can refresh a specific distribution point but if you try using update, it will affect all distribution points. You could try using refresh first and see if that works. If not, then maybe you can do this during off-peak hours?

Thanks but at this time it's hard for us to update the version package since its a really heavy sized! I think I'll take that as an answer... We're gonna get ready a new Image with some updates we've made... Then we're gonna send it... After that I'll check if it can be installed on those secondary sites. In case it's not I'll come back with you guys. Thanks!