Annoying Crashes on SBS
|
From: Les Connor [SBS MVP] on 24 Jan 2009 20:15 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: thejamie on 24 Jan 2009 20:15 Errors only related to wifi... If I am on the network I can move files that are as large as the disk size will allow... and they (the Raid 1 drive) are half tbyte... I've been thinking about the N... this one is a G. The BAK files are normally about 20 gig or so. Not sure if I mentioned that in addition to the DC, there is a SQL 2005 Ent running on a File Server Win2003 64 bit Ent. DC is 32 bit. Thanks for all the questions from everyone. It helps lead me in a better direction. I'm beginning to suspect it may actually be the way the wireless is connection is setup (RADIUS aka IAS on SBS). Likely that something is not configured correctly. I'm sure I am not the only one who has trouble with wifi. -- Regards, Jamie "Russ (www.SBITS.Biz)" wrote: > I move large files over my Wireless network often > Usually less than 2GB > But I've done 5GB with no issues. > But never seen this error before. > How big are these files? > 10GB? > > I'd be thinking there is an issue with your SBS server. > is it a PC with SBS on it? or a Real Server with Plug in RAID cards? > (And RAID1 RAID5 or Other) > > What kind of HD's do you have in the SBS server? > ATA? SATA? SCSI? > How Old is the Server? > > You can use FileZilla, FTP Server > But if the SBS Server DIES because of I/O error I think the issue is The > server > and not the file transfer... > > If you do think this is wifi related > when you use a 50' Cable do you get these errors? > > If not, Is your Wifi a N type? or B or G? > > Russ > > -- > Russell Grover - SBITS.Biz > Microsoft Gold Certified Partner > Microsoft Certified Small Business Specialist > World Wide 24hr SBS Remote Support - http://www.SBITS.Biz > > > "thejamie" <thejamie(a)discussions.microsoft.com> wrote in message > news:AD1ECEB8-39BC-4087-B5EF-B393C2EA4A8F(a)microsoft.com... > > FTP... ok, but what is the SCP or (ech)? > > I hadn't thought of FTP. I generally don't turn it on because I get so > > many > > unsolicited attempts to break in. > > -- > > Regards, > > Jamie > > > > > > "Joe" wrote: > > > >> thejamie wrote: > >> > 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. > >> > >> Have you tried a file transfer system, such as Filezilla, SCP or (ech) > >> FTP? It's going to take longer than CIFS/SMB, but fault tolerance always > >> comes at a price. A reliable protocol is just an unreliable one with > >> lots of patience. > >> > >> -- > >> Joe > >> > > >
From: thejamie on 25 Jan 2009 06:51 Thanks Les... always wondered about those numbers. This is a great answer. -- 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: thejamie on 25 Jan 2009 08:25 Good idea but a dead end. I ran tests against the server memory with UBCD - memory passes all tests - according to the debugger, the problem is memory. This leads me back to my original conclusion. If I try to move a large file from the Access Point over the wireless to the server, the server will crash. I put the latest crash events in at the end. I guess the question is why is there a failure to register the A record? Do I have the server set up incorrectly? Microsoft (R) Windows Debugger Version 6.10.0003.233 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\MEMORY.DMP] Kernel Summary Dump File: Only kernel address space is available Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x86 compatible Product: LanManNt, suite: SmallBusiness TerminalServer SmallBusinessRestricted SingleUserTS Built by: 3790.srv03_sp2_gdr.080813-1204 Machine Name: Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8 Debug session time: Sun Jan 25 07:25:26.549 2009 (GMT-5) System Uptime: 1 days 0:18:35.515 Loading Kernel Symbols ................................................................ .......................................................... Loading User Symbols Loading unloaded module list .. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7A, {c03dcbe8, c000000e, f72fa122, 1562f860} Probably caused by : memory_corruption Followup: memory_corruption --------- LATEST CRASH EVENT SERVER The reason supplied by user TERRAATLAS\Administrator for the last unexpected shutdown of this computer is: Other (Unplanned) Reason Code: 0xa000000 Bug ID: Bugcheck String: Comment: pass_me For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. CLIENT 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. -- 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: thejamie on 25 Jan 2009 08:49 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
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: SBS 2008 Migrate "a drive cannot be found" Next: AllSBSUsers Group Policy - doesn't exist |