Perforce Tickets Issues

scmuser created the topic: Perforce tickets issues
Some of the devs on my team have been asking about whether Perforce tickets really need to be bound to IPs. It’s pretty annoying to have to re-authenticate when switching from wireless to wired. When we first switched to OTP, I don’t recall it working this way, but perhaps I’m misremembering… Was this a change that was made later or has it always been this way since OTP went into use?

rajeshkumar replied the topic: Re: Perforce tickets issues
Not sure if you have got solution for your problem or not. If not, please use –a while login which will obtain ticket that is valid for all IP address and host till 24 hours.

Such as…

p4 login –a
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Force users to upgrade their perforce client software

rajeshkumar created the topic: force users to upgrade their perforce client software
How to force users to upgrade their perforce client software

kb.perforce.com/article/1363/how-to-forc…heir-client-software
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Perforce client version numbers v99999

rajeshkumar created the topic: Perforce client version numbers v99999
The mystery v99999 is an artifact of how older releases of the p4 command line client set the protocol level. In the code, it looked something like this:

client.SetProtocol( “api”, “99999” );

In the absence of better version information, the server logs the API protocol level, or if that’s not set, the client protocol level. Since 2004.2 p4 always sets the API level to 99999, so it’s a version of p4 that was built after that, but before they introduced an explicit version string (2005.2). So basically if you see v99999 it’s either a 2004.2, or 2005.1 p4.

reference:
kb.perforce.com/article/512
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

To know Password last changed for this perforce user

rajeshkumar created the topic: To know Password last changed for this perforce user
I have come across 2 ways..

1/. User form field will have following options…
PasswordChange: Read-only

The date and time of the user’s last password change. If the user has no password, this field is blank.

OR
p4 -p IP:PORT -u users -l | grep

Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Operation ‘dm-SubmitChange’ failed in perforce

rajeshkumar created the topic: Operation ‘dm-SubmitChange’ failed in perforce
Solution for following error…
Operation ‘dm-SubmitChange’ failed.
Sequence error: next changelist ‘Change 73’ already exists!
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Prompting password repeadetly in perforce

rajeshkumar created the topic: Prompting password repeadetly in perforce
Some checks need to be done.

1. Check .p4ticket folder exist or not? .p4ticket can be found iin %USERPROFILE%\p4tickets.txt(windows) and $HOME/.p4tickets(other OS)
2. Check .p4ticket file permission and its directory permission. May be its not able to write entry in .p4ticket due to permission issues.
3. Last options, deleting .p4qt folder. Remember this will delete all of your old existing reference. Instead deleting you can rename it. .p4qt folder can be found in %USERPROFILE%\.p4qt in windows and ~/Library/Preferences/com.perforce.P4V/ in mac and ~/.p4qt/ in unix.
4. Post me if you could not get it fixed 🙂

Reference
kb.perforce.com/article/667/locating-preferences-files-for-p4v
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Rollback vs Back Out in perforce

rajeshkumar created the topic: Rollback vs Back Out in perforce
Rollback vs Back Out in perforce
Both of these operations restore a set of files to a previous state. The difference being:

Back Out Submitted Changelist X
The restore operation is restricted to the files submitted in changelist X.

Roll Back
Rolling back can involve any number of files and to any point. You tell Perforce what point you want to rollback to (a specific rev, CL, label). The files are restored to the state that they were in at that point in time (a specific rev, CL, label).

Very useful reference is given in following url…

stackoverflow.com/questions/2775823/what…submitted-changelist
kb.perforce.com/article/14
kb.perforce.com/article/517
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Performance of Perforce Forwarding Replica (Smart Proxy)

pradeep created the topic: Performance of Perforce Forwarding Replica (Smart Proxy)
Hi Guys,
Does any one uses or tend to use Perforce’s Forwarding Replica (also known as Smart Proxy)?
From their documents it seems like a good option. But I would like to know from a User’s perspective on its performance and its response time.

Please reply with any comments you have on this.

– Pronita

rajeshkumar replied the topic: Re: Performance of Perforce Forwarding Replica (Smart Proxy)
Hi Pronita,

I had written this blog long back and you remind me to upload this today.

Please refer this. hope this will e helpful for you.

www.scmgalaxy.com/perforce/perforce-replication.html

if you have any specific questions, do share with me. I will try to help you out.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

pradeep replied the topic: Re: Performance of Perforce Forwarding Replica (Smart Proxy)
Thanks a lot Rajesh. This looks like a real good topic.

Tagged :

Perforce user deletion issues.

rajeshkumar created the topic: perforce user deletion issues.
Today i was trying to delete some perforce users and found some strange issues as below;

Problem
p4 user -d -f raj
User rajhas file(s) open on 2 client(s) and can’t be deleted

p4 -u raj-c -H opened
Access for user ‘raj’ has not been enabled by ‘p4 protect’.

p4 client -d -f raj_client
Client ‘raj_client7’ has files shelved; use ‘shelve -df’ to remove them, and then try again.

p4 -u raj -c raj_client -H revert -k //…
Access for user ‘raj’ has not been enabled by ‘p4 protect’.

Solution which I found out.

The messages receiving show that access for the user ‘raj’ has been disabled by removing all entries corresponding to this user from the Perforce Protections Table.

You can check this by running:
p4 protect -o | grep raj

Note you must be a superuser to run this command.

Granting the user ‘raj’ access to the areas of the depot where they have files open or shelved will allow you to delete these workspaces and shelves. You will then be able to delete the user from Perforce.

More information reference…
www.perforce.com/perforce/r10.2/manuals/…protect.html#1064878

Problem –
Client ‘bb_Workspace’ has files shelved; use ‘shelve -df’ to remove them, and then try again.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :