Run time error 429 as user - works as administrator

[dpeeling]

I've done a search and didn't come up with much. Hopefully you can help.

We have created an excel macro and we are having problems getting it working at a client location. The client is a large organization and may well have some odd security setup.

The macro uses a reference to a type library (tlb file) that we have created to allow excel to communicate with a software package that we develop in house. Essentially, we connect excel to our application and read some data from the application and report it in excel. It is not a database and does not use ADO.

The problem is that our client is experiencing run time error 429 when they try to run the macro on some of their systems when logged in with user permissions. Some details:

• It works perfectly if the user is logged in as a local administrator. This seems to indicate that the code is ok and it is installed ok.
• It gives the error if they are logged in as just a user. This suggests some sort of problem with permissions. There is at least one user that is able to run the software as a user but we don't know what is different.
• We have checked file permissions on the tlb file and the related application's exe and install folder and they seem ok
• We have checked registry permissions on the HKCR section of the registry where the tlb file is registered. They seem ok.
• The client systems are XP Pro and XP x64. The problem is mainly occurring on the x64 systems.
• We have other clients using the software on office 2003, 2007 and 2010 without issues.
• We have tried to reproduce the problem in-house but have not been able to.

I seem to be missing some aspect of security which is preventing our macro from working on these systems. Does anybody have any ideas for me?

Thanks in advance.

 

[Jerry Sullivan]

Hello and Welcome,

That is a strange problem. I don't know the cause of the inconsistent results or a permissions fix..however one approach might be to identify the line of VBA code that is throwing the error and to find an alternative that works for a user without admin rights.

Currently your code might be using an error handler which is displaying the error message. If you add this statement at the beginning of your code (but after any similar error hander), then the debugger will stop at the point of the error.

On Error GoTo 0

Please let us know when you solve this mystery.