Question : Exchange RPC Client Access service failing to start

A little background information:

I am running Exchange 2010 Standard Edition as a VM on a Hyper-V server. I had issues with the server, and was advised to remove the virtual hard drives from within the Hyper-V manager for the VM. Upon doing so, and adding them back on again, I was back to a version of the server several months old.

Every night, I backup the entire Exchange folder on the server. After I booted the server, I restored a copy of the Exchange folder back onto the server. I started the EMC and found that the mailboxes all appeared. I attempted to mount the mailbox database, and it would fail. All of the log files and other files were also copied over.

After reading, I recovered the database using eseutil, which completed successfully. It said that it had fixed all of the corruption. Then, I defragged the database, which also completed successfully. After this, I ran the isinteg tool, which failed. After some further research, I copied all of the log files out of the mailbox database folder, and reran that tool. After running for around 45 minutes, it also errored out. However, I was able to mount the mailbox database.

Now onto my problem:

The RPC client access service won't start. When I try to start it, it just hangs, and sometimes says that the service has terminated unexpectedly.

Any thoughts?

Answer : Exchange RPC Client Access service failing to start

The MVC framework is completely separate from your data-access technique so you can use whatever type of data access layer you want with it, including the plain old ADO.NET classes. A lot of the samples use direct table access because that is the way the wind is blowing at the moment and it offers the most flexibility.
Linq to SQL works pretty well with stored procedures so may well be of use to you.
The MVC Framework pretty much focusses on managing the views and controllers. The model part is left up to you to implement however you see fit.