ERROR_QUERYEXEC

Error message during the execution of a search request

Error <code> while performing query:
<message>

Indicates that some kind of error occurred while the query was performed.

Click OK to dismiss the message.

Common error codes

Code Description Comments
13 Access is denied

The data source returned HTTP status code 403 (Forbidden) or a similar code. This may be caused by too many queries in quick succession from the same IP address, possibly because the IP address is shared between multiple systems (for example, several computers using a shared proxy).

See Unusual traffic from your computer network on the Google web site for tips how to resolve this.

Alternatively, it may indicate that you do not have a valid access key for the data source.

13 The administrative limit for this request was exceeded

The data source denied (part of) the request because it received too many queries in too short a time from your IP address. This is typically caused by too many queries from your own system, especially if those queries each result in more than 100 results.

Alternatively, if your computer accesses the Internet through a local proxy server or a shared connection such as a shared ADSL router, it could be that other users are simultaneously accessing the data source as well and that the combined total number of queries exceeds Google Scholar's internal limit.

To resolve this problem, refrain from accessing the data source for 4-24 hours, then try again. Use Search Direct for any queries that failed.

264 Query pending

The query's parameters have changed and the query must be re-issued to obtain new results. This error code means that the current results do not correspond to the query as it is now defined, for example because it's a new query or you used the Query > Mark for Search command to mark the query for renewed lookup.

To resolve, perform a lookup action on the query. A normal Search action suffices; it is not necessary and not recommended to perform a Search Direct in this case.

514 There was no match for the specified key in the index

The query did not match any papers. Try changing some of the query parameters.

See the FAQ answer for more details.

519 The specified program requires a newer version of Windows

The query ran into a Google CAPTCHA, but the version of Internet Explorer on your system (which is required to solve the CAPTCHA) is too old and no longer supported.

This can happen if you have a version before Internet Explorer 11. It also happens if you are running Publish or Perish on Wine, which has an IE equivalent of approximately version 8.

See the FAQ answer for more details.

522 The data is invalid

The response from the data source contained no recognizable data. This can be due to a change in the output format; please report to Publish or Perish technical support if you suspect that this is the case.

Before reporting, please do the following:

  1. Check if an updated version of Publish or Perish is available. You can also use the Tools > Check for Updates command from the main menu.
  2. After installing the update, if any, repeat the query using the Search Direct button. This retrieves fresh data from Google Scholar, which might help to resolve the problem.

If nothing else helps, then please lodge an error report to Publish or Perish technical support by using the Tools > Report Error command from the main menu. This generates an error report (a plain text file) called PoPError.txt that you should attach to your email to the Publish and Perish support address. We need the information in the error report for an accurate diagnosis.

522 Invalid data

The data source returned an empty response. This is typically caused by a local access problem, for example interference by anti-virus tools or a firewall. Switch off your anti-virus tool temporarily and retry the query using Search Direct to see if that resolves the problem.

If nothing else helps, then please lodge an error report to Publish or Perish technical support by using the Tools > Report Error command from the main menu. This generates an error report (a plain text file) called PoPError.txt that you should attach to your email to the Publish and Perish support address. We need the information in the error report for an accurate diagnosis.

524 The directory service is unavailable The data source is temporarily unavailable, possibly due to maintenance. Try again later.
524 No results were returned The data source response contained no recognizable results. This might be due to refused access caused by an excessive number of prior queries. Retrying the query after an hour or two might resolve the situation.
526 The requested item could not be found

The data source reported a HTTP status code 404 (Not found). This may be caused by the following, among others:

  • A non-existing Google Scholar Profile ID
  • The use of an invalid query URL
  • A change in the data source's server configuration.

If nothing else helps, then please lodge an error report to Publish or Perish technical support by using the Tools > Report Error command from the main menu. This generates an error report (a plain text file) called PoPError.txt that you should attach to your email to the Publish and Perish support address. We need the information in the error report for an accurate diagnosis.

various File not found Internet Explorer is working in offline mode. To resolve this, start Internet Explorer, open its File menu and make sure that the Work offline option is not checked. If it is checked, click on it to uncheck it.
various Missing system file

The results data file belonging to the query is missing. This may be caused by accidental deletion. The resolution of this problem depends on the type of query:

  • Regular query: If the query is a regular search query, then perform a lookup action on the query. A normal Search action suffices; it is not necessary and not recommended to perform a Search Direct in this case.
  • Imported data: If the data were imported from another data source, then you must re-import them to restore the data.
various The operation was canceled by the user You pressed the Cancel button while the query was in progress.
various One or more parameters are illegal Publish or Perish sent a malformed query to the data source. Please lodge an error report to Publish or Perish technical support by using the Tools > Report Error command from the main menu.
various The attempt to connect to the server failed

Publish or Perish was prevented from accessing the data source server. This is typically caused by a firewall or proxy blocking outgoing connections from Publish or Perish. Try the following:

  • Check your firewall settings and make sure that Publish or Perish is not being blocked from accessing the Internet. Publish or Perish does not have to accept incoming connections, but it must be allowed to make outgoing Internet connections. Check all possible firewalls: Windows Firewall, any other local firewall software, and your anti-virus/Internet security tool, if that includes a firewall.
  • If your computer accesses the Internet through a proxy, make sure that the proxy settings are correct. Publish or Perish uses the same proxy settings as Internet Explorer, so you can check and test the proxy settings through the Internet Explorer options dialogs. If necessary, authenticate yourself on the proxy by using Internet Explorer.

After you have made the changes, retry the query using Search Direct to see if that resolves the problem.

If you are sharing a proxy with others, then the proxy might be limiting the number of connections made to the data source, particularly if you or your colleagues are issueing a lot of queries within a short timespan (a few hours or so).

If nothing else helps, then please lodge an error report to Publish or Perish technical support by using the Tools > Report Error command from the main menu. This generates an error report (a plain text file) called PoPError.txt that you should attach to your email to the Publish and Perish support address. We need the information in the error report for an accurate diagnosis.

other (various messages) Please lodge an error report to Publish or Perish technical support by using the Tools > Report Error command from the main menu. This generates an error report (a plain text file) called PoPError.txt that you should attach to your email to the Publish and Perish support address. We need the information in the error report for an accurate diagnosis.