ERROR_QUERYEXEC

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.

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.

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.

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

See the FAQ answer for more details.

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.

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.

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.

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.

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.

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.