David
Fri Oct 27 14:40:46 CDT 2006
I'm not certain what you mean by "initial default setting" - default of
what?
Reinstalling Windows 2000 Server will bring back an initial and
vulnerable version of IIS5 to virus attacks. You can only reinstall in
a non-networked environment, apply SP4 via CD, or use a Slipstream
Windows 2000 Server SP4 installation.
Personally, I'd rather reinstall IIS6 and Windows Server 2003 SP1
because those tricky default security hassles disappear.
//David
http://w3-4u.blogspot.com
//
Snow wrote:
> David:
>
> If I want to reinstall the server, what do I need to reinstall to go back to
> initial default setting? IIS and server pack? Thanks
>
> "David Wang" wrote:
>
> > Guessing at the problem and making random configuration changes is not
> > an effective strategy to troubleshoot.
> >
> > I suggest starting with the file that shows the error and troubleshoot
> > backwards towards the cause. Can you locate the exact file and exact
> > line of code which has the syntax error and verify it? Basically,
> > whenever the compiler complains about something, the user is wrong
> > about 99.999999999999999% of the time and must and must fix the named
> > issue. The compiler doesn't care that you claim that this file came
> > from another server that's been working for 5 years - it says you gave
> > it wrong syntax, and you must obey and fix.
> >
> > I suggest keeping your mind open for possible non-standard causes
> > because the issue does not look to be related to IIS nor programmatic
> > logic in your ASP source code.
> >
> > For example, maybe you have different copies of the same code - make
> > sure the copy you verified is the actual copy that is executed to
> > handle your test request. Be very careful about making any assumptions,
> > write everything down that has been tried, along with results and
> > rationale.
> >
> >
http://blogs.msdn.com/david.wang/archive/2005/12/31/HOWTO_Basics_of_IIS6_Troubleshooting.aspx
> >
> >
> > //David
> >
http://w3-4u.blogspot.com
> > //
> >
> >
> > Snow wrote:
> > > Thanks!
> > >
> > > Yes, the code was directly copied from working server to this server. The
> > > code had been worked fine on the working server for almost five years. No any
> > > single bit or line changed since copied. It worked fine on this server after
> > > copied at first time, but we want to set up https. We just clicked internet
> > > server manager. We did not change anything. However, the code suddenly did
> > > not working and showed different errors. Any ideas?
> > >
> > > "David Wang" wrote:
> > >
> > > > Have you verified that every single byte of every single source code
> > > > file of this application are the same between this server and the other
> > > > working server?
> > > >
> > > > I'm not saying that the code is wrong. I'm saying that without your
> > > > knowledge, something may have corrupted the source code files on one
> > > > server but not another such that the corrupted file has incorrect
> > > > syntax. This is very, very possible.
> > > >
> > > > There are many components involved with a functioning ASP page, and ASP
> > > > source code and IIS are simply two of them. I see no reason why you'd
> > > > assume that since the source code works on another server that the
> > > > problem is automatically IIS. Especially since the error text has
> > > > nothing to do with IIS - it is complaining about the contents of the
> > > > ASP page.
> > > >
> > > > I'm suggesting that even changing one BIT of a single file could cause
> > > > this.
> > > >
> > > >
> > > > //David
> > > >
http://w3-4u.blogspot.com
> > > > //
> > > >
> > > >
> > > > Snow wrote:
> > > > > David:
> > > > >
> > > > > Thanks for the suggestion, but it realy confused me that the same code
> > > > > worked fine on the same server window 2000 IIS 5.0. If this is the syntax
> > > > > problem, it should bnot work at all. Why does it work fine on the other
> > > > > server? Thanks
> > > > >
> > > > > "David Wang" wrote:
> > > > >
> > > > > > I suggest that you continue to troubleshoot the issue instead of
> > > > > > assuming you have identified the source of the issue. I say this
> > > > > > because this just does not look like an IIS issue and there are no IIS
> > > > > > settings to "fix syntax errors" or "make ASP pages work".
> > > > > >
> > > > > > I suspect that the script engine binaries are corrupted, or your ASP
> > > > > > source code got corrupted, or both.
> > > > > >
> > > > > > Since corrupted binaries rarely continue to function, I would start by
> > > > > > looking at whether the code in the ASP pages have syntax errors
> > > > > > introduced through file corruption. Maybe your hard drive is going bad.
> > > > > >
> > > > > > For example, if the ASP file became Unicode/UTF8 accidentally, or
> > > > > > something inserted a random non-printable character into the ASP source
> > > > > > file, you can see such compiler errors.
> > > > > >
> > > > > >
> > > > > > //David
> > > > > >
http://w3-4u.blogspot.com
> > > > > > //
> > > > > >
> > > > > >
> > > > > > Snow wrote:
> > > > > > > My iis5.0 somehow was changed. All the code is not working now. One of errors
> > > > > > > showed: Microsoft VBScript compilation (0x800A03FC)
> > > > > > > Expected 'Next'
> > > > > > >
> > > > > > >
> > > > > > > However this code worked fine before. It is not definitely syntax error. How
> > > > > > > could I fix IIS setting? Thanks a lot.
> > > > > >
> > > > > >
> > > >
> > > >
> >
> >