on 09-16-2014 8:32 AM
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Lavanya,
Take a look at the following to see if it will help troubleshoot the problem:
Ted Zimmerman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Do we have any other solution for this issue. We are still struck up with the same issue
Thanks,
Lavanya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.