Annoying Crashes on SBS
|
From: thejamie on 7 Feb 2009 09:42 Thanks to all for the help. We have been up and running for a dozen days without a crash on the DC. Solution seems to have been to place a parabolic antenna on the wireless access point. Ingenious... think someone here posted this or they sent me to a site with this link. Whoever it was - double thanks. http://binarywolf.com/249/diy-parabolic-reflector.htm -- Regards, Jamie "Les Connor [SBS MVP]" wrote: > The event log errors you're seeing are as a result of the server going down. > You have to resolve the stop error, one way or another. > > -- > ----------------------------------------------- > Les Connor [SBS MVP] > > "thejamie" <thejamie(a)discussions.microsoft.com> wrote in message > news:643DAFEC-1F3A-41D0-B361-69423754533E(a)microsoft.com... > > I was able to get the crash with a machine inside the network: > > > > CLIENT MACHINE SAYS: > > > > The master browser has received a server announcement from the computer > > MYDC > > that believes that it is the master browser for the domain on transport > > NetBT_Tcpip_{AE9618C6-E870-4AB3-AAA4-D6EDE7A1F0E4}. The master browser is > > stopping or an election is being forced. > > > > > > -- > > Regards, > > Jamie > > > > > > "Les Connor [SBS MVP]" wrote: > > > >> do analyses on that blue screen. > >> > >> http://blogs.technet.com/petergal/archive/2006/03/23/422993.aspx > >> > >> I'd suggest something wrong serverside. > >> > >> -- > >> ----------------------------------------------- > >> Les Connor [SBS MVP] > >> > >> "thejamie" <thejamie(a)discussions.microsoft.com> wrote in message > >> news:763C1692-549E-458B-B3A0-8D77ACE99E2E(a)microsoft.com... > >> > The server restart log is at 7:16 for this particular crash: > >> > The client says: > >> > The system failed to register host (A) resource records (RRs) for > >> > network > >> > adapter > >> > with settings: > >> > > >> > Adapter Name : {7790AD42-FFC6-43CD-AF09-5F4275B39533} > >> > Host Name : solsticedev > >> > Primary Domain Suffix : terraatlas.local > >> > DNS server list : > >> > 192.168.16.2 > >> > Sent update to server : <?> > >> > IP Address(es) : > >> > 192.168.1.2 > >> > > >> > The reason the system could not register these RRs was because either > >> > (a) > >> > the DNS server does not support the DNS dynamic update protocol, or (b) > >> > the > >> > authoritative zone for the specified DNS domain name does not accept > >> > dynamic > >> > updates. > >> > > >> > To register the DNS host (A) resource records using the specific DNS > >> > domain > >> > name and IP addresses for this adapter, contact your DNS server or > >> > network > >> > systems administrator. > >> > > >> > For more information, see Help and Support Center at > >> > http://go.microsoft.com/fwlink/events.asp. > >> > > >> > The server code is a bit less revealing: > >> > The reason supplied by user TERRAATLAS\Administrator for the last > >> > unexpected > >> > shutdown of this computer is: System Failure: Stop error > >> > Reason Code: 0x805000f > >> > Bug ID: > >> > Bugcheck String: 0x0000007a (0xc03dcdb8, 0xc000000e, 0xf736e5ef, > >> > 0x11ed1860) > >> > Comment: 0x0000007a (0xc03dcdb8, 0xc000000e, 0xf736e5ef, 0x11ed1860) > >> > > >> > For more information, see Help and Support Center at > >> > http://go.microsoft.com/fwlink/events.asp. > >> > > >> > > >> > THEN > >> > The Network Connections service was successfully sent a start control. > >> > > >> > For more information, see Help and Support Center at > >> > http://go.microsoft.com/fwlink/events.asp. > >> > > >> > > >> > AND > >> > > >> > Error code 0000007a, parameter1 c03dcdb8, parameter2 c000000e, > >> > parameter3 > >> > f736e5ef, parameter4 11ed1860. > >> > > >> > For more information, see Help and Support Center at > >> > http://go.microsoft.com/fwlink/events.asp. > >> > > >> > as it came BACK > >> > > >> > Printer Generic / Text Only (from SOLSTICEDEV) in session 0 was purged. > >> > > >> > For more information, see Help and Support Center at > >> > http://go.microsoft.com/fwlink/events.asp. > >> > > >> > (some more of these purges) PLUS many of what is below: > >> > -- > >> > for this particular time, there was a cd in the dvd drive with a bad > >> > sector > >> > - probably did not help... > >> > > >> > The device, \Device\CdRom0, has a bad block. > >> > > >> > For more information, see Help and Support Center at > >> > http://go.microsoft.com/fwlink/events.asp. > >> > > >> > > >> > -- > >> > Regards, > >> > Jamie > >> > > >> > > >> > "Les Connor [SBS MVP]" wrote: > >> > > >> >> Event logs, client and server please? > >> >> > >> >> -- > >> >> ----------------------------------------------- > >> >> Les Connor [SBS MVP] > >> >> > >> >> "thejamie" <thejamie(a)discussions.microsoft.com> wrote in message > >> >> news:841863AB-807A-48CF-A69E-4C2900AA7647(a)microsoft.com... > >> >> > I connect to the domain via a wireless access point - one job is to > >> >> > develop > >> >> > databases and frequently I move a large backup file from a laptop to > >> >> > the > >> >> > domain. Unfortunately, the connection is not always what it should > >> >> > or > >> >> > could > >> >> > be and the SBS DC interprets the missing packets as a bad sector on > >> >> > the > >> >> > hard > >> >> > disk, shuts down the domain... wow, so annoying! The simple > >> >> > solution > >> >> > is > >> >> > to > >> >> > never try to move a large file from the access point into the domain > >> >> > but > >> >> > that > >> >> > is not a practical solution for this infrastructure. > >> >> > > >> >> > Which is this. There is a WAP just over 50 feet away from my desk. > >> >> > It > >> >> > is > >> >> > authenticated through IAS and SBS sees it like a machine on the > >> >> > network. > >> >> > The > >> >> > IAS keeps just anyone from using it - anyone can login if they know > >> >> > the > >> >> > WAP > >> >> > password, but it won't get them authenticated. That part is fine. > >> >> > > >> >> > Since moving files conventionally seems to fail frequently I try to > >> >> > use > >> >> > the > >> >> > ESE.DLL in conjunction with the ESEUTIL.EXE that comes with Exchange > >> >> > and > >> >> > then > >> >> > pipe it: > >> >> > eseutil /y "G:\BIGFILE" /d "\\dcserver\Users\myspace\BIGFILE.bak" > >> >> > > >> >> > Neither this nor the file transfer method works. The minute the WAP > >> >> > gets > >> >> > fuzzy and some packets are lost, SBS says - aha, I lost the file - > >> >> > must > >> >> > be > >> >> > my > >> >> > hard disk so I am going to shut down and kaboom, down comes the > >> >> > domain. > >> >> > > >> >> > What can I do to fix the server so that it doesn't interpret the > >> >> > file > >> >> > transfers as a bad disk? > >> >> > > >> >> > Yep, I have been doing this for about a year - I go back, run the > >> >> > chkdsk > >> >> > for > >> >> > bad sectors on the mirror - nothing - the disks are fine. It is > >> >> > essentially > >> >> > something in the makeup of the way SBS is interpreting the file as > >> >> > it > >> >> > comes > >> >> > across from the WAP. > >> >> > > >> >> > If I didn't think it would raise hackles all over the place, I would > >> >> > call > >> >> > it > >> >> > a bug. Think of a disgruntled employee on a WAP and you'll get the > >> >> > picture. > >> >> > -- > >> >> > Regards, > >> >> > Jamie > >> >> > >> >> > >> >
From: Les Connor [SBS MVP] on 7 Feb 2009 11:54 totally weird, as far as I'm concerned ;-). But who's going to argue with what works - glad you got it resolved!. -- ----------------------------------------------- Les Connor [SBS MVP] "thejamie" <thejamie(a)discussions.microsoft.com> wrote in message news:45790766-2088-4C87-A49C-11A41A56808F(a)microsoft.com... > Thanks to all for the help. We have been up and running for a dozen days > without a crash on the DC. Solution seems to have been to place a > parabolic > antenna on the wireless access point. > > Ingenious... think someone here posted this or they sent me to a site with > this link. Whoever it was - double thanks. > > http://binarywolf.com/249/diy-parabolic-reflector.htm > > -- > Regards, > Jamie > > > "Les Connor [SBS MVP]" wrote: > >> The event log errors you're seeing are as a result of the server going >> down. >> You have to resolve the stop error, one way or another. >> >> -- >> ----------------------------------------------- >> Les Connor [SBS MVP] >> >> "thejamie" <thejamie(a)discussions.microsoft.com> wrote in message >> news:643DAFEC-1F3A-41D0-B361-69423754533E(a)microsoft.com... >> > I was able to get the crash with a machine inside the network: >> > >> > CLIENT MACHINE SAYS: >> > >> > The master browser has received a server announcement from the computer >> > MYDC >> > that believes that it is the master browser for the domain on transport >> > NetBT_Tcpip_{AE9618C6-E870-4AB3-AAA4-D6EDE7A1F0E4}. The master browser >> > is >> > stopping or an election is being forced. >> > >> > >> > -- >> > Regards, >> > Jamie >> > >> > >> > "Les Connor [SBS MVP]" wrote: >> > >> >> do analyses on that blue screen. >> >> >> >> http://blogs.technet.com/petergal/archive/2006/03/23/422993.aspx >> >> >> >> I'd suggest something wrong serverside. >> >> >> >> -- >> >> ----------------------------------------------- >> >> Les Connor [SBS MVP] >> >> >> >> "thejamie" <thejamie(a)discussions.microsoft.com> wrote in message >> >> news:763C1692-549E-458B-B3A0-8D77ACE99E2E(a)microsoft.com... >> >> > The server restart log is at 7:16 for this particular crash: >> >> > The client says: >> >> > The system failed to register host (A) resource records (RRs) for >> >> > network >> >> > adapter >> >> > with settings: >> >> > >> >> > Adapter Name : {7790AD42-FFC6-43CD-AF09-5F4275B39533} >> >> > Host Name : solsticedev >> >> > Primary Domain Suffix : terraatlas.local >> >> > DNS server list : >> >> > 192.168.16.2 >> >> > Sent update to server : <?> >> >> > IP Address(es) : >> >> > 192.168.1.2 >> >> > >> >> > The reason the system could not register these RRs was because >> >> > either >> >> > (a) >> >> > the DNS server does not support the DNS dynamic update protocol, or >> >> > (b) >> >> > the >> >> > authoritative zone for the specified DNS domain name does not accept >> >> > dynamic >> >> > updates. >> >> > >> >> > To register the DNS host (A) resource records using the specific DNS >> >> > domain >> >> > name and IP addresses for this adapter, contact your DNS server or >> >> > network >> >> > systems administrator. >> >> > >> >> > For more information, see Help and Support Center at >> >> > http://go.microsoft.com/fwlink/events.asp. >> >> > >> >> > The server code is a bit less revealing: >> >> > The reason supplied by user TERRAATLAS\Administrator for the last >> >> > unexpected >> >> > shutdown of this computer is: System Failure: Stop error >> >> > Reason Code: 0x805000f >> >> > Bug ID: >> >> > Bugcheck String: 0x0000007a (0xc03dcdb8, 0xc000000e, 0xf736e5ef, >> >> > 0x11ed1860) >> >> > Comment: 0x0000007a (0xc03dcdb8, 0xc000000e, 0xf736e5ef, 0x11ed1860) >> >> > >> >> > For more information, see Help and Support Center at >> >> > http://go.microsoft.com/fwlink/events.asp. >> >> > >> >> > >> >> > THEN >> >> > The Network Connections service was successfully sent a start >> >> > control. >> >> > >> >> > For more information, see Help and Support Center at >> >> > http://go.microsoft.com/fwlink/events.asp. >> >> > >> >> > >> >> > AND >> >> > >> >> > Error code 0000007a, parameter1 c03dcdb8, parameter2 c000000e, >> >> > parameter3 >> >> > f736e5ef, parameter4 11ed1860. >> >> > >> >> > For more information, see Help and Support Center at >> >> > http://go.microsoft.com/fwlink/events.asp. >> >> > >> >> > as it came BACK >> >> > >> >> > Printer Generic / Text Only (from SOLSTICEDEV) in session 0 was >> >> > purged. >> >> > >> >> > For more information, see Help and Support Center at >> >> > http://go.microsoft.com/fwlink/events.asp. >> >> > >> >> > (some more of these purges) PLUS many of what is below: >> >> > -- >> >> > for this particular time, there was a cd in the dvd drive with a bad >> >> > sector >> >> > - probably did not help... >> >> > >> >> > The device, \Device\CdRom0, has a bad block. >> >> > >> >> > For more information, see Help and Support Center at >> >> > http://go.microsoft.com/fwlink/events.asp. >> >> > >> >> > >> >> > -- >> >> > Regards, >> >> > Jamie >> >> > >> >> > >> >> > "Les Connor [SBS MVP]" wrote: >> >> > >> >> >> Event logs, client and server please? >> >> >> >> >> >> -- >> >> >> ----------------------------------------------- >> >> >> Les Connor [SBS MVP] >> >> >> >> >> >> "thejamie" <thejamie(a)discussions.microsoft.com> wrote in message >> >> >> news:841863AB-807A-48CF-A69E-4C2900AA7647(a)microsoft.com... >> >> >> > I connect to the domain via a wireless access point - one job is >> >> >> > to >> >> >> > develop >> >> >> > databases and frequently I move a large backup file from a laptop >> >> >> > to >> >> >> > the >> >> >> > domain. Unfortunately, the connection is not always what it >> >> >> > should >> >> >> > or >> >> >> > could >> >> >> > be and the SBS DC interprets the missing packets as a bad sector >> >> >> > on >> >> >> > the >> >> >> > hard >> >> >> > disk, shuts down the domain... wow, so annoying! The simple >> >> >> > solution >> >> >> > is >> >> >> > to >> >> >> > never try to move a large file from the access point into the >> >> >> > domain >> >> >> > but >> >> >> > that >> >> >> > is not a practical solution for this infrastructure. >> >> >> > >> >> >> > Which is this. There is a WAP just over 50 feet away from my >> >> >> > desk. >> >> >> > It >> >> >> > is >> >> >> > authenticated through IAS and SBS sees it like a machine on the >> >> >> > network. >> >> >> > The >> >> >> > IAS keeps just anyone from using it - anyone can login if they >> >> >> > know >> >> >> > the >> >> >> > WAP >> >> >> > password, but it won't get them authenticated. That part is >> >> >> > fine. >> >> >> > >> >> >> > Since moving files conventionally seems to fail frequently I try >> >> >> > to >> >> >> > use >> >> >> > the >> >> >> > ESE.DLL in conjunction with the ESEUTIL.EXE that comes with >> >> >> > Exchange >> >> >> > and >> >> >> > then >> >> >> > pipe it: >> >> >> > eseutil /y "G:\BIGFILE" /d "\\dcserver\Users\myspace\BIGFILE.bak" >> >> >> > >> >> >> > Neither this nor the file transfer method works. The minute the >> >> >> > WAP >> >> >> > gets >> >> >> > fuzzy and some packets are lost, SBS says - aha, I lost the >> >> >> > file - >> >> >> > must >> >> >> > be >> >> >> > my >> >> >> > hard disk so I am going to shut down and kaboom, down comes the >> >> >> > domain. >> >> >> > >> >> >> > What can I do to fix the server so that it doesn't interpret the >> >> >> > file >> >> >> > transfers as a bad disk? >> >> >> > >> >> >> > Yep, I have been doing this for about a year - I go back, run the >> >> >> > chkdsk >> >> >> > for >> >> >> > bad sectors on the mirror - nothing - the disks are fine. It is >> >> >> > essentially >> >> >> > something in the makeup of the way SBS is interpreting the file >> >> >> > as >> >> >> > it >> >> >> > comes >> >> >> > across from the WAP. >> >> >> > >> >> >> > If I didn't think it would raise hackles all over the place, I >> >> >> > would >> >> >> > call >> >> >> > it >> >> >> > a bug. Think of a disgruntled employee on a WAP and you'll get >> >> >> > the >> >> >> > picture. >> >> >> > -- >> >> >> > Regards, >> >> >> > Jamie >> >> >> >> >> >> >> >> >>
First
|
Prev
|
Pages: 1 2 3 4 5 Prev: SBS 2008 Migrate "a drive cannot be found" Next: AllSBSUsers Group Policy - doesn't exist |