• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1361
  • Last Modified:

Exchange 2007 SP3 - Update 3 - wants KB968389 ? ?

Updated my Windows 2003 (64bit) Running Exchange 2007 SP3 to have update 3 on.
From here : http://www.microsoft.com/downloads/en/details.aspx?FamilyID=17615f50-8a56-428c-bc1a-629795692da1

Remote & Local users seem to be running fine, but I guess something is up?

Now when I run EMC I get the following error message:

--------------------------------------------------------
Microsoft Exchange Warning
--------------------------------------------------------
The following warning(s) were reported while loading topology information:

Get-ActiveSyncVirtualDirectory
Completed

Warning:
Extended protection has not been enabled.  Install the operating system update specified in KB968389 onto server "maverick.syspal.co.uk" and try again. System.IO.IOException: The network path was not found.

   at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str)
   at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.LoadFromRegistry(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task)



Get-OabVirtualDirectory
Completed

Warning:
Extended protection has not been enabled.  Install the operating system update specified in KB968389 onto server "maverick.syspal.co.uk" and try again. System.IO.IOException: The network path was not found.

   at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str)
   at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.LoadFromRegistry(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task)



Get-OWAVirtualDirectory
Completed

Warning:
Extended protection has not been enabled.  Install the operating system update specified in KB968389 onto server "maverick.syspal.co.uk" and try again. System.IO.IOException: The network path was not found.

   at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str)
   at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.LoadFromRegistry(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task)

Warning:
Extended protection has not been enabled.  Install the operating system update specified in KB968389 onto server "maverick.syspal.co.uk" and try again. System.IO.IOException: The network path was not found.

   at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str)
   at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.LoadFromRegistry(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task)

Warning:
Extended protection has not been enabled.  Install the operating system update specified in KB968389 onto server "maverick.syspal.co.uk" and try again. System.IO.IOException: The network path was not found.

   at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str)
   at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.LoadFromRegistry(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task)

Warning:
Extended protection has not been enabled.  Install the operating system update specified in KB968389 onto server "maverick.syspal.co.uk" and try again. System.IO.IOException: The network path was not found.

   at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str)
   at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.LoadFromRegistry(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task)

Warning:
Extended protection has not been enabled.  Install the operating system update specified in KB968389 onto server "maverick.syspal.co.uk" and try again. System.IO.IOException: The network path was not found.

   at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str)
   at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.LoadFromRegistry(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task)


--------------------------------------------------------
OK
--------------------------------------------------------
0
thegiantsmurf
Asked:
thegiantsmurf
  • 14
  • 10
  • 6
  • +1
1 Solution
 
NetfloCommented:
Hi, you need to install the suggested update which provides stronger authentication for your Server 2003 box, not Server 2008.

Specific update for your server is: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=3ce0efe2-82ec-4134-9891-37efeab24e3a&displaylang=en

The error you are getting is a known issue that Microsoft are aware of and will be providing a solution shortly, you can for the time being leave the system as is or uninstall the RU3.

Please see the following link and last post by Kevin http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/80e3b96d-0f17-4ead-92ab-9875cc663ef3/

Hope this helps.
0
 
thegiantsmurfAuthor Commented:
I've installed the patch http://www.microsoft.com/downloads/en/details.aspx?FamilyID=36b476ef-6a57-47be-98ce-4b0b7d56fef7 - but still get the same error.

Should I un-install Roll Up 3 or just wait?

0
 
jpierce26Commented:
Any update on this?  I have the same problem.  However, I use the EMS from the server which is Windows 2008 R2.  The patch mentioned is for Windows Vista.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
NetfloCommented:
Jpierce26, see following link: http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/80e3b96d-0f17-4ead-92ab-9875cc663ef3/

Microsoft, Moderator

Hello Everyone,

We are still working out the documentation and proposed fix for this issue. The explanation I’ve gotten for this is as follows:
 
“This is caused by a channel binding implementation that was fixed in Rollup Update 2. We need to create a COM object (Microsoft.Web.Services) on the remote server to access the IIS Metabase of the remote server. We set the channel binding options on the Metabase causing the IIS server to implement channel binding. The problem is when a firewall is turned on, ahadmin can’t create the COM object through the firewall. The generic message displayed assumes you want to implement channel binding but isn’t specific enough to tell you the problem is the firewall.”
 
Right now the fix is to implement the firewall rules that I listed above.
 
There appear to be several variations posted in this thread. In short, if creating the firewall rules as mentioned above does not resolve your issue, you are experiencing a different problem and should troubleshoot it accordingly.

We are working to get a public document explaining this issue in detail with an official solution/fix. My goal is to have this within a couple of weeks, but again, for now, the firewall rules should be used to work around the warning displayed.
 
Thanks to everyone for your patience.
Kevin Ca - MSFT
0
 
NetfloCommented:
thegiantsmurf,

Is your Server 2003 firewall on or off?

I would keep an eye on the following post for an update, please note that a workaround has been mentioned at the bottom of the article: http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/80e3b96d-0f17-4ead-92ab-9875cc663ef3/
0
 
thegiantsmurfAuthor Commented:
Netflo,

The firewall on the 2003 Server is off (not even enabled on install)
0
 
NetfloCommented:
Thegiantsmurf and Jpierce26,

I have some good news (hopefully), after much reading into this particular issue and wanting to help you guys, please try the following:

IN THE FOLLOWING ORDER:

1. Uninstall Exch 2007 SP3 Rollup 3, reboot
2. Ensure you have a full backup of your server
3. Apply Exchange 2007 SP3 Rollup 3 v2 from here: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=17615f50-8a56-428c-bc1a-629795692da1
4. Recommend a reboot
5. Test the cmdlets and let me know how you get on.

Best of luck!
0
 
thegiantsmurfAuthor Commented:
Netflo,

I might be a chicken and wait for the Rollup 4 due in May.
http://bink.nu/news/released-update-rollup-3-for-exchange-2010-sp1-and-exchange-2007-sp3.aspx

I'm just nervous about removing rollup 3 and still having a working server at the end of it.
0
 
thegiantsmurfAuthor Commented:
Netflo,

Actually bite the bullet and did the update.
Same error when you click on Cliet Access on Server Configuration.
0
 
jpierce26Commented:
I have been waiting for Microsoft to come up with a fix for this.  I have an open case and the tech calls me occasionally to tell me that the case is still pending a fix.

Just an FYI
0
 
thegiantsmurfAuthor Commented:
jpierce26,

do you have the very same error (all bar a different server name?)
0
 
jpierce26Commented:
yes, I have the same issue.  I patched my Exchange 2007 Server running on Windows 2008 (NOT R2).

I patched the SP3, then applied the V2 fix.  When I launch the EMC I receive the same error listed above.  

It took several hours to get my Microsoft Tech support to believe me.  

Jeff
0
 
thegiantsmurfAuthor Commented:
Is there an update out for this as yet ?
0
 
NetfloCommented:
Hi all,

This issue has finally been acknowledged by MS, a follow on from the previous link I first posted. You need to contact MS PSS and they'll provide the fix for you. Please see the following link for more info:

http://support.microsoft.com/default.aspx?scid=kb;en-US;2538958

0
 
NetfloCommented:
Thegiantsmurf,

Can we get a little feedback on this issue? My last post was a solution only offered by contacting MS PSS, did you get this resolved?

Thanks!
0
 
thegiantsmurfAuthor Commented:
I've not managed to contact Microsoft as yet...........(due to holidays and trying to miss Firday 13th - just in case).
I'll probably phone them Monday.
0
 
thegiantsmurfAuthor Commented:
Managed to get hold of Microsoft........after 3 hours on the telephone, we are at the stage where our Exchange 2007 server is now on SP3 standard, RU 2, RU3 and RU3v2 were un-installed.

So......I guess I wait.......for the next update ?
0
 
jpierce26Commented:
They have to come up with some fix soon don't they?  I have been waiting a long time for a solution.
0
 
thegiantsmurfAuthor Commented:
jpierce26,

There is a temp fix for a 2008 server. (not a 2003 server!)
The Microsoft tech guy got me to check that port 7000 was not being used anywhere (using netsh firewall command (server 2003)) and also checking in regedit under Hkey-L_M->Software->Classes-> Find if {9fa5c497-f46d-447f-8011-05d03d7d7ddc} exist's - this is also related to port 7000.

This fix didn't work for us, as he kept onn saying it's for 2008 not 2003 server.
I dont know if this will help you ?....for us, it's just  a matter of waiting for RU4 and hoping that the fix is in that.  When this arrives, the techie guy would not comment due to issues with 2003 server.
0
 
jpierce26Commented:
I just got a call from someone at Microsoft a few moments ago.  (I swear they are reading these).  I have an open case with them waiting for the fix to come out.  He told me Roll-up Update3 will fix my problem and gave me this link:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=17615f50-8a56-428c-bc1a-629795692da1

But i already have that patch.  I am going to wait for RU4.

Jeff
0
 
NetfloCommented:
Gents, I hope MS can resolve this issue for you, seeing as they are aware of it now. Patiently, we wait...
0
 
thegiantsmurfAuthor Commented:
Gents,

Just as another update, just got off a call from the same Microsoft Techy, they instructed me to install RU3v2 (Exchange2007-KB2530488-v2-x64-EN.msp) BUT it still gave the same error on EMC

They are still stumpted as this should not affect our problem.......so for now, back to support for a fix :-(
0
 
thegiantsmurfAuthor Commented:
Gents,

Last update on this situation (don't know if EE will allow me to keep this open till there is an fix) BUT please see email content below from Microsoft support:

"It was my pleasure to serve you during your case for the issue “Extended Protection Warning Displayed in Exchange Management Console after installing RU2” issue. I hope that you were satisfied with the service provided to you. I am providing you with a summary of the key points of the case for your records. If you ever have any questions please feel free to call me. My contact information is below.

As we discussed, this issue is a known bug. We tried the work around but it was not applicable for Exchange 2007 on Windows 2003. I checked if there is any Interim Update available but as of now there is no Interim Update available. This issue is scheduled to be get fixed in Exchange 2007 SP3 RU5. However the scheduled release date for RU5 is not known yet.

As of now, we have uninstalled RU2 and RU3-V2 after which the warning message does not come up.

Since there is no resolution to this case currently we are providing refunds for this case."

So Gents......we need to wait for RU5 !
0
 
NetfloCommented:
Hmmm, not the answer to be expected and didn't expect MS to tell you to go back a few roll ups. I would probably stick with the latest RU even though an error message is received to ensure your system is fully up to date.

Thanks for the update.
0
 
thegiantsmurfAuthor Commented:
RU4 is out.
Has anyone else installed this yet ?
0
 
NetfloCommented:
I personally have not, following the RU4 recall on Exchange 2010 SP1.
0
 
RosenowWCommented:
...yes, I installed RU4 on the W2k8r2SP1 and W2k3SP2 Exchange 2007 servers of one of our customers. No effect: Warning still appearing when connecting from W2k3 to the W2k8r2 Exchange server...

Also uninstalled all RUs (1,2,3v2) and then installed RU4. All the same - no effect on this issue.

So I gues waiting for RU5 is the best option.

WR.
0
 
jpierce26Commented:
How much longer do we have to wait Microsoft?  They seem to be dragging their feet on this one.
0
 
thegiantsmurfAuthor Commented:
Update 5 installed and it's fixed my problems.
This can be found at : Exchange2007-KB2602324
0
 
NetfloCommented:
Brilliant news!
0
 
thegiantsmurfAuthor Commented:
Service pack supplied by Microsoft solved the problem
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 14
  • 10
  • 6
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now