Search
Closed
as Not Reproducible Help for as Not Reproducible

1
Sign in to vote
0
Sign in to vote
Sign in
 to vote
Type: Bug
ID: 484661
Opened: 8/22/2009 6:43:33 AM
Access Restriction: Public
0
Workaround(s)
1
User(s) can reproduce this bug
I use a Named pips communication, and received this error many times:

Communication Exception
There was an error writing to the pipe: The pipe is being closed. (232, 0xe8).

So how i solve this problem?
Details (expand)

Product Version

.NET Framework 3.5 SP1
Product Language
English

Operating System
Windows 7 (client)
Operating System Language
English

Architecture
x64

Priority
(1=blocking, 2=important, 3=nice to have)
1

Severity
(1=major functionality issue, 2=important functionality issue, 3=nice to have)
1

Steps to Reproduce
Using Named pips connection.
Actual Results
Exception
Expected Results
Perform the method invoke on the server
Component Usage
(any information on your scenario that may help in investigating your issue)
 

How often does this happen?
Sometimes Happens

Have you seen this problem in other versions?
 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 8/27/2009 at 2:38 PM
Hi,
I was looking into this one but we would really need some details before we can figure out what could be going on? Could you please attach a repro of the issue? Just a simple client and service piece of what is it that you are doing? Do you see the error when you have the service idle for some time and then the client makes a call after some time? Is your service web hosted?
I am resolving this bug as "No Repro" for now. Please feel free to reactivate it once you have some additonal details.
Thanks.
Piyush Joshi
[Program Manager]
© 2009 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement