Well, the "except" part is a bit tricky here. ;)

The EventSource code simply won't run with a default setup. The ASPNET account and the IUSR_MachineName do not have sufficient permissions to the registry to create a new Event source. So, whatever you try, the code won't run. Since this code fires whenever another error occurred, it's likely this is a problem.

Either comment out the code as per my previous post, or grant access to the necessary registry keys for the IUSR account.

The same is true for the database. If your application is not allowed to access the database, the Web application won't run successfully.

Cheers,

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

I have commented out the EventSource code, only in two locations I could find? Using a "Find in files" search through the entire project, subfolders included.

Thanks,
Mike

One more thing: Which accounts did you grant access to the WIndows temp folder? Since the site is using impersonation, it won't run under the default ASPNET account, but under IUSR_MachineName. This account needs access as well.

Take a look here: http://www.dotnet247.com/247referenc...31/157002.aspx

Is this the problem you're encountering?

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

There are three of them. Search for SourceExists and you'll find:

- Global.asax.cs
- ThePhile\PhilePage.cs
- AppException.cs

Did you see the additional instructions by Ankur Verma in the readme in the code download?

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

HURRAY! We've got it sorted.
I changed the impersonation value to "false" and it works!
Thank you so much for all your help it's very much appreciated.

Does the changing of impersonation have any security implications I should be made aware of?
Why was it set to "true"?

Many thanks,
Mike

To be honest, I don't know.
AFAIK, ASP.NET was designed to use the ASPNET account, a least privilege account. This means that by default, things should work and be safe out of the box.

You usually won't need to enable impersonation for a site that uses anonymous access. In that case, just the ASPNET account is used. If you want to use the original callers security context, you'll need to disable anonymous access and enable impersonation. That's one of the few (only??) reasons I would use impersonation, but maybe the original authors required the IUSR account somehow....

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.