OSD restore phase problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: "Huynh, T" <thuynh@xxxxxxx>
Date: Wed, 02 Nov 2005 15:26:44 -0500

I am experiencing some abnormal behavior in which some of my target machines
will report it can not connect to the installation package on the
distribution point (\\\\SMS-SS1\SMSPKGD$\MP10007C). No network provider
accepted the given path. (800704B3).

I am almost certain it's not the sms server or distribution point that is
having problems (works for some machines and not others in a small 5 machine
pilot) It certainly is not the network bandwidth as the I'm seeing left than
4 percent network utilization. It can't be sever IO since it's such a small
pilot. I can connect to the share from another machine when this message
pops up.

Going from Windows 2000 to windows XP SP1.
SMS 2003 SP1 on Windows 2003 server

Is there anything I should be looking for to figure out what the problem is?

This is the OSDagent.log file showing the errors.

Parsing param: /restore $$<OSDAgent><Mon Oct 31 8:33:56.530 2005 Eastern
Standard Time><thread=1816 (0x718)>
OSDAgent will be executing in restore mode. $$<OSDAgent><Mon Oct 31
8:33:56.540 2005 Eastern Standard Time><thread=1816 (0x718)>
Shared environment successfully initialized $$<OSDAgent><Mon Oct 31
8:33:56.620 2005 Eastern Standard Time><thread=1816 (0x718)>
Got connection request for \\SMS-SS1\SMSPKGD$\MP10007C $$<OSDAgent><Mon Oct
31 8:33:56.620 2005 Eastern Standard Time><thread=1816 (0x718)>
OS Version: 261 $$<OSDAgent><Mon Oct 31 8:33:56.630 2005 Eastern Standard
Time><thread=1816 (0x718)>
Connecting to \\SMS-SS1\SMSPKGD$\MP10007C $$<OSDAgent><Mon Oct 31
8:33:56.630 2005 Eastern Standard Time><thread=1816 (0x718)>
Failed to connect to \\SMS-SS1\SMSPKGD$\MP10007C (1203). Retry in 10
seconds. $$<OSDAgent><Mon Oct 31 8:33:57.932 2005 Eastern Standard
Time><thread=1816 (0x718)>
Connecting to \\SMS-SS1\SMSPKGD$\MP10007C $$<OSDAgent><Mon Oct 31
8:34:07.936 2005 Eastern Standard Time><thread=1816 (0x718)>
Failed to connect to \\SMS-SS1\SMSPKGD$\MP10007C (1203). Retry in 20
seconds. $$<OSDAgent><Mon Oct 31 8:34:08.016 2005 Eastern Standard
Time><thread=1816 (0x718)>
Connecting to \\SMS-SS1\SMSPKGD$\MP10007C $$<OSDAgent><Mon Oct 31
8:34:28.035 2005 Eastern Standard Time><thread=1816 (0x718)>
Failed to connect to \\SMS-SS1\SMSPKGD$\MP10007C (1203). Retry in 30
seconds. $$<OSDAgent><Mon Oct 31 8:34:28.035 2005 Eastern Standard
Time><thread=1816 (0x718)>
Connecting to \\SMS-SS1\SMSPKGD$\MP10007C $$<OSDAgent><Mon Oct 31
8:34:58.048 2005 Eastern Standard Time><thread=1816 (0x718)>
Failed to connect to \\SMS-SS1\SMSPKGD$\MP10007C (1203). Retry in 40
seconds. $$<OSDAgent><Mon Oct 31 8:34:58.048 2005 Eastern Standard
Time><thread=1816 (0x718)>
Connecting to \\SMS-SS1\SMSPKGD$\MP10007C $$<OSDAgent><Mon Oct 31
8:35:38.066 2005 Eastern Standard Time><thread=1816 (0x718)>
CHECK FAILED: (iTry < 5) || (uRet == 1219L) (Error = 800704B3)
$$<OSDAgent><Mon Oct 31 8:35:38.066 2005 Eastern Standard Time><thread=1816
(0x718)>
Failed to connect to \\SMS-SS1\SMSPKGD$\MP10007C (1203) $$<OSDAgent><Mon
Oct 31 8:35:38.076 2005 Eastern Standard Time><thread=1816 (0x718)>
CHECK FAILED: reconnect() (Error = 800704B3) $$<OSDAgent><Mon Oct 31
8:35:38.086 2005 Eastern Standard Time><thread=1816 (0x718)>
Stat Msg: 3221236577
MachineName=L2-14063
ClientID=GUID:6F3AD515-B891-46BD-A69D-6941CF0019B0
ProcessID=#1764
ThreadID=#1816
Win32ErrorCode=#0
DateTime=20051031133538.106000+000
Attrib400=MP10007C
Attrib401=MP1203B1
Insert1=\\SMS-SS1\SMSPKGD$\MP10007C
$$<OSDAgent><Mon Oct 31 8:35:38.106 2005 Eastern Standard
Time><thread=1816 (0x718)>
Connecting to server SMS-SS1 on port 80 $$<OSDAgent><Mon Oct 31 8:35:38.106
2005 Eastern Standard Time><thread=1816 (0x718)>
Successfully resolved server SMS-SS1 to 63.244.253.67 $$<OSDAgent><Mon Oct
31 8:35:38.126 2005 Eastern Standard Time><thread=1816 (0x718)>
Successfully connected to server SMS-SS1 $$<OSDAgent><Mon Oct 31
8:35:38.126 2005 Eastern Standard Time><thread=1816 (0x718)>
Status message was successfully received by server SMS-SS1 $$<OSDAgent><Mon
Oct 31 8:35:52.116 2005 Eastern Standard Time><thread=1816 (0x718)>
Running command line: "\\SMS-SS1\SMSPKGD$\MP10007C\osdenv.exe" /UnRegServer
$$<OSDAgent><Mon Oct 31 8:35:52.126 2005 Eastern Standard Time><thread=1816
(0x718)>
Successfully unregistered OSD environment object. $$<OSDAgent><Mon Oct 31
8:35:52.927 2005 Eastern Standard Time><thread=1816 (0x718)>
The operating system installation failed. Please contact your system
administrator for assistance.

Could not connect to the installation package on
\\SMS-SS1\SMSPKGD$\MP10007C. No network provider accepted the given network
path. (800704B3)

This message will automatically close in 30 minutes. $$<OSDAgent><Mon Oct
31 8:35:52.947 2005 Eastern Standard Time><thread=1816 (0x718)>
CHECK FAILED: g_JobEng.execute() (Error = 800704B3) $$<OSDAgent><Mon Oct 31
9:36:41.282 2005 Eastern Standard Time><thread=1816 (0x718)>
Installation failed with error code 800704B3 $$<OSDAgent><Mon Oct 31
9:36:41.282 2005 Eastern Standard Time><thread=1816 (0x718)>
Creating the temp logs folder : C:\WINDOWS\TEMP\SMSOSD $$<OSDAgent><Mon Oct
31 9:36:41.282 2005 Eastern Standard Time><thread=1816 (0x718)>
Saving Logs into the Temp Folder : C:\WINDOWS\TEMP\SMSOSD $$<OSDAgent><Mon
Oct 31 9:36:41.452 2005 Eastern Standard Time><thread=1816 (0x718)>
Cleaning up the Minint Folder $$<OSDAgent><Mon Oct 31 9:36:56.594 2005
Eastern Standard Time><thread=1816 (0x718)>
Archive File is present - not cleaning up the folder $$<OSDAgent><Mon Oct
31 9:36:56.654 2005 Eastern Standard Time><thread=1816 (0x718)>
Jobengine.execute returned code 800704B3 $$<OSDAgent><Mon Oct 31
9:36:56.674 2005 Eastern Standard Time><thread=1816 (0x718)>
CHECK FAILED: g_OSDAgent.Run() (Error = 800704B3) $$<OSDAgent><Mon Oct 31
9:36:56.684 2005 Eastern Standard Time><thread=1816 (0x718)>
Error Deployment agent failed to complete. Code 0x800704b3 $$<OSDAgent><Mon
Oct 31 9:36:56.694 2005 Eastern Standard Time><thread=1816 (0x718)>

.

Follow-Ups:
- Re: OSD restore phase problem
  - From: Huynh, T

Prev by Date: Re: OSD Upgrade from Windows 2000 Pro ends to a BSOD
Next by Date: Re: OSD restore phase problem
Previous by thread: Re: OSD Upgrade from Windows 2000 Pro ends to a BSOD
Next by thread: Re: OSD restore phase problem
Index(es):
- Date
- Thread

Relevant Pages

Re: OSD restore phase problem
... reproducible problem with the HP NC6000 laptop and the restore phase. ... I am not seeing this problem with other machines ... > will report it can not connect to the installation package on the ... > pilot) It certainly is not the network bandwidth as the I'm seeing left than ...
(microsoft.public.sms.tools)
Re: OSD restore phase problem
... Is it possible that the machines aren't getting a DHCP address fast enough? ... Often this can represent a network configuration issue (on Cisco switches, ... >> will report it can not connect to the installation package on the ...
(microsoft.public.sms.tools)
Re: How can I measure the network load ?
... >> the network load of some machines on a local area network ... >> the distribution of my processes over the network, ... For solaris linux cisco and every other device that speaks SNMP ...
(comp.unix.solaris)
Re: How can I measure the network load ?
... >> the network load of some machines on a local area network ... >> the distribution of my processes over the network, ... For solaris linux cisco and every other device that speaks SNMP ...
(comp.unix.questions)
Re: How can I measure the network load ?
... >> the network load of some machines on a local area network ... >> the distribution of my processes over the network, ... For solaris linux cisco and every other device that speaks SNMP ...
(comp.unix.misc)