Jump to content

p4api.net validation failure

P4Exception p4api p4command validation

  • Please log in to reply
No replies to this topic

#1 AlbertHo



  • Members
  • Pip
  • 1 posts

Posted 15 March 2016 - 01:10 AM

I am debugging an issue where I get P4Exception when I tried to checkout a large number of files (1500 files) through a P4Command edit.

It seems to be server-specific as the same piece works on most p4 server that the application connects to.

{Perforce.P4.P4Exception: '' validation failed:
: :

at Perforce.P4.P4Exception.Throw(String cmd, String[] args, P4ClientErrorList errors, P4ClientInfoMessageList details)
at Perforce.P4.P4Server.RunCommand(String cmd, UInt32 cmdId, Boolean tagged, String[] args, Int32 argc)
at Perforce.P4.P4Command.RunInt(StringList flags)
at Perforce.P4.P4CommandResult..ctor(P4Command cmd, StringList flags)
at Perforce.P4.P4Command.Run()
at EA.Blox.AssetStore.P4.PerforceClient.Run(String cmdName, P4Command cmd) in e:\contact\main\TnT\Code\External\EA\Blox\BloxAssetStore\source\assetstore.p4\PerforceClient.cs:line 1716} Perforce.P4.P4Exception

Opening up the P4Exception in the debugger, I get this:
CmdLine "edit -c 365154 E:\\....long list of filenames......
+ Details Count = 9 Perforce.P4.P4ClientInfoMessageList
+ details Count = 9 Perforce.P4.P4ClientInfoMessageList // contains a list of files currently checked out by others (non-exclusive lock though)
errorCode 857800705 int
ErrorCode 857800705 int
ErrorLevel E_FAILED Perforce.P4.ErrorSeverity
errorLevel E_FAILED Perforce.P4.ErrorSeverity
Message "'' validation failed: \n: : \n" string
message "'' validation failed: \n: : \n" string
+ NextError {Perforce.P4.P4Exception: '' validation failed:

Connection info:
User name: albertho
Workspace name: albertho
Workspace host: BUR1-D1044045
Workspace root: E:\
Current directory: e:
Workspace address:
Security: enabled
Server Name: MEC
Server address: bwm-perforce2:2000
Server root: /perforce/db
Server date: 2016/03/14 21:05:05 -0400 EDT
Server uptime: 2807:13:59
Server version: P4D/LINUX26X86_64/2015.1/1227227 (2015/08/27)
Server license: Electronic Arts [EA] (USA studios) 5001 users (support ends 2016/10/29)
Server license IP:
Monitor: enabled
Proxy Version: P4P/LINUX26X86_64/2014.2/962050 (2014/11/13)
Broker Address: bwm-perforce2:1234
Broker Version: P4BROKER/LINUX26X86_64/2015.1/1126382
Server case handling: insensitive
allowFetch: 2
proxyRoot: /p4proxy/bwm-perforce2_1234/cache
clientCase: insensitive
allowPush: 1
ServerID: mec-commit
ldapAuth: enabled
serverServices: commit-server
clientLock: none

Despite the exception, the files do get opened for edit. And I get the same exception from both 2015.1 and 2016.1 versions of p4api.

Any ideas?

Also tagged with one or more of these keywords: P4Exception, p4api, p4command, validation

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users