Richtx32.dll Error When Running Under Specific User 3

[TripleJHJO]

I have created a VB6 application and installed it on a Windows 2000 server. When I (administrator) run the application, it runs fine. When I run the program logged on as a non-administrative user, I get the following message:

"Run time error 339. Component Richtx32.ocx or one of its dependencies not correctly registered: a file is missing or invalid"

I have re-registered the ocx, which I don't think is the issue. Because the program runs properly under my administrative signon, my guess is it is a permissions issue.

Can anyone advise?

Thanks,
J.Jensen

 

[BobRodes]

That's my guess also. You might just evaluate the permissions on the file in question while in admin mode, and compare them to those of the userid that is having the trouble. You'll need to at least be able to read the file. I'd rule out this as a problem first.

 

[TripleJHJO]

I verified that as well. The users have read/execute rights on the directory/file and subdirectories. I have other VB6 programs loaded that the users can run. This one seems to be a little different.

 

[BobRodes]

The next thing to evaluate is whether any dependencies of the .ocx (dll's it uses) have security issues.

 

[TripleJHJO]

How do you check for dependencies?

 

[BobRodes]

try googling to "dependency checker".

 

[SBerthold]

Use the DependencyWalker on the ocx:

http://findfiles.com/list.php?string=depends22_x86.zip&size=610769&db=Mirrors

To see all dependencies, you will need to start your program and go to a mask where the RTF is used.

Will need to verify the versions of the RICHTTX32.OCX, Riched20.dll and SHLWAPI.dll.
Also, if IE installed on the clients and what version and SP of IE is then installed.

 

[BobRodes]

Very nice, SB.

 

[SBerthold]

Thanks Bob.

DependencyWalker:
Using in the "Profiling" mode is fun (start DependencyWalker, open your apps exe File, and hit F7)

 

[TripleJHJO]

Talk about seeing the forest through the trees!!!

My issue was the fact that the actual ocx did not have proper user permissions on it. After applying appropriate permissions, the program executed without error.

I was so busy chasing down the literal error message about a dependency issue, that I initially did not think to check the actual ocx.

That said, the dependency checker that SBerthold suggested is a great tool that I will add to my toolbox for future debugging.

A star to both you and Bob.

Thanks everyone.

 

[BobRodes]

Ah, I didn't read your first response carefully enough! Looks like you were thinking I was saying directory, and I was saying file. Oh well, no harm done in the end.

 

[SBerthold]

Thank you TripleJHJO, my first thought about it was also that it could be the permissions and BobRodes hit it on the nail, but you had said that was already verified.
Even though, more has come out of this thread, also for others with similar problems: In a situation like this, check the permissions first, no matter what the error message lead you to believe otherwise, even though they are somewhat understandable in this case as to why they report what they do.