"My ASP script works on my server but it does not work on your server."

Components

Sometimes, it could be due to a missing component in the server. Take for example, if your ASP script contains lines that look like ....

Set objNewMail = Server.CreateObject("CDONTS.NewMail")

... this means that your script needs the CDONTS component to be installed in the live server. (By default, Windows 2003 server does not have this component installed. Microsoft took it out of the Windows 2003 server.)

CDONTS is an example that we are all very familiar with. But some are not as obvious.

Take for example, if your script contains lines that look like ....

Set Mail = Server.CreateObject("Persits.MailSender")

.... that means your script needs the component "AspEmail" installed. When you were developing your script in your test server, you may have installed this component to make your script work. If the same component is not installed in our server, your script will not work in our server.

You may say, "But AspEmail is a very common component. Shouldn't you guys have installed it in the first place?" Well, what is deemed as "common" to one programmer may be obscure to another. More importantly, a basic security guideline is, "If you don't need it, don't install it." That is why we do not install it every component under the sun by default.

If your ASP script depends on a particular component, and if this particular component will not be installed in a default installation of the Windows 2003 server and IIS 6, it would be a good idea to let us know that you need this particular component. If our security policies allow it, (and of course, after licensing issues are covered), we'll install the component for you.

If your script needs a SMTP host, you can use "127.0.0.1".