Error Id 16389.pxe
Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. We use cookies to let you log in, for ads and for analytics. OK PXE ERROR - 16389 - WDS start with error Started by VFJ , Jan 18 2012 07:44 PM Please log in to reply 2 replies to this topic #1 VFJ VFJ Newbie Established Members 2 posts Posted 18 January 2012 - 07:44 PM Hi, My name is Victor. I'm from Brazil and I have a SCCM 2007 R3 instaled. I alread saw at other topic that many people have problem with OSD and PXE. I was deploying some images in my corporation, but i'm with this problem that isn't solution. Anybody have some solution for this problem?? When i remove my PXE Service Point and I remove my WDS role and install it again, works, but i don't want to do this. When i restart my server, this problem repeat. I alread moved startup type of WDS to delayed start, but not solved. Do Exist some fix of Microsoft to solve this? A part of SCCM log --> PXE Control Manager detected PXE service point is not responding to PXE requests. The error is 16389. A part of Windows Log Application --> Log Name: Application Source: WDSIMGSRV Date: 17/01/2012 17:49:06 Event ID: 258 Task Category: (1) Level: Error Keywords: Classic User: N/A Computer: 3188-dc01-00084.credicitrus.com.br Description: The description for Event ID 258 from source WDSIMGSRV cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: 0xC1030104 =========================================================================================== PS: When i restart the WDS Service, i see that is modified the permissions of folder: C:\Windows\Temp\PXEBootFiles where the Owner of this folder is now the TrustedInstaller. Because this, the PXE don't have access to use this folder. If anybody have this solution, help me!!!!! Thanks Victor Felippe José Back to top #2 VFJ VFJ Newbie Established Members 2 posts Posted 24 January 2012 - 07:18 PM Some Information????? Back to top #3 wmmayms wmmayms MCITP Established Members 325 posts Gender:Male Location:Sweden Interests:Soccer, Computers Posted 2
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home2012Previous VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: SCCM 2007 R2 : WDS Service is not starting Error Message : Service Specific error code : 16389. System Center Configuration Manager > Configuration Manager 2007 General Question 0 Sign in to vote Hi, After installing PXE role, WDS Service is not starting Error Message : Service Specific error code : 16389. Event Id : 257 Source https://www.windows-noob.com/forums/topic/4862-pxe-error-16389-wds-start-with-error/ WDSServer An Error Occurred while trying to start the Windows Deployment Services Server. Error Information : 0x4005. More Information : I am having SCCM 2007 R2, DHCP, PXE Role and WDS Role in the Same Server. Please help me to fix the issue. MNYash Edited by Mahesh Gowda . S Wednesday, June 06, 2012 10:48 https://social.technet.microsoft.com/Forums/systemcenter/en-US/d383eb38-9e04-430a-b973-2e582aeab41d/sccm-2007-r2-wds-service-is-not-starting-error-message-service-specific-error-code-16389?forum=configmgrgeneral AM Thursday, February 02, 2012 10:19 AM Reply | Quote Answers 0 Sign in to vote Hi, I would following this guide and remove and add it back again, http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx Regards, jörgen-- My System Center blog ccmexec.com -- Twitter @ccmexec Marked as answer by Sabrina Shen Tuesday, February 21, 2012 5:14 AM Thursday, February 02, 2012 12:19 PM Reply | Quote Moderator All replies 0 Sign in to vote Hi, Here is a great guide on how to troubleshoot SCCM PXE point setup and WDS: http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx Did you configure the WDS services before adding the PXE role? Regards, Jörgen-- My System Center blog ccmexec.com -- Twitter @ccmexec Thursday, February 02, 2012 10:30 AM Reply | Quote Moderator 0 Sign in to vote Hi, Yes, I have configured the WDS Service before adding the PXE Role. Please let me know the best practice to Install WDS and PXE Role in Same Server which is having DHCP and SCCM 2007 R2 Server Installed.MNYa
PicturesVideos HomeDeploymentProblems starting WDS after PXE point is enabled in SCCM Problems starting WDS after PXE point is enabled in SCCM September 16, 2010 Leave a Comment Written by Oddvar Moe The Configmgr status viewer is showing this: PXE Control Manager detected PXE service point is not responding to PXE https://msitpros.com/?p=1003 requests. The error is 16389. The event log on the server says: Event 257, WDSServer http://www.networksteve.com/enterprise/topic.php/PXE_roll_Errors_-_WDS_will_not_start/?TopicId=15185&Posts=1 An error occurred while trying to start the Windows Deployment Services server. Error Information: 0x2740 If you convert 0x2740 to decimal it becomes 10048. If you type "net helpmsg 10048" you will get this explanation: "Only one usage of each socket address (protocol/network address/port) is normally permitted." This means that another service is currently using the port that wds is trying error id to use. This will be normal if PXE point is enabled on a server that also hosts DHCP. In order to fix this you go into registry: "HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesWDSServerProvidersWDSPXE" Here you change the UseDHCPPorts from 1 to 0. This will make sure that WDS will not use DHCP ports. You can also verify the service that is using the port by using : netstat –ano This will give you a output like this: UDP 172.20.240.5:67 *:* error id 16389.pxe 1952 UDP 172.20.240.5:68 *:* 1952 UDP 172.20.240.5:88 *:* 640 UDP 172.20.240.5:137 *:* 4 UDP 172.20.240.5:138 *:* 4 UDP 172.20.240.5:389 *:* 640 UDP 172.20.240.5:464 *:* 640 UDP 172.20.240.5:2535 *:* 1952 UDP [::]:123 *:* 796 UDP [::]:161 *:* 2232 UDP [::]:500 *:* 480 UDP [::]:3702 *:* 796 UDP [::]:3702 *:* 796 UDP [::]:56423 *:* 1964 UDP [::]:60147 *:* 796 UDP [::1]:53 *:* 1964 UDP [::1]:56421 *:* 1964 As you can see PID 1952 is using port 67. You can find out what service this is by going into task manager and adding PID column. This is located under View – Select Columns. Here you can add the PID column. Then you will be able to locate the service that is using your port. Deployment PXE, SCCM 2007 Problems pushing SCCM Clients – It’s not always WMI Configuration Manager 2007 R3 is here! 4 Comments Tim August 26, 2011 Awesome… Thanks for the info. Banging my head for a while on this one. Reply sheikaltaf October 30, 2012 that great its very helpful Reply Sanaan Barzinji August 6, 2013 i updated registry still having the same problem, and i checked PID in task manager, 1952 is not listed. Reply Erie901 August 27, 2013 OMG… Thank you!!! Worked like a charm Reply Leave a Reply Cancel reply Your email address will not be published.
cannot start the WDS service at all it just hangs & errors. Ive read it could be a permissions isue with connecting to the primary site DB but if it was wouldnt my seconday site have loads of errors as more the PXe will require the connection.? The secondar site was working without errors till I added PXE roll. The SMS PXE Service Point failed to read and configure the registry keys necessary for this component.Possible cause: The registry information is not available yet. Solution: Restart the WDS Service. The SMS PXE Service Point failed to Initialize the Database Connection. The SMS PXE Service Point failed to initialize the WDS PXE Provider. Check Previous Messages for more error information. XE Control Manager detected PXE service point is not responding to PXE requests. The error is 16389. Possible cause: PXE service point is not started or not responding. Solution: Manually restart the PXE service point. Possible cause: WDS service is not responding. Solution: Manually restart the WDS service. August 29th, 2010 1:03pm What happens if you set the WDS service to startup type "manual", reboot the server, wait until every service is up and running? Would WDS start then manually? Free Windows Admin Tool Kit Click here and download it now August 29th, 2010 2:52pm Hi Torsten, Ive set to manual & tried starting the serivces 5 mins after the server has been rebooted but get 'Service-Specific error 16389'. August 29th, 2010 9:03pm Anything in the eventlog? Or the WDS logs (there's a kb article that talks about enabling verbose logging). Free Windows Admin Tool Kit Click here and download it now August 29th, 2010 10:23pm Hi Torsten, Yes, there is errors in event viewer on the server. See below. Were I have installed PXe roll several times. ive got 6 PXE certificates with 5 blocked & 1 unblocked. The working cert is avalible till 2011. Event ID 265 An error occurred while trying to initialize provider SMSPXE. Since the provider is marked as critical, the Windows Deployment Services server will be shutdown. Error Information: 0x4005 Event ID 513 An error occurred while trying to initialize provider WDSPXE from C:\Windows\system32\wdspxe.dll. Windows Deployme