Downloaded the Chapter 12 code, to get a better understanding of completed code. Sorry I learn in reverse.

I am getting a compile error in Controls/PTORequests.ascx.cs


cgvPTORequests.LoadMethodParameters.Add(((BasePage)Page).CurrentUser.ID);
NullReferenceException was unhandled by user code.

I have setup the db and changed my an account to match my domain information.
What am I missing? This seems to be a common problem within the VS environment.

Thanks

Went back to the basics,

1. Deleted Existing db and solution files.
2. Ran SQL Script to setup db
3. Open Chpt 12 Solution

On compile I got db access errors, which I am able to understand and overcome.
After I got them resolved, Compiled again. I thought I had it but it points right back to the above error. Am I missing something in the book?

It thinks the value is null. What db information is it looking for?

This is about as far as my comprehension for this error goes. It could be so many different possibilities. Anyone else willing to try my steps to reproduce?

Thanks

So still doing digging and have come to the conclusion that something in the db connection string may be the cause for this problem.

I will give you more insight into the SQL permissions errors that I got earlier.

The first one I got after initial setup is:

Cannot open database "HRPaidTimeOff" requested by the login. The login failed.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

I know this is the account that windows uses to authenticate when Integrated Security is turned on.
Should I not be using Integrated Security?

What I did to get around the SQL permissions issue, was grant it CRUD permissions after adding it as a user to the HRPaidTimeOff db.

It no longer notifies me of db connection issues, but instead gives the message from the first post.

Thanks

I was able to resolve my problem.

Turns out after thinking about it more in depth, it was an issue with my IIS configuration.

As noted above the line of code I pointed out was receiving a null value. After eliminating he cause being related to the db and code, I began to trace the permission access.

Sure enough it was.

What I did to resolve this was, disable anonymous access, then enable digest authentication so IIS will look at the domain. In the realm area select or type your fully qualified domain and this should work.

Excellent book, I have learned more from this one book about how to properly use .NET and a great foundation on code reuse.

Thanks

Sorry I didn't see this post earlier. I knew what it was right away. The application uses the user's window's logon to find them in the ENTUserAccount table. If anonymous access is turned on the Page.User.Identity.Name property returns NULL. Enabling windows authentication fixes the issue.