0x102 ошибка sccm

Hi,

Thanks for posting in TechNet.

1. The error code 0x102 means «The wait operation timed out.» The issue may be network related. Please help check the smsts.log and smspxe.log for more information.

2.General speaking, Microsoft does not recommend using DHCP options， the recommended and supported method for PXE booting client computers on remote subnets is to use IP Helpers. Notice that, in certain instances, configuring DHCP options 60, 66, and 67 may
make it appear that the PXE boot process is proceeding further along than it did before these options were configured. However, in most cases, the process is actually proceeding along an incorrect path.

IP Helpers aren’t required if the DHCP server, the client computer, the ConfigMgr server that is running Windows Deployment Services (WDS), and the PXE-enabled Distribution Point (DP) are all on the same subnet or VLAN.

IP Helpers must be configured on the routers if any of the DHCP server, the client computer, or the Configuration Manager server that is running WDS and the PXE-enabled DP are on separate subnets or VLANs. This is usually the case in most environments.

IP Helpers are necessary because the PXE request that is generated by the client computer is a broadcast that doesn’t travel outside the local subnet or VLAN. If the DHCP server or the WDS/PXE-enabled DP aren’t on the same subnet or VLAN as the client computer,
they will not see or hear the PXE request broadcast from the client. Therefore, the servers will not respond to the PXE request. To have the PXE request broadcast travel between subnets or VLANs, the PXE request broadcast has to be forwarded by the router
to DHCP and WDS/PXE Service Point servers so that they can correctly respond to the client’s PXE request.

For more information, please refer to:
Troubleshooting PXE boot issues in Configuration Manager
Use PXE to deploy Windows over the network with Configuration Manager

Thanks for your time.

Best regards,
Simon

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.

Marked as answer by

Tuesday, June 9, 2020 11:02 AM

Источник

2 Replies

Have you tried to run diskpart to clean the disk before? If there is a bad image on it then it may be causing a conflict.

Boot it to the command prompt, assuming it won’t boot now. At the DISKPART prompt, type «list disk»

At the DISKPART prompt, type: sel disk 0 (This selects disk to edit; make sure to type in the right #

Then clean.

Try it again after that.

If it does boot, you can clear anything leftover in C:MININT and then delete everything inside the C:windowspanther folder.

See if those resolve the issue. It shouldn’t add it into AD until the last step, so if you are just PXE booting into WINPE to start an image, it hasn’t reached that point yet.

Was this post helpful?
thumb_up
thumb_down
habanero

Imaging, Deployment, & Patching Expert
- check
  205
  Best Answers
- thumb_up
  197
  Helpful Votes
- format_list_bulleted
  12
  How-tos
Have you attempted to right click on the collection and choose Clear PXE Deployments?

Was this post helpful?
thumb_up
thumb_down

Источник

Login

Continue with LinkedIn

Continue with Facebook

Continue with Google

Continue with Twitter

Forget

Remember Me

Register Now

Create an account

Home/ Windows 10/after PXE boot load the TS giving error message Error code – 0x102

after PXE boot load the TS giving error message Error code – 0x102

Question

after PXE boot load the TS giving error message Error code – 0x102

solved 0

Windows 10 Vishal Pachkhande 2 years 2021-04-23T16:00:00+05:30 2021-04-23T16:00:00+05:30 2 Answers 1606 views Beginner

Vishal Pachkhande

About Vishal PachkhandeBeginner

Answers ( 2 )

Jitesh Kumar
1

2021-04-26T12:32:55+05:30 April 26, 2021 at 12:32 PM

Reply
Hello Vishal, Any update on this? Had you reinitiate the deployment, How many incident occurred?

+ Error code 0x102 means “The wait operation timed out”, the issue may be network related. Please review the smsts.log and smspxe.log

Best answer
Anoop C Nair
0

2021-04-23T16:46:01+05:30 April 23, 2021 at 4:46 PM

Reply
Have you seen this issue with many devices?

If so, I think there should more troubleshooting from network trace from the client and server (DHCP, WDS, etc) end to understand where it’s getting blocked?

Leave an answer

Sorry, you do not have permission to answer to this question .

Previous question

Next question

Источник

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Closed

keithslater opened this issue

Oct 24, 2017

· 9 comments

Comments

Having problems getting connected to a SQL Server. Here is the command I’m using for testing —

sqlcmd -S 10.10.0.81,1434 -U username -P password -d database

I have assigned the static port 1434 to the named instance 10.10.0.81SQLEXPRESS.

I have tested this connected via Navicat and it connects successfully through the IP and port. The port is wide open to all internal IPs.

unixODBC 2.3.1

Not sure what else to try at this point.

@keithslater, to connect to a named instance on a static port, you need to use port number. Please see here. You can also check the related issues: #442, #340, #190, #175.

I understand that. My example shows me using the port 1434.

@keithslater, your problem may come from many places. It is difficult to pinpoint where the problem comes from. Here’s a list of solution for you to try out:

Make sure SQL Server is not listening on a dynamic port (see here).
Make sure ODBC is installed properly. What is the output for:

1. odbcinst -j
2. odbcinst -q -d -n "ODBC Driver 13 for SQL Server"
3. sudo find /usr 2>/dev/null -name "libodbc*"
4. php -i | grep "Configure Command"

Disable any firewall, as mentioned in connection failed #190.
Make sure SQL Server is listening to the right port. Run the following to make sure the correct port is being listened to.

USE MASTER
GO
xp_readerrorlog 0, 1, N'Server is listening on'
GO

odbcinst -j
unixODBC 2.3.4
DRIVERS............: /usr/local/etc/odbcinst.ini
SYSTEM DATA SOURCES: /usr/local/etc/odbc.ini
FILE DATA SOURCES..: /usr/local/etc/ODBCDataSources
USER DATA SOURCES..: /home/anvil/.odbc.ini
SQLULEN Size.......: 8
SQLLEN Size........: 8
SQLSETPOSIROW Size.: 8

odbcinst -q -d
[PostgreSQL]
[MySQL]
[ODBC Driver 13 for SQL Server]

sudo find /usr 2>/dev/null -name "libodbc*"
/usr/lib64/libodbc.so
/usr/lib64/libodbc.so.2
/usr/lib64/libodbcdrvcfg2S.so.2
/usr/lib64/libodbcdrvcfg2S.so.2.0.0
/usr/lib64/libodbcinst.so
/usr/lib64/libodbcinst.so.2
/usr/lib64/libodbcinst.so.2.0.0
/usr/lib64/libodbcminiS.so.2
/usr/lib64/libodbcminiS.so.2.0.0
/usr/lib64/libodbcmyS.so
/usr/lib64/libodbcmyS.so.2
/usr/lib64/libodbcmyS.so.2.0.0
/usr/lib64/libodbcnnS.so
/usr/lib64/libodbcnnS.so.2
/usr/lib64/libodbcnnS.so.2.0.0
/usr/lib64/libodbc.so.2.0.0
/usr/lib64/libodbcpsqlS.so
/usr/lib64/libodbccr.so.2
/usr/lib64/libodbcpsqlS.so.2
/usr/lib64/libodbccr.so
/usr/lib64/libodbcdrvcfg1S.so
/usr/lib64/libodbccr.so.2.0.0
/usr/lib64/libodbcdrvcfg2S.so
/usr/lib64/libodbcdrvcfg1S.so.2
/usr/lib64/libodbctxtS.so
/usr/lib64/libodbcpsqlS.so.2.0.0
/usr/lib64/libodbctxtS.so.2
/usr/lib64/libodbcdrvcfg1S.so.2.0.0
/usr/lib64/libodbctxtS.so.2.0.0
/usr/lib64/libodbcminiS.so
/usr/local/lib/libodbcinst.so.2.0.0
/usr/local/lib/libodbcinst.so.2
/usr/local/lib/libodbcinst.so
/usr/local/lib/libodbcinst.la
/usr/local/lib/libodbc.so.2.0.0
/usr/local/lib/libodbc.so.2
/usr/local/lib/libodbc.so
/usr/local/lib/libodbc.la
/usr/local/lib/libodbccr.so.2.0.0
/usr/local/lib/libodbccr.so.2
/usr/local/lib/libodbccr.so
/usr/local/lib/libodbccr.la

php -i | grep «Configure Command»
returns nothing.

Double checking the port but I can connect to it on the port via Navicat.

@keithslater, looks like you have 2 different unixODBC installed. I’m not sure if this is the source of the problem, but after you’ve checked the port number of your SQL Server, you can try to uninstall your current unixODBC, and then install the latest unixODBC version using apt-get. You can revisit issue 231 to see how to uninstall and install unixODBC properly.

Which IP (IP1 to IPAll) did you change? Make sure the IP you’re configuring is the one you want to use. One thing you can try is to change the TCP Port in IPAll to 1434.

So IP2 had the IP address listed I was trying to connect on 10.10.0.81 with the static port configured 1434. So from what I can tell, IP2 was configured correctly.

However, IPAll had the dynamic port listed that I was able to actually connect on.

We’re going to change IP2 back to dynamic and move the static port to IPAll. Hopefully that should fix the issue. Not exactly sure why it didn’t work.

Switching the static port to IPAll fixed the issue.

Источник

What error do you get when you PXE boot the clients (HP Probook’s like 650 G3 or 650 G4)?.

Thread Starter
#3

Hi,

I get the following error code:

Windows Deployment Services (SERVER IP: (server IP SCCM Server))
Windows Deployment Services encountered an error:
Error Code: 0x102

See screenshot as attachment.

SCCM_error.jpg

315.6 KB

· Views: 12

Are you using IP helpers or DHCP options ?.

Thread Starter
#5

We use both, IP-helpers are configured on the switch and DHCP options are active on the scope.

Before updating to the newest hotfix everything works fine, after the update one or two models can’t connect with PXE.

Hi,
Did you get a resolution to this issue?
I upgraded our ADK and WinPE Extensions to 2004 and now PXE boot is not working.
PXE attempts just fail and error with the same error you have posted.

Thread Starter
#7

No, this one specific device will not deploy PXE or connect to PXE. Other devices works fine.

I’m getting this same issue on some laptops and desktops as well. Seems completely random

— HP EliteBook 840 G6
— HP ProDesk 600 G4 Mini Desktop

I’ve seen on other forums that switching to IP Helpers instead of DHCP options resolves this issue but I’m not exactly sold on that. I know IP Helpers should be used in general — although I need to jump through hoops to get my network team to make this change across all our networks.

Any other suggestions?

We have configured an OSD server on VM. Getting this error while starting PXE boot. We have updated DHCP scope option 66 and 67. Can anybody help please?

WDS Error.PNG

112.3 KB

· Views: 4

Hi all
I have the same problem
You have resolve?

Having the same problem with a specific model of drop-in PC module from Viewsonic (WDS Error Code: 0x102 when trying to contact the server). All other devices in our inventory are PXE booting/imaging without error.

I am told that IP helper addresses are configured, but much like Chris F stated above, I cannot confirm this, as I work in an organization large enough to have some degree of separation between the systems admin and network infrastructure teams. The DHCP options are configured, but when they are removed, PXE boot fails for all devices — not just the new Viewsonics we’re currently having an issue with.

This leads me to believe that the IP helper addresses are not correctly configured, but the issue remains that with the use of DHCP options, we can successfully PXE boot/image everything in our inventory with the exception of this model (VPC25-W33-P1-1T/VS18617).

Version 2111
Site version: 5.0.9068.1000

Last edited: Aug 3, 2022

Источник

2 Replies

Login

Register Now

after PXE boot load the TS giving error message Error code – 0x102

About Vishal PachkhandeBeginner

Related questions

Bitlocker Key Tenant to Tenant Migration without Intune

How to enable thunderbolt boot support in BIOS using script/registry settings

AppLocker Group Policy

Wmi query to find pre reboot pin is enabled or not

WMIC.EXE removal

Answers ( 2 )

Leave an answer

Comments

Читайте также: