Ok, thanks. Looks like it is proabably not configuration or infrastructure related but some form of coruption since we found we could launch some other forms in the app using a roundabout path.

The particular corruption is beyond me right now since I opened a copy of the file in a hex editor and saw no strange characters. But something is causing ASP.NET to not like this aspx file.

>
>Here is a check list I created for my ASP.NET projects. It is a shot in the dark for your problem.
>
>ASP NET Login Issues for anonymous users
>
>

>Problem:
>
>Error message – Login failed for user ‘NT AUTHORITY\ANONYMOUS LOGON’.
>
>Reason:
>
>IIS not set correctly
>
>Resolution:
>
>1.	Open IIS
>2.	Go to Default Web Site
>3.	Right Click on Web Project of interest
>4.	Select Properties
>5.	Select Directory Security
>6.	Go to “Anonymous access and authentication control”
>7.	Select “Edit”
>8.	Uncheck “Anonymous access”
>9.	Select OK
>10.	Select Apply
>11.	Select OK
>
>Problem:
>
>Error message – Login failed for user ‘(null)’. Reason”: Not associated with a trusted SQL Server connection.
>
>Reason:
>
>IIS and/or Web.config may not be set correctly
>
>Resolution:
>
>See above to set IIS.
>
>In the Web.config file add the following line after the <system.web> tag and before the </system.web> end tag
>
><identity impersonate = "true"/>
>

>
>Tom