Activex component CANNOT CREATE OBJECT

<i><b>Originally posted by : Colin (colin.waters@ncr.com)</b></i><br />I have an NT server that I created a COM object on using Visual Studio. I registered the dll successfully. I am using PWS as the web server here. Within my ASP page.. I make reference to the COM object in Javascript like so:<br /><br />var one = new ActiveXObject ("R2demo.Test.1")<br />CurrentItem=one.GetText(); <br /><br />This works fine on MACHINE 1.<br /><br />MACHINE 2 is running NT and uses IIS as the web server. I transferred the dll to MACHINE 2 and it registers successfully. However when I try to pull up the ASP page, it chokes on this line. <br /><br />var one = new ActiveXObject ("R2demo.Test.1")<br /><br />and I get the error: Automation server error, cannot create object..<br /><br />It has nothing to do with the COM object cause I ran a quick vbscript program on it and it registers and returns the correct thing..<br /><br />I am now thinking that it may be a server problem.. Pws vs. IIS<br /><br />Any comments or suggestions on this..<br />Thanks<br />CW.

<i><b>Originally posted by : Barry B</b></i><br /><br />Make sure that the NT permissions are correctly set for the folder. IIUSR_MachineName must have permissions to use the file.<br /><br />------------<br />Colin at 4/6/2000 12:58:38 PM<br /><br />I have an NT server that I created a COM object on using Visual Studio. I registered the dll successfully. I am using PWS as the web server here. Within my ASP page.. I make reference to the COM object in Javascript like so:<br /><br />var one = new ActiveXObject ("R2demo.Test.1")<br />CurrentItem=one.GetText(); <br /><br />This works fine on MACHINE 1.<br /><br />MACHINE 2 is running NT and uses IIS as the web server. I transferred the dll to MACHINE 2 and it registers successfully. However when I try to pull up the ASP page, it chokes on this line. <br /><br />var one = new ActiveXObject ("R2demo.Test.1")<br /><br />and I get the error: Automation server error, cannot create object..<br /><br />It has nothing to do with the COM object cause I ran a quick vbscript program on it and it registers and returns the correct thing..<br /><br />I am now thinking that it may be a server problem.. Pws vs. IIS<br /><br />Any comments or suggestions on this..<br />Thanks<br />CW.