RE: Boot device error 0x0000007B+0xf789e63c

Hello,

Thanks for your post.

Based on my research, you needn't rejoin computer to new domain if you have
already run the "Computer Migration Wizard" in ADMT.

During running the "Computer Migration Wizard", you need to keep all
clients' machine that you want to migrate running. And after migration,
all the clients should restart to take the migration effect. During
migration it dispatches an agent to each computer being migrated. The agent
will restart each computer after the computers join the target domain.
However, for down-level machine such as win98, you need manually restart
the client so that win98 can join to the new domain.

We recommend migrate the groups and user objects in the following order and
please refer to the following article:

Migration of a Windows NT 4.0 Account Domain to Active Directory
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook
/cookchp9.mspx

The accounts and objects migration sequence have been addressed in Figure
9.8

For more information about ADMT:

Active Directory Migration Tool Overview
http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.
asp

HTH!

Thanks & Regards

Amanda Wang [MSFT]

Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

====================================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================================

--------------------
>Thread-Topic: Boot device error 0x0000007B+0xf789e63c
>thread-index: AcVVO5NrOT1LYoFZQ0mYBgfrTiySfg==
>X-WBNR-Posting-Host: 62.168.123.98
>From: "=?Utf-8?B?VmlrdG9yIEt2YXBpbA==?=" <viktor,kvapil@sk,hvb-cee,com>
>References: <45760F7E-7B83-4696-8ACA-C1A366E815B6@xxxxxxxxxxxxx>
<gTtE$PHVFHA.3336@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: Boot device error 0x0000007B+0xf789e63c
>Date: Tue, 10 May 2005 01:38:01 -0700
>Lines: 182
>Message-ID: <08B87AAC-AF6B-484E-BF2E-E628ED504EA7@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.migration
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:10084
>X-Tomcat-NG: microsoft.public.windows.server.migration
>
>Hi Amanda,
>
>I think that what we are getting is inaccessible boot device BOD. Hewlett
>Packard, says that main problem with booting servers from SANs is
>multipathing. With other words upgrade setup process is looking on the
same
>disk 4 times, (2 HSV controllers, 2 FC switches, 2 HBAs) 4 possible paths
to
>same storage area. We tried to use upgrade without adding drivers through
F6
>and we have also tried to add same driver through F6. I can't uninstall
>driver in live OS because system will be unstable then, it's booting from
SAN.
>
>
>--
>Viktor Kvapil
>IT servers system group
>
>
>"Amanda Wang [MSFT]" wrote:
>
>> Hello,
>>
>> Thanks for posting.
>>
>> I understand you encountered a blue screen error about STOP 0x0000007B
>> (0xF789E63C, 0Xc0000034, 0X00000000, 0x00000000).
>>
>> To locate the exact problem of the stop error, we need to analyze the
crash
>> dump file. Unfortunately, we cannot help you analyze the dump file in
>> newsgroup. To trouble shoot this problem efficiently, I suggest that you
>> speak directly with a Microsoft Support Professional so that the crash
dump
>> can be analyzed. Here are some articles that will help prepare you for
this
>> call:
>>
>> Blue Screen Preparation Before Contacting Microsoft
>> ID: 129845.KB.EN-US
>> http://support.microsoft.com/?id=129845
>>
>> Gathering Blue Screen Information After Memory Dump in Windows 2000 or
>> Windows NT
>> ID: 192463.KB.EN-US
>> http://support.microsoft.com/?id=192463
>>
>> For a complete list of Microsoft Customer Support Services phone numbers
>> and information about support costs, please go to the following address
on
>> the World Wide Web:
>> <http://support.microsoft.com/directory/overview.asp>
>>
>> To obtain the phone numbers for specific technology request please take
a
>> look at the web site listed below.
>> http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
>>
>> If you are outside the US please see http://support.microsoft.com for
>> regional support phone numbers.
>>
>> Meanwhile, based on the current information you have provided, I'd like
to
>> give you with some suggestions below:
>> Step 1:
>> 1. Open the Device Manager.
>> 2. Locate the problem device with error code.
>> 3. Right click it and choose Uninstall.
>> 4. Reboot the computer and install the updated driver.
>> Step 2:
>> 1. Turn on the computer, press the F8 key during the startup process,
>> select Safe Mode, and boot up.
>> 2. Check to see if the issue happens again.
>> Step 3:
>> Please follow this suggestion to isolate this problem:
>>
>> 1. Click Start, click Run, and then in the Open box, type "MSCONFIG"
>> (without the quotation marks). Click OK.
>>
>> 2. In the System Configuration Utility (MSConfig) window, click to
select
>> the Selective Startup button.
>>
>> 3. Click to clear the check mark from the "Load startup items" below
>> Selective Startup.
>>
>> 4. Click the Services tab, click to check the "Hide All Microsoft
Services"
>> box, and remove all the check marks from the remained Non-Microsoft
>> Services. *note that please make sure that you do not uncheck the
Microsoft
>> services.
>>
>> 5. Click OK to close the MSConfig window. Click Yes when you are asked
to
>> restart your computer in order to enable the changes.
>>
>> 6. After restarting, please check whether this issue will reoccur.
>>
>> If this issue does NOT reoccur following the Selective Startup, please
>> continue these steps to find the exact cause:
>>
>> 1. Click Start, click Run, in the Open box type "MSCONFIG" (without the
>> quotation marks), and click OK.
>>
>> 2. In the System Configuration Utility (MSConfig) window, click the
Startup
>> tab or the Services tab.
>>
>> 3. Add one check mark at a time to the entries under the Startup tab or
the
>> Services tab, and then restart each time to see if the additional entry
>> reproduces the original problem.
>>
>> For more references:
>>
>> How to troubleshoot "Stop 0x0000007B" errors in Windows XP (It is also
>> applied to Win2k3 Server)
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;324103
>>
>> 811408 STOP 0x7B error after you remove or reinstall Roxio Easy CD
Creator 5
>> http://support.microsoft.com/?id=811408
>>
>> HTH! If you need further assistance on this issue, please feel free to
>> contact CSS to get the most qualified pool of respondents. Thanks for
your
>> understanding.
>>
>> Thanks & Regards
>>
>> Amanda Wang [MSFT]
>>
>> Microsoft Online Partner Support
>>
>> Get Secure! - www.microsoft.com/security
>>
>> ====================================================================
>>
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>>
>> =====================================================================
>>
>> --------------------
>> >Thread-Topic: Boot device error 0x0000007B+0xf789e63c
>> >thread-index: AcVUWgTDwsOqVSKCR6eIh4hYD2JKEA==
>> >X-WBNR-Posting-Host: 62.168.123.98
>> >From: "=?Utf-8?B?VmlrdG9yIEt2YXBpbA==?=" <viktor,kvapil@sk,hvb-cee,com>
>> >Subject: Boot device error 0x0000007B+0xf789e63c
>> >Date: Sun, 8 May 2005 22:43:25 -0700
>> >Lines: 24
>> >Message-ID: <45760F7E-7B83-4696-8ACA-C1A366E815B6@xxxxxxxxxxxxx>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Newsgroups: microsoft.public.windows.server.migration
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:10068
>> >X-Tomcat-NG: microsoft.public.windows.server.migration
>> >
>> >Hi all,
>> >
>> >we are trying to upgrade our NAS server from W2000SP4 std to W2003 std.
>> >Here's the HW configuration:
>> >
>> >HP Proliant ML370G3, 4GB RAM, boot from SAN
>> >2x Emulex LP952L fw.3.92a2, driver Scsi port 5.5.10a10 (HP brand is
>> Storage
>> >works HBA 2101), fibre channel connectivity to HP EVA 3000, fw 3025
>> >
>> >After first reboot from W2K to upgrade screen I pressed F6 I added
>> certified
>> >scsi port driver from emulex. After that system displays bootng screen
>> with
>> >Windows server 2003 logo and runs to BOD with message 'A problem has
been
>> >detected and windows has been shut down to prevent damage to your
computer'
>> >
>> >***STOP 0x0000007B (0xF789E63C, 0Xc0000034, 0X00000000, 0x00000000
>> >
>> >it seems like system has unaccessible boot device, but we also tried to
>> add
>> >stor port driver v1-10a4c-2b with same results.
>> >
>> >Please any hint will be very appreciated and helpful.
>> >
>> >--
>> >Viktor Kvapil
>> >IT servers system group
>> >
>>
>>
>

.