Named Pipes Provider, error: 40 - Could not open a connection To SQL Server

I am trying to setup a notification service sample (from Joel Webb's book) for SQL server 2000 and notification service 2.0.

When i run nscontrol create at the cmd prompt, i am getting the following error:

Notification Services failed to retrieve the SQL Server edition.

SqlServerError:
Source: .Net SqlClient Data Provider
Number: 53
State: 0
Class: 20
Server:
Message: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL
Server)
Procedure:
Line Number: 0

Any help on how this could be resolved would be really appreciated.

Thanks,

Nirmala

Hi Nirmala -

Thanks for buying the book. I hope you find it useful!

As for your issues, you may want to double check the name of the server and SQL Server instance to make sure they are correct. You may also want to verify that the server does indeed allow remote connections and that it is using named pipes as a communication protocol.

HTH...

Joe|||

I tried all the suggested things but unfortunately still seeing the same errors. Any more thoughts?

Thanks,

Nirmala

|||In the description of the problem you mention SQL Server 2000 and SSNS v2.0. However, in the actual error message it references SSNS 2005.

SSNS v2.0 was developed using version 1.1 of the .net framework and will only work with SQL Server 2000. SSNS 2005 was developed with v2.0 of the .net framework and is only available for use with SQL Server 2005.

Could it be that you have mismatched versions? And that is what is causing the problems you are seeing?

HTH...

Joe|||

Hi

I had a similar error in analysis project.

In my case I did not use the real servername as I had put an alias name for the server in my hosts file.

When I changed the server name in my datasource to reflect the real server name in stead of the alias name, I was able to deploy the project.

Regards

Per

Named Pipes Provider, error: 40 - Could not open a connection To SQL Server

I am trying to setup a notification service sample (from Joel Webb's book) for SQL server 2000 and notification service 2.0.

When i run nscontrol create at the cmd prompt, i am getting the following error:

Notification Services failed to retrieve the SQL Server edition.

SqlServerError:
Source: .Net SqlClient Data Provider
Number: 53
State: 0
Class: 20
Server:
Message: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL
Server)
Procedure:
Line Number: 0

Any help on how this could be resolved would be really appreciated.

Thanks,

Nirmala

Hi Nirmala -

Thanks for buying the book. I hope you find it useful!

As for your issues, you may want to double check the name of the server and SQL Server instance to make sure they are correct. You may also want to verify that the server does indeed allow remote connections and that it is using named pipes as a communication protocol.

HTH...

Joe|||

I tried all the suggested things but unfortunately still seeing the same errors. Any more thoughts?

Thanks,

Nirmala

|||In the description of the problem you mention SQL Server 2000 and SSNS v2.0. However, in the actual error message it references SSNS 2005.

SSNS v2.0 was developed using version 1.1 of the .net framework and will only work with SQL Server 2000. SSNS 2005 was developed with v2.0 of the .net framework and is only available for use with SQL Server 2005.

Could it be that you have mismatched versions? And that is what is causing the problems you are seeing?

HTH...

Joe|||

Hi

I had a similar error in analysis project.

In my case I did not use the real servername as I had put an alias name for the server in my hosts file.

When I changed the server name in my datasource to reflect the real server name in stead of the alias name, I was able to deploy the project.

Regards

Per

Named Pipes Provider, error: 40 - Could not open a connection To SQL Server

I am trying to setup a notification service sample (from Joel Webb's book) for SQL server 2000 and notification service 2.0.

When i run nscontrol create at the cmd prompt, i am getting the following error:

Notification Services failed to retrieve the SQL Server edition.

SqlServerError:
Source: .Net SqlClient Data Provider
Number: 53
State: 0
Class: 20
Server:
Message: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL
Server)
Procedure:
Line Number: 0

Any help on how this could be resolved would be really appreciated.

Thanks,

Nirmala

Hi Nirmala -

Thanks for buying the book. I hope you find it useful!

As for your issues, you may want to double check the name of the server and SQL Server instance to make sure they are correct. You may also want to verify that the server does indeed allow remote connections and that it is using named pipes as a communication protocol.

HTH...

Joe|||

I tried all the suggested things but unfortunately still seeing the same errors. Any more thoughts?

Thanks,

Nirmala

|||In the description of the problem you mention SQL Server 2000 and SSNS v2.0. However, in the actual error message it references SSNS 2005.

SSNS v2.0 was developed using version 1.1 of the .net framework and will only work with SQL Server 2000. SSNS 2005 was developed with v2.0 of the .net framework and is only available for use with SQL Server 2005.

Could it be that you have mismatched versions? And that is what is causing the problems you are seeing?

HTH...

Joe|||

Hi

I had a similar error in analysis project.

In my case I did not use the real servername as I had put an alias name for the server in my hosts file.

When I changed the server name in my datasource to reflect the real server name in stead of the alias name, I was able to deploy the project.

Regards

Per

Named Pipes Provider

Hi!

I tryed to make an silent mode install for SQL express edition, for example:

start/ wait setup.exe /qn ADDLOCAL=ALL SECURITYMODE=SQL SAPWD=***** SQLBROWSERAUTOSTART=1 DISABLENETWORKPROTOCOLS=0

When i run it from a .bat file it's ok but i'm using this command in a .ini file in some apllication.
It doesn't install all the SQL, i mean in services it appears only SQL Server VSS Writer.
I also get the error Named Pipes Provider. The application that i want to install gets installed but can't connect to server.
I really need some help.

Seems your server is not installed at all. If no server is running, you will see the Named Pipes Provider error. So, make your server is installed first. How do you initiate the setup from a .ini file?

Named Instance naming rules

Hi, I'm trying to wrap the MSDE command line installer with an
InstallShield setup. One of the requirements is that the user can choose to
install a named instance and can choose the name of the named instance.
Here's what I found on SQL BOL:
"A new instance name must begin with a letter, an ampersand (&), or an
underscore (_), and can contain numbers, letters, or other characters. SQL
Server sysnames and reserved names should not be used as instance names. For
example, the term "default" should not be used as an instance name because
it is a reserved name used by Setup."
That's a little vague for trying to write an installer. Does anyone know the
specific rules for a naming a named instance? For example - how long can the
name be? can there be spaces in the name? what exactly are "other
characters" - anything?Refer "Instance Name" under "instance names" in BOL
--
Thanks
Ravi
"Andy Gaskell" wrote:
> Hi, I'm trying to wrap the MSDE command line installer with an
> InstallShield setup. One of the requirements is that the user can choose to
> install a named instance and can choose the name of the named instance.
> Here's what I found on SQL BOL:
> "A new instance name must begin with a letter, an ampersand (&), or an
> underscore (_), and can contain numbers, letters, or other characters. SQL
> Server sysnames and reserved names should not be used as instance names. For
> example, the term "default" should not be used as an instance name because
> it is a reserved name used by Setup."
> That's a little vague for trying to write an installer. Does anyone know the
> specific rules for a naming a named instance? For example - how long can the
> name be? can there be spaces in the name? what exactly are "other
> characters" - anything?
>
>|||Thanks Ravi.
"Ravi" <Ravi@.discussions.microsoft.com> wrote in message
news:AAC8D56C-739C-4C63-8EC2-AABF3937382F@.microsoft.com...
> Refer "Instance Name" under "instance names" in BOL
> --
> Thanks
> Ravi
>
> "Andy Gaskell" wrote:
>> Hi, I'm trying to wrap the MSDE command line installer with an
>> InstallShield setup. One of the requirements is that the user can choose
>> to
>> install a named instance and can choose the name of the named instance.
>> Here's what I found on SQL BOL:
>> "A new instance name must begin with a letter, an ampersand (&), or an
>> underscore (_), and can contain numbers, letters, or other characters.
>> SQL
>> Server sysnames and reserved names should not be used as instance names.
>> For
>> example, the term "default" should not be used as an instance name
>> because
>> it is a reserved name used by Setup."
>> That's a little vague for trying to write an installer. Does anyone know
>> the
>> specific rules for a naming a named instance? For example - how long can
>> the
>> name be? can there be spaces in the name? what exactly are "other
>> characters" - anything?
>>

Named Instance naming rules

Hi, I'm trying to wrap the MSDE command line installer with an
InstallShield setup. One of the requirements is that the user can choose to
install a named instance and can choose the name of the named instance.
Here's what I found on SQL BOL:
"A new instance name must begin with a letter, an ampersand (&), or an
underscore (_), and can contain numbers, letters, or other characters. SQL
Server sysnames and reserved names should not be used as instance names. For
example, the term "default" should not be used as an instance name because
it is a reserved name used by Setup."
That's a little vague for trying to write an installer. Does anyone know the
specific rules for a naming a named instance? For example - how long can the
name be? can there be spaces in the name? what exactly are "other
characters" - anything?Refer "Instance Name" under "instance names" in BOL
--
Thanks
Ravi
"Andy Gaskell" wrote:

> Hi, I'm trying to wrap the MSDE command line installer with an
> InstallShield setup. One of the requirements is that the user can choose t
o
> install a named instance and can choose the name of the named instance.
> Here's what I found on SQL BOL:
> "A new instance name must begin with a letter, an ampersand (&), or an
> underscore (_), and can contain numbers, letters, or other characters. SQL
> Server sysnames and reserved names should not be used as instance names. F
or
> example, the term "default" should not be used as an instance name because
> it is a reserved name used by Setup."
> That's a little vague for trying to write an installer. Does anyone know t
he
> specific rules for a naming a named instance? For example - how long can t
he
> name be? can there be spaces in the name? what exactly are "other
> characters" - anything?
>
>|||Thanks Ravi.
"Ravi" <Ravi@.discussions.microsoft.com> wrote in message
news:AAC8D56C-739C-4C63-8EC2-AABF3937382F@.microsoft.com...[vbcol=seagreen]
> Refer "Instance Name" under "instance names" in BOL
> --
> Thanks
> Ravi
>
> "Andy Gaskell" wrote:
>sql

Named Instance naming rules

Hi, I'm trying to wrap the MSDE command line installer with an
InstallShield setup. One of the requirements is that the user can choose to
install a named instance and can choose the name of the named instance.
Here's what I found on SQL BOL:
"A new instance name must begin with a letter, an ampersand (&), or an
underscore (_), and can contain numbers, letters, or other characters. SQL
Server sysnames and reserved names should not be used as instance names. For
example, the term "default" should not be used as an instance name because
it is a reserved name used by Setup."
That's a little vague for trying to write an installer. Does anyone know the
specific rules for a naming a named instance? For example - how long can the
name be? can there be spaces in the name? what exactly are "other
characters" - anything?
Refer "Instance Name" under "instance names" in BOL
Thanks
Ravi
"Andy Gaskell" wrote:

> Hi, I'm trying to wrap the MSDE command line installer with an
> InstallShield setup. One of the requirements is that the user can choose to
> install a named instance and can choose the name of the named instance.
> Here's what I found on SQL BOL:
> "A new instance name must begin with a letter, an ampersand (&), or an
> underscore (_), and can contain numbers, letters, or other characters. SQL
> Server sysnames and reserved names should not be used as instance names. For
> example, the term "default" should not be used as an instance name because
> it is a reserved name used by Setup."
> That's a little vague for trying to write an installer. Does anyone know the
> specific rules for a naming a named instance? For example - how long can the
> name be? can there be spaces in the name? what exactly are "other
> characters" - anything?
>
>
|||Thanks Ravi.
"Ravi" <Ravi@.discussions.microsoft.com> wrote in message
news:AAC8D56C-739C-4C63-8EC2-AABF3937382F@.microsoft.com...[vbcol=seagreen]
> Refer "Instance Name" under "instance names" in BOL
> --
> Thanks
> Ravi
>
> "Andy Gaskell" wrote:

name of instance

I just setup a new database machine... in my home environment
and want to test replication and subscribion
I am using windows 2003 server and sql 2000 server,
i have create a instance name while installion... but after around 15
days...
the instance name automatic changed to "local".. and then I can not create a
replication anymore because the sql server said that "local" can as a name
of distributor ...
any anyone tell me what i can/should do?
Many Thanks..
Thanks in advanced.
Hi
If the instance is called (local) this would imply a default instance and
not a named instance! You can refer to a default instance by the machine name.
John
"beachboy" wrote:

> I just setup a new database machine... in my home environment
> and want to test replication and subscribion
> I am using windows 2003 server and sql 2000 server,
> i have create a instance name while installion... but after around 15
> days...
> the instance name automatic changed to "local".. and then I can not create a
> replication anymore because the sql server said that "local" can as a name
> of distributor ...
> any anyone tell me what i can/should do?
> Many Thanks..
> Thanks in advanced.
>
>

name of instance

I just setup a new database machine... in my home environment
and want to test replication and subscribion
I am using windows 2003 server and sql 2000 server,
i have create a instance name while installion... but after around 15
days...
the instance name automatic changed to "local".. and then I can not create a
replication anymore because the sql server said that "local" can as a name
of distributor ...
any anyone tell me what i can/should do?
Many Thanks..
Thanks in advanced.Hi
If the instance is called (local) this would imply a default instance and
not a named instance! You can refer to a default instance by the machine nam
e.
John
"beachboy" wrote:

> I just setup a new database machine... in my home environment
> and want to test replication and subscribion
> I am using windows 2003 server and sql 2000 server,
> i have create a instance name while installion... but after around 15
> days...
> the instance name automatic changed to "local".. and then I can not create
a
> replication anymore because the sql server said that "local" can as a name
> of distributor ...
> any anyone tell me what i can/should do?
> Many Thanks..
> Thanks in advanced.
>
>

name of instance

I just setup a new database machine... in my home environment
and want to test replication and subscribion
I am using windows 2003 server and sql 2000 server,
i have create a instance name while installion... but after around 15
days...
the instance name automatic changed to "local".. and then I can not create a
replication anymore because the sql server said that "local" can as a name
of distributor ...
any anyone tell me what i can/should do?
Many Thanks..
Thanks in advanced.Hi
If the instance is called (local) this would imply a default instance and
not a named instance! You can refer to a default instance by the machine name.
John
"beachboy" wrote:
> I just setup a new database machine... in my home environment
> and want to test replication and subscribion
> I am using windows 2003 server and sql 2000 server,
> i have create a instance name while installion... but after around 15
> days...
> the instance name automatic changed to "local".. and then I can not create a
> replication anymore because the sql server said that "local" can as a name
> of distributor ...
> any anyone tell me what i can/should do?
> Many Thanks..
> Thanks in advanced.
>
>

Mysterious SQL Server Dropping Tables

We had just setup MS SQL 2000 (SP3), running on Windows 2000 (SP4). Both SQL
and Windows2000 Server has been patched with all security updates as per
Microsoft websites.
On the server PC, it is also running Norton Antivirus Corporate Edition 7.6
with the latest AV definition. I've also lost count of how many times we
scan the server for virus but none were found.
This is a newly setup server but we're observing the tables in the SQL
server dropping out of no apparent reason. A check on the actual data
directory we found that the database .LDF is missing and the EM marks it as
'suspect'.
What kind of information should I provide in order to further trouble shoot
this problem?
Since this is a test server we're only running it on 2 x 80GB IDE harddisk
and as far as I can tell there is no bad sectors found. Has anyone encounter
anything of such? Please help. TQ.
--
Steven Ung
"The source of all greatness lies within you" - Anonymous> This is a newly setup server but we're observing the tables in the SQL
> server dropping out of no apparent reason. A check on the actual data
> directory we found that the database .LDF is missing and the EM marks it
> as
> 'suspect'.
The tables, or the log file? Sounds like both are happening. Once you get
the system back where it should be, you might want to use a program like
filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
process is accessing the LDF file.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:ulucZdfHEHA.2876@.TK2MSFTNGP09.phx.gbl...
> The tables, or the log file? Sounds like both are happening.
Both, but the tables are the ones dropping/missing first.
Does drive caching has anything to do with it? The Windows Event Log
complaints that drive cache is disabled. I've temporary enable it and still
checking the results. But since no one has had this problem before, I'm not
certain of whether this is the solution or what is causing the tables to
drop or go missing.

> Once you get
> the system back where it should be, you might want to use a program like
> filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
> process is accessing the LDF file.
I've downloaded the utility but could not find any process out of the
extraordinary.
Steven Ung
"The source of all greatness lies within you" - Anonymous

Mysterious SQL Server Dropping Tables

We had just setup MS SQL 2000 (SP3), running on Windows 2000 (SP4). Both SQL
and Windows2000 Server has been patched with all security updates as per
Microsoft websites.
On the server PC, it is also running Norton Antivirus Corporate Edition 7.6
with the latest AV definition. I've also lost count of how many times we
scan the server for virus but none were found.
This is a newly setup server but we're observing the tables in the SQL
server dropping out of no apparent reason. A check on the actual data
directory we found that the database .LDF is missing and the EM marks it as
'suspect'.
What kind of information should I provide in order to further trouble shoot
this problem?
Since this is a test server we're only running it on 2 x 80GB IDE harddisk
and as far as I can tell there is no bad sectors found. Has anyone encounter
anything of such? Please help. TQ.
--
Steven Ung
"The source of all greatness lies within you" - Anonymous> This is a newly setup server but we're observing the tables in the SQL
> server dropping out of no apparent reason. A check on the actual data
> directory we found that the database .LDF is missing and the EM marks it
> as
> 'suspect'.
The tables, or the log file? Sounds like both are happening. Once you get
the system back where it should be, you might want to use a program like
filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
process is accessing the LDF file.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:ulucZdfHEHA.2876@.TK2MSFTNGP09.phx.gbl...
> > This is a newly setup server but we're observing the tables in the SQL
> > server dropping out of no apparent reason. A check on the actual data
> > directory we found that the database .LDF is missing and the EM marks it
> > as
> > 'suspect'.
> The tables, or the log file? Sounds like both are happening.
Both, but the tables are the ones dropping/missing first.
Does drive caching has anything to do with it? The Windows Event Log
complaints that drive cache is disabled. I've temporary enable it and still
checking the results. But since no one has had this problem before, I'm not
certain of whether this is the solution or what is causing the tables to
drop or go missing.
> Once you get
> the system back where it should be, you might want to use a program like
> filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
> process is accessing the LDF file.
I've downloaded the utility but could not find any process out of the
extraordinary.
--
Steven Ung
"The source of all greatness lies within you" - Anonymous

Mysterious SQL Server Dropping Tables

We had just setup MS SQL 2000 (SP3), running on Windows 2000 (SP4). Both SQL
and Windows2000 Server has been patched with all security updates as per
Microsoft websites.
On the server PC, it is also running Norton Antivirus Corporate Edition 7.6
with the latest AV definition. I've also lost count of how many times we
scan the server for virus but none were found.
This is a newly setup server but we're observing the tables in the SQL
server dropping out of no apparent reason. A check on the actual data
directory we found that the database .LDF is missing and the EM marks it as
'suspect'.
What kind of information should I provide in order to further trouble shoot
this problem?
Since this is a test server we're only running it on 2 x 80GB IDE harddisk
and as far as I can tell there is no bad sectors found. Has anyone encounter
anything of such? Please help. TQ.
Steven Ung
"The source of all greatness lies within you" - Anonymous
> This is a newly setup server but we're observing the tables in the SQL
> server dropping out of no apparent reason. A check on the actual data
> directory we found that the database .LDF is missing and the EM marks it
> as
> 'suspect'.
The tables, or the log file? Sounds like both are happening. Once you get
the system back where it should be, you might want to use a program like
filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
process is accessing the LDF file.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
|||"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:ulucZdfHEHA.2876@.TK2MSFTNGP09.phx.gbl...
> The tables, or the log file? Sounds like both are happening.
Both, but the tables are the ones dropping/missing first.
Does drive caching has anything to do with it? The Windows Event Log
complaints that drive cache is disabled. I've temporary enable it and still
checking the results. But since no one has had this problem before, I'm not
certain of whether this is the solution or what is causing the tables to
drop or go missing.

> Once you get
> the system back where it should be, you might want to use a program like
> filemon (http://www.sysinternals.com/ntw2k/utilities.shtml) to see what
> process is accessing the LDF file.
I've downloaded the utility but could not find any process out of the
extraordinary.
Steven Ung
"The source of all greatness lies within you" - Anonymous

My Report feature

Currently - our Reporting Services site is setup so that all Domain Users can access it. We are starting to use Report Builder now. I have enabled the My Reports folder feature that that creates a user folder for anyone that logs onto the site. Is there a way to just create the user folders for certain people?

Yes. You do not have to use the "My Reports" function at all. Just create a folder for each user under the Home folder and then assign them at least browser rights to that folder. Also, be sure they have browser rights to the Home folder or they will not be able to see their own folder as this follows a hierachial structure.