Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 928
  • Last Modified:

Exchange 2010 BPA on Edge Server Error

Hi,

I have run the BPA on an 2010 exchang edge server and I am getting the following:

Incorrect kerbauth.dll loaded. The kerbauth.dll module loaded in IIS points to an incorrect location: 'C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dll'. It should point to '%EXCHBINPATH%\Bin\kerbauth.dll'.

I have this error for both my hub role servers from the edge servers, but if i run the bpa on the hub servers i get no error.

I have found:Microsoft Solution

But from what I can see this is setup correctly.

Any help would be great.

Thanks.
0
Colchester_Institute
Asked:
Colchester_Institute
1 Solution
 
Sigurdur HaraldssonSystem AdministratorCommented:
I get the same error and cannot see that anything's out of the ordinary like you. I thought of reregistering the dll but haven't gotten around to it.

 I found this though at http://social.technet.microsoft.com/Forums/vi-VN/exchange2010/thread/efe35658-72b3-4625-aa89-31b182e2a05e:

-KERBAUTH should only be registered in IIS under modules on the PowerShell Site (not at the Default Site, and not at the Server level)
-KERBAUTH should only be registered as NATIVE, not as Managed at the PowerShell Site in IIS
-KERBAUTH should only be registered directly at the PowerShell Site in IIS, not Inherited.

If the Kerbauth.dll is registered as a "Managed" module not a "Native" Module, do the following:
• Remove Kerbauth from the Powershell web site as a Managed Module
• Verify if Kerbauth.dll is in the C:/Program Files/Microsoft/Exchange/V14/BIN directory.  
• In IIS go to the server level and register Kerbauth.dll using the name "Kerbauth" and the path to  C:/Program Files/Microsoft/Exchange/V14/BIN/KERBAUTH.DLL
• Go back to the Server level in IIS and Remove Kerbauth.  
Note: We are simply removing it from the server level, and since it is registered now, it should be available at lower levels.
• Under IIS Powershell in MODULES select Manage Native Modules, and check by Kerbauth which now should appear.
• Ran IISRESET from a Command Prompt
• Try opening EMC and EMS again.

2) Check to see if the Default Web Site has HTTP Redirect setting enabled, by selecting Default Web Site on IIS, and expanding “HTTP Redirect”.
If it is enabled, try the workaround of selecting the option under “Redirect Behavior”:

“Only redirect requests to content in this directory (not subdirectories)

Note:  By default the HTTP Redirect is disabled.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now