Re: I set: Local and remote connections/Using both TCP/IP and Named Pipes

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Using Sql Server Configuration Manager

I enabled Named Pipes, disabled TCP/IP, left VIA disabled and Shared Memory enabled

Using SQL Server 2005 Surface Area Configuration/Surface Area Configuration for Services and Connections/SQLEXPRESS/Database Engine/Remote Connections

I set: Local and remote connections/Using Named Pipes only



Still appears to work so thanks again.




Uri Dimant wrote:
I do not think you need both

"AAaron123" <aaaron123@xxxxxxxxxxxxxx> wrote in message
news:uAk$17cFKHA.4432@xxxxxxxxxxxxxxxxxxxxxxx
There is a Local System
And a Local Service

I changed to Local System

I was wondering about
Using both TCP/IP and Named Pipes
Is that OK and needed?

Thanks a lot



Uri Dimant wrote:
Aaron
The Log On is NT AUTHORITY/NteworkService.

Perhaps to System Local account



"AAaron123" <aaaron123@xxxxxxxxxxxxxx> wrote in message
news:eofHt5TFKHA.4316@xxxxxxxxxxxxxxxxxxxxxxx
For Error: Failed to generate a user instance of SQL Server due to
a failure in starting the process for the user instance.


Suggestion1 from the Internet:

Go to configuration manager right click on SQL Server Express
properties and change the account from network service to Local
Systems. I did not do this.





Suggestion2 from the Internet:

Delete C:\Documents and Settings\USERNAME\Local
Settings\Application Data\Microsoft\Microsoft SQL Server
Data\SQLEXPRESS. What I did:

I searched for SQLEXPRESS in Documents and Settings and deleted it.

Using Sql Server Configuration Manager

I enabled Named Pipes.

SQL Server (SQLEXPRESS) service Start Mode is Automatic

The Log On is NT AUTHORITY/NteworkService.

Using SQL Server 2005 Surface Area
Configuration/SQLEXPRESS/Database Engine/Remote Connections

I set: Local and remote connections/Using both TCP/IP and Named
Pipes Now everything is working but I expect it is not the best
configuration. Is there something in the way I have it set up that
you would change?



Thanks in advance


.

Relevant Pages

  • Re: Dot Net 2.0 or SQL Server 2005 problem?
    ... Configuration' and set the option to 'Using Both TCP/IP and Named Pipes'. ... 'Surface Area' used in conjuction with databases.) ... I already have SQL Server 2000 Developer installed so my SQL ... under the default settings SQL Server does not allow remote connections. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cannot connect to MSSQL2005
    ... Yes it is configured to allow remote connections using this document ... I'm sure i'm doing something wrong but still cant get it to connect. ... Configuration tool to allow connections? ... Microsoft OLE DB Provider for SQL Server error '80004005' ...
    (microsoft.public.inetserver.asp.db)
  • Re: Dot Net 2.0 or SQL Server 2005 problem?
    ... Assume the SQLExpress set up is OK, whther you can actually access the SQL ... After installing SQL Server Express, if you did not add any SQL login ... Configuration' and set the option to 'Using Both TCP/IP and Named Pipes'. ... under the default settings SQL Server does not allow remote connections. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Problem upgrading Microsoft Office Accounting Professional from 2008 to 2009 using SQL Express 2
    ... However if your SQL Server is on a computer named BOSTON and the connection string says BOSTON\SQLEXPRESS you could change the connection string to tcp:BOSTON\SQLEXPRESS and see if that works. ... Rick Byham, SQL Server Books Online ... Server Express Edition locally, but cannot connect remotely, and if the SQL Server Express Edition is listening on Named Pipes, then I suspect a firewall issue on the computer that is running SQL Server Express Edition. ... While this is not the standard configuration for MOA 2009, using the 2008 version of SQL Express should be a viable configuration. ...
    (microsoft.public.sqlserver.connect)
  • Re: Error: provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
    ... Since you have a Named Pipes error and are using an IP address, ... Or move it ahead of TCP in the SQL Server ... Configuration Manager list for the client. ...
    (microsoft.public.sqlserver.connect)