The 80070057 error appears in code and has actually a lot of variations. The following are illustrations of the error taking different faces. It is important that you recognize them, so you will know exactly how to deal with them.
Type 1: Server object error ‘ASP 0177: 80070057
/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. This is when the VBScript cannot recognize what exactly “ForReading” is. When the command returns, it generates an error message. To avoid this, use the number 1 as the constant for the OpenTextFile ForReading method, the number 2 as the constant for ForWriting, and the number 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 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 most complicated types of error 80070057. There are simpler versions of the error that you can solve by doing the following:
- Update your computer to R10P.
- Uninstall, reinstall, and update QB (Quick Books) in your computer. (There are numerous cases of the error 80070057 occurring in the Quick Books software.)
- Reboot your server and adjust your user information. Some QuickBooks services (like QuickBooksDB17) do not start if user credentials are incorrect. Change the password qbdataserviceuser17 and match it with the password under the QuickBooksDB17 user.
- You can also update Quickbooks via the local administrator account. If you are not a local administrator, you will not be able to run the update.
- Remove the firewall on your computer.
- If you can’t solve it on your own, by all means, call technical support.
If you are performing crucial work, always have a back up. 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.