Background:
My team has a web app that is used by dozens of client companies. Our latest version includes a .NET assembly used for encryption/transfer. Our installation includes an executable that allows the client to enter a server site name and it will add full trust to that site on the client PC.
Usually when there is an error it's one of the following:
- They don't have enough admin rights to add (not machine level)
- Incorrect spelling of site
- They added multiple entries for the same site
However today I was working with one that has me baffled. From my workstation - I am able to access the client server and download the assembly without issue, so it doesn't seem to be a server configuration issue.
I've checked his caspol, the entry looked identical to my own when i successfully connected. The site is listed in his IE Trusted sites as well (even though he's on IE6 and it shouldn't need it to be). I've tried the following:
- Had him reset caspol and add the code group entry for the site
- Had him remove the site code group entry and add a caspol entry that gives "FullTrust" to the "Trusted" sites IE zone (works with other clients).
- Had him close out of IE every time we make a change and attempt to re-enter the part of our web app that requires the assembly download.
Every time he attempts to access the area where the assembly would download he gets the old "Object doesn't support this property or method" error. I have him check his fusion bind errors in IE history and it tells him that the "assembly does not allow partially trusted callers".
BTW, allowing partially trusted callers is not an option. I have hundreds of users as dozens of locations using this same setup - so I don't believe it is a code issue.
Are there IE security settings that would prohibit .NET from looking at the caspol settings?
He's having to work around the group policy that runs every few hours to change settings. But doing a "caspol -lg" lists the machine level code entries correctly.
I realize it could be some kind of firewall issue at the client location, but we haven't run into that type of thing yet.
Any help would be appreciated.
-ZE
My team has a web app that is used by dozens of client companies. Our latest version includes a .NET assembly used for encryption/transfer. Our installation includes an executable that allows the client to enter a server site name and it will add full trust to that site on the client PC.
Usually when there is an error it's one of the following:
- They don't have enough admin rights to add (not machine level)
- Incorrect spelling of site
- They added multiple entries for the same site
However today I was working with one that has me baffled. From my workstation - I am able to access the client server and download the assembly without issue, so it doesn't seem to be a server configuration issue.
I've checked his caspol, the entry looked identical to my own when i successfully connected. The site is listed in his IE Trusted sites as well (even though he's on IE6 and it shouldn't need it to be). I've tried the following:
- Had him reset caspol and add the code group entry for the site
- Had him remove the site code group entry and add a caspol entry that gives "FullTrust" to the "Trusted" sites IE zone (works with other clients).
- Had him close out of IE every time we make a change and attempt to re-enter the part of our web app that requires the assembly download.
Every time he attempts to access the area where the assembly would download he gets the old "Object doesn't support this property or method" error. I have him check his fusion bind errors in IE history and it tells him that the "assembly does not allow partially trusted callers".
BTW, allowing partially trusted callers is not an option. I have hundreds of users as dozens of locations using this same setup - so I don't believe it is a code issue.
Are there IE security settings that would prohibit .NET from looking at the caspol settings?
He's having to work around the group policy that runs every few hours to change settings. But doing a "caspol -lg" lists the machine level code entries correctly.
I realize it could be some kind of firewall issue at the client location, but we haven't run into that type of thing yet.
Any help would be appreciated.
-ZE