Posted 19 February 2015 - 01:37 PM
I installed P4V version 2014.3 and it seems not to contain P4EXP. It was part of version 2014.1.
Was P4EXP removed?
Posted 19 February 2015 - 09:00 PM
Yes, P4EXP was removed, as you observed.
Perforce Technical Support recommends that users of Perforce P4V and P4EXP on Windows (only) upgrade to P4V 2014.3/998867, or the latest P4V 2014.2 patch 4 version (2014.2/1003436).
The Windows installer for the new P4V 2014.3 release will automatically uninstall the Perforce Windows Explorer Plugin (P4EXP). The latest P4V 2014.2 version will also automatically uninstall P4EXP. The 2014.2 builds of P4EXP are known to cause server crashes due to leaving connections open.
The updated P4V installers can be downloaded from the Perforce web site here:
If you have a user who requires P4EXP, please follow the directions in the following Knowledge Base article to manually install the latest stable version (2012.2) of the P4EXP plugin.
Additional details on the P4V/P4EXP installer patches can be found in their respective release notes:
We will be releasing a stand-alone installer for P4EXP in March, 2015.
Posted 19 February 2015 - 10:36 PM
Could you give us a list of P4EXP version strings, in both forms, that have been released and we should be watching out for?
Posted 04 March 2015 - 06:07 PM
just to make sure, if some users currently still have P4V 2014.1, do they need to upgrade, or is it safe for them to keep this version at the moment.
I.e. does the P4EXP version shipped with 2014.1 causes problems as well, or do the server crashes only occur with a 2014.2 P4EXP version ?
Thanks and regards,
Posted 05 March 2015 - 12:16 AM
I've got an user in a remote office with a lot of open idle connections. When I look up the process IDs in my server log, the client ID string is "[dot-net-api-p4/1.0]". They appear to be doing mostly "user-fstat" commands of various files on the user's computer. I would almost say the commands are all "user-fstat", but i haven't looked at all of individual commands and there are a LOT of them.
Posted 05 March 2015 - 01:01 AM
Yes there was also a problem with the .Net API which was fixed as stated here in the release notes:
Bugs fixed in 2014.2 Patch 1
#960568 (Bug #75389, #75997) *
A memory leak has been fixed which could previously cause
crashes in client applications built with the .NET API.
Connections are now properly closed on the server side after
a command has run.
Posted 05 March 2015 - 01:08 AM
P4EXP 2014.2 has been rebuilt with the patched P4API.NET 2014.2.
This addresses the affects of P4API.NET bugs #75389 and #76072
which originated in P4API.NET 2014.2 but have been fixed as of
change #960568. See p4api.netnotes.txt for further details.
Also tagged with one or more of these keywords: P4EXP, P4V, 2014.3
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users