J
Jan Peter Stotz
Hi.
I am in the progress of migrating an ASP/vbscript application to
ASP.net/VB.
At the moment my asp.net code still contais a lot of late bound
com-objects with worked well until I installed the latest asp.net
security-patch from MS.
The application is (at the moment) impersonated via web.config to a
domain administrators account (via aspnet_setreg.exe).
Now even the creation of the simplest Com-Object fails with a
System.Exception: Cannot create ActiveX component
<%@ Page Language="VB" Debug="true" ASPCompat="true" %>
<script runat="server">
Sub Page_Load (ByVal Sender As Object, _
ByVal E As EventArgs)
dim objRootDSE = GetObject("LDAP://rootDSE")
End Sub
</script>
<html><body>
</body></html>
Did any body else notices a similar behaviour or knows a way to avoid
this problem?
Jan
I am in the progress of migrating an ASP/vbscript application to
ASP.net/VB.
At the moment my asp.net code still contais a lot of late bound
com-objects with worked well until I installed the latest asp.net
security-patch from MS.
The application is (at the moment) impersonated via web.config to a
domain administrators account (via aspnet_setreg.exe).
Now even the creation of the simplest Com-Object fails with a
System.Exception: Cannot create ActiveX component
<%@ Page Language="VB" Debug="true" ASPCompat="true" %>
<script runat="server">
Sub Page_Load (ByVal Sender As Object, _
ByVal E As EventArgs)
dim objRootDSE = GetObject("LDAP://rootDSE")
End Sub
</script>
<html><body>
</body></html>
Did any body else notices a similar behaviour or knows a way to avoid
this problem?
Jan