RE: Event 19011: SBS Monitoring services wont auto-start
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Mon, 14 Aug 2006 11:08:35 GMT
Hi Alex,
Thanks for using the SBS newsgroup.
From your description, I understand the issue is that the SBS monitoringservice can not auto-start and the Pop3 Virtual Server can not be
automatically start when rebooting the SBS server. If I am off base, please
don't hesitate to let me know.
Let us perform the following steps to isolate the issue:
1. Let us ensure the MSSQL$SBSMONITORING service and the Microsoft Exchange
POP3 service is configured start type as "Automatic". To do so:
1). Ensure that the MSSQL$SBSMONITORING service and SQLAgent$SBSMonitoring
service startup type is Automatic. Click Log on tab, please ensure check
the box of "Local System Account".
The detail steps: Go to Start/Administrative Tools/Services then double
click on SQLAgent$SBSMonitoring and change the startup to automatic and
start the service.
2). Double-click "Microsoft Exchange POP3" service to ensure startup type
as "Automatic". And click Log on tab, please ensure check the box of "Local
System Account".
2. If above issue persists, let us book a non-business time and perform a
clean boot on the server to check if it is third party application
conflicts.
1) Run MSCONFIG.EXE.
2) In the Services tab, click "Hide All Microsoft Services" and click
"Disable All".
3) In the Startup tab, click "Disable All". Click OK. (This will
temporarily prevent third-party programs from running automatically during
start-up.)
4) Restart the computer and check whether the problem still persists.
If the issue persists, please help me collect the following information for
analyze:
1. Please clean the Event logs in event viewer and then reboot the server,
then please collect the System, Application and Security log files for
analyze.
Please save the System, Application and Security log files as .evt format
and send to my working mailbox: v-yanniw@xxxxxxxxxxxxx
2. Please run the following command to get system information for analyze.
To do so:
a. Click Start and then Run.
b. Type in "msinfo32" without the quotations and click OK.
c. Once System Information is up and running, click File and then Save.
Save the system information to a .nfo file.
I appreciate your time. I am happy to be of assistance to you and look
forward to your reply.
Have a nice day!
Sincerely,
Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: "AlexBohner" <alexbohner@xxxxxxxxx>20:37:05 GMT)
Newsgroups: microsoft.public.windows.server.sbs
Subject: Event 19011: SBS Monitoring services wont auto-start
Date: 13 Aug 2006 13:37:00 -0700
Organization: http://groups.google.com
Lines: 38
Message-ID: <1155501420.432277.56610@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 69.171.107.76
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1155501425 31546 127.0.0.1 (13 Aug 2006
X-Complaints-To: groups-abuse@xxxxxxxxxxNET CLR 1.1.4322),gzip(gfe),gzip(gfe)
NNTP-Posting-Date: Sun, 13 Aug 2006 20:37:05 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1;
Complaints-To: groups-abuse@xxxxxxxxxxTK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!msrtrans!n
Injection-Info: 75g2000cwc.googlegroups.com; posting-host=69.171.107.76;
posting-account=rnuOPQ0AAACUY7dAvCASm995a_7n1JD0
Path:
ewsfeed.media.kyoto-u.ac.jp!postnews.google.com!75g2000cwc.googlegroups.com!
not-for-mail
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:289365
X-Tomcat-NG: microsoft.public.windows.server.sbs
Hi all,
I have been running running SBS2003 SP1 for about 18 months with no
issues at all. About 2 months ago I started receiving the following
notification upon rebooting the server:
Event Type: Warning
Event Source: MSSQL$SBSMONITORING
Event Category: (8)
Event ID: 19011
Date: 8/12/2006
Time: 1:24:10 AM
User: N/A
Computer: ZEUS
Description:
The description for Event ID ( 19011 ) in Source ( MSSQL$SBSMONITORING
) cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a
remote computer. You may be able to use the /AUXSOURCE= flag to
retrieve this description; see Help and Support for details. The
following information is part of the event: (SpnRegister) : Error 1355.
Although the service wouldn't start at boot it wasn't a show-stopper
because the service starts fine manually. Then, about 2 weeks ago,
after a reboot, I could no longer POP3 into the box. A little
investigation showed that the Pop3 Virtual Server wasn't started in the
Exchange System Manager. A quick right click->Start and it's up and
running again.
I suppose it isn't a big deal since I can start the services manually
after each reboot, but I'm a bit concerned that something bigger may be
happening here. Does anyone have any insight to this problem, or have
suggestions where I should start looking? Thanks for any suggestions
or help tracking down possible problems.
Thanks,
Alex
.
- References:
- Event 19011: SBS Monitoring services wont auto-start
- From: AlexBohner
- Event 19011: SBS Monitoring services wont auto-start
- Prev by Date: Re: Alert notifications
- Next by Date: Re: Trend Micro Firewall in SBS Environment (Problems)
- Previous by thread: Event 19011: SBS Monitoring services wont auto-start
- Next by thread: Re: does exchange server have to default profile?
- Index(es):
Relevant Pages
|