[p4] 2007.2 Problem (Changelist empty)

[Chuck Emary]

Hello,
I seem to recall similar strange behavior like this when we upgraded.  Our issue turned out to be related to the fact that the user's clientspec contained lines to areas where they were denied access to via the protect file.  Once they removed the lines from the clientspec where they did not have permissions to, the problem went away.  Not sure if that will help, but it seemed similar enough to mention.

Good Hunting,
Chuck Emary
Software Configuration Manager
CSI Inc.

-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of Monica Sanchez
Sent: Thursday, September 13, 2007 1:17 PM
To: perforce-user at perforce.com
Subject: [p4] 2007.2 Problem (Changelist empty)

Hello,



I just upgrade the perforce server to 2007.2 from 2005.1. Most of my
clients were using 2005.1 perforce client application, but others were
using 2004.



Two of the users on 2004 had problems just after the server upgrade. The
error/warning was "Excessive combinations of wildcard...in path and
maps" and they were not able to submit any files because the changelist
looked empty.

I upgraded one of the users and then reverted the changes and she is
working fine now because she did not have a lot of pending changelists.

The other user has a lot of pending changelist and after the upgrade he
is able to see the files on the changelist but when we try to submit
there is not files to submit on the submit form.

Also he is getting the error "Change spec appears to be badly damage!".



I don't want him to backup-revert-checkin-restore all his files. Do you
know what the correct way to fix change spec is?



Thanks,

Monica







_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user