Nick Antonelli Posted June 9, 2020 Report Share Posted June 9, 2020 Hello, I am attempting to sync a Perforce stream with our PlasticSCM installation. I spun up a Windows 2019 Base install on AWS and installed PlasticSCM, then I setup the command per the documentation. I had downloaded the 2018.3 p4api.net.dll from Perforce's website and placed it in the same directory as the `cm` command. When I execute `cm synchronize`, I get the following: Quote Error: Could not load file or assembly 'p4api.net, Version=2016.1.140.7015, Culture=neutral, PublicKeyToken=f6b9b9d036c873e1' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) I have tried looking for an earlier version of the DLL, both on Perforce's website and elsewhere, but I have not been able to locate a copy. Are there any plans to use an updated DLL for the porting of Perforce code to PlasticSCM? Is there any workaround that can mitigate the issue? It's not the end of the world if we can't migrate this stream, but I would prefer to do so if possible. Thanks! Link to comment Share on other sites More sharing options...
calbzam Posted June 10, 2020 Report Share Posted June 10, 2020 Hi Nick, How did you install Plastic? What is the specific installer? I've installed the last Plastic version for WIndows and the "p4api.net.dll" file is included in the Plastic "client" folder. You don't need to download it from P4 website. Regards, Carlos.p4api.net.zip Link to comment Share on other sites More sharing options...
Nick Antonelli Posted June 10, 2020 Author Report Share Posted June 10, 2020 I downloaded it off of the plasticscm website, since it was a fresh install on AWS. I think I clicked on the Enterprise version. Now that you mention it, I don't know if I installed the server component - I definitely installed the client for Plastic. Let me reinstall and I'll get back to you. Link to comment Share on other sites More sharing options...
Nick Antonelli Posted June 10, 2020 Author Report Share Posted June 10, 2020 That did it! Installing the server component installed the proper p4api.net.dll file. Might be good to include that with just the client installation as well. Appreciate the help, thank you! Link to comment Share on other sites More sharing options...
calbzam Posted June 10, 2020 Report Share Posted June 10, 2020 Ok, thanks for the upate Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now