Active X Control problem

[Eichelmännchen]

Hello newsgroup.

I have a problem concerning Active X components.
When clicking on any "Export grid to Excel" link in PWA i get the following
message:
"The ActiveX Control on whick this feature dependes could not be created.
Because of this error, you can only copy the XML data to the Clipboard. Do
you want to continue?"
When I click on "Yes" I get "An error occured while copying the XML data to
the clipboard.

We have an infrastructure with three servers MSP Server 2003. Development,
Quality and Productive. The strange thing about it is, that it works for two
of them but not on the productive one! Active X controls must have been
downloaded correctly then and it can't be anything in the internet explorer
security settings.
The difference on the servers is that this server works with SSL and has no
WSS installed. But as far as I know this shouldn't be a problem. The error
occours for all users only on this server and not on the others.

Does anyone have an idea?
Thank you for your help.

regards
Sylvia

 

[Prj_Mngr]

Sylvia - Just checking that you realized that even though you get the error
message it does create the Excel (xml) file with the data in.

 

[Eichelmännchen]

Hello Julian.

I don't get the Excel file on the mentioned system. Only on other systems.
I also found out that it is related to an alias we use for the server.

When I login to PWA using the <fully qualified path>/Projectserver I get the
file without an error. But when I login using the alias
https://projectserver.company.com/projectserver I get the error and no file.
THe problem is that we're supposed to use the alias because the SSL
certificate is related to it but didn't find a solution yet.

kind regards
Sylvia

 

[NCLonghorn]

I switched to make sure I was using the full path, but I still get the dialog
about not being able to create the activex component. It does save the data
to the clipboard, but I'd rather have it work without those extra steps.

Could it be a permissions issue?

 

[David Schmitt]

We have corrected this error on all machines giving us the problem by adding
the web server (i.e. http://projectserver) to the Trusted Sites in the user's
Internet Options. (Bring up the Internet Options control panel, click on the
Security tab, click on Trusted sites, click on the Sites button and add the
site.)

Perhaps the problem with the full path working and not the alias is that the
full path was in the trusted sites and not the alias.

Hope this helps,

David