Re: WSUS 3.0 SP1 / MSSQL$SBSMonitoring saga

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Thanks for your reply Henrik

It would appear to be so in most cases. We have found servers with 2Gb RAM
running WSUS 2.0 don't give this error, but when WSUS 3.0 SP1 gets loaded,
the problem appears.

We look after about 30 SBS servers and this pattern is emerging, except for
on one server that does have 4Gb ram already. This is also a fairly recently
implemented server, so I am confident that it is not suffering form other
problems. In fact, the day after accepting and applying the WSUS 3.0 SP1
update, it reported the 'error'.


"Henrik (Hear)" wrote:

I have had that problems just a few times and Its has always been related to
the fact that the server was running out of resources (Ram etc).

I cant speak for your environment but can you relate to this, the lack of
resources?

//Henrik, MCP-SBS,

"SitsWithMouse" <SitsWithMouse@xxxxxxxxxxxxxxxxxxxxxxxxx> skrev i
meddelandet news:93FF82AF-E23D-4C22-A6A6-455C58BCC911@xxxxxxxxxxxxxxxx
hi Les

Yes, this one



An error occurred on the page you are trying to view.
________________________________________
To work around this problem, perform the following steps. After each step,
try again to access the page.
. Ensure that the MSSQL$SBSMONITORING service is started.
. Ensure that the server is not low on memory or disk space.
. Restart the server.
. Verify that the server is functional and that there are no system-wide
problems.
. Run the Set Up Monitoring Reports and Alerts task in the Server
Management
Monitoring and Reporting taskpad.


"Les Connor [SBS MVP]" wrote:

I'm not clear on what the problem is. Is it that the monitoring page
won't
render (display)?

--
Les Connor [SBS MVP]
________________________
Get the SBS BPA here:
http://support.microsoft.com/kb/940439/en-us


"SitsWithMouse" <SitsWithMouse@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:2A64AF3C-DA74-4C19-BE71-3E1B64AD1A60@xxxxxxxxxxxxxxxx
Good morning forum

Has anyone found a solution to the WSUS 3.0 SP1 and MSSQP$SBSMonitoring
issue that works and stays working?

I have read some of Les's posts but they were followed with posts that
appear as though the problem still exists?

Its quite frustrating as the reports work for a number of days, then
the
SBSMonitoring page gets emailed and then it works again the following
days
with no intervention.






.

Relevant Pages

  • RE: Unable to reconnect other second server to SBS
    ... Small Business Server 2003-based computer ... This newsgroup only focuses on SBS technical issues. ... Your SBS server is not generating reports any more. ... |> here after we resolve the first issue. ...
    (microsoft.public.windows.server.sbs)
  • Re: Best practice on virtualizing SBS
    ... Would the /3GB switch give me problems if I only have 3 GB of ram and not 4? ... If you do install a full HostOS, then make the HostOS a Standalone Server ... and install SBS with any other OS as Guests. ... At the moment my SBS is running on 1GB of ram, the host box will get 3GB ...
    (microsoft.public.windows.server.sbs)
  • Re: Virtual Server on SBS
    ... SBS) won't be able to recognise it. ... can only use 4 GB of RAM. ... Since you're 2800 is running your SBS server, you are in 32 bit mode, ... So I'd need a device CAL for Virtual Server? ...
    (microsoft.public.windows.server.sbs)
  • Re: Virtual Server on SBS
    ... I wasted my money then on the extra RAM. ... can get a used box to handle MOSS and get by until the 64-bit version of SBS ... So I'd need a device CAL for Virtual Server? ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS
    ... Les Connor [SBS MVP] ... Is your server exhibiting significant performance problems, and if so, how ... SQL Server: ... >No wonder SBS brings servers with 4GB of RAM to their knees. ...
    (microsoft.public.windows.server.sbs)