Hello,
Exactly,
I have executed set-executionPolicy --->unrestricted
and It works
Regards
Bibi
Main Topics
Browse All TopicsHello,
Herewith, I try to execute this powershell and I have this error :
D:\Scripts>Collect-dba_sta
Exception calling "Fill" with "1" argument(s): "An error has occurred while est
ablishing 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 d
oes not allow remote connections. (provider: Named Pipes Provider, error: 40 -
Could not open a connection to SQL Server)"
At D:\Scripts\Collect-dba_sta
+ $x=$SqlAdapter.Fill( <<<< $DataSet)
Unable to index into an object of type System.Data.DataTableColle
At D:\Scripts\Collect-dba_sta
+ $DataSet.Tables[0 <<<< ]
Thanks
Regards
Bibi
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: sstadPosted on 2009-11-06 at 00:58:34ID: 25757633
This could be due to the following causes:
1 Incorrect connection string, such as using SqlExpress.
2 NP was not enabled on the SQL instance.
3 Remote connection was not enabled.
4 Server not started, or point to not a real server in your connection string.
5 Other reasons such as incorrect security context.
This website can probably help you solve your problem: http://blogs.msdn.com/sql_ protocols/ archive/20 07/03/31/n amed-pipes -provider- error-40-c ould-not-o pen-a-conn ection-to- sql-server .aspx