- <TITLE>Errors</TITLE>
- <P>
- Errors in P4Web and Perforce can be caused by a number of reasons:
- <UL>
- <P>
- <LI><A HREF="auth?help">Password</A> problems.
- <P>
- <LI>Incorrect <A HREF="settings?help">configuration settings</A>.
- <P>
- <LI>Using <A HREF="tips?help#bookmarks">browser bookmarks</A>
- that don't work with P4Web in
- <A HREF="browseonly?help">Viewer mode</A>.
- <P>
- <LI>Maxresults limits:
- <blockquote>
- In some environments,
- turning on the "Show recent activity" preference in the
- <a href="pathbrowser?help">Tree view</a> can cause
- <font color=red>
- "Request too large (over <i>nnnnnn</i>); see 'p4 help maxresults'"
- </font>
- to appear in the <a href="controlpanel?help">control panel</a>.
- You can work around the problem by either:
- <P>
- <ul>
- <li>Turning off recent activity display --- click the
- "Hide recent activity" shortcut button or use the
- <a href="settings?help">Settings</a> page.
- <li>Navigating down the depot path hierarchy until the messages
- disappear.
- </ul>
- <p>
- ("Maxresults" can be set by the Perforce administrator to
- prevent the Perforce server from getting swamped by reporting
- commands.
- See the <a href="http://www.perforce.com/perforce/technical.html"><i>
- Perforce System Administrator's Guide</i></a> for more information.)
- </blockquote>
- <P>
- <LI>Maxscanrows limits:
- <blockquote>
- In some environments, setting the <b>Files matching...</b> filter to
- search for files can cause
- <font color=red>
- "Too many rows scanned (over <i>nnnnnn</i>); see 'p4 help maxscanrows'"
- </font>
- to appear as an error.
- <P>
- You can prevent this error from occurring by entering a more specific query.
- <P>
- For instance, rather than entering:
- <p>
- <TABLE BORDER=1 cellpadding=5 width=200>
- <TR>
- <TD><KBD>//...<i>aaa</i>...</KBD></TD>
- </TR>
- </table>
- <P>
- Enter a more specific path, like:
- <p>
- <TABLE BORDER=1 cellpadding=5 width=200>
- <TR>
- <TD><KBD>//depot/main/...<i>aaa</i>...</KBD></TD>
- </TR>
- </table>
- <p>
- ("Maxscanrows" can be set by the Perforce administrator to
- prevent the Perforce server from getting swamped by reporting
- commands.
- See the <a href="http://www.perforce.com/perforce/technical.html">
- <i>Perforce System Administrator's Guide</i></a> for more information.)
- </blockquote>
- <P>
- <LI>Having your
- <a href="defs?help#clientworkspace">client workspace</a>
- and your browser on different machines.
- <blockquote>
- Unless your P4Web is running
- on Unix, you won't be able to
- <a href="launcheditor?help">launch editors</a>, or
- run the interactive <a href="resolve?help">resolve</a> program
- if your browser and your workspace are on different host machines.
- Also, the <a href="filebrowser?help">File Browser's</a>
- link to local workspace files may not work unless your browser is running on the
- machine where your workspace is.
- </blockquote>
- </ul>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 12234 | Matt Attaway | Rejigger P4Web project in preparation for official sunsetting The bin directory contain...s the last official builds of P4Web from the Perforce download site. P4Web is soon to be completely sunsetted; these builds are here for folks who don't want to build their own. To better handle the archived builds the source code has been moved into a separate src directory. « |
10 years ago | |
//guest/perforce_software/p4web/Help/errors.html | |||||
#1 | 8914 | Matt Attaway | Initial add of the P4Web source code | 11 years ago |