Problem with connection to Facebook (Parameter DriverFolder is invalid)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Problem with connection to Facebook (Parameter DriverFolder is invalid)

L4 Transporter

Hello CyberArk community!

 

I am having a hard time troubleshooting my configuration to Facebook website. When I try to connect I get the message:

Field_Content_versions_oct20__068Ht00000VfFuyIAF.pngI verified that there are no spelling mistakes in my DriverFolder value:

Field_Content_versions_oct20__068Ht00000VfFv3IAF.png 

And also made sure that I have the driver in the specified folder on my PSM server:

Field_Content_versions_oct20__068Ht00000VfFvDIAV.png 

I tried removing the value DriverFolder completely read that if the driver is located in the Components folder it will be found automatically, but I am still getting the "Parameter DriverFolder is invalid" error when I try to connect. I do not restart any services when I delete or add the DriverFolder setting, do I maybe need to restart something in order for changes to get applied?

 

Can someone please help, what can be the reason of this problem and how to solve it?

1 accepted solution

Accepted Solutions

L6 Presenter

Since the parameter is DriverFolder, try going with C:\Program Files(x86)\CyberArk\PSM\Components instead. Remove the exe file at the end and try again

View solution in original post

5 REPLIES 5

L6 Presenter

Since the parameter is DriverFolder, try going with C:\Program Files(x86)\CyberArk\PSM\Components instead. Remove the exe file at the end and try again

Hello TPandey,

 

I have just tried your suggestion and I am still getting the same error. I suspected that the problem might be with the Program File (x86) folder, so I tried specifying it in different ways, like: Program Files(x86), Program Files (x86), none of them worked. Is there a way I can check which folder specifically cannot be found?

 

Update:

 

I was able to solve the DriverFolder problem, once I put the path like this: C:\Program Files (x86)\CyberArk\PSM\Components\

 

However, now when I click connect, I get this error:

Field_Content_versions_oct20__068Ht00000VfG4vIAF.png 

Here is my browser path (even though I don't think there is a problem with it):

Field_Content_versions_oct20__068Ht00000VfG50IAF.png 

Can you please help, how do I solve this problem? I removed the comments that were restricting the browser in the AppLocker file and ran the ps1 script.

Can you confirm that chrome.exe is present in that path? Note that this is looking in Program Files and not Program Files(x86). If you have a 64-bit Chrome installed, you'll find it in Program Files and if it's a 32-bit installation, it'll be in Program Files(x86). Depending on which one you're trying to use, ensure that relevant path is whitelisted in AppLocker. That's all I can think of as the BrowserPath can only point to either the exe not being in the path or AppLocker blocking it

Ok, I was able to solve the problem, I just switched to Edge and everything works fine now XD!

 

Thanks for your help, TPandey!

 

I do have one final question, do you know if it's possible to upload and download files during the HTTP session? If you don't know that's ok, I guess that's a whole different topic and deserves a separate post.

  • 1 accepted solution
  • 474 Views
  • 5 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!