Re: windows script issue

On Fri, 13 Apr 2018 15:02:57 -0400, Chuck Miller via 4D_Tech wrote: > Hi All, > > I need to run a command line script on windows to retrieve a password. > > I have filled a text variable to use with launch external process and > set to pasteboard. When I run from cmd prompt. I get expected

RE: windows script issue

At first look, the escaping seems invalid. Specifically, you escape the folder separator after the drive letter (E:\\) but you are not escaping the folder separator between the folders themselves (\CyberArk\ApplicationPasswordSdk\CLIPasswordSDK.exe). Honestly its best to just use the Folder

Re: Clients cannot see v16 R6 on windows server

On Apr 13, 2018, at 2:00 PM, John Baughman wrote: > First off, I think I found the problem. Looking at the Firewall rules I see > that the ports are being managed by application and I see both R5 and R6 are > listed twice. What I did not notice right off was that the action for R6 was > set to

windows script issue

Hi All, I need to run a command line script on windows to retrieve a password. I have filled a text variable to use with launch external process and set to pasteboard. When I run from cmd prompt. I get expected results but when tun from launch external process I get nothing no in, no out no

RE: Clients cannot see v16 R6 on windows server

John, > Someone else pointed out, I think off list, that I would have a conflict with > 19814. So I did a bit of testing with netstat. Based on the netstat results I > don’t believe that 4D is necessarily grabbing one below and one above the set > application port. You are correct, 4D doesn't

Re: Clients cannot see v16 R6 on windows server

Hi Janet, First off, I think I found the problem. Looking at the Firewall rules I see that the ports are being managed by application and I see both R5 and R6 are listed twice. What I did not notice right off was that the action for R6 was set to Blocked. I have changed it to Allow but

Re: Clients cannot see v16 R6 on windows server

When you specify port 19813, 4D is using 19812-19814. When you specify 19815, 4D uses 19814-19816. The 2 4Ds may be clashing on port 19814. JJ > > Message: 12 > Date: Thu, 12 Apr 2018 15:38:59 -1000 > From: John Baughman > To: 4D iNug Technical <4d_tech@lists.4d.com> >

Re: Clients cannot see v16 R6 on windows server

Resolved I was missing the 4D extensions folder in the built client -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive:

Re: Clients cannot see v16 R6 on windows server

I am getting something similar since I update to R6 this week. The EnginedServer.4Dlink file is not being recognised on windows 7 but it ok on win8. My 2 win7 clients always display the connect dialog but no servers are present. They connect okay if I manually enter the details in custom. And when

RE: Web Server Freeze

We are only using the HTTP port as this does not require a secure connect, just a stable one! ;-) Best, Steve -Original Message- From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of JBellos via 4D_Tech Sent: Thursday, April 12, 2018 9:31 PM To: 4d_tech@lists.4d.com Cc: