Re: After upgrading 2000 server to 2003 server keeps restarting
From: Joe Wu [MSFT] (joewu_at_online.microsoft.com)
Date: 03/19/04
- Next message: Jimmy Andersson [MVP]: "Re: Kerberos and NTLM"
- Previous message: Joe Wu [MSFT]: "Re: 2000 to 2003"
- In reply to: Tom: "Re: After upgrading 2000 server to 2003 server keeps restarting"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 19 Mar 2004 09:14:43 GMT
Hello,
Thanks for your reply.
We need to move the hard disk to another computer and use "Load Hive"
function to change the problematic system's registry.
The [HKLM\CurrentControlSet\Control\CrashControl] hive is saved in the
%SystemRoot%\system32\CONFIG\SYSTEM file (no file extension).
I hope this helps. Thanks!
Regards,
Joe Wu
Product Support Services
Microsoft Corporation
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.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: google@mti-ca.com (Tom)
| Newsgroups: microsoft.public.windows.server.migration
| Subject: Re: After upgrading 2000 server to 2003 server keeps restarting
| Date: 18 Mar 2004 10:20:16 -0800
| Organization: http://groups.google.com
| Lines: 270
| Message-ID: <c2f8c4e3.0403181020.1cca5608@posting.google.com>
| References: <OJ8#O277DHA.2764@TK2MSFTNGP09.phx.gbl>
<zhUjiI97DHA.3852@cpmsftngxa07.phx.gbl>
<8a6b9a65.0402190942.1b3e2968@posting.google.com>
<X3X#gXC#DHA.1992@cpmsftngxa07.phx.gbl>
| NNTP-Posting-Host: 63.198.215.210
| Content-Type: text/plain; charset=ISO-8859-1
| Content-Transfer-Encoding: 8bit
| X-Trace: posting.google.com 1079634016 30889 127.0.0.1 (18 Mar 2004
18:20:16 GMT)
| X-Complaints-To: groups-abuse@google.com
| NNTP-Posting-Date: Thu, 18 Mar 2004 18:20:16 +0000 (UTC)
| Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onlin
e.de!news.glorb.com!postnews2.google.com!not-for-mail
| Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.migration:8919
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| But how do you edit the registry if the computer keeps rebooting??
|
| You can't look at the stop error.
| You can't boot in safe mode.
|
| What else is there to do expect re-install the OS?
|
|
|
| joewu@online.microsoft.com (Joe Wu [MSFT]) wrote in message
news:<X3X#gXC#DHA.1992@cpmsftngxa07.phx.gbl>...
| > Hello Brian,
| >
| > Thank you for your post. Yes, sometime we need to change this setting
by
| > edit the registry directly using another system. Actually the ""
setting is
| > saved in the following register value:
| >
| > WARNING: Using Registry Editor incorrectly can cause serious problems
that
| > may require you to reinstall your operating system. Microsoft cannot
| > guarantee that problems resulting from the incorrect use of Registry
Editor
| > can be solved. Please pay additional attention to these operations.
| >
| > [HKLM\CurrentControlSet\Control\CrashControl]
| >
| > AutoReboot
| > Type: REG_DWORD
| >
| > We can set it to 0 so that the system will not automatically reboot
when a
| > kernernel mode error occurs.
| >
| > I hope this helps. Thanks for using our newsgroups!
| >
| > Regards,
| > Joe Wu
| > Product Support Services
| > Microsoft Corporation
| >
| > 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.
| > ====================================================
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --------------------
| > |From: brian@max-comp.com (Brian)
| > |Newsgroups: microsoft.public.windows.server.migration
| > |Subject: Re: After upgrading 2000 server to 2003 server keeps
restarting
| > |Date: 19 Feb 2004 09:42:48 -0800
| > |Organization: http://groups.google.com
| > |Lines: 163
| > |Message-ID: <8a6b9a65.0402190942.1b3e2968@posting.google.com>
| > |References: <OJ8#O277DHA.2764@TK2MSFTNGP09.phx.gbl>
| > <zhUjiI97DHA.3852@cpmsftngxa07.phx.gbl>
| > |NNTP-Posting-Host: 68.219.6.157
| > |Content-Type: text/plain; charset=ISO-8859-1
| > |Content-Transfer-Encoding: 8bit
| > |X-Trace: posting.google.com 1077212568 3348 127.0.0.1 (19 Feb 2004
| > 17:42:48 GMT)
| > |X-Complaints-To: groups-abuse@google.com
| > |NNTP-Posting-Date: Thu, 19 Feb 2004 17:42:48 +0000 (UTC)
| > |Path:
| >
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGXS01.phx.gbl!TK2MSFTNGXA0
| >
5.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!130.59
| >
10.21.MISMATCH!irazu.switch.ch!switch.ch!news.maxwell.syr.edu!postnews1.goo
| > gle.com!not-for-mail
| > |Xref: cpmsftngxa07.phx.gbl
microsoft.public.windows.server.migration:7983
| > |X-Tomcat-NG: microsoft.public.windows.server.migration
| > |
| > |Considering what Joe Wu from microsoft said, if the system is
| > |constantly restarting how would it be possible for him to go into the
| > |windows system, right click on my computer, etc....
| > |
| > |is there another workaround for this? is there another way to change
| > |this setting? is this a registry setting that can be changed? is it a
| > |variable in a config file we can change? please advise.. .this is a
| > |problem that has plauged me for a while with my clients.
| > |
| > |Brian
| > |
| > |joewu@online.microsoft.com (Joe Wu [MSFT]) wrote in message
| > news:<zhUjiI97DHA.3852@cpmsftngxa07.phx.gbl>...
| > |> Hello Martin,
| > |>
| > |> Thank you for your post.
| > |>
| > |> My name is Joe Wu, and it is my pleasure to work with you on this
issue.
| > |>
| > |> Does the No.2 DC keep rebooting automatically with out any error or
| > warning
| > |> messages?
| > |>
| > |> If so, I think this problem should be a blue screen issue. Please
check
| > my
| > |> analysis and suggestions below:
| > |>
| > |> Analysis:
| > |> =========
| > |>
| > |> The automatically restart issue is actually a blue screen stop issue
(we
| > |> can enable the system to show the blue screen when the problem
occurs).
| > |> Windows 2000\XP\2003 uses separate user mode and kernel mode memory
| > space,
| > |> Blue Screen issue is always caused by a certain kernel potion
component,
| > |> such as a device driver, backup software or anti-virus services
(buggy
| > |> services).
| > |>
| > |> The system goes to a blue screen when some exception occurs in the
| > kernel
| > |> (either the device driver errors or the service errors), and Windows
| > system
| > |> implements this mechanism: When it detects some errors occur in the
| > kernel,
| > |> it will kill the box in case some more severe damage happens. Then
we
| > get a
| > |> blue screen or the system reboots (it depends on what the system
| > settings
| > |> are).
| > |>
| > |> Actually, troubleshooting blue screen stop/automatically restart
issues
| > are
| > |> very complicated. We need to collect memory dump files (which is
very
| > |> large) and perform debug operations to find the culprit that caused
the
| > |> Kernel mode crash.
| > |>
| > |> Due to the complexity of the blue screen stop/automatically restart
| > issues
| > |> (the dump file are generally more than 100 MB depending on the RAM
size
| > on
| > |> the problematic machines, and debug needs checking source), I would
like
| > to
| > |> suggest that you contact Microsoft Product Support Services via
| > telephone
| > |> so that a dedicated Support Professional can assist you recover the
| > server
| > |> in a more efficient manner. Please be advised that contacting phone
| > support
| > |> will be a charged call.
| > |>
| > |> 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.
| > |>
| > |> Also, I would like to share some general troubleshoot information
for
| > this
| > |> kind of problem with you:
| > |>
| > |> [General Suggestions For Troubleshooting Blue Screen
Stop/Automatically
| > |> Restart Issues]:
| > |> =====================
| > |>
| > |> 1. Please configure the system to display a blue screen with more
| > |> information when the automatically restart problem occurs.
| > |>
| > |> To do so, please right click [My computer] and choose [Properties].
On
| > the
| > |> [Advanced] table, click [Settings] in [Startup and Recovery]. In
that
| > |> dialog uncheck "Automatically reboot". Make sure the "Write an event
to
| > the
| > |> system log" and "Send an administrative alert" check boxes are
chosen.
| > |>
| > |> After you have performed the steps above, please restart the
computer
| > and
| > |> keep monitoring it. Generally, if the problem occurs, there should
be a
| > |> blue screen stop error which indicates to us some information about
the
| > |> error. Such as follows:
| > |>
| > |>
| >
----------------------------------------------------------------------------
| > |> ----------
| > |> STOP: 0x00000050 (0xbc3cb000, 0x00000001, 0x80461b64, 0x00000000)
| > |> PAGE_FAULT_IN_NONPAGED_AREA - NDIS.SYS
| > |> ..
| > |>
| >
----------------------------------------------------------------------------
| > |> ----------
| > |>
| > |> If there is a file name recorded in the error message (for example,
| > |> NDIS.sys in the above example), you can check if it is a file added
by a
| > |> certain application.
| > |>
| > |> 2. If the system still reboots suddenly without generating a blue
| > screen,
| > |> or many blue screen errors with different crash IDs (0x00000050 in
the
| > |> above example) occur randomly on a system, we can suspect that the
| > problem
| > |> may be related to a hardware failure. To verify it, we can build a
| > parallel
| > |> Windows system on another partition with enough space. If these blue
| > screen
| > |> errors still occur with the new dual-booted system, it is very
likely a
| > |> hardware issue.
| > |>
| > |> 3. Blue screen stop issue is always caused by a certain kernel
potion
| > |> component, such as a device driver, backup software or anti-virus
| > services
| > |> (buggy services). Therefore, please check if the previously install
| > device
| > |> drivers, applications are fully compatible with Windows Server 2003.
If
| > |> possible, please restore the No.2 DC from backup media, uninstall
| > |> unnecessary applications, upgrade device drivers, unplug unnecessary
| > |> devices, and then try the upgrade to see if it works.
| > |>
| > |> 4. It is better to contact Microsoft Product Support Services via
| > telephone
| > |> and work with a dedicated Support Professional on this issue. This
will
| > be
| > |> the most efficient solution for this kind of problem. You can find
the
| > |> related contact information above.
| > |>
| > |> Thanks for taking time to read this long post. I hope it helps. Have
a
| > nice
| > |> day!
| > |>
| > |> Regards,
| > |> Joe Wu
| > |> Product Support Services
| > |> Microsoft Corporation
| > |>
| > |> 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.
| > |> ====================================================
| > |> This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| > |>
| > |> --------------------
| > |> |From: "Admi" <administrator@soh.dk>
| > |> |Subject: After upgrading 2000 server to 2003 server keeps restarting
| > |> |Date: Tue, 10 Feb 2004 11:06:29 +0100
| > |> |Lines: 14
| > |> |X-Priority: 3
| > |> |X-MSMail-Priority: Normal
| > |> |X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| > |> |X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| > |> |Message-ID: <OJ8#O277DHA.2764@TK2MSFTNGP09.phx.gbl>
| > |> |Newsgroups: microsoft.public.windows.server.migration
| > |> |NNTP-Posting-Host: 217.61.212.7
| > |> |Path:
| > |>
| >
cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08
| > |> .phx.gbl!TK2MSFTNGP09.phx.gbl
| > |> |Xref: cpmsftngxa07.phx.gbl
| > microsoft.public.windows.server.migration:7670
| > |> |X-Tomcat-NG: microsoft.public.windows.server.migration
| > |> |
| > |> |I am upgrading from 2000 AD to 2003 AD
| > |> |i run forestprep and domainprep the server white Schema Master and
| > upgradet
| > |> |it to 2003 server whiteout problems.
| > |> |
| > |> |i then upgradet my DC no. 2 to 2003 server but after the upgrade
the
| > server
| > |> |keeps restarting.
| > |> |
| > |> |i have tryed to start in safe mode, but no luck, it just restarted.
| > |> |
| > |> |help pls.
| > |> |
| > |> |Martin Mollerup
| > |> |
| > |> |
| > |> |
| > |
|
- Next message: Jimmy Andersson [MVP]: "Re: Kerberos and NTLM"
- Previous message: Joe Wu [MSFT]: "Re: 2000 to 2003"
- In reply to: Tom: "Re: After upgrading 2000 server to 2003 server keeps restarting"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
