Re: 80072AFC

Hi Don,
From your log "Failed to resolve address to server TEST-SMS2003", does
TEST-SMS2003 exist?

Please check that you can resolve correctly this server over DNS/WINS. Maybe
the DNS / WINS settings are missing in the DHCP options?

Best regards,

Berni

"Don" <Don@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D6139B8B-332E-4ADD-8E85-FF8B6E6F118E@xxxxxxxxxxxxxxxx
Ok, I went back in and copied the Log file from the MiniNT folder. There
were only 4 logs OSDInstallCD.log, OSDInstallWizard.log, OSDrun.log, and
OSDshell.log

I found this in the OSDrun.log it shows an exit code of 13:

<![LOG[Command line: /w2kPlus /ShowError
OSDICW.EXE]LOG]!><time="10:32:10.621+000" date="08-03-2006"
component="OSDRUN" context="" type="0" thread="3672" file="main.cpp:184">
<![LOG[Shared environment successfully
initialized]LOG]!><time="10:32:10.621+000" date="08-03-2006"
component="OSDRUN" context="" type="1" thread="3672"
file="osdenvlib.cpp:208">
<![LOG[Executing command line: "OSDICW.EXE"]LOG]!><time="10:32:10.641+000"
date="08-03-2006" component="OSDRUN" context="" type="1" thread="3672"
file="commandline.cpp:476">
<![LOG[Command line: /w2kPlus /ShowError
OSDICW.EXE]LOG]!><time="10:36:19.271+000" date="08-03-2006"
component="OSDRUN" context="" type="0" thread="2764" file="main.cpp:184">
<![LOG[Shared environment successfully
initialized]LOG]!><time="10:36:19.271+000" date="08-03-2006"
component="OSDRUN" context="" type="1" thread="2764"
file="osdenvlib.cpp:208">
<![LOG[Executing command line: "OSDICW.EXE"]LOG]!><time="10:36:19.301+000"
date="08-03-2006" component="OSDRUN" context="" type="1" thread="2764"
file="commandline.cpp:476">
<![LOG[Process completed with exit code 13]LOG]!><time="10:38:00.455+000"
date="08-03-2006" component="OSDRUN" context="" type="1" thread="2764"
file="commandline.cpp:535">
<![LOG[Command line completed with exit code
13]LOG]!><time="10:38:00.455+000" date="08-03-2006" component="OSDRUN"
context="" type="1" thread="2764" file="main.cpp:80">

And this in the OSDInstallWizard:

<![LOG[Starting installation wizard.]LOG]!><time="14:18:54.869+000"
date="08-08-2006" component="OSDInstallWizard" context="" type="1"
thread="2028" file="ripwiz.cpp:329">
<![LOG[Loading X:\i386\system32\RIPInfo.ini]LOG]!><time="14:18:54.919+000"
date="08-08-2006" component="OSDInstallWizard" context="" type="1"
thread="2028" file="ripstate.cpp:189">
<![LOG[Wizard title: Laptops]LOG]!><time="14:18:54.929+000"
date="08-08-2006" component="OSDInstallWizard" context="" type="0"
thread="2028" file="ripstate.cpp:200">
<![LOG[Number of images available = 1]LOG]!><time="14:18:54.929+000"
date="08-08-2006" component="OSDInstallWizard" context="" type="0"
thread="2028" file="ripstate.cpp:214">
<![LOG[Local user may specify image
location]LOG]!><time="14:18:54.929+000"
date="08-08-2006" component="OSDInstallWizard" context="" type="0"
thread="2028" file="ripstate.cpp:228">
<![LOG[Local user may specify computer name]LOG]!><time="14:18:54.929+000"
date="08-08-2006" component="OSDInstallWizard" context="" type="0"
thread="2028" file="ripstate.cpp:247">
<![LOG[Shared environment successfully
initialized]LOG]!><time="14:18:54.929+000" date="08-08-2006"
component="OSDInstallWizard" context="" type="1" thread="2028"
file="osdenvlib.cpp:208">
<![LOG[Starting installation wizard.]LOG]!><time="14:20:51.397+000"
date="08-08-2006" component="OSDInstallWizard" context="" type="1"
thread="1876" file="ripwiz.cpp:329">
<![LOG[Loading X:\i386\system32\RIPInfo.ini]LOG]!><time="14:20:51.427+000"
date="08-08-2006" component="OSDInstallWizard" context="" type="1"
thread="1876" file="ripstate.cpp:189">
<![LOG[Wizard title: Laptops]LOG]!><time="14:20:51.427+000"
date="08-08-2006" component="OSDInstallWizard" context="" type="0"
thread="1876" file="ripstate.cpp:200">
<![LOG[Number of images available = 1]LOG]!><time="14:20:51.427+000"
date="08-08-2006" component="OSDInstallWizard" context="" type="0"
thread="1876" file="ripstate.cpp:214">
<![LOG[Local user may specify image
location]LOG]!><time="14:20:51.427+000"
date="08-08-2006" component="OSDInstallWizard" context="" type="0"
thread="1876" file="ripstate.cpp:228">
<![LOG[Local user may specify computer name]LOG]!><time="14:20:51.427+000"
date="08-08-2006" component="OSDInstallWizard" context="" type="0"
thread="1876" file="ripstate.cpp:247">
<![LOG[Shared environment successfully
initialized]LOG]!><time="14:20:51.427+000" date="08-08-2006"
component="OSDInstallWizard" context="" type="1" thread="1876"
file="osdenvlib.cpp:208">
<![LOG[Failed to resolve address to server TEST-SMS2003
(11004)]LOG]!><time="14:21:13.359+000" date="08-08-2006"
component="OSDInstallWizard" context="" type="3" thread="1876"
file="http.cpp:148">

I set this one up the same way as all of my other images, so I am not sure
why I am having this problem. Also, I just tried one of my other images,
and
it is working just fine.

"Berni" wrote:

Hi Don,
That means that you were be able to access the DP Share?
Are you able to access the local Disk?
Is there any "C:\~SMS_ICW" Folder available?
Any errors in the C:\MININT logs?
What else is different to the other Systems that you deploy over OSD?

Maybe in one of this questions we can find a solution...

Berni

"Don" <Don@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6F5DE826-B493-4686-B194-4D2E8E3343B4@xxxxxxxxxxxxxxxx
I just tried loading the LAB version of PE and was able to successfully
ping
the IP of the server and map a network drive, so I know that the
network
drivers are working properly. Also the software distribution account
is
already setup. I have other images that are working fine via OSD/RIS.
It
is
just these laptops that are giving me a problem.

"Berni" wrote:

Hi Don,
Did you load the NIC Drivers into PE?
Otherwise enable the option "Allow installation of Operating System
Packages
from a location provided by the local computer installer" or exchange
the
osdshell.exe (on the PE CD under I386\system32) with the
osdshell.lab.exe
(on your SMS Server under SMS\OSD) to be able to start the cmd Prompt
over
F8 and verify Network connectivity, Disk access, etc.
If Networking is ok verify that you have set correctly the Network
Access
Account on the SMS Component Settings under "Software Distribution".
This
account is used to access the DP where the Image is located.

I hope this helps.

Berni

"Don" <Don@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DE5A14E6-44EC-460E-A411-FDDD3F9935CE@xxxxxxxxxxxxxxxx
I am attempting to push out an OSD image to an IBM laptop that uses
the
Intel
Pro1000 NIC card. I got it RIS/OSD to recognize the NIC card, but
once
I
choose which image I want to install in WinPE I get the following
message:
"An error occurred trying to path to distribution for this operating
system
package(80072AFC)." I cannot find any information on this error.
Any
ideas?








.

Relevant Pages

  • Re: Network drives - slow initial access
    ... Just to clarify the actual fix in this case, it was within Network control ... To think of all the settings I've changed on the server in the last month! ... And does this happen if an admin logs onto a workstation, ...
    (microsoft.public.windows.server.sbs)
  • Re: What would prevent an ISAPI extension from opening a socket on IIS 6?
    ... Both fail when they try to make that network ... I looked through the local security policy settings ... >> Are you talking about an ISAPI Extension or an ISAPI Filter? ... >> on your Windows Server 2003 but not your customer's? ...
    (microsoft.public.inetserver.iis.security)
  • Re: Open file - security warning....How do I disable it?
    ... I want to be able to specify anything with a url that starts: ... IE security settings. ... We are in the process of migrating to windows server 2003. ... and then remove security inside the network. ...
    (microsoft.public.security)
  • Re: Connecting to two different domains
    ... Plug your laptop on the network. ... I have Active Directory Set-up on my Windows 2003 home server. ... to restore my previous settings to get it to boot properly ...
    (microsoft.public.windowsxp.general)
  • Re: Diskless client for windows 2000
    ... Configure DHCP options to MAC address, bootfile name and boot server ... Create bootable Network Client Disk ...
    (microsoft.public.win2000.general)