Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Keywords: 1129 Oleinitiate: Initiate Failed
GMUI = ObjectCreate("gmw.ui")What should be my troubleshooting strategy?(It works fine on all other machines)
Most likely cause is the DLL or exe that implements the object has gone missing or is in the wrong location. The brute force solution may be to simply (or not so simply) reinstall or re-register the COM Automation object.
1129 Oleinitiate: Initiate Failed Obj=ObjectOpen("WSERVER.APPCTRL") WinBatch 32 96M WIL Version: 2.3mbnThe object can be initialized and its methods executed from either of those applications - only WinBatch is having a problem. Any ideas?
Sometimes Running the application involved first, before trying to open the object helps as less registry entries have to be 100% correct.
joe = createobject("WSERVER.APPCTRL") frank = joe.GetAppToRun()* this works.
Opening the object in VB is a little different:
Private Sub Form_Load() ' AppCtrl is the class in the WSERVER DLL Set oWserver = New AppCtrl End Sub Private Sub Command1_Click() MsgBox oWserver.GetAppToRun(), vbOKOnly, "WSERVER" End Sub Private Sub Form_Unload(Cancel As Integer) Set oWserver = Nothing End SubWhat do you mean exactly by RUNning the application first to see if that will help the object creation?
xxx=ObjectOpen("APPCTRL")We don't generally need to know *where* the object is defined (exe or dll) as the registry takes care of that for us.
Not knowing what WSERVER.APPCTRL is I dont know what to do with it. Seeing it used in running code helps me understand its nature. It looks from the VB code that the WSERVER part was throwing us off.
Re..Running an EXE. Some objects are defined in EXE files, and sometimes have bad registry entries making it difficult to find, but if the application is already running it steps in during the ObjectOpen process and says "Hey I can handle that sort of object") and bypasses a few registry lookup operations.
I'm not sure what is wrong. I still strongly suspect invalid registry entries or an improperly setup CLSID.
We tested OLE creation under VB 4.0 and the WinBatch script opened its object without a hitch. It seems the way the 5.0 platforms must register objects differently than in 4.0.
Article ID: W12940
Filename: 1129 OLE Initiate Failed Error.txt
File Created: 2014:05:29:09:14:46
Last Updated: 2014:05:29:09:14:46