Moving along, again....the MSADC virtual folder needed a little tweaking.  It also was re-configured in the mystery change yesterday afternoon.

Things look ok, now.  Hope it stays that way.

Bill

Bummer.  Not everything was cleared up.  Some issues still remain regarding some remote scripting issues.  Not good.  A lot of stuff was done with that "old technology.  Well, back to the drawing board, so to speak.

Cool...yeah, that has happened to me before too but that particular issue always raises a totally different behavior and error!  Glad you got it going!

Just got it solved.

I actually thought the same way you did and followed the permissions/security path.  Lots of dead-ends and no solutions through that route.

The problem was that the web app got mapped to the 2.0 framework...it was written for the 1.1 framework.  How that happened is still a deep, deep mystery.  I ran the following script from the proper framework folder on the server:

aspnet_regiis -s W3SVC/1/ROOT/MyAppName

That cleared everything up.  It remapped my server scripts to the proper framework. 

Thanks a lot for responding!!
Bill

It sounds like something chaged either within IIS or the security on the machine.  When I run into things like this, I start to backtrack and see what changed and where versus making changes to the application until I understand what happened.

This is also one of those things that I would have to actually see in front of me so that I could see the point of failure.  Sorry for such as ambiguous answer, but when dealing with IIS and errors like this, there are a lot of external things that can have an impact on the application and the outcome of something like this.  Sorry

I will say this, though, I sounds like it falls on the side of security and permissions.  I might start there if nothing else is coming up (i.e. temporarily provide loosened permissions, etc.)

I have been working on this for nearly 24 hours and still have not been able to discover the solution.  I am turning to the knowledge in the SF collective to see if anyone has run into something like this before.

Something changed on our IIS yesterday that brought everything to a screeching halt.  One of the main errors that I received was this one:

Invalid postback or callback argument. Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.

I added the tag to the web.config file (as the error suggests) knowing that this is an intranet application and I am comfortable doing this...the app began working again; however, not everything works.  Most pages will not run local scripts.  Some pages do not run server scripts (from postbacks).  I am completely baffled as to what is going on.  I recreated the virtual folder...I even moved the entire app to another server...the same thing is happening.

I am really hoping someone here can shed some light on this.  Some of our critical systems are involved.  Many are breathing heavily down my neck ready to pounce on me.

Thanks!
Bill