WCF based named pipe naming convention.

I found the following msdn article http://blogs.msdn.com/b/rodneyviana/archive/2011/03/22/named-pipes-in-wcf-are-named-but-not-by-you-and-how-to-find-the-actual-windows-object-name.aspx
which states how to acquire the memory mapped file name in order to infer the actual pipe name, however my results are not proving successful. Further, the screen caps that the author took don't jive with my results either. I do not reveal the mmap file name
but the actual named pipe (obviously) when listing pipes.
Does anyone know how to infer the name of the pipe accepting input? I am required to provide access to code written in Python which is why I need the actual pipe name.
Thanks!

Long answer in "teaching to fish" style of how to actually get the pipe name:
I attached WinDbg to a program hosting a WCF service using named pipe transports and ran the following commands:
.loadby sos clr
!DumpHeap -type Pipe
I clicked through several of the objects and ultimately found this one whose relevant properties are also dumped below:
0:009> !DumpHeap /d -mt 00007ffd7b23de38
         Address               MT     Size
0000004409939f28 00007ffd7b23de38       64
Statistics:
              MT    Count    TotalSize Class Name
00007ffd7b23de38        1           64 System.ServiceModel.Channels.PipeConnectionListener
Total 1 objects
0:009> !DumpObj /d 0000004409939f28
Name:        System.ServiceModel.Channels.PipeConnectionListener
MethodTable: 00007ffd7b23de38
EEClass:     00007ffd7ac778a8
Size:        64(0x40) bytes
File:        C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll
Fields:
              MT    Field   Offset                 Type VT     Attr
Value Name
00007ffd907886d0 4000653        8           System.Uri 0 instance 00000044098eaba8 pipeUri
00007ffd917837c8 4000654       28         System.Int32 1 instance             8192 bufferSize
00007ffd7b23ab28 4000655       2c         System.Int32 1 instance                0 hostNameComparisonMode
00007ffd9177f370 4000656       34       System.Boolean 1 instance                0 isDisposed
00007ffd9177f370 4000657       35       System.Boolean 1 instance                1 isListening
00007ffd7aaf9040 4000658       10 ...em.ServiceModel]] 0 instance 0000004409939f68 pendingAccepts
00007ffd9177f370 4000659       36       System.Boolean 1 instance                1 anyPipesCreated
00007ffd7b239320 400065a       18 ....PipeSharedMemory 0 instance 000000440993bb38 sharedMemory
00007ffd42824968 400065b       20 ...ifier, mscorlib]] 0 instance 0000000000000000 allowedSids
00007ffd9177f370 400065c       37       System.Boolean 1 instance                1 useCompletionPort
00007ffd917837c8 400065d       30         System.Int32 1 instance              255 maxInstances
0:009> !DumpObj /d 00000044098eaba8
Name:        System.Uri
MethodTable: 00007ffd907886d0
EEClass:     00007ffd90364db0
Size:        72(0x48) bytes
File:        C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll
Fields:
              MT    Field   Offset                 Type VT     Attr
Value Name
00007ffd91780bd8 40012d6        8        System.String 0 instance 00000044097e1190 m_String
00007ffd91780bd8 40012d7       10        System.String 0 instance 0000000000000000 m_originalUnicodeString
00007ffd90786c30 40012d8       18     System.UriParser 0 instance 00000044097e6088 m_Syntax
00007ffd91780bd8 40012d9       20        System.String 0 instance 0000000000000000 m_DnsSafeHost
00007ffd90757ba8 40012da       30        System.UInt64 1 instance 54766272512 m_Flags
00007ffd90787390 40012db       28   System.Uri+UriInfo 0 instance 00000044098eb328 m_Info
00007ffd9177f370 40012dc       38       System.Boolean 1 instance                1 m_iriParsing
00007ffd91780bd8 40012c9      cd8        System.String 0   static 00000044097e5530 UriSchemeFile
00007ffd91780bd8 40012ca      ce0        System.String 0   static 00000044097e5510 UriSchemeFtp
00007ffd91780bd8 40012cb      ce8        System.String 0   static 00000044097e5558 UriSchemeGopher
00007ffd91780bd8 40012cc      cf0        System.String 0   static 00000044097e5480 UriSchemeHttp
00007ffd91780bd8 40012cd      cf8        System.String 0   static 00000044097e54a8 UriSchemeHttps
00007ffd91780bd8 40012ce      d00        System.String 0   static 00000044097e54d0 UriSchemeWs
00007ffd91780bd8 40012cf      d08        System.String 0   static 00000044097e54f0 UriSchemeWss
00007ffd91780bd8 40012d0      d10        System.String 0   static 00000044097e55d0 UriSchemeMailto
00007ffd91780bd8 40012d1      d18        System.String 0   static 00000044097e55a8 UriSchemeNews
00007ffd91780bd8 40012d2      d20        System.String 0   static 00000044097e5580 UriSchemeNntp
00007ffd91780bd8 40012d3      d28        System.String 0   static 00000044097e5670 UriSchemeNetTcp
00007ffd91780bd8 40012d4      d30        System.String 0   static 00000044097e5698 UriSchemeNetPipe
00007ffd91780bd8 40012d5      d38        System.String 0   static 00000044097e60d8 SchemeDelimiter
00007ffd90749608 40012dd      d40 ...etSecurityManager 0   static 0000000000000000 s_ManagerRef
00007ffd917811b8 40012de      d48        System.Object 0   static 00000044097e60f8 s_IntranetLock
00007ffd9177f370 40012df      a94       System.Boolean 1   static                0 s_ConfigInitialized
00007ffd9177f370 40012e0      a95       System.Boolean 1   static                0 s_ConfigInitializing
00007ffd907442f0 40012e1      a90         System.Int32 1   static                0 s_IdnScope
00007ffd9177f370 40012e2      a96       System.Boolean 1   static                1 s_IriParsing
00007ffd917811b8 40012e3      d50        System.Object 0   static 0000000000000000 s_initLock
00007ffd91781ed8 40012e4      d58        System.Char[] 0   static 00000044097e6110 HexLowerChars
00007ffd91781ed8 40012e5      d60        System.Char[] 0   static 00000044097e6190 _WSchars
0:009> !DumpObj /d 00000044097e1190
Name:        System.String
MethodTable: 00007ffd91780bd8
EEClass:     00007ffd91111aa8
Size:        94(0x5e) bytes
File:        C:\Windows\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll
String:      net.pipe://localhost/WCFPS_14840-0
Fields:
              MT    Field   Offset                 Type VT     Attr
Value Name
00007ffd917837c8 40000ab        8         System.Int32 1 instance               34 m_stringLength
00007ffd91781f38 40000ac        c          System.Char 1 instance               6e m_firstChar
00007ffd91780bd8 40000ad       18        System.String 0   shared           static Empty
                                 >> Domain:Value 0000004408b16a10:NotInit <<
0:009> !DumpObj /d 000000440993bb38
Name:        System.ServiceModel.Channels.PipeSharedMemory
MethodTable: 00007ffd7b239320
EEClass:     00007ffd7ac76498
Size:        48(0x30) bytes
File:        C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll
Fields:
              MT    Field   Offset                 Type VT     Attr
Value Name
00007ffd7b239398 400066a        8 ...FileMappingHandle 0 instance 000000440993bb18 fileMapping
00007ffd91780bd8 400066b       10        System.String 0 instance 000000440993aa58 pipeName
00007ffd91780bd8 400066c       18        System.String 0 instance 0000000000000000 pipeNameGuidPart
00007ffd907886d0 400066d       20           System.Uri 0 instance 00000044098eaba8 pipeUri
0:009> !DumpObj /d 000000440993aa58
Name:        System.String
MethodTable: 00007ffd91780bd8
EEClass:     00007ffd91111aa8
Size:        116(0x74) bytes
File:        C:\Windows\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll
String:
\\.\pipe\987a898d-7980-4703-b03e-8830a8a5a24c
Fields:
              MT    Field   Offset                 Type VT     Attr
Value Name
00007ffd917837c8 40000ab        8         System.Int32 1 instance               45 m_stringLength
00007ffd91781f38 40000ac        c          System.Char 1 instance               5c m_firstChar
00007ffd91780bd8 40000ad       18        System.String 0   shared           static Empty
                                 >> Domain:Value 0000004408b16a10:NotInit <<
I then ran !gcroot 0000004409939f28 to see where it came from:
            -> 000000440990aba0 System.ServiceModel.Dispatcher.ChannelDispatcher
            -> 0000004409901868 System.ServiceModel.Channels.NamedPipeDuplexChannelListener
            -> 0000004409939ee8 System.Action
            -> 0000004409921ff8 System.ServiceModel.Channels.ExclusiveNamedPipeTransportManager
            -> 000000440993a0d8 System.ServiceModel.Channels.ConnectionDemuxer
            -> 000000440993a1f8 System.ServiceModel.Channels.ConnectionAcceptor
            -> 0000004409939fb0 System.ServiceModel.Channels.BufferedConnectionListener
            -> 0000004409939f28 System.ServiceModel.Channels.PipeConnectionListener
Running !gcroot 000000440990aba0 System.ServiceModel.Dispatcher.ChannelDispatcher shows that one of the ways it is bound is through the class in the program that I used to create the service host(WCFPS from
my blog post here):
    -> 00000044097e1220 WCFPSExecutor.WCFPS
    -> 00000044097e6ae0 System.ServiceModel.ServiceHost
    -> 000000440981d960 System.ServiceModel.Dispatcher.ChannelDispatcherCollection
    -> 000000440981d988 System.Collections.Generic.List`1[[System.ServiceModel.Dispatcher.ChannelDispatcherBase, System.ServiceModel]]
    -> 000000440990d0f8 System.Object[]
    -> 000000440990aba0 System.ServiceModel.Dispatcher.ChannelDispatcher
So now that I knew that, I did a !do on the ServiceHost object and found that the ChannelDispatcherCollection was contained in a member named channelDispatchers. Doing that again on that member, I saw that the collection came from a member named items.
One more time, and now I knew that System.Object[] came from items. Finally, the first element in that array was the ChannelDispatcher. At that point, I subsequently repeated the process of off ChannelDispatcher to get to PipeConnectionListener
and ultimately PipeSharedMemory which resulted in the following path to getting the pipe name:
(ServiceHost that the program opened).channelDispathers.items.items ->For each ChannelDispatcher until PipeSharedMemoryIsFound -> (ChannelDispatcher).listener.messageReceivedCallback.target.connectionDemuxer.acceptor.listener.connectionListener.sharedMemory
One will have to use System.Reflection (or something even more complicated) to access all of that at runtime, but there's a string member named pipeName at that point with an actual name, and a fileMapping member whose handle member contains a handle that
you can use to get/verify the pipe name as well with
GetFileInformationByHandleEx.
WinSDK Support Team Blog: http://blogs.msdn.com/b/winsdk/

Similar Messages

Export and Import using Named Pipes

Hai,
I need an clarification in export, import and compress of dumps using named pipes.I am using Oracle 9i RAC 9.2.0.4 in AIX 5.3. Every month i have to move list of tables from one database to another database after taking export dumps. The list of activities done by me at present are given below.
1. Taking export and gziping the dump file at the same time using named pipes.
2. Doing uncompress and import in the second database using named pipes.
We are doing compress for space constraints. Now my doubt is whether using named pipes, we can do both operation of import and compress of dump file at the same time. i.e, at the time of export itself , using named pipes, i need both import in the another database and compress the zip file. Is it possible?

mknod exp.out p
exp dbadmin/admindb file=exp.out owner=scott log=export.log statistics=none &
imp dbadmin/admindb file=exp.out fromuser=scott touser=foobar log=import.log
rm exp.out
cat import.log
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export file created by EXPORT:V10.02.01 via conventional path
import done in US7ASCII character set and UTF8 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
. importing SCOTT's objects into FOOBAR
. . importing table                        "BONUS"          0 rows imported
. . importing table                         "DEPT"          4 rows imported
. . importing table                          "EMP"         14 rows imported
. . importing table                     "SALGRADE"          5 rows imported
About to enable constraints...
Import terminated successfully without warnings.Edited by: sb92075 on Jan 1, 2010 1:42 PM

Async named pipe server

I was looking at some threaded named pipe server code compared to async implementations such as http://www.codeproject.com/Tips/492231/Csharp-Async-Named-Pipes and
I am wondering how this works in a busy env, only one client can be processed concurrently as another instance is only spun up once the single running instance finishes.
Does anyone know of any async implementations that are complete that I might study?
Thanks.

This type of async does use a threadpool, but you don't manage the callbacks directly since it's an IO type and not a worker type. I'd base the decision on what I was more comfortable doing.
What do you mean by unable to enumerate the actual pipe name? I haven't explicitly tried with WCF, but even if it doesn't directly expose it, a named pipe is going to boil down to a file handle that is open in the process. The name of the pipe
can be extracted from the handle with
GetFileInformationByHandleEx. System.Reflection would let you see private members down to the point of where that pointer is if nothing else.
WinSDK Support Team Blog: http://blogs.msdn.com/b/winsdk/

Flex 2.0 Naming an Coding Conventions

Hello,
I'm new with Flex 2.0 and Actionscript 3.0.
They asked me to define naming and coding conventions for
Flex 2.0 and Actionscript 3.0 for our company.
I'm looking for documents for naming and coding conventions
for Flex 2.0 and Actionscript 3.0 so I can make conventions for our
company.
Who can help me?
Thanks in advance.
Simson

I think you could do one based on Sun's coding convention for
Java, since the syntax is similar. Take a look at the Java
convention and you'll get a pretty good idea

Does LabView support the Named Pipe function for interprocess communications

I have searched around ni.com enough to know that LabView for Unix supports this feature but don't know about for the PC running Win 2000 Pro.
I am trying to have a LabView program that collects data and displays it using another program (non-LabView) running concurrently. The non-LabView program would display the data in a PPI window. We would like to use a Named Pipe method to transfer the data from the LabView program to the non-LabView program. Can that be done using LabView?
Thanks.
SonarRob

There is a project on OpenG I have started which does implement pipes
access under Windows in a similar way as has been available for Unix
already in LabVIEW.
The library is still to be considered Beta and there is no OpenG
Commander package yet. I actually intend to also port it over to Linux
but that could take a while. If you want to get the library for the
time being, you will probably have to learn how to use CVS to access
that library on the CVS servers on sourceforge. Alternatively you can
access the repository over the web based CVS interface under
http://cvs.sourceforge.net/viewcvs.py/opengtoolkit/pipe/. Here you will
have to download everything in the "source" directory and if you want
to see some examples for their use also the "test" directory.
Rolf Kalbermatter
Message Edited by rolfk on 07-07-2005 04:41 PM

Named Pipes Provider: Could not open a connection to SQL Server

We are running into an error on a SQL request from SQL-IDA to the SQL-IDB server. Both servers are on Windows 2005 with MS SQL Server 2003 SP3.
OLE DB provider "SQL-IDA" for linked server "SQL-IDB" returned message "Login timeout
expired".
OLE DB provider "SQL-IDA" for linked server "SQL-IDB" returned 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.".
Msg 53, Level 16, State 1, Line 0
Named Pipes Provider: Could not open a connection to SQL Server [53].
It seems to suggest that SQL-IDA cannot find the network path to SQL-IDB. We've followed the steps in this article http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277 but it did not resolve our issue. Is it possible that the MSDTC dynamic port range
should be set to a specific range on both servers?
Any help is greatly appreciated.
Albert

Hi Albert,
Can you try to use the SQL Server Management Studio on server ‘SQL-IDA’ to connect to the instance on server ‘SQL-IDB’ to see if it works or not?
There are possible reasons to error 53:
a) typo in the server name, or using "/" rather than "\" between server name and instance name, e.g. "myserver/myinst" is not correct.
b) name resolution to the server name is not correct, "ping -a yourserver" would tell if that's the case
c) The server machine is firewall'ed and file sharing is not in the exception list. You need put "File and Printer Sharing" in exception.
For more information:
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server (Microsoft SQL Server, Error: XXX).
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Stephanie Lv
TechNet Community Support

Named Pipes provider, error:40 could not open a connection to sql server. Only happens on one of the front end SRS servers

when testing a datasource connection I get the following error.
Named Pipes provider, error:40 could not open a connection to sql server.
I've read all the posts on this and nothing works. This is a scale out deployment and the connection
works from the other server I have setup with SRS that is connected to the same backend SRS databases. It just doesn't work from one of the SRS front ends. I'm at a loss.. please help

Enable both named pipe and TCP communications.
Make sure client is using the same (named) pipe name as server for connection.
Kalman Toth Database & OLAP Architect
Free T-SQL Scripts
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Reporting Services 2008 R2 configuration error: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

Hi, I am using SQL Server 2008 R2 and on one of our dev boxes I am trying to setup ReportServer using ReportingServices Configuration manager. This is was installed longtime back and during installation they created a service account for reporting services.
When I try to configure the service account I do not get the service account created during the installation in the pull down and if I were to use something different I get this "Named Pipes Provider, error: 40 - Could not open a connection to SQL Server"
error.
Thanks in advance...........
Ione

Hi,
Take a look at this blog - http://blogs.msdn.com/b/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx
I hope it will help.

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

Hi,
I'm encountering an issue with "Named Pipes Provider, error: 40 windows" and am having problems determining how to fix it due to the environment I'm using. I have two SQL Servers installed on two separate Win2K3 Server boxes, one is SQL Server 2000 and the other is SQL Server 2005. The SQL Server 2000 contains the actual application data. The 2005 database is used only for Reporting Services. I've set up the reports on SSRS such that their datasources hit the 2000 server. This is using SQL Server authentication.
When testing the reports via SSRS (in Visual Studio 2005), the connection to the data works and the reports are generated fine. When I deploy them to the reporting server and launch IE to test locally (still on the 2005 box), I get this "Named Pipes Provider, error 40" issue. I made sure that Named Pipes and TCP were enabled and the port set at 1433 (to match that on the 2000 box).
Now I changed the datasource's authentication from SQL Server to Windows authentication. I tested this in SSRS and this works too. When I redeployed the reports with this authentication change, testing the reports via IE locally (on the 2005 box) worked. Great. Now when I open IE on an external box, i.e. on the 2000 box, and try to test the reports, I get this same error 40 issue. I've been through a few threads describing the error 40, fiddling around with the SQL Server configuration as well as SSRS, to no avail. I have a feeling this error 40 issue has to due with permissions/authentication between the SQL Server boxes but I can't really be sure. Anyone have any ideas on how to troubleshoot my situation. Thanks.
larry

Named Pipes Provider, error: 40 - Could not open a connection to SQL Server :
I. Incorrect connection string, such as using SqlExpress.
Check out: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=558456&SiteID=17
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1245564&SiteID=1
The typical error when dealing with Express includes:
a. User is not aware of SqlExpress was installed as a named instance, consequently, in his/her connection string, he/she only specify ".","localhost" etc instead of ".\SqlExpress" or "<machinename>\Sqlexpress".
b. Np was disabld by default after installing SqlExpress.
c. If Sqlexpress was installed on the remote box, you need to enable remote connection for Express.
Please read the following blog for best practice of connecting to SqlExpress.
http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx
II. Named Pipes(NP) was not enabled on the SQL instance.
Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=136253&SiteID=1
Oppose to SQL 2000 which turn on all protocols, SQL 2005 SKUs turn off NP by default. So, when you see this error, please check:
1) Go to SQL Server Configuration Manager, See Server has NP enabled.
2) %windir%\program files\microsoft sql server\mssql.1\mssql\log, notepad ERRORLOG, see whether Server is listening on NP. You should see "Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ] or [\\.\pipe\mssql$<InstanceName>\sql\query]"
3) Notice that "sql\query" is the default pipe name, so you need to know server is listening on which pipe name. eg: if you specify server pipe name is "sql\query1", then you would see in the errorlog that server listening on [ \\.\pipe\sql\query1 ], and go to SQL Server Configuration Manager, click client Named Pipe properties, see whether the pipe name is same with the one server listening on.
4) If you are using SQL Native Client ODBC/OLEDB provider({SQL Native Client} or SQLNCLI), go to SQL Configuration Manager, click client protocols, make sure NP and TCP are both enabled. Right click properties of NP, make sure client is using the same pipe name as server for connection.
5) If you are using MDAC ODBC/OLEDB({SQL Server} or SQLOLEDB) provider, in command line, launch "cliconfg.exe" and make sure NP enabled and right pipe name specified.
III. Remote connection was not enabled.
Check out: when you right click on the Server in SQL Server Management Studio, in Connections, the Remote server connections part, you have enabled the "Allow remote connections to this server" check box
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=322792&SiteID=1
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=763875&SiteID=1
If you are making a remote connection, namely, your target SQL Server is on the different box as client application, you might need to check whether:
a. "File and Printer Sharing" was opened in Firewall exception list.
b. Please see the blog for enabling remote connection for express and troubleshooting tips of remote connection.
http://blogs.msdn.com/sql_protocols/archive/2005/11/14/492616.aspx
http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
IV. Server not started, or point to not a real server in your connection string.
Check out: Open SQL Server Surface Area Configuration and ensure all the required services are started, Remote Connections are configured.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=348662&SiteID=1
a. use "sc query mssqlserver" for default instance or "sc query mssql$<instancename>" to make sure SQL Server was started. Sometimes, reseason behind the broken of your client application w/ this error:40 might be SQL server restarted and failed, so, it'd better for you to double check.
b. User specified wrong server in their connection string, as described in the forum discussion, "MSSQLSERVER" is an invalid instance name. Remember, when you connect to default instance, <machinename> could be best representitive for the instance, when you connect to a named instance such as sqlexpress, you should specify <machinename>\<instancename> as data source in your connection string.
V. Other reasons such as incorrect security context.
Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=192622&SiteID=1
Such error also occured during user operation such as moving database or db mirroring or cluster, any DB OP that might invovle different sql instances, namely, the destination database is located in another sql instance and user is not aware of the state of the destination. I recommend you first isolate whether this fail is during connection stage or data operation stage.
a. During data operation, you are normally asked to type in the destination server name whether it is default to "(local)" or another server "<remotemachinename>". So, remember the exact string that represent the target instance, then when the error repros, open command line, use "sqlcmd -S<representitive> -E" ,see what happens, if the connection fail, please follow up above I - IV troubleshooting lists. otherwise continue.
b. If you can make basic conection, but still face the error, then there must be something that server reject the connection or client close the connection for some reason.
VI. Please try basic connectivity tests between the two mahcines you are working on. One simple way to verifty connectivity is to use command line tools, such as osql.exe. For example, osql -E -Stcpervername\instancename. If it connects cross-machine successfully, please also verify that your connection string in your scenario is correct.
Here are some blogs which could be helpful: just follow the basic connectivity troubleshooting guidelines on the SQL Protocols blog, see:
SQL Server 2005 Connectivity Issue Troubleshoot - Part I
http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx
and
SQL Server 2005 Connectivity Issue Troubleshoot - Part II
http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx
Hope this helps.

Getting FMS to broadcast a media file being read via a named pipe.

I know you can broadcast partial AVI videos due to it's format. What I want to do, is feed an avi file to fms which is being generated by software on the local machine. If I create a named-pipe(on windows), will I be able to feed an avi file to fms while it's being read?

Thanks Balusc!!
I have made use of your code to display PDF files in an IFRAME tag too!!! I just dint believe that this would be possible. Please just take a look at my JSP page.
<h:form id="CaseLookUp">
     <%
     String path = request.getContextPath()+"";
     out.print(path);
     %>
<iframe scrolling="auto" src="<%=path%>/imageServlet?file=D:\70-229 V5.pdf" width="80%" height="600" ></iframe>
     </h:form>

Connecting to sqlserver using named pipe

I would like to connect to mssql (running on same PC as SQL Developer) using named pipes.
The host is listed in the Windows Service Manager as \\SX3102971\SIMSLOCAL
I have gone to the 'Oracle' tab, selected 'Advanced' and in the 'Custom JDBC URL'
entered
jdbc:jtds:sqlserver:\\SX3102971\SIMSLOCAL;namedPipe=true;user=<username>;password=<password>
where <username> and <password> are the true values.
I receive a message
Staus : Failure -Invalid connection information specified. Verify the URL format for the specified driver.
Can anyone advise on what may be wrong?
Also, can SQLDeveloper handle blank passwords?
The database is installed as part of a third party application, which sets the default dba logon with no password. SQL Developer states that a password is required. For the example above I have created my own log on.

Hi,
I managed to solve the problem. So don't worry about it.
For others who are looking for the solution...
- I have referred to the http://www.qint.de/joria/doc/jdbc/jtds.html.
- I have changed the URL element in IDEConnections.xml file located under where SQLDEVELOPER software is installed.
- The URL must look like the following ...
<URL>jdbc:jtds:sqlserver://\\.\;namedPipe=true;instance=<name of the database - without the server name>;</URL>
Hope this helps.
Regards
Raja
Message was edited by:
rajaram_r

What should be started and enabled in SQL express 2008 R2? Shared memory, TCP/IP , named pipes, VIA

I copied my Visual Studio 2008 projects to a new computer and am having trouble getting the database to attach to my website to continue with it.
I uninstalled SQL 2005 express and installed SQL 2008 R2 Express.
When I looked in the SQL Server configuration manager, I wasn't sure what should be running and what should be stopped and what protocols should be enabled, etc so I started everything and enabled everything.
However, the SQL Server Agent will not start. Maybe I did something wrong by enabling everything. I have everything to start automatically, and all enabled:
SQL Native Client: I right clicked and opened and under client protocols, have enabled all: Shared memory, TCP/IP , named pipes, VIA
and under SQL Server Network Configuration, I opened that and under there is listed protocols for SQLEXPRESS AND I enabled same things: Shared memory, TCP/IP , named pipes, VIA
When I could not start the SQL Server Agent before from the SQL Server configuration mgr. I went into services and started it that way and it did start. But since I have rebooted, it will not start that way either and I now get this message: Windows could
not start the SQL Server Agent(SQLEXPRESS) Service on local computer. Error 1067
I'm just trying to get my visual studio project working again. Would appreciate any help. Maybe I should uninstall SQL and reinstall 2005??

Windows could not start the SQL Server Agent(SQLEXPRESS) Service on local computer.
As the others already wrote, with SQL Server Express in Version 2008 the "SQL Server Agent" will be installed, but it's not a Feature of the Express Edition and therefore you can't start & use it.
In SQL Server 2005 Express the Agent was completly missing (not installed), therefore you haven't this "issue" before.
Olaf Helper
[ Blog] [ Xing] [ MVP]

SQL*Loader Named Pipe Load Thread goes to 0

Hi,
Running SQL*Loader 10.2.0.1.0 on XP pro against 10g EE 10.2.0.2.0 Production, RAC.
Control file:
OPTIONS ( MULTITHREADING=TRUE, DIRECT=TRUE, ROWS=5000000, COLUMNARRAYROWS = 200000 )
UNRECOVERABLE
LOAD DATA
--INFILE 'C:\Program Files\Delta Data Software, Inc\DDS Twenty Two C\SQL_LOADER\LDR.DAT' "fix 427"
INFILE '\\.\pipe\testpipe' "fix 427"
BADFILE 'C:\Program Files\Delta Data Software, Inc\DDS Twenty Two C\DataGen\S-INTERSP-DL.bad'
DISCARDFILE 'C:\Program Files\Delta Data Software, Inc\DDS Twenty Two C\DataGen\S-INTERSP-DL.dsc'
INSERT
INTO TABLE "TDW999999"
Data File is 1 million row text file, 427 byte per line
Problem:
When calling SqlLdr directly against the data file, the import runs in 1:47(min\secs).
Total stream buffers loaded by SQL*Loader main thread: 408
Total stream buffers loaded by SQL*Loader load thread: 2036
However, when I pipe the same data to SqlLdr via a simple c# application with a named pipe, it takes 5:56(mins\secs).
Pipe Base Load:
Total stream buffers loaded by SQL*Loader main thread: 104249
Total stream buffers loaded by SQL*Loader load thread: 0
It looks like SqlLdr can not go parallel when input is from a named pipe.
Any Ideas on how I can get my load thread count back up when using pipes ?
Thanks

Hi,
According to http://www.mcse.ms/archive27-2006-1-2068094.html you can do the following (substitute your c# program for 'type load.dat'):
>
type load.dat|sqlldr control=load.ctl userid=user/password data=\"-\"
Alternative (for both , unix and windows)- infile syntax:
load data
infile "-"
into table...
Metalink note 191043.1 may be interesting for you as well.
Does the performance then improve?
Cheers,
Colin

SQL Server Agent - [165] ODBC Error: 0, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001]

Hi,
I keep receiving the error below in the SQL Server Agent Error Log;
[165] ODBC Error: 0, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001]
It is occurring approximately 20 times an hour and i cannot link it to any job failures. All jobs on the same SQL instance are working.
The server is a clustered server and there are no errors occuring in the SQL Server error log at the same time. I have attempted to trace using profiler looking for errors and warnings but anything that does occur doesn't seem to correspond to the reported
times of the errors within the sql agent error log.
Please could someone point me where to look next?
Many thanks.

Please may I add that this is on a SQL Server 2008 R2 Enterprise edition patched to 10.50.1600.
Nah, that server is not patched at all, because 10.50.1600 is the RTM version. Find Service Pack 2 and install at the next maintenance window, after having performed tests according to your local policy.
It is not going to resolve your particular problem though.
It seems like you have a job that attempts to a connect to s server that is down or non-existing. The job may be configured to return success also on failures. I would check if there are jobs that target other servers.
Erland Sommarskog, SQL Server MVP, [email protected]

Named Pipes Provider, error: 40 on workgroup workstations

I am having issues with a vendor supplied application. It generates an error when run from workstations that are not part of an Active Directory domain. The error is “provider: Named Pipes Provider, error: 40 –
Could not open a connection to SQL Server)”. It runs as expected when ran from a workstation that is a member of the domain. Obviously adding the workstation to the domain is a solution. However, because of concern of what might break this is not our preferred
solution.
The database is SQL Server 2008 on a 2008R2 system that is a member server of a domain. The systems that are having the error are workgroup systems running Windows 7. Except for the final step, I have pretty much
eliminated the other possibilities in Steps to troubleshoot SQL connectivity issues.
That, and the fact that the application successfully runs from a workstation that is a member of the domain lead me to believe it is an account/authentication issue on the workstation.
From what I have determined SQL authentication is required in this scenario and I have confirmed that the database server is configured for Windows and SQL Server authentication. I have also examined
the configuration file the application uses. It contains the user name and password for the account. Are these credentials not used to establish a connection?
The only thing I can think of, which I haven’t tested because 1) it is a production system and 2) it is a vendor supplied application, is the application needs to be run under a local workstation
account with the same credentials as the SQL Server account.
Could this be the case or is there something else I should be look at?
Thanks in advance.

Thanks for your response. I had posted a reply earlier but for some reason it doesn't appear to have uploaded.
The server name in the connection string is ntsrv12.xxx.yyy.edu. I am able to ping that name and ntsrv12 as well from workstations where the application fails.
I have some information from some additional testing I have done. Using my workstation, which is a domain member, I can successfully run the application when logged on with my domain user account.
However, if I logon with a local account the application fails with the error described above.
I have also been able to match Audit Failures in the SQL Server event log with failed attempts to run the application. There is a two error sequence that appears several times for 15 seconds until the application times out and displays the error message.
I have listed the errors below but certainly the application appears to see the server. Any ideas on what to check next?
Thank you.
The first error in the sequence is this:
Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:
5/6/2014 1:50:05 PM
Event ID:      4776
Task Category: Credential Validation
Level:         Information
Keywords:      Audit Failure
User:
N/A
Computer:      Ntsrv12.xxx.yyy.edu
Description:
The computer attempted to validate the credentials for an account.
Authentication Package:
MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon Account: <MyLocalAccount>
Source Workstation:
<LocalSystemName>
Error Code:
0xc0000064
This error is followed by this one:
Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:
5/6/2014 1:50:05 PM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:
N/A
Computer:      Ntsrv12.xxx.yyy.edu
Description:
An account failed to log on.
Subject:
Security ID:
NULL SID
Account Name:
Account Domain:
Logon ID:
0x0
Logon Type:
3
Account For Which Logon Failed:
Security ID:
NULL SID
Account Name:
<MyLocalAccount>
Account Domain:
<LocalSystemName>
Failure Information:
Failure Reason:
Unknown user name or bad password.
Status:
0xc000006d
Sub Status:
0xc0000064
Process Information:
Caller Process ID:
0x0
Caller Process Name:     -
Network Information:
Workstation Name:        <LocalSystemName>
Source Network Address:
10.1.36.70
Source Port:
50145
Detailed Authentication Information:
Logon Process:
NtLmSsp
Authentication Package:
NTLM
Transited Services:
Package Name (NTLM only):
Key Length:
0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

WCF based named pipe naming convention.

Similar Messages

Maybe you are looking for