What's new
Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED SMSPXE.LOG Rebuild on Distribution Point

  • Thread starter Thread starter KyleASimpz
  • Start date Start date
  • Replies Replies 8
  • Views Views 11K
Status
Not open for further replies.
KyleASimpz

KyleASimpz

Well-Known Member
Messages
52
Reaction score
0
Points
6
Hi,

I noticed that the smspxe.log stopped gathering information. How do I rebuild the log file to get it working?
 
Sort by date Sort by votes
The DP will rebuild the log file if required. You may also see additional log files with date stamp. Why do you want to rebuild that log file ?.
 
Upvote 0 Downvote
Prajwal Desai said:
The DP will rebuild the log file if required. You may also see additional log files with date stamp. Why do you want to rebuild that log file ?.
Click to expand...
I see two different locations for the SMSPXE log file. Also the log file hasn't had an updated since beginning of August in one location and 2018 in another location,
 
Upvote 0 Downvote
Hi Prajwal,

So renaming the log file didn't do a thing. I also removed the DP role, rebooted, and set back up the DP role but still the log file didn't rebuild. I see some other log files stuck back to August date as well.
 
Upvote 0 Downvote
Prajwal Desai said:
So when you PXE boot any device, is that log file not updating ?. Is that what you are saying ?.
Click to expand...
Hi Prajwal,

That is correct the SMSPXE.log doesn't update at all anymore since August.

Even after removing the DP and setting it backup, it won't rebuild the smspxe.log file
 
Last edited:
Upvote 0 Downvote
Hey, did you ever figure this out? I have the same issue right now. The last log entry I have is from January 2020 on my primary site server. I think PXE is still working, but it isn't logging anything, and we have a couple of computers that are no PXE booting, but others will. My assumption here is that the tech is using a network dongle that has been previously associated with another computer, and I can usually from this log phish out the mac address of the dongle and add it to the hierarchy as a duplicate hardware id.

Actually my log blew chow back in June of 2019 by the looks of it, here is the last bit of my log.
6/4/2019 9:28:22 AM ================= PXE Provider shutdown. ===================== SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM Failed to shutdown IO completion port. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM PXE provided failed to shutdown worker threads. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM PXE::CPolicyProvider::ShutdownWorkerThreads failed; 0x80070057 SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM Failed to shutdown worker threads. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM PXE Provider failed to perform a clean shutdown. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM Prioritizing local MP SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM Not in SSL SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM RequestMPKeyInformation: Send() failed. SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM Unsuccessful in getting MP key information. 80004005. SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM PXE::CPolicyProvider::Shutdown failed; 0x80070057 SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM Failed to shutdown PXE provider. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 5728 (0x1660)
6/17/2019 11:31:08 AM Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 6812 (0x1A9C)
6/17/2019 11:31:09 AM MAC Ignore List Filename in registry is empty SMSPXE 6812 (0x1A9C)
6/17/2019 11:32:31 AM ================= PXE Provider shutdown. ===================== SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM Failed to shutdown IO completion port. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM PXE provided failed to shutdown worker threads. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM PXE::CPolicyProvider::ShutdownWorkerThreads failed; 0x80070057 SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM Failed to shutdown worker threads. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM PXE Provider failed to perform a clean shutdown. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM Prioritizing local MP . SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM Not in SSL SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM RequestMPKeyInformation: Send() failed. SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM Unsuccessful in getting MP key information. 80004005. SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM PXE::CPolicyProvider::Shutdown failed; 0x80070057 SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM Failed to shutdown PXE provider. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 6292 (0x1894)
1/18/2020 11:55:13 PM Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 35592 (0x8B08)
1/18/2020 11:55:13 PM MAC Ignore List Filename in registry is empty SMSPXE 35592 (0x8B08)
1/18/2020 11:58:14 PM ================= PXE Provider shutdown. ===================== SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM Failed to shutdown IO completion port. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM PXE provided failed to shutdown worker threads. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM PXE::CPolicyProvider::ShutdownWorkerThreads failed; 0x80070057 SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM Failed to shutdown worker threads. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM PXE Provider failed to perform a clean shutdown. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM Prioritizing local MP. SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM Not in SSL. SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM RequestMPKeyInformation: Send() failed. SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM Unsuccessful in getting MP key information. 80004005. SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM PXE::CPolicyProvider::Shutdown failed; 0x80070057 SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM Failed to shutdown PXE provider. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 37360 (0x91F0)
 
Last edited:
Upvote 0 Downvote
MorganJ said:
Hey, did you ever figure this out? I have the same issue right now. The last log entry I have is from January 2020 on my primary site server. I think PXE is still working, but it isn't logging anything, and we have a couple of computers that are no PXE booting, but others will. My assumption here is that the tech is using a network dongle that has been previously associated with another computer, and I can usually from this log phish out the mac address of the dongle and add it to the hierarchy as a duplicate hardware id.

Actually my log blew chow back in June of 2019 by the looks of it, here is the last bit of my log.
6/4/2019 9:28:22 AM ================= PXE Provider shutdown. ===================== SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM Failed to shutdown IO completion port. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM PXE provided failed to shutdown worker threads. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM PXE::CPolicyProvider::ShutdownWorkerThreads failed; 0x80070057 SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM Failed to shutdown worker threads. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM PXE Provider failed to perform a clean shutdown. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM Prioritizing local MP SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM Not in SSL SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM RequestMPKeyInformation: Send() failed. SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM Unsuccessful in getting MP key information. 80004005. SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM PXE::CPolicyProvider::Shutdown failed; 0x80070057 SMSPXE 5728 (0x1660)
6/4/2019 9:28:22 AM Failed to shutdown PXE provider. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 5728 (0x1660)
6/17/2019 11:31:08 AM Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 6812 (0x1A9C)
6/17/2019 11:31:09 AM MAC Ignore List Filename in registry is empty SMSPXE 6812 (0x1A9C)
6/17/2019 11:32:31 AM ================= PXE Provider shutdown. ===================== SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM Failed to shutdown IO completion port. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM PXE provided failed to shutdown worker threads. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM PXE::CPolicyProvider::ShutdownWorkerThreads failed; 0x80070057 SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM Failed to shutdown worker threads. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM PXE Provider failed to perform a clean shutdown. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM Prioritizing local MP . SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM Not in SSL SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM RequestMPKeyInformation: Send() failed. SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM Unsuccessful in getting MP key information. 80004005. SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM PXE::CPolicyProvider::Shutdown failed; 0x80070057 SMSPXE 6292 (0x1894)
6/17/2019 11:32:31 AM Failed to shutdown PXE provider. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 6292 (0x1894)
1/18/2020 11:55:13 PM Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 35592 (0x8B08)
1/18/2020 11:55:13 PM MAC Ignore List Filename in registry is empty SMSPXE 35592 (0x8B08)
1/18/2020 11:58:14 PM ================= PXE Provider shutdown. ===================== SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM Failed to shutdown IO completion port. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM PXE provided failed to shutdown worker threads. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM PXE::CPolicyProvider::ShutdownWorkerThreads failed; 0x80070057 SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM Failed to shutdown worker threads. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM PXE Provider failed to perform a clean shutdown. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM Prioritizing local MP. SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM Not in SSL. SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM RequestMPKeyInformation: Send() failed. SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM Unsuccessful in getting MP key information. 80004005. SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM PXE::CPolicyProvider::Shutdown failed; 0x80070057 SMSPXE 37360 (0x91F0)
1/18/2020 11:58:14 PM Failed to shutdown PXE provider. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) SMSPXE 37360 (0x91F0)
Click to expand...
I had to remove the secondary site and rebuild on a new drive but turned it into a DP instead which is working now.
 
Upvote 1 Downvote
Status
Not open for further replies.

Similar threads

  • SOLVED Not able to use Powershell to create Packages based on folder names
  • PENDING PXE deployment issue WDS encountered an error: 0x102
  • PENDING Issues with OSD in secondary MCM 2509 site
  • PENDING Distribution Point transfer problems
  • PENDING Problems after upgrading to CM2509

    • Forum statistics

    Threads
    7,185
    Messages
    28,035
    Members
    18,323
    Latest member
    daxxi

    Latest posts

    Trending content
    Back
    Top