SBS Microsoft ##SSEE

[bigfoot6]

Hi

I've done some reading on the internet, and there are some questions that are simular to mine, but not the exact same problem....

On my SBS 2003 R2 box (SP2 - 6GB of RAM) there is a sql process thats taking up to 600MB of RAM. When the box is first turned it starts off at 100MB and will grow the longer its been on. This has been been causing allocated memory alerts in my system monitor. I tracked down the pid to Microsoft##SSEE instance.

Now this is where my problem is slightly different. The SBS system montoring tool, when seleted from the server management tool, will spend 5 mins "loading" in which time this process will hit over 70% then it will bomb out... If you then "repair" the this feature and reset it back up it will work for a few days then, not work again.
The same is true when selecting the update services tab...

I installed SQL management studio express, to see if I could connect to this particular instance, and I get an error stating that "remote connections my not be enable for this instance" (If you would like the exact error let me know and I'll get it for you as it's not to hand at the moment.)

So my question is obviously how do I fix this, as it sounds like the instance is screwed, and what is dependant on ##SSEE.

Many Thanks

[Zenon]

Have a look on this thread - MSSQL$MICROSOFT##SSEE : Access to table dbo.backupmediaset is blockedbecause the signature is not valid., it might help you !!