Anyone successful with binding to Perforce?

This forum is for all Flare issues related to using Source Control.
Post Reply
bunnycat
Propeller Head
Posts: 70
Joined: Tue Nov 03, 2015 6:44 am

Anyone successful with binding to Perforce?

Post by bunnycat »

I'm using Flare 2021 R3 (but same experience with older Flare 2020 R3). Binding a Flare project to Perforce Helix just doesn't function, I receive an error of "Bind failed: Server path does not exist | myServer:1666."

Bind project dialog uses my credentials just fine.
Can select Depot as the Type.
Can traverse through the paths in my depot to the directory I want.
But it fails at the last step.
  • For server name, I've tried shortname, IP address, FQDN - thinking it was the format of the servername
    Removed the port number 1666 from the server - thinking that maybe Flare didn't need it. Flare did need it. Else it errors out with a login failure rather than "server path does not exist" failure.
    I've tried binding a project that was never in Perforce. Failed
    Tried binding project already in Perforce, but just not bound via Flare setting. Failed.
Do I assume that binds to Perforce just don't work and I should write up a defect for MadCap support?

Thanks!!

CAT
Post Reply