How to Deal With the 80070057 Error

The 80070057 error appears in code and has a lot of variations. This causes it to become misleading.
The following examples show the different ways in which the error manifests. It is important that you recognize them, so you will know exactly what to do when they appear.

  • Type 1: Server object error ‘ASP 0177: 80070057

    Server.CreateObject Failed

    /secure/rcm/thanks.asp, line 23

  • The operation completed successfully.

  • Type 2: <%
    Set objFSO = CreateObject (“Scripting.FileSytemObject”)

    Set objFILE = objFSO.OpenTextFile (“c:\boot.ini”, ForReading)

  • The first two types are caused by using constant names for FileSystemObject values. When this is done, VBScript cannot recognize what exactly “ForReading” is. Because of this, the command generates an error message when it returns.

    To avoid this, use the number 1 as the constant for the OpenTextFile ForReading method, the number 2 as the constant for ForWriting, and 8 as the constant for ForAppending.

  • Type 3: Active Directory error ‘800750057’
  • One or more arguments are invalid.
    This type can occur when you create an ADSI code with an improper value. An example of this is forgetting to put the username in the user query.

  • Type 4: Microsoft OLE DB Provider for ODBC Divers error ‘80070057’
  • The parameter is incorrect.

    This type can occur when you use adOpenSchema without including ADOVBS.INC.

These four types are the more complicated errors that come with the 80070057 Error. There are simpler versions of the error that you can solve by doing the following:

  1. Update your computer to R10P.
  2. Uninstall, reinstall, and update QB (Quick Books) in your computer. (There are numerous cases of the error 80070057 occurring in the Quick Books software.)
  3. Reboot your server and adjust your user information. Some QuickBooks services (like QuickBooksDB17) do not start if user credentials are incorrect. Change the password of qbdataserviceuser17 and match it with the password under the QuickBooksDB17 user.
  4. You can also update Quickbooks via the local administrator account. If you’re not a local administrator, you won’t be able to run the update.
  5. Remove the firewall on your computer.
  6. If you can’t solve it on your own, by all means, call technical support.


If you are performing crucial work, have a back up always. This error is pretty much like a pop-up, which could happen when you are downloading, updating, and even when you are already backing up.