Re: SBS about to die?
- From: "Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx>
- Date: Sun, 17 Feb 2008 14:47:21 -0500
You might also want to download, install and run a scan with the SBS 2003
BPA to see if it can find any problems with your configuration:
Microsoft Windows Small Business Server 2003 Best Practices Analyzer
http://www.microsoft.com/Downloads/details.aspx?familyid=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en
How to Use the Windows SBS 2003 BPA
http://blogs.technet.com/sbs/archive/2007/10/22/how-to-use-the-windows-sbs-2003-bpa.aspx
--
Merv Porter [SBS-MVP]
============================
"Billy Burrows" <billy.burrows@xxxxxxxxxxxx> wrote in message
news:sVZtj.803$ay3.677@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for your help!
I did check the obvious including free drive space and RAM, a quick look
for any obvious hardware issues and a malware scan.
I will def go check everything on eventid.net and cross my fingers.
The driver issue, is that because a client machine has the driver and the
server does not? If so is it worth installing it on the server? It only
seems to happen when I connect via remote desktop or VPN?
Thanks
"Jim Behning SBS MVP" <jimbehning@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:taogr3p7oj1v7nvh0um17bbgs7q21om955@xxxxxxxxxx
That driver is nothing to worry about.
How much space free on your C: drive? Have you deleted old temp files
off the C: and run a defrag. Low idle time could be the server is
spending too much time search for fragmented files.
Those other errors you can probably work through to decide if they are
critical or not.
www.eventid.net is where I go when warning events concern me.
On Sun, 17 Feb 2008 12:47:49 GMT, "Billy Burrows"
<billy.burrows@xxxxxxxxxxxx> wrote:
Hi guys, thanks for taking a look see @ my nightmare!
I have had SBS running for about a year but now im getting all these
errors
croping up in the log and im a little concerned! I suspect a re-install
is
going to be required but just in case one of you guru's has an idea
please
take l look at the logs below.
I have looked at the Microsoft support pages for these and really dont
fancy
editing config files directly!
In the event the thing is boned how do I backup (file shares, public
folders
etc) to guarante restore will work, last time it point blank refused to
use
the backups.
Recent history involves adding a security certificate and we have had
issues
with our service provider messing up the configs of our router so OWA RWW
and VPN all stopped working due to port forwards being removed, they are
fixed now and would somethinglike that cause the errors below?
I have had (for a while) warnings about low idle time on C: drive and
processes consuming high amounts of RAM but again can they be related?
Also
events in the log complaining about print drivers not being known, I
think
this is because some clients have printers installed on them that are not
installed on the server, should they be installed on the server too?
Regardless of all the errors everything does appear to be working?
Any and all help will be seriously appreciated!
Server name is replaced with "****" in the logs below
Thanks :-)
Critical Errors in Application Log
Source
Event ID
Last Occurrence
Total Occurrences
SQLAgent$SHAREPOINT
324
16/02/2008 13:47
1
SQLAgent is not allowed to run.
Source
Event ID
Last Occurrence
Total Occurrences
dsrestor
1005
16/02/2008 12:27
1
The DSRestore Filter failed to connect to local SAM server.
Error returned is <id:997>.
Source
Event ID
Last Occurrence
Total Occurrences
MSExchangeDSAccess
2103
16/02/2008 12:20
1
Process MAD.EXE (PID=2856). All Global Catalog Servers in use
are not responding: ****FILESERVER.****.Server For more information,
click
http://www.microsoft.com/contentredirect.asp.
Source
Event ID
Last Occurrence
Total Occurrences
Windows SharePoint Services 2.0
1000
16/02/2008 12:20
1
#50070: Unable to connect to the database
STS_****FILESERVER_1
on ****FILESERVER\SharePoint. Check the database connection information
and
make sure that the database server is running.
Source
Event ID
Last Occurrence
Total Occurrences
MSExchangeAL
8026
16/02/2008 12:20
3 *
LDAP Bind was unsuccessful on directory
****FILESERVER.****.Server for distinguished name ''. Directory returned
error:[0x51] Server Down. For more information, click
http://www.microsoft.com/contentredirect.asp.
Source
Event ID
Last Occurrence
Total Occurrences
MSExchangeAL
8250
16/02/2008 12:20
1
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.
Source
Event ID
Last Occurrence
Total Occurrences
MSExchangeDSAccess
2102
16/02/2008 12:20
1
Process MAD.EXE (PID=2856). All Domain Controller Servers in
use
are not responding: ****FILESERVER.****.Server For more information,
click
http://www.microsoft.com/contentredirect.asp.
Source
Event ID
Last Occurrence
Total Occurrences
SQLAgent$SBSMONITORING
318
16/02/2008 12:19
1
Unable to read local eventlog (reason: The event log file has
changed between read operations).
Source
Event ID
Last Occurrence
Total Occurrences
Userenv
1030
16/02/2008 11:43
57 *
Windows cannot query for the list of Group Policy objects.
Check
the event log for possible messages previously logged by the policy
engine
that describes the reason for this.
Source
Event ID
Last Occurrence
Total Occurrences
Userenv
1058
16/02/2008 11:43
57 *
Windows cannot access the file gpt.ini for GPO
CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=****,DC=Server.
The file must be present at the location
<\\****.Server\sysvol\****.Server\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.
(Configuration information could not be read from the domain controller,
either because the machine is unavailable, or access has been denied. ).
Group Policy processing aborted.
Critical Errors in Security Log
Source
Event ID
Last Occurrence
Total Occurrences
Security
537
16/02/2008 12:20
2 *
Logon Failure:
Reason:
An error occurred during logon
User Name:
****FILESERVER$
Domain:
****.SERVER
Logon Type:
3
Logon Process:
Kerberos
Authentication Package:
Kerberos
Workstation Name:
-
Status code:
0xC00000DC
Substatus code:
0x0
Caller User Name:
-
Caller Domain:
-
Caller Logon ID:
-
Caller Process ID:
-
Transited Services:
-
Source Network Address:
-
Source Port:
-
* The text shown is for the most recent occurrence of this event. For
more
information, see the Event log.
Critical Errors in System Log
Source
Event ID
Last Occurrence
Total Occurrences
TermServDevices
1111
16/02/2008 12:53
4 *
Driver Send To Microsoft OneNote Driver required for printer
Send To OneNote 2007 is unknown. Contact the administrator to install the
driver before you log in again.
.
- Follow-Ups:
- Re: SBS about to die?
- From: Billy Burrows
- Re: SBS about to die?
- References:
- SBS about to die?
- From: Billy Burrows
- Re: SBS about to die?
- From: Jim Behning SBS MVP
- Re: SBS about to die?
- From: Billy Burrows
- SBS about to die?
- Prev by Date: Re: SBS2003 SP2 / Exchange 2003 SP2 / Outlook 2003 SP3
- Next by Date: Re: Remote Web Desktop
- Previous by thread: Re: SBS about to die?
- Next by thread: Re: SBS about to die?
- Index(es):
Relevant Pages
|
