Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Deploying ASP Script

Status
Not open for further replies.

ironthorn

Programmer
May 9, 2000
13
0
0
US
Basic problem. <br>*<br>Need to deploy an ASP script using an<br>OLE Object. Origional script was written<br>in InterDev. DLL that is used already<br>exists on target machine. IIS is the<br>Inet server. <br>*<br>Problem is Interdev will not deploy<br>without Front Page extensions. I have<br>downloaded and installed Microsoft Posting<br>Acceptor but this does not seem to work. <br>It also appears to be causing a software<br>conflict with other software installed on<br>the machine. <br>* <br>Is there a way to deploy an Interdev <br>script WIHTHOUT installing Front Page<br>extensions on the target. If not is<br>there a way to port the ASP script to<br>another product that does not require<br>Front Page Extensions or does ASP require<br>Front Page Extensions to run? <br><br><br><br>
 
The definition of 'deploy' varies with the developer.&nbsp;&nbsp;Deployment of ASP pages can be as simple as copying the files to the server and using MMC to create the IIS application. Very easy to do manually.&nbsp;&nbsp;Alternatively, you can write scripts to do it all for you.&nbsp;&nbsp;We never use the front page extentions to deploy our stuff. <p>nick bulka<br><a href=mailto:nick@bulka.com>nick@bulka.com</a><br><a href= > </a><br>
 
&nbsp;&nbsp;&nbsp;We are using a 3rd part API in the script. When we just copy the files and<br>double check the class ID the object isn't initialized properly. The origional<br>developer ran into the same problem on our dev server and did a formal deploy<br>using Interdev and this worked. Somehow we need to figure out what Interdevs<br>formal deploy is doing and duplicate that. The dll does exist on the target <br>server.
 
Interesting.&nbsp;&nbsp;What's so special about this third party component?&nbsp;&nbsp;And can you elaborate on:<br><br>what do you mean when you say the object isn't initialized properly.<br><br>what do you mean by double checking the class id?<br> <p>nick bulka<br><a href=mailto:nick@bulka.com>nick@bulka.com</a><br><a href= > </a><br>
 
&gt;Interesting.&nbsp;&nbsp;What's so special about this third party component?&nbsp;&nbsp;And can you<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;elaborate on:<br><br>The DLL we are using allows us to use the API for a 3rd part product. <br><br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;what do you mean when you say the object isn't initialized properly.<br> If Not WebIServer.IsRunning Then<br> rsp = rsp & &quot;WebI Server is NOT running&lt;BR&gt;&quot;<br> Err.raise 1, , &quot;WebI Server not responding.&quot;<br> Exit Sub<br> End if<br><br>The object always responds with not running since it apparently is never <br>initialized. It exists, and works for the Application it was installed with. <br>On our Dev server we ran into the same problem but since we allow <br>Front Page extensions on in house servers we were able to do a formal<br>deploy. This solved this problem. <br><br>&gt;&nbsp;&nbsp;&nbsp;what do you mean by double checking the class id?<br><br>&lt;OBJECT RUNAT=Server SCOPE=Session ID=WebIServer<br>CLASSID=&quot;C91AC765-FC91-11D1-AE98-00A0C9A32806&quot;&gt;&lt;/OBJECT&gt;<br><br>This ClassID was the same on both servers.&nbsp;&nbsp;<br><br><br>
 
This is a rather obvious question,&nbsp;&nbsp;but just in case:&nbsp;&nbsp;You have registerd your component in the registry, right?<br><br> <p>nick bulka<br><a href=mailto:nick@bulka.com>nick@bulka.com</a><br><a href= > </a><br>
 
The DLL is registered. The installation of the application does that. <br>As for the script nope. I'm assuming that is exactly whats missing<br>in the deployment. Registry entries somewhere. Where I'm not sure. <br>
 
To try to find out what the problem is with your component, you can create a test page that instanciates the component using CreateObject().&nbsp;&nbsp;You should be able to inspect the err object after the call to see what the error message is.<br> <p>nick bulka<br><a href=mailto:nick@bulka.com>nick@bulka.com</a><br><a href= > </a><br>
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top