linked server can not connect using Named Pipes

Push Transactional Replication

Replication was running fine, we switched one of the servers in the local lan to named pipes.

We can still connect to the database with Query Analyzer (QA) and Enterprise Manager (EM) but replication failed.

We realized that the linked server on the distributer for that subscriber could not connect.

We switched back to TCP and all is well again.

We can issue a Net Use \\server\ipc$ with success so it seems the pipe is ok, and we can still connect with QA and EM.

Why would the protocol make a difference. Why can't we connect a linked server with Named Pipes when it connects fine with TCP, and why even though the linked server can not connect can swe till connect with QA or EM.

More info please:

What agent is failing, distribution agent? Is logreader/snapshot agent functioning properly?

Which machine was configured to use named pipes, distributor or subscriber?

Did you change this at the client level or server level?

When you use QA/EM, are you connecting locally or remotely?

What error are you getting?

Linked server

Hi All,
I'm using Sql Server 2005 express, what i want is?
in my requirement the LAN may disconnected for sometime for some reason what ever it may? during that time i want to store the details in MS Access database which is present in the local machine....once the LAN Connection established i want to transfer the data from MS Access to Sql Server...? IS it possible..? or otherwise i want to Sync the data between MS Access and Sql Server 2005 Express is it possible.

I'm using C# .net Desktop Application for development.

I taught of creating a linked server, Is it correct or some other things to perform to do this operation.
plz help me...

-Amjath

I don't think that the concept of a 'Linked Server' will solve your problem. You are indicating that the problem is that the link is not dependable. You indicate that you need the ability to store locally, and 'push' to the server when the server is available.

I suggest that you may find that having the application store the data locally as a 'persisted' xml dataset when the server is not available, and that the application could periodically check for server connection and 'push' the data to the server when connected. Alternatively, the data could be stored in a local Access database or even a local SQL Express database.

Storing locally in SQL Express and then using Replication might solve the problem, but it would require that the server was using SQL Standard Edition.