Knowledge Base

No Error Message when Remote Link Services is Wrong for DLS

Article ID: 196078

Article Last Modified on 6/28/2004

Microsoft SNA Server 3.0 Service Pack 4
Microsoft SNA Server 4.0
Microsoft SNA Server 3.0 Service Pack 2
Microsoft SNA Server 3.0 Service Pack 3
Microsoft SNA Server 4.0
Microsoft SNA Server 4.0 Service Pack 1

This article was previously published under Q196078

SYMPTOMS

When configuring a Distributed Link Service (DLS), if you specify an invalid resource for Remote Link Services such as \\Snasoga\Sample, you may observe that connection hangs in Pending state with no reported events in the Event Viewer.

If an SNA Server internal trace is captured for the particular Remote Link Service (SnaRemx) in question, it will show that remote link service received the following error:

"RPC failure, service not found."

RESOLUTION

Microsoft has confirmed this to be a problem in SNA Server versions 3.0, 3.0 SP1, 3.0 SP2, 3.0 SP3, 4.0, and 4.0 SP1. We are researching this problem in SNA Server version 3.0 and will post more information here in the Knowledge Base as it becomes available.

This problem was corrected in the latest SNA Server version 4.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

MORE INFORMATION

After applying the update, an event will be logged in the Application Event Log when this error occurs. The Remote Link Service will now report the failure, and include an invalid link service name as in the following example:

"Couldn't open distributed link service connection to remote link service \\<server>\<service> -- Remote link service not found."

Keywords: kbbug kbfix KB196078