429 ActiveX component can't create object

Unfortunately I have a client that insists on using an old copy of Crystal Reports v8 on a W7 workstation. We have several machines where this works fine but they were all started back in older times and evolved as Windows evolved. This is a new computer with an old copy of Crystal. Everything appears to install properly but when we go to run Crystal we get '429 ActiveX component can't create object'. I have registered all the usual dlls but nothing has helped.  Aside from running sysinternals is there anything else I can try to track down this error? Client is not willing to pay for much more time to resolve this and our response is that they should not be using software that is so outdated so we are at loggerheads.
LVL 1
rwheeler23Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

vastoCommented:
When you install Crystal did you right click on setup.exe and use "run as administrator" ? Crystal 8 has weird setup , which may not start as administrator and includes some html pages which might be blocked by the security especially on 64 bit machines. You may need also to turn off UAC http://windows.microsoft.com/en-us/windows/turn-user-account-control-on-off#1TC=windows-7
0
rwheeler23Author Commented:
UAC was turned off and Run As Adminstrator was used. My next step was to uninstall and reinstall MS Office.
0
Ido MilletProfessor of MIS at Penn State Erie and Owner, Millet SoftwareCommented:
ProcessMonitor would probably let you identify the problem.  See: https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

Error is triggered when you start Crystal 8 Designer?  Or when you load a report?  If report, perhaps it's a missing UFL issue.  

Does the customer need Crystal 8 to design reports or just to run them?  If just to run them, consider installing one of the free/inexpensive 3rd-party viewers listed at http://kenhamady.com/bookmarks.html
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

rwheeler23Author Commented:
The users just need to run reports. I will check out the third party viewers.
0
rwheeler23Author Commented:
These viewers will not work because the client has a product that uses Crystal to render the reports. So there are parameters that are passed from the program to Crystal. This is why I was thinking of uninstalling Office and reinstalling because this product is heavily dependent on Windows and Office components.
0
Ido MilletProfessor of MIS at Penn State Erie and Owner, Millet SoftwareCommented:
This means the problem is probably not with Crystal 8 but with a very old application developed using the Crystal 8 runtime.  You need to make sure you deploy that runtime. Unfortunately the Crystal 8 runtime wasn't provided via Merge Modules so you are facing "dll hell".  

Some of the 3rd-party viewers provide a command line API (parameters, login, and more...), so it would be an easy replacement to call a viewer instead of the old app.
0
rwheeler23Author Commented:
I have advised the software vendor of this and they advised us to uninstall and reinstall their runtime engine. They claim 99% of the time this corrects this issue. Looks like we are one of the lucky 1%. I have warned the client if they insist on tracking this down it is going to cost big time because we get into sysinternals and looking at page after page of log file trying to find the offending dll(s).
0
vastoCommented:
Is it 64 or 32 bits machine ?
0
rwheeler23Author Commented:
64 bit running a 32 bit program.
0
vastoCommented:
Then check if the reports are using UFL because they will be in a 32 bit  dll. On 32 bits machine these dll will be placed in system32 but on 64 bits machine they should be placed and registered in C:\Windows\SysWOW64. Also when you register the dll you should use C:\Windows\SysWOW64\regsvr32.exe instead of the one placed in C:\Windows\System32. Check also if craxdrt.dll is in C:\Windows\SysWOW64. It should be registered in the same way
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rwheeler23Author Commented:
Thank you. They will be in tomorrow so I will connect and check it out.
0
rwheeler23Author Commented:
Thnaks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Crystal Reports

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.