I am trying to deploy an ASP application on Windows 2003 server. The application relies on RDS. Now in Windows 2000, I just create a virtual diretory of MSADC and it would work. Now in 2003, I am getting an error Internet Server Error: Object/module not
found. I have read that I just need to enable the web extension for MSADC, but it's still not working. There's somethign I read also that indicates that RDS has some security issues and probably fixed it. There's suppose to be a link to enable MSADC, but microsoft took it down or something like that. Does anyone know what's going on. Thanks,
I have a page that inserts a record into a SQL database. when on the development server and the development database this worked fine. I then moved everything to production and now it inserts 2 identical records into the database. I even tried pointing my dev code at the prod database and everything works fine. when I point the prod code at the dev database it inserts 2 records. the 2 sets of code are identical. Has anyone seen this before and if so do you have any possible solutions
Has anyone seen this before. Actually what is happening is that when I call my asp file that gets the data from the form and does the insert into the database the file is being called twice in production only once on the dev server. any suggestions.
uhm, I tried the exact code you described and it worked for me (in IE that is). Are you using a different browser?
As reference though, this is a more programatically correct approach:
var frm = document.getElementById("fp");
if (frm) frm.submit();
<form id='fp' name='fp' action='http://localhost' method='post'>
<select name='fptype' onChange='onchangeOptions()'>
We've included the id attribute for the <form> and so we can use:
getElementById DOM method
which is better than using the document.elementname approach as this searches through all the DOM collections. With multiple FORMs on the page (in my experience) the latter didn't always return the object, whereas the former does.
Ahh this old chestnut. I'm going to take a stab in the dark here and say that you've got a Response.Redirect in the Login.asp file. This is getting called after you've written some data out to the client. There is a simple fix for this, just add
Response.Buffer = true
at the top of the asp file and you should find that all will be well.
Setting Response.Buffer to true, tells asp to buffer all of the output until the page has been fully parsed and is ready to go. This means that if you make a change to the HTTP headers mid-page (Response.Redirect sends HTTP headers telling the browser that the requested item has been moved somewhere else [in this case wherever you Response.Redirected to]), asp will just issue out the final headers. Without buffered output, asp will have already sent an HTTP header saying that the resource was found as is following, then it will try to tell the browser that it moved (hence the error)
You will probably find that this page would work "as is" in IIS 5.0 as buffering is turned on by default, whereas in IIS 4.0 it was turned off.
If I'm wrong and this doesn't fix things for you, then please provide the broken code and I will try to help you further.
Thanks, but I already know how to search for free web analysis tools. I am asking for peoples opinions on any ones that they already have used or heard about. I am looking for personal recommendations.
Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert