Perforce 2012.3: P4Sandbox User's Guide

Chapter 6

Troubleshooting P4Sandbox

Troubleshooting

This chapter lists solutions to issues you may encounter when using P4Sandbox.

For help with using P4Sandbox, contact your Perforce Technical Support representative at [email protected].

Localhost connection error

When you execute a command, P4Sandbox returns a Perforce client error message similar to the following:

Perforce client error: TCP connect to localhost:1999 failed. connect: 127.0.0.1:1999: Connection refused

This message that indicates P4Sandbox is disconnected and probably stopped. To restart P4Sandbox:

1.	Issue a stop command to ensure that the P4Sandbox is actually stopped:

•	p4: No command necessary

•	P4V: Connection > Close Connection

2.	Restart P4Sandbox:

•	p4: p4sandbox start

•	P4V: Connection > Open Recent > localhost connection to P4Sandbox

P4Sandbox does not relaunch in P4V

P4Sandbox successfully launched during the initial configuration. But when you restart P4V, your P4Sandbox does not relaunch automatically.

This behavior indicates that P4Sandbox is disconnected from P4V. To restart P4Sandbox:

1.	Click the P4Sandbox Configuration icon.

•	Mac OS X: Applications > p4sandbox-config.app

•	Windows: Start > All Programs > Perforce

•	P4V: Connection > Configure Sandbox

2.	Click Next to go through the P4Sandbox Configuration Wizard pages and restart the P4Sandbox.

3.	In P4V, go to Connection > Open Recent to select your localhost server.

P4Sandbox and P4V password issue

When you are logged into P4V and are attempting to perform local stream to mirror stream tasks, you receive the following error message:

Perforce password (P4PASSWD) invalid or unset. Central server for remote depot 'remote' at address <host:port> is not currently accessible.

This message indicates that you are not logged into the shared service. To log into the shared service:

1.	Type the following command in p4:

p4 -p <shared service port setting> login

For example:

p4 -p play:1999 login

2.	When prompted, enter your Perforce password.

Cannot copy up files

You cannot copy up files from the P4Sandbox to the mirror stream.

Verify that you have merged down the latest changes from the shared service to the local stream. See the following sections:

•	p4 users: Updating P4Sandbox with shared service changes.

•	graphical client application users: Merging down changes from the shared service.

Files shelved to an incorrect stream

You accidentally shelved files to a different stream than the intended stream.

Fix this issue using one of the following methods:

p4 print method

1.	Switch to the desired stream; type:

$ p4 switch //streams/right_stream

2.	For each file that you want, type the following p4 print command sequence:

p4 print -o <local file system path> <depot path>@=<shelved changelist number>

$ p4 print -o path/to/file.cpp //streams/wrong_stream/path to file/file[email protected]=1234

$ p4 print -o path/to/file.h   //streams/wrong_stream/path to file/file[email protected]=1234

3.	Open these files (and any others) for edit; type:

$ p4 reconcile

The p4 reconcile command opens the following for edit:

•	All the files that you printed in step 2.

•	Any files in the directory that you have modified without running p4 edit.

Zip method

1.	While still in the incorrect stream, make an archive of the directory that contains the files you want. Zip or duplicate the directory.

2.	Switch to the desired stream.

3.	Replace the directory contents with the archived content.

4.	Open the appropriate files for edit; type:

$ p4 reconcile

The p4 reconcile command opens the following for edit:

•	All the archived content files.

•	Any files in the directory that you have modified without running p4 edit.