Error 429 occurs only when run via Citrix

[KeithWilliams]

Hi,

I have distilled this problem down to a one-line program. If I create an application with one form, and put the following code in the Form_Load event:

Dim objOutlook as Outlook.Application
Set objOutlook = CreateObject("Outlook.Application")

I have included a reference to the Microsoft Outlook 11.0 Object Library. And I've set the form to open up during the application Startup.

And that's all I need to reproduce the problem. The database runs fine on our Windows Server 2003. But as soon as I try to run it via Citrix, it fails with "run-time error '429': ActiveX component can't create object".

Citrix is supposed to act as a terminal server, just passing the screen display through to the client, so I don't understand how it can do anything differently to running direct on the server.

I'd really appreciate your advice, expertise on running Access through Citrix, or suggestions.

Many Thanks,
Keith.

 

[FoFa]

Is the outlook client loaded on the citrix server?

 

[KeithWilliams]

Yes, Office 2003 is installed, including Outlook 2003.

 

[KeithWilliams]

Hi,

I've now resolved this issue. I was able to eliminate Access from the equation by creating a Custom Citrix session, and attempting to open Outlook from within this. Outlook failed to open, although it did not return any error message.

I then found that there was a known problem with Citrix and Outlook, and there was a hotfix available for Citrix. Its a bit of a minefield trying to identify which fix to apply to a particular OS, but we found we could resolve the problem by installing the latest patch to the server.

Hope that helps someone,
Keith.

 

[Rx_]

Citrix, the same issue in Access VBA referencing Excel. The code works perfectlly when going directly to the X:\ drive (where Citrix resides) and the Excel reference is to my PC C:\ drive path. (early binding).
But, when users log onto Citrix, there is no useable reference.

While I am still researching, this was found on the Citrix Forum.

Have you tried setting the security in the registry to force it allow macros? I had a similar issue and it worked. 
HKEY LOCAL MACHINE > Microsoft > Office > 11.0 > Excel > create new key Security and add DWORD value named Level and give it a value of 1.