Inherited a Win Server 2003 mess

[maliawit]

I recently started working for a small printing business that uses Windows Server 2003, which was installed just a few weeks ago. The person who did the initial install did so with no plan and left no information regarding how the network was configured when they quit a few days ago. I have never used Win Server 2003 and am a bit of a loss as to where I should start trying to figure out what's going on. When I boot the server up I get a myriad of errors (logs below) and PC's on the network are unable to share files/printers and just generally don't seem to be networked.

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 2/21/2006
Time: 11:43:25 AM
User: N/A
Computer: INKITFS01
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information. The service could not be initialized. Make sure that the operating system was installed properly.

For more information, click

http://www.microsoft.com/contentredirect.asp.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 2/21/2006
Time: 11:43:25 AM
User: N/A
Computer: INKITFS01
Description:
LDAP Bind was unsuccessful on directory inkitfs01.InkIt.local for distinguished name ''. Directory returned error:[0x51] Server Down.

For more information, click

http://www.microsoft.com/contentredirect.asp.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 2/21/2006
Time: 11:43:24 AM
User: N/A
Computer: INKITFS01
Description:
LDAP Bind was unsuccessful on directory inkitfs01.InkIt.local for distinguished name ''. Directory returned error:[0x51] Server Down.

For more information, click

http://www.microsoft.com/contentredirect.asp.

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 2/21/2006
Time: 11:43:19 AM
User: N/A
Computer: INKITFS01
Description:
Process MAD.EXE (PID=2776). All Domain Controller Servers in use are not responding:
inkitfs01.InkIt.local


For more information, click

http://www.microsoft.com/contentredirect.asp.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 2/21/2006
Time: 11:43:18 AM
User: N/A
Computer: INKITFS01
Description:
LDAP Bind was unsuccessful on directory inkitfs01.InkIt.local for distinguished name ''. Directory returned error:[0x51] Server Down.

For more information, click

http://www.microsoft.com/contentredirect.asp.

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2104
Date: 2/21/2006
Time: 11:43:17 AM
User: N/A
Computer: INKITFS01
Description:
Process INETINFO.EXE (PID=884). All the DS Servers in domain are not responding.

For more information, click

http://www.microsoft.com/contentredirect.asp.

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

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 2/21/2006
Time: 11:47:29 AM
User: N/A
Computer: INKITFS01
Description:
Faulting application BRSVC01A.EXE, version 1.0.0.2, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 42 52 53 ure BRS
0018: 56 43 30 31 41 2e 45 58 VC01A.EX
0020: 45 20 31 2e 30 2e 30 2e E 1.0.0.
0028: 32 20 69 6e 20 75 6e 6b 2 in unk
0030: 6e 6f 77 6e 20 30 2e 30 nown 0.0
0038: 2e 30 2e 30 20 61 74 20 .0.0 at
0040: 6f 66 66 73 65 74 20 30 offset 0
0048: 30 30 30 30 30 30 30 0000000


I'm wondering if I should try to fix this mess or if I should just start over. I was planning to download/install the service pack, but not sure if that would help or hurt my situation. Any input is greatly appreciated.

 

[cbrunet17]

Seems like it all has to do with exchange. Is there alot of data currently on the server? Would it really be that difficult to redo the server? YOu might simply try uninstalling Exchange 2003 and seeing how the system boots that way. You'll lose mailboxes and everything, but your active directory will still be intact, and if it was just created 2 weeks ago, there cant be that much information in users mailboxes. I think you could also export the mailbox also if your that worried about data loss.

 

[maliawit]

Actually, after poking around some I realized they don't even use Exchange here. Everyone uses internet-based mail, so uninstalling Exchange may solve my problems. Thanks for that

I did manage to get all the pc's talking to each other and mapped to the various drives/printers/copiers we use here, so things are looking up...finally.

 

[58sniper]

Some of those error's you'll see if you're in the process of rebooting, shutting down, or booting the server.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)