Re: Automation Error

[Guest]

Graham,
thanks for your help so far.

I tried everything you suggested, and still not luck.

1. Word.Application did not work, neither did outlook.application.11, howeve, excel.application seemed to work fine (well, it did not produce the error message in question)
2a and 2b seemed fine (hard to compare every digit, but essentially looked ok) ... I tried 2c) "outlook.exe /regserver" anyhow and got "Cannot start Microsoft office outlook. The command line argument is not valid. Verify the switch you are using." ... I did winword.exe /regserver and winword loaded fine (without the "cannot start..." error message but winword still does not work when you try to "createobject(word.application)" or "createobject(word.application.11)"
3. All the file versions checked out ok. I tried regsvr32 and it worked on all of them except asycfilt.dll, which produced this error message "Asycfilt.dll was loaded, but the DllRegisterServer entry point was not found." ... I checked on the mircosoft web site and found out that this normally means that it is not a real dll file??? so i copied it from my system that does work and still the same problem ... i tried regsvr32 on the system that does work, and the same "Asycfilt.dll was loaded..." error message, however, you can still createobject("outlook.application") on this machine...

I am very lost and confused.

Why should automation work on two of my machine and not on the other two?

The are brand new machines with all windows and office updates and very few other applications.

Any advice?

Thanks in advance for your help,
Joe

 

[Graham Mandeno]

Hi Joe

I see that /regserver no longer works on Outlook 2003 for some inscrutible
reason (see http://support.microsoft.com/?id=827593). Also, you are right
about Asycfilt.dll - that is expected behaviour. Sorry I put you wrong
there.

I'm afraid I'm running out ideas. Something you could possibly try is to
put the same code into an Excel module and see if the same error occurs.

Here are some more long shots:

1) Change the declaration of the myOlApp to "As Object"

2) Try a Help > Detect and repair in Outlook

3) Try removing all the references from your Access project, then decompile
and add the references back again. To decompile, start Access with the
/decompile switch"
"<path to msaccess.exe>" "<path to your mdb>" /decompile

--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

Graham,
thanks for your help so far.

I tried everything you suggested, and still not luck.

1. Word.Application did not work, neither did outlook.application.11,

howeve, excel.application seemed to work fine (well, it did not produce the
error message in question)

2a and 2b seemed fine (hard to compare every digit, but essentially looked

ok) ... I tried 2c) "outlook.exe /regserver" anyhow and got "Cannot start
Microsoft office outlook. The command line argument is not valid. Verify
the switch you are using." ... I did winword.exe /regserver and winword
loaded fine (without the "cannot start..." error message but winword still
does not work when you try to "createobject(word.application)" or
"createobject(word.application.11)"

3. All the file versions checked out ok. I tried regsvr32 and it worked

on all of them except asycfilt.dll, which produced this error message
"Asycfilt.dll was loaded, but the DllRegisterServer entry point was not
found." ... I checked on the mircosoft web site and found out that this
normally means that it is not a real dll file??? so i copied it from my
system that does work and still the same problem ... i tried regsvr32 on the
system that does work, and the same "Asycfilt.dll was loaded..." error
message, however, you can still createobject("outlook.application") on this
machine...

 

[Guest]

Thank you for your help so far

I have tried these three things and none of them fixed the problem

Any other ideas

I can not undetsand why this is happening, but your help has been invaluable.

 

[TC]

Joe, please retain the text of the previous posts, when you reply to a post.
Just add your reply or further question, to the top or bottom of everything
that was said before. Then other people can jump in & help, if they can.

If you delete all the previous text, no-one will bother to look back for
your previous posts, to see what your problem is.

HTH,
TC

Thank you for your help so far.

I have tried these three things and none of them fixed the problem.

Any other ideas?

I can not undetsand why this is happening, but your help has been

invaluable.

 

[Guest]

Thank you for your help

Can anyone please help me with this Automation error -214702477

Thanks
Jo

Previous messages

Joe, please retain the text of the previous posts, when you reply to a post
Just add your reply or further question, to the top or bottom of everythin
that was said before. Then other people can jump in & help, if they can

If you delete all the previous text, no-one will bother to look back fo
your previous posts, to see what your problem is

HTH
T

Thank you for your help so far

invaluable

Hi Jo

I see that /regserver no longer works on Outlook 2003 for some inscrutibl
reason (see http://support.microsoft.com/?id=827593). Also, you are righ
about Asycfilt.dll - that is expected behaviour. Sorry I put you wron
there

I'm afraid I'm running out ideas. Something you could possibly try is t
put the same code into an Excel module and see if the same error occurs

Here are some more long shots

1) Change the declaration of the myOlApp to "As Object

2) Try a Help > Detect and repair in Outloo

3) Try removing all the references from your Access project, then decompil
and add the references back again. To decompile, start Access with th
/decompile switch
"<path to msaccess.exe>" "<path to your mdb>" /decompil

--
Good Luck

Graham Mandeno [Access MVP
Auckland, New Zealan

Graham
thanks for your help so far

howeve, excel.application seemed to work fine (well, it did not produce th
error message in question

2a and 2b seemed fine (hard to compare every digit, but essentially looke

ok) ... I tried 2c) "outlook.exe /regserver" anyhow and got "Cannot star
Microsoft office outlook. The command line argument is not valid. Verif
the switch you are using." ... I did winword.exe /regserver and winwor
loaded fine (without the "cannot start..." error message but winword stil
does not work when you try to "createobject(word.application)" o
"createobject(word.application.11)

3. All the file versions checked out ok. I tried regsvr32 and it worke

on all of them except asycfilt.dll, which produced this error messag
"Asycfilt.dll was loaded, but the DllRegisterServer entry point was no
found." ... I checked on the mircosoft web site and found out that thi
normally means that it is not a real dll file??? so i copied it from m
system that does work and still the same problem ... i tried regsvr32 on th
system that does work, and the same "Asycfilt.dll was loaded..." erro
message, however, you can still createobject("outlook.application") on thi
machine..

Jo

Hi Jo

If your code compiles OK then there can be no problem with broke
references

Here are some more things to try

1) First, see if the problem is confined to Outlook. Try this
Dim o as Objec
Set o = CreateObject("Word.Application"
o.Qui
Set o = Nothin

You could also try "Excel.Application" and "Outlook.Application.11

If Word and Excel are OK, then do steps 2 a,b,c, else step 3

2a) Check the following registry keys

HKEY_CLASSES_ROOT\Outlook.Application\CLSI
(Default) should be {0006F03A-0000-0000-C000-000000000046

HKEY_CLASSES_ROOT\Outlook.Application\CurVe
(default) should be Outlook.Application.1

HKEY_CLASSES_ROOT\Outlook.Application.11\CLSI
(Default) should be {0006F03A-0000-0000-C000-000000000046

2b) Export the registry key:
HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}

The output should be something like this:
========= Start .REG file =============
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}]
@="Microsoft Office Outlook"

[HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}\InprocHandle
r32]
@="ole32.dll"
"ThreadingModel"="Apartment"

[HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}\InprocServer
32]
"Class"="Microsoft.Office.Interop.Outlook.ApplicationClass"
"RuntimeVersion"="v1.1.4322"
"Assembly"="Microsoft.Office.Interop.Outlook, Version=11.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c"

[HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}\InprocServer
32\11.0.0.0]
"Class"="Microsoft.Office.Interop.Outlook.ApplicationClass"
"RuntimeVersion"="v1.1.4322"
"Assembly"="Microsoft.Office.Interop.Outlook, Version=11.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c"

[HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}\LocalServer3
2]
@="C:\\PROGRA~1\\MICROS~2\\OFFICE11\\OUTLOOK.EXE"
"LocalServer32"=hex(7):27,00,5d,00,67,00,41,00,56,00,6e,00,2d,00,7d,00,66,00
,
28,00,5a,00,58,00,66,00,65,00,41,00,52,00,36,00,2e,00,6a,00,69,00,4f,00,55,
00,54,00,4c,00,4f,00,4f,00,4b,00,46,00,69,00,6c,00,65,00,73,00,3e,00,69,00,
72,00,40,00,58,00,37,00,63,00,72,00,24,00,25,00,40,00,75,00,24,00,7d,00,26,
00,56,00,37,00,7b,00,34,00,70,00,27,00,00,00,28,00,66,00,27,00,5e,00,56,00,
6e,00,2d,00,7d,00,66,00,28,00,5a,00,58,00,66,00,65,00,41,00,52,00,36,00,2e,
00,6a,00,69,00,4f,00,55,00,54,00,4c,00,4f,00,4f,00,4b,00,46,00,69,00,6c,00,
65,00,73,00,3e,00,69,00,72,00,40,00,58,00,37,00,63,00,72,00,24,00,25,00,40, 00,75,00,24,00,7d,00,26,00,56,00,37,00,7b,00,34,00,70,00,27,00,00,00,00,00

[HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}\ProgID]
@="Outlook.Application.11"

[HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}\Typelib]
@="{00062FFF-0000-0000-C000-000000000046}"
=============== End .REG file =============

2c) If anything looks wrong with the above, re-register Outlook:

Start > Run
"<path to outlook.exe>" /RegServer
OK

The default path to Outlook.exe is:
"C:\Program Files\Microsoft Office\OFFICE11\OUTLOOK.EXE"

3) If Word and Excel are also broken, then check these files (all in
C:\Windows\System32)

The versions below are what is on my laptop:
Asyncfilt.dll 3.50.5014.0
Oleaut32.dll 3.50.5016.0
Olepro32.dll 5.0.5014.0
Stdole2.tlb 3.50.5014.0
Stole32.tlb 2.10.3027.1

Try reregistering the DLLs above with RegSvr32

Start>Run
RegSvr32 C:\Windows\System32 xxxxx.DLL
OK

--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

Graham,
thanks for your help so far.
1. You are right, I copied the code incorrectly into the previous message - it should have read:
Set myOlApp = CreateObject("Outlook.Application")
1. Yes, I just reinstalled office from original CDs and did a "detect and repair" and all seems ok
2. Yes, the code compiles without errors

the asycfilt.dll is not registered properly, but not sure about the best way
to fix this.
Hi Joe

For a start, you should assign your CreateObject to your object variable,
otherwise you will not be able to do anything with it:

Set myOlApp = CreateObject("Outlook.Application")

Some questions:
Are you sure Outlook is correctly installed on the computers where the code
is failing?
Does the code compile without errors?

--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

I have a Microsoft Acccess Application that works fine on two computers,

however, when I installed it on two new computers, I received the following
error message:

Error no: -2147024770; description: automation error
The specified module could not be found.

I have used the debugger and found that the error occurs on "CreateObject"

this line of code:
Dim myOlApp As Outlook.Application
CreateObject("Outlook.Application")

 

[Graham Mandeno]

Hi Joe

I'm scratching the bottom of the barrel here :-/

Did I ever suggest you try:
Set MyOlApp = New Outlook.Application
? I have no idea why it should behave differently, but it's worth a try.

Is Outlook already running on the system? If so, then try closing it first.
If not then try launching it first.

As this is a general Office automation problem and not specific to Access,
you might like to try posting to the
microsoft.public.office.developer.automation newsgroup.

I'm sorry, but the only other thing I can suggest is a *complete* uninstall
and reinstall of Office 2003.

--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

Thank you for your help so far.

I have tried these three things and none of them fixed the problem.

Any other ideas?

I can not undetsand why this is happening, but your help has been

invaluable.

 

[Graham Mandeno]

Hi Joe

I'm so glad you have found a solution!

I felt that the problem had to be in the class registrations, but such
problems are very difficult to diagnose.

Did Registry Mechanic generate a log, or in some other way tell you what it
was "fixing"? If so, I would be *very* interested to see it. Perhaps you
could email it to me at graham-at-mvps-dot-org. It would be much
appreciated and might even lessen someone else's pain in the future!
--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

Graham,
thank you so much for your help.
I have tried a few other things and found a solution (below).
Thanks again.
Joe

Solution:
If it helps anyone, this is how I solved this problem...
I used "Registry Mechanic" (shareware) which fixed some registry problems

(not sure why there was any, because these are two brand new machines).

Then I received a different error message "429 activex component can't create object"
I then repaired Microsoft Office (using the add/remove programs).
Problem fixed.

Thank you for everyone who helped me.
Joe

Original question:
I have a Microsoft Acccess Application that works fine on two computers,

however, when I installed it on two new computers, I received the following
error message:

Error no: -2147024770; description: automation error
The specified module could not be found.

I have used the debugger and found that the error occurs on "CreateObject" this line of code:
Dim myOlApp As Outlook.Application
CreateObject("Outlook.Application")

Microsoft Windows XP Professional
Microsoft Office Professional 2003

If it can somehow make any difference, the two new computers are laptops,

but I can not see how that should make any difference.