ERROR_QUERYEXEC

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
2 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.
5 Access is denied.

Google Scholar returned HTTP status code 403 (Forbidden). This is usually 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.

13 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 Lookup 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.

35 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 Lookup command to mark the query for renewed lookup.

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

573 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 Google Scholar or Microsoft Academic Search query, then perform a lookup action on the query. A normal Lookup action suffices; it is not necessary and not recommended to perform a Lookup 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.
1169 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.
1223 The operation was canceled by the user. You pressed the Cancel button while the query was in progress.
4313 Unable to read from or write to the database.

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 Lookup 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.

8207 The directory service is unavailable. The data source is temporarily unavailable, possibly due to maintenance. Try again later.
8224 An operations error occurred. An unknown data source error occurred. Please lodge an error report to Publish or Perish technical support by using the Tools > Report Error command from the main menu.
8228 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 Google Scholar as well and that the combined total number of queries exceeds Google Scholar's internal limit.

To resolve this problem, refrain from accessing Google Scholar for 24 hours, then try again. Use Look up Direct for any queries that failed.

8233 Inappropriate authentication. The application ID that was sent to the data source was invalid or revoked. If you are using your own application ID, then make sure it is still valid.
8255 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.
8256 The specified method is not supported. The query syntax is not supported by 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.
8257 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.
12029 The attempt to connect to the server failed.

Publish or Perish was prevented from accessing the Google Scholar 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 Lookup 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 Google Scholar, 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.