ERROR OCCURRED: The content results for AltaVista was not in the expected format. There's two possible causes for this:
1) An error occurred while querying the engine such as 'Server is temporarily unavailable'. In other cases, results may come back incomplete or truncated. View the actual search results page to see if there were problems in the search. If so, try the search again since engines are not yet 100% reliable. 2) AltaVista may have changed its HTML output format recently in a way which affects WebPosition. If error persists but the actual search page looks OK, try checking for a new WebPosition update by clicking the 'Check for Update box' on the Results Tab and re-running the Mission, or go to www.webposition.com/updates2.htm.
If neither corrects the problem, E-mail FirstPlace Software with details on what Engine, URL and keywords are needed to duplicate the error and attach copy of your Mission file. We'll try to issue a fix ASAP.
[ERROR MESSAGE: 'Record begin string was not found in search results.]'
ERROR OCCURRED: The content results for AltaVista was not in the expected format. There's two possible causes for this:
1) An error occurred while querying the engine such as 'Server is temporarily unavailable'. In other cases, results may come back incomplete or truncated. View the actual search results page to see if there were problems in the search. If so, try the search again since engines are not yet 100% reliable. 2) AltaVista may have changed its HTML output format recently in a way which affects WebPosition. If error persists but the actual search page looks OK, try checking for a new WebPosition update by clicking the 'Check for Update box' on the Results Tab and re-running the Mission, or go to www.webposition.com/updates2.htm.
If neither corrects the problem, E-mail FirstPlace Software with details on what Engine, URL and keywords are needed to duplicate the error and attach copy of your Mission file. We'll try to issue a fix ASAP.
[ERROR MESSAGE: 'Record begin string was not found in search results.]'
ERROR OCCURRED: The content results for AltaVista was not in the expected format. There's two possible causes for this:
1) An error occurred while querying the engine such as 'Server is temporarily unavailable'. In other cases, results may come back incomplete or truncated. View the actual search results page to see if there were problems in the search. If so, try the search again since engines are not yet 100% reliable. 2) AltaVista may have changed its HTML output format recently in a way which affects WebPosition. If error persists but the actual search page looks OK, try checking for a new WebPosition update by clicking the 'Check for Update box' on the Results Tab and re-running the Mission, or go to www.webposition.com/updates2.htm.
If neither corrects the problem, E-mail FirstPlace Software with details on what Engine, URL and keywords are needed to duplicate the error and attach copy of your Mission file. We'll try to issue a fix ASAP.
[ERROR MESSAGE: 'Record begin string was not found in search results.]'
ERROR OCCURRED: The content results for AltaVista was not in the expected format. There's two possible causes for this:
1) An error occurred while querying the engine such as 'Server is temporarily unavailable'. In other cases, results may come back incomplete or truncated. View the actual search results page to see if there were problems in the search. If so, try the search again since engines are not yet 100% reliable. 2) AltaVista may have changed its HTML output format recently in a way which affects WebPosition. If error persists but the actual search page looks OK, try checking for a new WebPosition update by clicking the 'Check for Update box' on the Results Tab and re-running the Mission, or go to www.webposition.com/updates2.htm.
If neither corrects the problem, E-mail FirstPlace Software with details on what Engine, URL and keywords are needed to duplicate the error and attach copy of your Mission file. We'll try to issue a fix ASAP.
[ERROR MESSAGE: 'Record begin string was not found in search results.]'
ERROR OCCURRED: The content results for AltaVista was not in the expected format. There's two possible causes for this:
1) An error occurred while querying the engine such as 'Server is temporarily unavailable'. In other cases, results may come back incomplete or truncated. View the actual search results page to see if there were problems in the search. If so, try the search again since engines are not yet 100% reliable. 2) AltaVista may have changed its HTML output format recently in a way which affects WebPosition. If error persists but the actual search page looks OK, try checking for a new WebPosition update by clicking the 'Check for Update box' on the Results Tab and re-running the Mission, or go to www.webposition.com/updates2.htm.
If neither corrects the problem, E-mail FirstPlace Software with details on what Engine, URL and keywords are needed to duplicate the error and attach copy of your Mission file. We'll try to issue a fix ASAP.
[ERROR MESSAGE: 'Record begin string was not found in search results.]'