Re: [VW 7.4.0] Intermittent error using WinProcess>>cshOne: "Pipe creation has failed. ErrorCode: 127."

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [VW 7.4.0] Intermittent error using WinProcess>>cshOne: "Pipe creation has failed. ErrorCode: 127."

Denis Johnson
Hi Stewart, has the use of the ExternalProcessStreams resolved your issue ?

I have been using ExternalProcessStreams albeit the earlier version
(prior to it using threaded call out) and customers sporadically also
receive the same error i.e. 127 Pipe creation failed.

I'll see if updating to the latest makes any difference

cheers Denis

On 2/28/07, Stewart MacLean <[hidden email]> wrote:

> Thanks Michael,
>
> I'll check it out...
>
> Cheers,
>
> Stewart
>
> >-----Original Message-----
> >From: Michael Lucas-Smith [mailto:michael.lucas-
> >[hidden email]]
> >Sent: 27 February 2007 6:56 p.m.
> >To: Stewart MacLean
> >Cc: [hidden email]
> >Subject: Re: [VW 7.4.0] Intermittent error using WinProcess>>cshOne:
> "Pipe
> >creation has failed. ErrorCode: 127."
> >
> >I'd suggest you use ExternalProcessStreams in public store instead of
> >the dodgy WinProcess>>cshOne stuff.
> >
> >Cheers,
> >Michael
> >
> >>
> >>
> >>
> >> Hi,
> >>
> >>
> >>
> >> I?m using
> >>
> >>
> >>
> >> ^((ExternalProcess defaultClass cshOne: 'ipconfig /all') readStream
> >>
> >> skipThroughAll: 'Physical';
> >>
> >> upTo: $:;
> >>
> >> upToSeparator;
> >>
> >> upToSeparator) trimBlanks
> >>
> >>
> >>
> >> to establish the MAC address.
> >>
> >>
> >>
> >> However this is failing fairly regularly with a ?Pipe creation has
> >failed. ErrorCode: 127.?
> >>
> >>
> >>
> >> Can some please tell me what does this error means, and how can I
> >> avoid it?. Any pointers appreciated.
> >>
> >>
> >>
> >> Cheers,
> >>
> >>
> >>
> >> Stewart
> >>
> >>
> >>
> >> PS I?ve also come across the following:
> >>
> >>
> >>
> >> // Fetches the MAC address and prints it
> >>
> >> static void GetMACaddress(void)
> >>
> >> {
> >>
> >> IP_ADAPTER_INFO AdapterInfo[16]; // Allocate information
> >>
> >>
> //
> >for up to 16 NICs
> >>
> >> DWORD dwBufLen = sizeof(AdapterInfo); // Save memory size of
> buffer
> >>
> >>
> >>
> >> DWORD dwStatus = GetAdaptersInfo( // Call GetAdapterInfo
> >>
> >> AdapterInfo,
> //
> >[out] buffer to receive data
> >>
> >> &dwBufLen);
> >> // [in] size of receive data buffer
> >>
> >> assert(dwStatus == ERROR_SUCCESS); // Verify return value is
> >>
> >>
> //
> >valid, no buffer overflow
> >>
> >>
> >>
> >> PIP_ADAPTER_INFO pAdapterInfo = AdapterInfo; // Contains pointer to
> >>
> >>
> //
> >current adapter info
> >>
> >> do {
> >>
> >> PrintMACaddress(pAdapterInfo->Address); // Print MAC address
> >>
> >> pAdapterInfo = pAdapterInfo->Next; // Progress
> >through
> >>
> >>
> //
> >linked list
> >>
> >> }
> >>
> >> while(pAdapterInfo);
> //
> >Terminate if last adapter
> >>
> >> }
> >>
> >>
> >>
> >> From
> >> http://www.codeguru.com/Cpp/I-
> >N/network/networkinformation/article.php/c5451.
> >>
> >>
> >>
> >> How easy would it be to adapt this to ExternalInterface? (I?m no C
> >expert!)
> >>
> >>
> >>
> >>
> >>
> >>
> >>
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

RE: [VW 7.4.0] Intermittent error using WinProcess>>cshOne: "Pipe creation has failed. ErrorCode: 127."

Stew MacLean
Hi Denis,

I downloaded ExternalProcessStreams and had a brief look. As it required
SUnit and some other stuff as prerequisites, and that the problem hasn't
occurred for sometime, I haven't taken the time to reimplement using
this. (If it ain't broke...).

As you are also getting this error using ExternalProcessStreams, I
suspect that this one of Windows little mysteries...

Cheers,

Stewart



>-----Original Message-----
>From: Denis Johnson [mailto:[hidden email]]
>Sent: 12 April 2007 4:18 p.m.
>To: Stewart MacLean
>Cc: [hidden email]
>Subject: Re: [VW 7.4.0] Intermittent error using WinProcess>>cshOne:
"Pipe
>creation has failed. ErrorCode: 127."
>
>Hi Stewart, has the use of the ExternalProcessStreams resolved your
issue ?

>
>I have been using ExternalProcessStreams albeit the earlier version
>(prior to it using threaded call out) and customers sporadically also
>receive the same error i.e. 127 Pipe creation failed.
>
>I'll see if updating to the latest makes any difference
>
>cheers Denis
>
>On 2/28/07, Stewart MacLean <[hidden email]> wrote:
>> Thanks Michael,
>>
>> I'll check it out...
>>
>> Cheers,
>>
>> Stewart
>>
>> >-----Original Message-----
>> >From: Michael Lucas-Smith [mailto:michael.lucas-
>> >[hidden email]]
>> >Sent: 27 February 2007 6:56 p.m.
>> >To: Stewart MacLean
>> >Cc: [hidden email]
>> >Subject: Re: [VW 7.4.0] Intermittent error using WinProcess>>cshOne:
>> "Pipe
>> >creation has failed. ErrorCode: 127."
>> >
>> >I'd suggest you use ExternalProcessStreams in public store instead
of

>> >the dodgy WinProcess>>cshOne stuff.
>> >
>> >Cheers,
>> >Michael
>> >
>> >>
>> >>
>> >>
>> >> Hi,
>> >>
>> >>
>> >>
>> >> I?m using
>> >>
>> >>
>> >>
>> >> ^((ExternalProcess defaultClass cshOne: 'ipconfig /all')
readStream

>> >>
>> >> skipThroughAll: 'Physical';
>> >>
>> >> upTo: $:;
>> >>
>> >> upToSeparator;
>> >>
>> >> upToSeparator) trimBlanks
>> >>
>> >>
>> >>
>> >> to establish the MAC address.
>> >>
>> >>
>> >>
>> >> However this is failing fairly regularly with a ?Pipe creation has
>> >failed. ErrorCode: 127.?
>> >>
>> >>
>> >>
>> >> Can some please tell me what does this error means, and how can I
>> >> avoid it?. Any pointers appreciated.
>> >>
>> >>
>> >>
>> >> Cheers,
>> >>
>> >>
>> >>
>> >> Stewart
>> >>
>> >>
>> >>
>> >> PS I?ve also come across the following:
>> >>
>> >>
>> >>
>> >> // Fetches the MAC address and prints it
>> >>
>> >> static void GetMACaddress(void)
>> >>
>> >> {
>> >>
>> >> IP_ADAPTER_INFO AdapterInfo[16]; // Allocate information
>> >>
>> >>
>> //
>> >for up to 16 NICs
>> >>
>> >> DWORD dwBufLen = sizeof(AdapterInfo); // Save memory size of
>> buffer
>> >>
>> >>
>> >>
>> >> DWORD dwStatus = GetAdaptersInfo( // Call GetAdapterInfo
>> >>
>> >> AdapterInfo,
>> //
>> >[out] buffer to receive data
>> >>
>> >> &dwBufLen);
>> >> // [in] size of receive data buffer
>> >>
>> >> assert(dwStatus == ERROR_SUCCESS); // Verify return value is
>> >>
>> >>
>> //
>> >valid, no buffer overflow
>> >>
>> >>
>> >>
>> >> PIP_ADAPTER_INFO pAdapterInfo = AdapterInfo; // Contains pointer
to

>> >>
>> >>
>> //
>> >current adapter info
>> >>
>> >> do {
>> >>
>> >> PrintMACaddress(pAdapterInfo->Address); // Print MAC address
>> >>
>> >> pAdapterInfo = pAdapterInfo->Next; // Progress
>> >through
>> >>
>> >>
>> //
>> >linked list
>> >>
>> >> }
>> >>
>> >> while(pAdapterInfo);
>> //
>> >Terminate if last adapter
>> >>
>> >> }
>> >>
>> >>
>> >>
>> >> From
>> >> http://www.codeguru.com/Cpp/I-
>> >N/network/networkinformation/article.php/c5451.
>> >>
>> >>
>> >>
>> >> How easy would it be to adapt this to ExternalInterface? (I?m no C
>> >expert!)
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>>
>>
>>
>>