Errors

Errors in P4Web and Perforce can be caused by a number of reasons:

• Password problems.

• Incorrect configuration settings.

• Using browser bookmarks that don't work with a P4Web Viewer.

• Maxresults limits:

  In some environments, turning on the "Show recent activity" preference in the Path Browser can cause "Request too large (over nnnnnn); see 'p4 help maxresults'" to appear in the control panel. You can work around the problem by either:

  • Turning off recent activity display --- click the "Hide recent activity" shortcut button or use the Settings page.
  • Navigating down the depot path hierarchy until the messages disappear.

  ("Maxresults" can be set by the Perforce administrator to prevent the Perforce server from getting swamped by reporting commands. See the Perforce System Administrator's Guide for more information.)

• Maxscanrows limits:

  In some environments, running the Show -> Files matching... command to search for files can cause "Too many rows scanned (over nnnnnn); see 'p4 help maxscanrows'" to appear as an error.

  You can prevent this error from occurring by entering a more specific query.

  For instance, rather than entering:

  //...aaa...

  Enter a more specific path, like:

  //depot/main/...aaa...

  ("Maxscanrows" can be set by the Perforce administrator to prevent the Perforce server from getting swamped by reporting commands. See the Perforce System Administrator's Guide for more information.)

• Having your client workspace and your browser on different machines.

  Unless your P4Web Helper is running on Unix, you won't be able to launch editors, or run the interactive resolve program if your browser and your workspace are on different host machines. Also, the File Browser's link to local workspace files may not work unless your browser is running on the machine where your workspace is.