Definition of a Failed AddWeb 6 Submission
Previous  Top  Next



When you do a submission with AddWeb 6, and engines fail, it can mean any one of several things as outlined here:

·The engine is down. It may have gone offline temporarily, or may have been take down for good. When we see the same engine continuously fail, we investigate and update our database.  
·The engine has made a change that AddWeb 6 is not accounting for, so we must change our submission script. As with the above, when we investigate, we update our database with the changes.  
·The connection timed out. This can be a result of you having the timeout value set too low, or you are running too many threads. You can change both settings on the Options page.  
·There is a connection problem between you and the server accepting submissions. This can often be an issue that cannot be fixed. Sometime you are just too many hops away from the server and your connection cannot process the submission. This is a very common reason for failure. Luckily, it usually only happens with a small percentage of engines or directories.  
·You are behind a proxy server, and have incorrect proxy settings. This will cause all engines to fail. Contact your network administrator for the correct proxy server information and enter it in the options page.  
·Your IP number is not accepted by the engine. Sometimes engines will not allow computers on specific networks to submit. There is nothing you can do about this.  

Because all of the above factors can exist in a submission run, it is not uncommon to have a couple hundred failures in a full submission. Failures in many hundreds or many thousands of submissions are typically credited to a failed submission to one of the Server Side Submission engines. Check a submission report to determine the specific engine.