MICROSOFT##SSEE blocks Surface Area Configuration in SQL 2005?

I am running a Windows Small Business Server with SQL Server 2005 on it. I am having a problem in that one of the applications I'm running needs to acess the xp_cmdshell component which is disabled by default. The problem I'm running into is, trying to run the Surface Area Configuration Wizard to turn this on fails because the system is unable to access the MICROSOFT##SSEE instance on the machine.

I dont want to modify the MICROSOFT##SSEE instance, I want to modify a different instance but the wizard detects ALL instances of SQL and craps out trying to access the MICROSOFT##SSEE instance.

Is there a way for me to activate the xp_cmdshell component on other instances without the wizard?

Hi,

Run this code in your query window:

Code Snippet

sp_configure 'xp_cmdshell', 1

reconfigure

Regards,

Janos

|||

I get the following message:

Msg 15123, Level 16, State 1, Procedure sp_configure, Line 51

The configuration option 'xp_cmdshell' does not exist, or it may be an advanced option.

|||

Hi Ron,

First you need to switch on the advanced options, then configure the xp_cmdshell.

run this please:

Code Snippet

sp_configure 'show advanced options', 1

reconfigure

sp_configure 'xp_cmdshell', 1

reconfigure

regards,

Janos

|||Thank you, that did the trick... now I just have to get my code to work <grin>

Microsoft SQL Server, Error: 10060

Every now and then I receive this error, usually when trying to
establish a connection to a new server. I checked and confirmed in
surface area configuration that remote connections are enabled across
tcp/ip. Also there are no firewall issues. This is sql server 2005. Any
ideas? Thank you.
TITLE: Connect to Server
--
Cannot connect to magneto2.
ADDITIONAL INFORMATION:
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. (provider: TCP Provider, error: 0 - A connection attempt
failed because the connected party did not properly respond after a
period of time, or established connection failed because connected host
has failed to respond.) (Microsoft SQL Server, Error: 10060)
For help, click:
http://go.microsoft.com/fwlink?Prod...60&LinkId=20476
BUTTONS:
OK
--Hi
As this is periodic it does not seem to be the configuration that is
necessarily the issue. Check the network settings and routing. Also check if
TCP/IP is the protocol being used. Virus scanners can effect communications
if named pipes are being used. See
http://support.microsoft.com/kb/309422/en-us and
http://support.microsoft.com/kb/827422/en-us
John
"tootsuite@.gmail.com" wrote:

> Every now and then I receive this error, usually when trying to
> establish a connection to a new server. I checked and confirmed in
> surface area configuration that remote connections are enabled across
> tcp/ip. Also there are no firewall issues. This is sql server 2005. Any
> ideas? Thank you.
> TITLE: Connect to Server
> --
> Cannot connect to magneto2.
> --
> ADDITIONAL INFORMATION:
> 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. (provider: TCP Provider, error: 0 - A connection attempt
> failed because the connected party did not properly respond after a
> period of time, or established connection failed because connected host
> has failed to respond.) (Microsoft SQL Server, Error: 10060)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...60&LinkId=20476
> --
> BUTTONS:
> OK
> --
>