Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
Errors
- 1129 and Object Open Interface in Type Library
- 1129 OLE Initiate Failed
- 1261 Ole Exception error
- 1690 ObjectCollectionOpen Error
- 3052 Error with OLE
- 3130 OleTerminate Bad Ole Channel
- 3246 OLE Object Not Found
- Error 1129 with Outlook Express
- Error 3157 Oleinitiate - Too many open channels
- ObjectAccess 1594 Error
- OLE Error Trapping
- Running Compiled EXE Generates OLE Error
- Windows 95 OLE Exported Function Error
- Word and 1129 Errors with InProcess Server
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Windows 95 OLE Exported Function Error
Question:
I have a program which contains no OLE code or references. I've compiled it as a large exe using the 2004E compiler, and it runs perfectly under Windows XP. However, under Windows 95, the same executable crashes on startup, with the message...wbdecc44i.dll Unable to locate exported function #185 in OLEAUT32.DLLI saw a knowledge base article here recommending I replace DCOM on the Windows 95 machine, but that machine is too sensitive for such a major operation, and yet my program needs to run there. Can anyone suggest another way round this problem?
I should add that the previous version of my program, compiled with the compiler that was available last November, had no problems on Windows 95.
Answer:
WB 2004B and later require at least Windows 95 OSR2 or later. This is because the "OLE" support is no longer in a separate DLL but included in the main WIL DLL.Hmmm. The only choices I can see is to either update OLE on the WIndows 95 machine OR simple used the 2004A version of Winbatch for that machine.
Article ID: W16579
File Created: 2005:02:18:12:21:32
Last Updated: 2005:02:18:12:21:32