Find contentI am having a problem opening named pipes in Windows.
I have used this for linux and older Windows servers, but seem to have issues with newer Windows servers.
I create 2 pipes in a separate process (which are inbound and outbound pipes for Glovia).
I can open the outbound pipe from Glovia fine.
But I get a permission error when trying to open the inbound pipe to Glovia.
I am using standard naming protocol (\\.\pipe\glovia_in and \\.\pipe\glovia_out).
I define them as external files with a SEQ type.
Like mentioned, I have used this successfully in linux and older WIndows servers, so not sure what has changed and what needs to be done to use them.
Any feedback would be appreciated.
