Error 800a03ea on winserver 2008?
in [VbScript]
|
Prev: How to send request by HTTP POST method in VBS script?
Next: Add user to local security group in Win7
From: EPP on 2 Mar 2010 11:38 I have a set of older .asp files that have been running uneventfully for several years on our old web server, but now as part of our testing on a new web server which has Windows Server 2008, I've discovered that the programs are NOT working, but rather throwing a syntax error 800a03ea on the very first code line, with the pointer at the "F" in function, in the include file the .asp progs bring in. My first guess is that because ws2008 is so much more stringent in security etc, something needs to be changed in my code, but then I found this on a board: "There is no reason at all why you would get this error as this is the first line to be run in the RTE and is for a Function. If your server is throwing an error at this point it suggests that there is something seriously wrong with the server that you are using. " And I have a lot of old "classic asp" .asp progs that have already been ported over to this new server, and they work fine as well. I don't think any of those reference this particular include file, but still, the original version of this one on the old server works OK. The code that is flagging is below, where the first actual line has the error pointer: <% function isvaliddate(mm,dd,yy,typ) on error resume next funcflag = true err.clear 'additional code eliminated for brevity 'check year = 4 digits if len(yy) = 4 then if yy < "1900" then funcflag = false end if else funcflag = false end if isvaliddate = funcflag on error goto 0 end function %> Makes me wonder if there's something in IIS7(?) elsewhere? that needs to be changed for this? Any thoughts? Rewriting them to Visual Studio is not an option at this time, unfortunately. Thanks elaine
From: EPP on 2 Mar 2010 11:46
DUH!!!! Never mind!! The .asp was pointing to an ever so slightly different file with the same name, but in another folder. Changed it to point to the right one, and it worked fine. I will slink back into obscurity now :) elaine On Mar 2, 11:38 am, EPP <eppuse...(a)gmail.com> wrote: > I have a set of older .asp files that have been running uneventfully > for several years on our old web server, but now as part of our > testing on a new web server which has Windows Server 2008, I've > discovered that the programs are NOT working, but rather throwing a > syntax error 800a03ea on the very first code line, with the pointer at > the "F" in function, in the include file the .asp progs bring in. My > first guess is that because ws2008 is so much more stringent in > security etc, something needs to be changed in my code, but then I > found this on a board: > > "There is no reason at all why you would get this error as this is the > first line to be run in the RTE and is for a Function. If your server > is throwing an error at this point it suggests that there is something > seriously wrong with the server that you are using. " > > And I have a lot of old "classic asp" .asp progs that have already > been ported over to this new server, and they work fine as well. I > don't think any of those reference this particular include file, but > still, the original version of this one on the old server works OK. > > The code that is flagging is below, where the first actual line has > the error pointer: > > <% > function isvaliddate(mm,dd,yy,typ) > on error resume next > funcflag = true > err.clear > > 'additional code eliminated for brevity > 'check year = 4 digits > if len(yy) = 4 then > if yy < "1900" then > funcflag = false > end if > else > funcflag = false > end if > > isvaliddate = funcflag > > on error goto 0 > end function > %> > > Makes me wonder if there's something in IIS7(?) elsewhere? that needs > to be changed for this? Any thoughts? Rewriting them to Visual Studio > is not an option at this time, unfortunately. > > Thanks > > elaine |