The Module DLL D:\Microsoft\Exchange Server\V14\Bin\kerbauth.dll failed to load. The data is the error

seems path for your path is incorrect...
can you check the actual path of the file kerbauth.dll

ones you find the file copy the path and put in the below file.
C:\Windows\System32\inetsrv\config\applicationHost.config

in the file search for below line and put the correct path
<add name=”kerbauth” image=”c:\ExchangeServer\V14\Bin\kerbauth.dll” />

ones changes are made save the file, the restart IIS by giving below command
IISRESET /NOFORCE

On my exchange server Kerbauth.dll is located D:\Microsoft\Exchange Server\V14\Bin\kerbauth.dll

There is not Microsoft Folder on the C Drive

Ok.can you confirm the path is same in application host.config file... And there is no typo...

Yes, This is exactly what I have in the applicationhost.config
<add name="kerbauth" image="D:\Microsoft\Exchange Server\V14\Bin\kerbauth.dll" />

1. Remote PowerShell uses Kerberos to authenticate the user connecting. IIS implements this Kerberos authentication method via a native module. In IIS Manager, if you go to the PowerShell Virtual Directory and then look at the Modules, you should see Kerbauth listed as a Native Module, with the dll location pointing to C:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll. If the Kerbauth module shows up as a Managed module instead of Native, or if the Kerbauth module has been loaded on the Default Web Site level (instead of, or in addition to, the PowerShell virtual directory), you can experience this issue. To correct this, make sure that the Kerbauth module is not enabled on the Default Web Site, but is only enabled on the PowerShell virtual directory. The entry type of "Local" indicates that the Kerbauth module was enabled directly on this level, and not inherited from a parent.

http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx

1) Kerbauth is only applied to the powershell with the module type=Native.
2) Kerbauth is not applied to the Default Website.
3) There is no C:\Program Files\Microsoft Folder nor C:\Microsoft There is only a D:\Microsoft folders

Because this solution resolved it