Scripting execution problem in Outlook 2003

[Sander Kooij]

Hello,

I have a problem with an Outlook form using Microsoft Office 2003.
This form allows users to send fax messages from Outlook using our own
iXware Unified Messaging system. The form is installed at many
customers and is working properly for quite a while.

Last week we installed the forms at a new customer where a strange
problem occurred on some workstations. The custom form actions do not
appear to be executed. When I took a closer look at the form in design
mode, I noticed that it was impossible to access the script code
('view code' button from the toolbar). When I tried to do this, I got
an 'Access Denied' error (This is NOT the security warning which
appears when you try to access restricted information from outlook and
ask you if you want to grant access for some time, but a normal
message box). To see if the problem was related to this specific form
I tried to access the code from the IPM.Note form. When I did this,
the same error occurred.

To exclude to possibility of this being a rights issue I logged on to
the PC as a domain administrator user which has full exchange rights.
This user is also local administrator. But, again, the same error did
occur.

The odd thing is that some workstations at the same company do not
seem to have this problem, so think this is a local problem. But after
comparing almost every setting I could think of, I could not find the
problem.

I have tried to reproduce this problem on other workstations, but with
no success. I have tried to disable the Windows Scripting host, set my
security settings to high, etc. But in all situations the form did
keep working properly.

My question is: Is there someone who has encountered this problem
before, or knows how to solve this problem?


Thanks in advance,


- Sander Kooij

 

[Sue Mosher [MVP-Outlook]]

I haven't seen that problem but the first thing I'd do is run Office setup and make sure that all the components related to forms and scripting are installed.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sander Kooij]

Thanks for your response. Sorry for my delayed response, but the
customer was on vacation, and therefore could not reached. After
contacting the customer yesterday, I found out that the systems have
the same base image (office included) so the installation in both
cases is exactly the same. Do you have any more suggestions?

Thanks in advance,

- Sander Kooij

 

[Sue Mosher [MVP-Outlook]]

But did you do what I suggested and actually check whether those components are installed? Or run Help | Detect and Repair on the affected workstations?
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

Thanks for your response. Sorry for my delayed response, but the
customer was on vacation, and therefore could not reached. After
contacting the customer yesterday, I found out that the systems have
the same base image (office included) so the installation in both
cases is exactly the same. Do you have any more suggestions?

Thanks in advance,

- Sander Kooij

 

[Sander Kooij]

That was the trick, the customer checked it on a working workstation,
where VBScripting was enabled. He said it was the same base image and
therefore an exact copy of the other office installation. But after
cross-checking it seemed that VBscript was disabled.

Thank you verry much for your help !!!

- Sander Kooij