Help with smspxe.log, please

[boyjaew2]

I have been running SCCM 2012 since beta with SQL 2008 Standard. I recently upgraded to SCCM 2012 RTM and everything still worked, but then I upgraded to SQL 200 R2 SP1 + CU6 (three days ago) and can't quite tell if it's working well or not.

 

Yesterday I experienced the symptom of loosing the ability to PXE- boot clients to receive an image. I googled around and searched the forum a bit, but found the usual solutions, all of which I had seen before and as it has been working great until the SQL upgrade didn't think they were applicable.

 

I also had a few errors in the component status view which I hadn't seen before, but looking at it this morning everything seems "normal" again.

 

I did have a look at the smspxe.log, but even after about a year of working with SCCM I am still clearly a noob.

 

So, I'm going to attach the entire log as text if someone would be so kind as to look at it and see if anything seems strange. Also, if there is a good resource that someone could provide that might help explain what I'm looking at in this particular log file it would be greatly appreciated.

 

The only thing I see that is a glaring error is this:

 

 

RequestMPKeyInformation: Send() failed. SMSPXE 9/4/2012 6:04:51 PM 2976 (0x0BA0)

Failed to get information for MP: http://MYSCCMSITE.domain.com 80004005. SMSPXE 9/4/2012 6:04:51 PM 2976 (0x0BA0)

PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 9/4/2012 6:04:51 PM 2976 (0x0BA0)

PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 9/4/2012 6:04:51 PM 2976 (0x0BA0)

PXE Provider failed to initialize database connection.

Unspecified error (Error: 80004005; Source: Windows) SMSPXE 9/4/2012 6:04:51 PM 2976 (0x0BA0)

 

But this only happened yesterday and not today when I looked at it again. I'm going to try and PXE-boot again right now as my original intent was to troubleshoot the component errors which are mysteriously gone today.

 

Thanks in advance for any help.

smsPXElog.txt

[boyjaew2]

SMSPXE.log - This is new this morning:

 

 

Begin validation of Certificate [Thumbprint 76A1F747FFA33163E7DB0DEC217D11D17DDE96C6] issued to '{A36E2639-05CC-4D5E-A4B4-4CEECA42C58A}' SMSPXE 9/5/2012 8:05:08 AM 5316 (0x14C4)

Completed validation of Certificate [Thumbprint 76A1F747FFA33163E7DB0DEC217D11D17DDE96C6] issued to '{A36E2639-05CC-4D5E-A4B4-4CEECA42C58A}' SMSPXE 9/5/2012 8:05:08 AM 5316 (0x14C4)

PXE::CNotifyTimer::Init SMSPXE 9/5/2012 8:05:08 AM 5316 (0x14C4)

PXE::CNotifyTimer::CancelTimer SMSPXE 9/5/2012 8:05:08 AM 5316 (0x14C4)

PXE::CNotifyTimer::RegisterTimeout SMSPXE 9/5/2012 8:05:08 AM 5316 (0x14C4)

PXE::CNotifyTimer::TimerSignalFunc SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C)

PXE::CNotifyTimer::ProcessTimer SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C)

PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C)

PXE::CBootImageManager::PurgeOldImages SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C)

PXE::CNotifyTimer::Init SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C)

PXE::CNotifyTimer::CancelTimer SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C)

PXE::CNotifyTimer::RegisterTimeout SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C)

Set media certificate in transport SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8)

Set authenticator in transport SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8)

Set authenticator in transport SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8)

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8)

Getting boot action for unknown machine: item key: 2046820352 SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8)

Set media certificate in transport SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8)

Set authenticator in transport SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8)

Set authenticator in transport SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8)

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>

SMSPXE 9/5/2012 8:15:47 AM 3272 (0x0CC8)

Client Identity: {A36E2639-05CC-4D5E-A4B4-4CEECA42C58A} SMSPXE 9/5/2012 8:15:47 AM 3272 (0x0CC8)

Set media certificate in transport SMSPXE 9/5/2012 8:15:47 AM 3272 (0x0CC8)

Set authenticator in transport SMSPXE 9/5/2012 8:15:47 AM 3272 (0x0CC8)

Set authenticator in transport SMSPXE 9/5/2012 8:15:47 AM 3272 (0x0CC8)

 

2046820352 - This is the "x86 Unknown Computer" that is located in the Devices group by default, but is also in my End Users device group. What is going on? Is this supposed to do this?

[anyweb]

i hope you didnt upgrade from BETA 2 to the RTM release and what you really mean is you did a clean install of Configuration Manager 2012 RTM,

on your site server are your component status logs healthy especially for your management point ?

 

anyhow, have you checked that your boot images have the option enabled on them to be deployed on a PXE server, check the data source tab for that on the boot images.

[boyjaew2]

Oh, man. I upgraded from the last release candidate version to RTM.

 

I do have "Deploy this boot image from the PXE service point" box checked - Info from properties on Boot image (x64)

 

Strangely, today I just PXE-booted successfully. The only thing that I did last night was remove all clients from my Image Deployment device group. I don't really see how that would change anything though.

 

I am concerned now about your upgrade comment. Should I just start over and do a clean install of SCCM 2012? Everything looks healthy. As I mentioned, Component status view gives me green across the board, but I guess it could be inaccurate.

[anyweb]

upgrade from Release Candidate was not supported and there are many changes in the database that can only be created at install time so sooner or later you may hit an issue related to the 'upgrade' that will not be supported by Microsoft as it's not supported to upgrade from release candidate to RTM (sorry to repeat it but the message needs to be said).

 

back up what you have, export everything you can think of, and start again, that's my advice. Is it a big environment ?

[boyjaew2]

Not a big environment - about 500 clients.

 

Well, that is a bummer.

 

I guess the thing that worries me the most is how the current SQL stuff is going to react if I do a clean install of SCCM 2012. I am even more ignorant concerning SQL. Any advice other than what you have already stated concerning the clean install?

 

I plan on using the exact same settings as I did when I first installed SCCM 2012.

[boyjaew2]

Ok, how about this? Can you tell me whether I should clean install SCCM and then upgrade SQL or upgrade SQL then install SCCM?

[Oneone]

Install everything first, side-by-side . And then move all the objects you need to the new clean installation.

 

edit, what do you mean by upgrading sql? u need to install CU 6 to be able to install the SCCM databse on the SQL server.

[boyjaew2]

Install everything first, side-by-side . And then move all the objects you need to the new clean installation.

 

edit, what do you mean by upgrading sql? u need to install CU 6 to be able to install the SCCM databse on the SQL server.

 

I've been running SQL 2008 Standard since SCCM 2012 RC1, and installing each new iteration of CM on top of it, but as you can guess it started to get a bit quirky, mostly with Reporting. So, I'm actually thinking of clean installing both. Upgrading from SQL standard to standard R2 SP2 should suffice I think unless it doesn't include CU6, I guess. The reason I want to do both clean installs is the SQL upgrade I did before worked, but it wasn't very fun to do.

 

Since my last post I have reverted back to a snap shot (vmware) that I took before I upgraded SQL (which was after I upgraded CM to RTM) and things are a bit strange. In the CM console it's telling me it is RC v.5.0.7703.0, but when I look at the attributes of SMS-MP-CCM-SERVER.MYDOMAIN.COM in AD, on the mSSMSCapabilities attribute it has Version 5.00.7711.0000.

 

So, I'm not really sure what's going on. I'd rather not rebuild everything, but I can't be sure things are working correctly.

 

On a side note, if upgrade from RC2 to RTM is not supported, WHY is there an upgrade option when you run the install for the RTM version? I don't mean that in a smart-assy way. I would just really like to know.

 

Thanks for the input.