• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1823
  • Last Modified:

SBS 2008 Post Installation Issues, WSUS, SQL

Hi Guys,

This is another sbs 2008 post install problem i'm having.

Everything installed nicely then I did updates and had a profile problem(with the default admin account created when installing sbs2008), so I renamed profile pathand deleted the reg entry...
HKLM\Software\Microsoft\Windows NT\Current Version\ProfileList relevant user entry...
logged off and logged on again (this fixed profile prob) then I noticed a few other things wrong.

So I'm not sure if the profile fix caused the problems or if it was the updates, as I simply hadnt noticed them while I was trying to fix profile issue.

The last update I installed was MS SQL Server Ex with adv Services service pack 3 (kb955706)

The first thing I noticed was WSUS was not reporting in the SBS console, I then noticed that the Security tab in the console wasnt reporting and the printer wasnt being listed in devices.

So I open Update services snap in in advanced management console, to find a big red X. So I tried to connect to server but couldnt.

So I then tried to open SQL Express Server management but it failed to open.

The event viewer shows the following, on server startup I get 2 identical warnings for SQLBrowser, "SBSMONITORING" and "MICROSOFT##SSEE"...

The configuration of the AdminConnection\TCP protocol in the SQL instace "" is not valid.

When SQL manager crases on startup I get the following info...

Prob event name:              appcrash
App name:                         ssmee.exe
app version:                      2005.90.4035.0
app timestamp:                  492b1643
fault module name:            kernel32.dll
fault module version:         6.0.6001.18000
fault module timestamp:        4791a81d
exception code:                e06d7363
exception offset:                0002f35f
os version:                         6.0.6001.2.1.0.305.9

So back to security tab in console, when i click "view summary of virus protection or view summary of spyware protection I get the message, 'No computers were found'.

The reason I'm giving all this info is I cant help but think its all related to same issue, but that is where I become stuck.

Thanks for the help.
Shaun
0
easiman
Asked:
easiman
  • 2
1 Solution
 
wolfman007Commented:
Check which port SQL Server Express is running on?

Also can you connect locally by doing "sqlcmd -S.\sqlexpress" at the command prompt locally on the machine?

You could also try manually setting the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\<MSSQL.x>\MSSQLServer\SuperSocketNetLib\AdminConnection\Tcp

NOTE: <MSSQL.x> is the SQL instance. The default instance is "MSSQL.1"

Please change the value "TcpDynamicPort" to 1434 and then click Start->Run,
type: Services.msc -> Restart the SQL Server Browser service and then check
if the error still appears.

NOTE: Using Registry Editor incorrectly can cause serious problems that may
require you to reinstall Windows. Microsoft cannot guarantee that problems
resulting from the incorrect use of Registry Editor can be solved. Use
Registry Editor at your own risk.
sqlcmd -S.\sqlexpress

Open in new window

0
 
easimanAuthor Commented:
Thanks for the help.

How do I check which port?

When I try to connect locally at the command prompt i get the following...

HResult 0x2, Level 16, State 1
Named pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An Error has occurred while establishing a connection to the server. When connecting to SQL Server 2005. this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

When I look up the registry key above the path stops at...

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\<MSSQL.x>\MSSQLServer\SuperSocketNetLib

the only entry I have at this point is 'Np', nothing else.

I Hope this sheds some light.
Thanks
0
 
easimanAuthor Commented:
Turns out the profiles were corrrupt so i had to delete them and start again
0
 
PeteSheehanCommented:
What profiles were corrupt and how did you delete them?  

Thanks, I am getting this exact same error and I want to clarify exactly what was done before I assume incorrectly.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now