Re: Microsoft##SSEE SQL Server (what is it?)

Additional note:

I checked the Output log file and it contains this:

Changed database context to 'SUSDB'.
Using SUSDB
No work to do. Record already exists.
Automatic Approval For Detection is already enabled
Target group of approval for detection is not "AllComputers"
Inserting "AllComputers" group
"AllComputers" Group added
Msg 156, Level 15, State 1, Server \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query, Line 40
Incorrect syntax near the keyword 'IF'.

So there appears to be something wrong in the script!

Siv


"Siv" <g@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:1F1D0D7F-2684-464D-919E-6A257A859D75@xxxxxxxxxxxxxxxx
Jon,
I went through your procedure:

I read through the KB article.

I downloaded and updated to WSUS 3.0 SP1 that went fine.

I ran the script in "Method 2" of KB 945985 it seemed to execute without error, my only concern with the script is that the grey block containing the script had scrollbars but in IE7 when I view the page they are greyed out and being a developer I know there should be some more code beyond what I could see (at least and "END IF") I copied the file to notepad and saved it as per the instructions but I am concerned there is more code that you just can't get from the website.

Does anyone have the full script as a text file that I could download as I am concerned that there was more than just an END IF and I have only run a fraction of the script.

Needless to say after running the script nothing has changed. I tried to do it manually using Method 1 but got stumped by the first option as it says "Under Automatic Approvals" ... well in WSUS console 3.0 SP1 there is no entry for "Automatic Approvals" that I can see??

Any help appreciated as I am going nowhere at the moment.

I did manage to download the Express SQL Server 2005 management studio and drop the database memory footprint to 256MB though so that should help!

Siv


"Siv" <g@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:09FCC4F6-F709-4E55-B82E-F58810A92428@xxxxxxxxxxxxxxxx
Jon,
Phew!!

I will have a bash at this when I have a few hours to spare which probably won't be until later this week as this looks quite a procedure.

I'll report back here when I have completed your suggested steps.

Thanks for all your help!

Siv

"Jon-Alfred Smith" <jonsmi@xxxxxxxxxxxxxxxx> wrote in message news:4gt3s39jgqj151osvdadi5n24qh993epeg@xxxxxxxxxx
On Sun, 24 Feb 2008 20:53:59 -0000, "Siv" <g@xxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

You are right, somewhere a while a go I ran a best practices tool from
Microsoft and it recommended that I upgrade WSUS, I followed the procedure
and am running that OK but as you say, it isn't integrated into the normal
"Server Management" tool, when I click WSUS I get this:

"Windows Small Business Server (Windows SBS) Update Services is not running
because it automatically turns off if you customize Windows Server Update
Services (WSUS). For a list of specific settings that cause Windows SBS
Update Services to turn off, see the Microsoft Web site. Even if WSUS is
managing updates for your network, the accuracy of the status in the Windows
SBS monitoring report or on the Update Services home page cannot be
guaranteed. To use Windows SBS Update Services, reverse the changes that you
have made to WSUS or reinstall Windows SBS 2003 R2. "

(1) All right this is addressed by "Software updates are not managed
by Microsoft Windows Small Business Server 2003 Update Services."
http://support.microsoft.com/kb/921910

However, you might perhaps want to take it a step further:

"WSUS 3.0 SP1 is now RTM."
http://blogs.technet.com/wsus/archive/2008/02/07/wsus-3-0-sp1-is-now-rtm.aspx

(2) Download Windows Server Update Services 3.0 SP1:
http://www.microsoft.com/downloads/details.aspx?FamilyId=F87B4C5E-4161-48AF-9FF8-A96993C688DF&displaylang=en

(3) "Software updates are not managed by Windows Small Business Server
2003 Update Services after you upgrade to Windows Server Update
Services 3.0 Service Pack 1."
http://support.microsoft.com/kb/945985/en-us

I did not do any effort on integrating WSUS with Server Management
before I had installed WSUS 3.0 SP1, so I skipped step 1, and it
really works with step 2 and 3.

But you are not finished yet. Seems like a lot of folks have
experienced that the instance of embedded SQL 2005 is quite
memory-hungry. After just some hours, PF Usage moved from 2,40 GB to
3,20 GB (and this is before I'm going to reinstall Symantec Endpoint
Protection management tools that take another 1/2 GB).

Basically virtual memory handling in Windows is not very easy to grasp
(some parts are next to completely incomprehensible). And it does not
get any better with the addition of SQL Server, which is quite
comfortable with grasping up to 2 GB, however, cooperative as well
with releasing needed memory.

To make a long story short, I left the thinking to the SBS Diva (she
seems to have done quite lot of it). However, you need SQL Server "SQL
Server Management Studio Express", a free download from
http://msdn.microsoft.com/vstudio/express/sql/download/

That is, if you have the PE and SQL 2005 with SQL Server Management
Studio, you can drop this step.

Then go to the Diva. I'm currently experimenting with a limit of 256
MB for the Microsoft##SSEE instance.

http://msmvps.com/blogs/bradley/archive/2007/12/25/adjusting-sql-embedded-instances.aspx

Was all this worth it? Definitely. As far as I can tell, WSUS 3.0/SP1
represents a vast improvement of what I believe is WSUS 2.0.

jas



.

Relevant Pages

  • Re: A fatal error occurred either while synchronizing the Update Services computer groups
    ... Please perform the WSUS 2.0 uninstall steps to confirm that you had ... The MSIZap.exe utility is included with the Microsoft Windows Server 2003 ... Installing Microsoft Windows Server Update Services 3.0 on Windows Small ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS - no longer working
    ... The SP2 is specific for Windows ... Windows 2003 service pack 2 known issues on Small Business Server 2003 ... to collect the MPS WSUS report on SBS. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Microsoft##SSEE SQL Server (what is it?)
    ... I downloaded and updated to WSUS 3.0 SP1 that went fine. ... I did manage to download the Express SQL Server 2005 management studio and drop the database memory footprint to 256MB though so that should help! ... For a list of specific settings that cause Windows SBS ... Update Services to turn off, ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS - no longer working
    ... Your WSUS 2.0 does not work after failed upgrade to WSUS 3.0, ... After you recover the server, ... Open Windows Explorer to the hard disk volume that contains the most ... This is the database backup file that was created while installing WSUS ...
    (microsoft.public.windows.server.sbs)
  • Re: Microsoft##SSEE SQL Server (what is it?)
    ... Microsoft and it recommended that I upgrade WSUS, ... because it automatically turns off if you customize Windows Server Update ... For a list of specific settings that cause Windows SBS ... Update Services to turn off, ...
    (microsoft.public.windows.server.sbs)