Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 Extensions Documentation | 2025.1

# Server extension errors and troubleshooting

As seen from the client-side, here are some errors and where to look for answers:

Error | Action
--- | ---
extName validation failed: logged by server | When a trigger or server extension has a failure, the logged by server message can be presented. It is an intentionally uninformative message because trigger or server extension failures can include stack traces for that user code, which might be sensitive information. The server’s log file will contain the full output.
Partner exited unexpectedly | This message means that the remote procedure call (RPC) connection between the client and server was not gracefully closed. The cause could be in the physical network connection or the server. The server’s log file might provide more details about the problem. For example, the following error indicates a server crash: Perforce server error: Process 1234 exited on a signal 11! This should be reported to Perforce Technical Support.

Your search for returned results