asked on

Windows SBS 2011 Standard

The Server hangs and needs a forced Restart.
Here are the Event logs that happens around the crash before the reboot;

event1, msexchange autodiscover
event1005, msexchange mailbox replication
event1006, grouppolicy
event1026, msexchangemailsubmission
event1054, grouppolicy
event1126, activedirectory_domainservice
event1129, grouppolicy
event1206,adws
event2001, msexchange rpc over http autoconfig
event2102, msechange adaccess
event2103, msexchange adaccess
event4000, dns-server-service
event4001, msexchange auditlogsearchevent4004, dns-server-service
event4015, dns-server-service
event8026, msexchangeal
event8365, msexchangeal
event9106, msexchangeapplicationlogic

Seems as the server cant access domain controller/active directory.
We ran a Intel Confidence Test, which pasted.

Simon Butler (Sembee)

Event numbers on their own are close to useless.
Put the event ID's in to http://www.eventid.net/ and you will see how many variants there are.

Need more information about the system - patch status, hardware type etc.
If the machine is a branded system, ensure that it has the latest drivers, BIOS etc.

Simon.

jmanishbabu

Attached

Using GenMiniDump.exe (Note: GenMiniDump.zip is attached below):

Place genminidump.exe and dbghelp.dll in a folder
cd into that folder
Run the following from cmd: genminidump.exe <PID> or genminidump.exe <Process name> Example: C:\Temp\GenMiniDump\genminidump msdev.exe

jmanishbabu

Generate the mindump and provide us the .dmp file

stevenvanheerden

ASKER

Board: Intel Corporation S5520HC E26045-454
2.40 gigahertz Intel Xeon (2 installed)
16324 Megabytes Usable Installed Memory
Intel MegaSR SCSI Disk Device (998.99 GB) -- drive 1
Intel MegaSR SCSI Disk Device (498.99 GB) -- drive 0

Everything checks out, the store uses all the memory! (Standard SBS Issue)

Will check for the drivers and updates!
event1--msexchange-autodiscover.txt
event1005--msexchange-mailbox-re.txt
event1006--grouppolicy.txt
event1026--msexchangemailsubmiss.txt
event1054--grouppolicy.txt
event1126--activedirectory-domai.txt
event1129--grouppolicy.txt
event1206-adws.txt
event2001--msexchange-rpc-over-h.txt
event2102--msechange-adaccess.txt
event2103--msexchange-adaccess.txt
event4000--dns-server-service.txt
event4001--msexchange-auditlogse.txt
event4004--dns-server-service.txt
event4015--dns-server-service.txt
event8026--msexchangeal.txt
event8365--msexchangeal.txt
event9106--msexchangeapplication.txt

stevenvanheerden

ASKER

where's the attached file?

SOLUTION

Cliff Galiher

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

ASKER CERTIFIED SOLUTION

Cris Hanna

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

stevenvanheerden

ASKER

Ran SBS best practice advisor, which showed a few warnings. Will be resolving these issues during the next couple of days.

stevenvanheerden

ASKER

I updated all drivers...
Ran and Repaired issues in best practice advisor besides the error below.

The server hanged after all this (besides below issue), is there a later repair procedure to rectify the journal wrap (MS Support only has previous OS Fix)

----------------------------------------
Category: Configuration

Source: 229

Issue: The server is in a journal wrap condition.

Impact: In a journal wrap condition, the system volume is not shared. As a result, the domain controller cannot replicate with other domain controllers. Additionally, the server cannot authenticate network users until the journal wrap condition is resolved.

Resolution: For more information, see "How to troubleshoot journal_wrap errors on Sysvol and DFS replica sets" at http://go.microsoft.com/fwlink/?LinkId=143372.
--------------------------

Thanks for all the help so far!