Re: SBS Monitoring Issues

From: David Copeland [MSFT] (davidcop_at_online.microsoft.com)
Date: 08/30/04


Date: Sun, 29 Aug 2004 21:40:10 -0500

Fred,

That kinda makes me wonder if either the master database is corrupt.. From
the > prompt of osql try the following to see if it reports errors (you
might also check the ERRORLOG file in the \program files\microsoft sql
server\mssql$sbsmonitoring\log directory)

> dbcc checkdb
> go

As far as companyweb is the sharepoint instance of sql still there? running?
Companyweb disappearing from IIS doesn't sound related to the other issue..
Was anything done to IIS?

-- 
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Newsgroups:
SBS v4.x : microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Fred Orcutt" <anonymous@discussions.microsoft.com> wrote in message 
news:029801c48e15$9aa4b740$a401280a@phx.gbl...
> David,
>
> Thanks for taking a deeper look at this for me.  At
> the 'go' command, I get the following return:
>
> "Message 7105, Level 22, State 6, Server Sticker-
> 17e2br\SBSMONITORING, procedure sp_addsrvrolemember, Line
> 50
> Page <1:72>, slot 31 for text, ntext, or image node does
> not exist"
>
> Not sure if this indicates a syntax error on my part or
> more substantive.
>
> No, unfortunately, no backup :(.
>
> Also, Sharepoint Central and companyweb have disappeared
> from IIS list of webs.
>
> Thanks,
>
> Fred
>
>>-----Original Message-----
>>Fred,
>>
>>Sorry, I missed that part in the text.. saw the error
> message.. I was able
>>to reproduce the 103 event message after removing the
> BUILTIN\Administrators
>>from having login rights to the sbsmonitoring instance..
> and then re-adding
>>it.. but not putting the BUILTIN\Administrators group
> back into the SysAdmin
>>role
>>
>>If you are logged on to the server as Administrator.. are
> you still able to
>>logon to the sbsmonitoring instance using the following
>>
>>osql -E -S servername\sbsmonitoring
>>
>>If so trying doing the following at the > prompts
>>
>>> sp_addsrvrolemember N'BUILTIN\Administrators', sysadmin
>>> go
>>
>>Then see if the sqlagent$monitoring will start.
>>
>>Do you have backups of the sbsmonitoring databases?
>>
>>
>>-- 
>>
>>Hope that helps,
>>David Copeland
>>Microsoft Small Business Server Support
>>
>>This posting is provided "AS IS" with no warranties, and
> confers no rights.
>>
>>Newsgroups:
>>SBS v4.x : microsoft.public.backoffice.smallbiz
>>SBS 2000: microsoft.public.backoffice.smallbiz2000
>>SBS 2003: microsoft.public.windows.server.sbs
>>
>>
>>"Fred Orcutt" <anonymous@discussions.microsoft.com> wrote
> in message
>>news:23d901c48dec$cc64c190$a601280a@phx.gbl...
>>> David,
>>>
>>> As mentioned in my original post, sqlagent$sbsmonitoring
>>> is set for auto start as a local system account.
> However,
>>> it doesn't start at boot and won't start thereafter.  It
>>> terminates immediately after attempting to start it
> going.
>>>
>>> That's the problem I'm trying to resolve.
>>>
>>> Fred Orcutt
>>>
>>>>-----Original Message-----
>>>>Fred,
>>>>
>>>>For the 103 error regarding sqlagent$sbsmonitoring can
>>> you check in
>>>>Start/Administrative Tools/Services and see if the
>>> service is running and
>>>>should be configured to run as Local System.  You should
>>> be able to right
>>>>click on the service and select Properties and then
> click
>>> on the Log On tab
>>>>to set it to logon as Local System account (interact
> with
>>> desktop should not
>>>>be checked).
>>>>
>>>>With the SBSMonitoring instance it does need to be
>>> running in order to run
>>>>it's scheduled jobs to do things such as remove entries
>>> that are older than
>>>>90 days (by default) from the database.
>>>>
>>>>-- 
>>>>
>>>>Hope that helps,
>>>>David Copeland
>>>>Microsoft Small Business Server Support
>>>>
>>>>This posting is provided "AS IS" with no warranties, and
>>> confers no rights.
>>>>
>>>>Newsgroups:
>>>>SBS v4.x : microsoft.public.backoffice.smallbiz
>>>>SBS 2000: microsoft.public.backoffice.smallbiz2000
>>>>SBS 2003: microsoft.public.windows.server.sbs
>>>>
>>>>
>>>>"Fred Orcutt" <anonymous@discussions.microsoft.com>
> wrote
>>> in message
>>>>news:20c301c48d6c$a1d98cb0$a501280a@phx.gbl...
>>>>> My SBS2003 server has been experiencing a significant
>>>>> problem with monitoring.  The SQLAgent$SBSMonitoring
>>>>> service is set for auto startup under a local system
>>>>> account, but will not start on boot. When trying to
>>> start
>>>>> it, the message appears that it started and then
>>> stopped.
>>>>>
>>>>> Reports are transmitted as configured but the content
>>>>> states as follows:
>>>>> --------------------------------
>>>>>
>>>>> Server Error in '/' Application.
>>>>> ---------------------------------
>>>>> The resource cannot be found.
>>>>> Description: HTTP 404. The resource you are looking
> for
>>>>> (or one of its dependencies) could have been removed,
>>> had
>>>>> its name changed, or is temporarily unavailable.
> Please
>>>>> review the following URL and make sure that it is
>>> spelled
>>>>> correctly.
>>>>>
>>>>> Requested Url: /monitoring/perf.aspx
>>>>> ------------------------------------------
>>>>>
>>>>> The following appears in EV after any unsuccessful
>>> attempt
>>>>> to start up the service.  I cannot determine any
> obvious
>>>>> way to satisfy the requirement report in the event.
>>>>>
>>>>> ------------------------------------------
>>>>> Event ID: 103
>>>>> Source: SQLAgent$SBSMonitoring
>>>>>
>>>>> SQLServerAgent could not be started (reason:
>>>>> SQLServerAgent must be able to connect to SQLServer as
>>>>> SysAdmin, but '(Unknown)' is not a member of the
>>> SysAdmin
>>>>> role).
>>>>>
>>>>> -------------------------------------------
>>>>>
>>>>> Additionally, the CEICW will not complete, indicating
>>>>> firewall settings cannot be configured.  I have
>>>>> uninstalled and reinstalled IIS, but same result.
> Also,
>>>>> the default web site regurlarly stops and must be
>>>>> restarted.
>>>>>
>>>>> Expert help is appreciated!!
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Fred Orcutt
>>>>>
>>>>
>>>>
>>>>.
>>>>
>>
>>
>>.
>> 


Relevant Pages

  • Re: SYSTEMS ENGINEER/ VAX-VMS/ CAREER POSITION
    ... System Administration and database admin from NIIT, ... salary details and generate reports and enclosures,and calculates ... Responsibilities: ... Write New programs from user requirements, Programming Changes ...
    (comp.os.vms)
  • Re: Advice needed for a growing Access 2000 project
    ... However, it turned out that quite a few of those were "leftovers" from previous releases, no longer accessible from anywhere but the database window, and, thus, no longer used. ... But that certainly isn't the _norm_ -- without any 'heroic' measures, there are routine reports of split Access DBs ... Finally, in my opinion, for "Windows apps", that is, individual-user applications, modest-sized multiuser applications, and client-server applications of any size, Dot Net does NOT "help along" any of these issues. ... The post I reference was in reference its self to the MS Access Help file under "Microsoft Access database general specifications" ...
    (comp.databases.ms-access)
  • Re: running report cause fatal error- on Win98, not XP
    ... It is actually not that difficult to crash JET with complex queries, ... another query. ... only the more complex reports cause the crash- the others do ... Then compact the database: ...
    (microsoft.public.access.reports)
  • Re: running report cause fatal error- on Win98, not XP
    ... another query. ... only the more complex reports cause the crash- the others do ... Then compact the database: ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.reports)
  • Re: running report cause fatal error- on Win98, not XP
    ... In the final query that the report ... only the more complex reports cause the crash- the others do ... Then compact the database: ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.reports)