Geek asks and answers

Unknown field name 'SubmitOptions' after Perforce update

I just migrated / upgraded from installing Windows 2003 Perforce 2009.2 to Windows 2008 R2 2010.2, and noted that after the update, the only problem that seems to be present is the inability to create / edit workspaces from the user interface - as this tries to set the SubmitOptions parameter and throws

Error at line 0 of field 'SubmitOptions' in client specification.
Unknown field name 'SubmitOptions'.

Yes, I can create / modify a client specification with p4 client, if I am not trying to enable a parameter SubmitOptions.

As far as I can tell, all aspects of the upgrade were successful (replacing p4d, p4d -xufor updating the database, having a license, etc.)

Any ideas? Did not find the whisper of this problem on the Internet (and my google fu is pretty good ...)

Updates: Conclusion from p4 spec -o client(I deleted all comments)

# A Perforce Spec Specification.
Fields:
    301 Client word 32 key
    302 Update date 20 always
    303 Access date 20 always
    304 Owner word 32 optional
    305 Host word 32 optional
    306 Description text 128 optional
    307 Root line 64 required
    308 AltRoots llist 64 optional
    309 Options line 64 optional
    310 LineEnd select 12 optional
    311 View wlist 64 optional

Words:
    View 2

Formats:
    Client 1 normal
    Update 2 L
    Access 4 L
    Owner 3 R
    Host 5 R
    LineEnd 0 L

Values:
    Options noallwrite/allwrite,noclobber/clobber,nocompress/compress,unlocked/locked,nomodtime/modtime,normdir/rmdir
    LineEnd local/unix/mac/win/share
+3
source share
1 answer

In the end, providing the following additions to the customer specification resolved the issue:

Fields:
    313 SubmitOptions select 25 optional
    314 Stream line 64 optional
Formats:
    SubmitOptions 0 L
Values:
    SubmitOptions submitunchanged/submitunchanged+reopen/revertunchanged/revertunchanged+reopen/leaveunchanged/leaveunchanged+reopen

I added them to the previous values ​​and presented the changes using a combination

p4 configure set spec.custom=1

p4 spec -i client < fixedp4clientspec.txt

The first command was required because I got an error "Custom spec of type 'client' is not allowed. Set spec.custom=1 to override."when I tried to update the specification without it. And I really don’t know that to solve this problem, line 314 was needed, but it was suggested when it was different from the specification, which worked elsewhere.

Thanks for the help!

+4
source

More articles:


All Articles