I'll look up how to set that and see if that fixes the issue. Please hold.
Hm, standard windows sc config command is saying:
Set-Content : A positional parameter cannot be found that accepts argument 'binPath='. At line:1 char:1 + sc config Perforce2 binPath= "D:\Program Files\Perforce\Server2\p4s.e ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Set-Content], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetContentCommand
I assume that means the service's definition lacks the binPath value to be set, so fun. I'll start checking perforce commands, maybe there's something there.
Turns out it does, I was just using the CMD command rather than Powershell's command. It -appears- to be fixed, it started, so now I'll see if I can connect.
Success! I can connect.
Thank you. I'll have to make note of how to verify and set the service path. Seems like that should be a step in the creation process that isn't listed on that page or is out of date.