cancel
Showing results for 
Search instead for 
Did you mean: 

Error calling external object function intialize

Former Member
0 Kudos

Hi all,

In our application we are using CaseDocs.DocCasesCtl control.

We are recieving "Error calling external object function intialize" when the below line of code is being executed.

ole_1.object.Initialize(is_case , gl_obsessionhandle)

FYI. The same code is working in XP machine but not in Windows 7.

We tried re-registering CaseDocs.ocx but had no luck.

Please advice on this.

Thanks in advance,

Lavanya.


Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

Hi ,

I have also the got the similar issue while running one of my application.when i try to generate the ms word documents by that application i am getting the error " Error calling external object function intialize" and the error message alert is displaying.

Initially when i run the application i got  the  first error " unable to start the OLE server process error" after that frequently i am getting that  error " Error calling external object function initialize" when i am running and generating word documents.

I am using windows 7 64 bit os.can you tel me how to fix it.

0 Kudos

Hello Lavanya,

I liked to know have you solved this problem ? we have the same problem calling a fingerprint OCX function

We have registered the ocx and copy it to syswow64 (w7 - 64bit)

We have checked using ole browser and found all the functions listed in the OCX

But why the PB 12 can't find the function, the error code is 39 - error accessing external object property

Is it the same old issue ?

Thanks for any help.

Regards,

RW

Former Member
0 Kudos

If your pb application is 32bit you have to use a 32bit version of the ocx.

0 Kudos

I used the 32 bit ocx , and it register successfull

Is this PB bugs ? cannot call the OCX  external functions ?

Former Member
0 Kudos

Hello Lavanya,
Take a look at the following to see if it will help troubleshoot the problem:

http://scn.sap.com/community/developer-center/powerbuilder/blog/2014/09/24/how-to-capture-error-mess...

Ted Zimmerman

Former Member
0 Kudos

NEED HELP.

Can anyone tell whether Windows 7 supports Powerbuilder 11.5 version.

We are not able to figure out the solution for this.

Can anyone help on this.

Thanks in advance,

Lavanya

Former Member
0 Kudos

Lavanya,

PowerBuilder 11.5.1 (build 4675 or higher) Supports Microsoft Windows

7.

Beverly Duquette

Former Member
0 Kudos

Hi,

Do we have any other solution for this issue. We are still struck up with the same issue

Thanks,

Lavanya

Former Member
0 Kudos

Hi Lavanya;

1) Are you sure that the control your using is W7 certified?

2) I would suggest wrapping the OLE script in a TRY..CATCH. Quite often, more information is provided on the error in the Exception object.

Are you using the W7 32bit or 64bit O/S?

Regards ... Chris

Former Member
0 Kudos

Hi Chris,

Yes, we are using Windows7 32bit O/S.

Can you please let me know how to identify whether the control is Windows7 certified and also how to get this OCX work in Windows7.

Note: We are able to replicate this issue in XP machine by unregistering the same OCX.

So we are assuming that the issue in Windows7 is due to this OCX .

Thanks,

Lavanya

Former Member
0 Kudos

Hi Lavanya;

  I would suggest contacting the OCX vendor and checking with them on the control's W7 compliance aspect.

Regards ... Chris

Former Member
0 Kudos


Hi Chris,

The OCX that we are using is our own application and this ocx is being called from PowerBuilder.

Also the same OCX is working fine when called from the VB application.

Can you please help us to resolve this.

Thanks in Advance,

Lavanya.

CobyKako
Advisor
Advisor
0 Kudos

How did you register your OCX? using regvr32 from c:\windows\system32 ?

Is your Windows 7 a 64-bit machine?

If yes, can you try to re-register your OCX control (32-bit?) using regsvr32 from correct folder:

1. Open a DOS command prompt (run as administrator)

2. Change directory to C:\Windows\SysWOW64

3. Unregister the control using the command "regsvr32 /U xxxx.ocx"

4. Re-Register using the command "regsvr32 xxxx.ocx"

Indeed, you have to use a 32-bit OCX with PowerBuilder

HTH,

Jacob

Former Member
0 Kudos

Hi Jacob,

Thanks for your quick response.

We are using Windows 7 , 32-bit machine.

We placed the ocx in C:\Windows\System32 and re-registered the ocx after unregistering but we are still getting same error.

(Also i could not find any folder named SysWOW64).

Thanks,

Lavanya.

CobyKako
Advisor
Advisor
0 Kudos

SysWOW64 folder is created with 64-bit machines only.

As for your problem, is it possible to have a way to recreate it?