giptbl.cxx(1786)\combase.dll! 80070057 The parameter is incorrect.

Question

熙铭徐 41

MFC program interface display, has been running on other computers, no such error

onecore\com\combase\dcomrem\giptbl.cxx(1786)\combase.dll! 7791B2C4: (Caller: 6D1DE6E7) ReturnHr(14) TID (5994) 80070057 The parameter is incorrect.

Microsoft C++ exception: wil::ResultException, located at memory location 0x001598C0.

Microsoft C++ exception: [rethrow], located at 0x00000000.

Microsoft C++ exception: wil::ResultException, located in memory 0x00159980.

Microsoft C++ exception: [rethrow], located at 0x00000000.

Microsoft C++ exception: wil::ResultException, located at memory location 0x00159AC0.

Microsoft C++ exception: [rethrow], located at 0x00000000.

RLWA32 51,886 Reputation points

2022-05-18T08:13:06.803+00:00

Are these messages only seen when running the program under the debugger?

Does the program run correctly even though these messages appear?
熙铭徐 41 Reputation points

2022-05-18T08:15:29.983+00:00

The program works fine. It shows up in the output window during debugging. I've tried it on other computers and it doesn't show up
YujianYao-MSFT 4,296 Reputation points Microsoft External Staff

2022-06-08T07:42:14.67+00:00

Hi @熙铭徐 ,

This issue introduces 0x80070057 The parameter is incorrect and the solution, I suggest you read it carefully.

1 answer

RLWA32 51,886 Reputation points

2022-05-18T08:13:06.803+00:00

Are these messages only seen when running the program under the debugger?

Does the program run correctly even though these messages appear?
熙铭徐 41 Reputation points

2022-05-18T08:15:29.983+00:00

The program works fine. It shows up in the output window during debugging. I've tried it on other computers and it doesn't show up
YujianYao-MSFT 4,296 Reputation points Microsoft External Staff

2022-06-08T07:42:14.67+00:00

Hi @熙铭徐 ,

This issue introduces 0x80070057 The parameter is incorrect and the solution, I suggest you read it carefully.

Answer 1

RLWA32 51,886

I wouldn't worry about these informational messages that only appear in a debugger even when programs execute properly.

Apparently, some system DLLs provide additional error reporting when they determine that a debugger is attached to a process. See my response in this thread - why-does-native-only-debugging-cause-windows-dlls.html