Re: OSC Image Capture Wizard Network Error

From: Andrew Griffin (AndrewGriffin_at_discussions.microsoft.com)
Date: 11/24/04 

Date: Wed, 24 Nov 2004 11:57:03 -0800

Brett,

Thanks for the info, I wasn't aware of the location of the log file.
Looking through it, I saw something strange - here's the last few lines of
the SMScapture.log:

![LOG[EmptyRecycleBin Completed]LOG]!><time="13:42:10.445+000"
date="11-24-2004" component="OSDICW" context="" type="1" thread="3616"
file="ICW_Finish.cpp:220">
<![LOG[Retrieve SysprepParams Completed]LOG]!><time="13:42:10.445+000"
date="11-24-2004" component="OSDICW" context="" type="1" thread="3616"
file="ICW_Finish.cpp:229">
<![LOG[ChangeAdminPassword Completed]LOG]!><time="13:42:10.785+000"
date="11-24-2004" component="OSDICW" context="" type="1" thread="3616"
file="ICW_Finish.cpp:275">
<![LOG[RunSysprep executing C:\sysprep\sysprep.exe -reseal -mini -quiet
]LOG]!><time="13:42:10.785+000" date="11-24-2004" component="OSDICW"
context="" type="1" thread="3616" file="ModelMachine.cpp:312">
<![LOG[RunSysprep finished executing exitcode
=259]LOG]!><time="13:42:10.795+000" date="11-24-2004" component="OSDICW"
context="" type="1" thread="3616" file="ModelMachine.cpp:317">
<![LOG[RunSysprep Completed]LOG]!><time="13:42:10.795+000"
date="11-24-2004" component="OSDICW" context="" type="1" thread="3616"
file="ICW_Finish.cpp:284">
<![LOG[CICW_Sysprep::~CICW_Sysprep]LOG]!><time="13:42:10.805+000"
date="11-24-2004" component="OSDICW" context="" type="1" thread="3616"
file="ICW_Sysprep.cpp:82">
<![LOG[CICW_SourceDest::~CICW_SourceDest]LOG]!><time="13:42:10.805+000"
date="11-24-2004" component="OSDICW" context="" type="1" thread="3616"
file="ICW_SourceDest.cpp:105">

If you cut and paste that in to a .log file and view it with Trace32, it's a
lot easier to read. The strange things I noticed - sysprep only takes 1
second to run. I would think sysprep would need to take a lot longer than
that. Second - the log file just sort of stops without mentioning initiating
a reboot or anything. What do you think?

"Brett Flegg (MS)" wrote:

> Hi Andrew,
>
> It sounds like the capture wizard is failing in the full OS for some reason.
> Can you please check the C:\~SMS_ICW directory for logs before you reboot
> the machine? Do you see any errors?
>
> Thanks,
>
> -- Brett
>
> --
>
> brett flegg | software design engineer/test | SMS | OSD FP
>
> This posting is provided AS IS with no warranties and confers no rights.
>
>
> "Andrew Griffin" <AndrewGriffin@discussions.microsoft.com> wrote in message
> news:F26C1FB8-271C-48E7-950B-CF123D9A6944@microsoft.com...
> >I actually have two issues -
> >
> > 1. When I run the first step of the image capture wizard, i.e. when the PC
> > is built and Windows is running, at the end of the wizard it states the PC
> > will now be rebooted. Well, it doesn't reboot automatically. I've tried
> > it
> > on 2 computers using 2 differen discs created from 2 different .iso files
> > with the same result. It's no big deal, I reboot manually and boot off of
> > the same CD and the second step of the image capture wizard initiates.
> >
> > 2. The real issue is when the second part of the wizard tries to upload
> > the
> > captured image. Windows PE initiates fine, the image capture progress
> > window
> > is displayed and shortly after that I get an error stating: "An error
> > occured
> > while capturing the image. (error code: 1231). The network location
> > cannot
> > be reached" At first I thought it was due to an incompatible NIC card,
> > so I
> > tried again using a 3Com and an Intel Pro 10/100, with the same result.
> > I've
> > also tried two differen LAN cables and connecting to 3 different switches,
> > all with the same result.
> >
> > I know OSD is pretty new, so any help is greatly appreciated.
>
>
>

Relevant Pages

  • RE: Office 2007 Setup Auto Reboots
    ... You'll only see this on silent installs where there is a file in use that ... files - you just don't want to reboot (usually safe for adding a product like ... config.xml and a sample log file. ... Microsoft Office Professional Plus Setup.txt specified ...
    (microsoft.public.office.setup)
  • Re: WSS errors and SP install issues........
    ... After research into your log file, I found the following resolution for you: ... Please reboot your SBS server first. ... Copy %windir%\system32\oleaut32.dll to the %windir%\system32\wbem folder. ... Run the upgrade again. ...
    (microsoft.public.windows.server.sbs)
  • How to axs the system log??
    ... "The next time it does this, go into your control panel\administrative ... that correspond to the time of your reboot. ... or the problem\conflict if in the system log. ... there is a log file or something that I can look at to see this same thing ...
    (microsoft.public.windowsxp.general)
  • Re: Corrupt Outbox.dbx
    ... The ....netsh winsock reset / reboot didn't work. ... Mike ... | Make a log file when you send. ... |> Regards. ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: X in Sid
    ... > this problem leaves no errors in the log file. ... That sounds too strange to me. ... always use Ctrl+Alt+Backslash to kill X. ...
    (Debian-User)