Windows Server 2003 Service Pack 2 and the Scalable Networking Pack

Remember all the heart ache we had with this … and having to disable TCP Chimney just for the server to actually stay working :-|

 Wel Michael has found the latest installment in the way of a new KB that essentially sets EnableTCPChimney, EnableRSS,and EnableTCPA to 0

948496 An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers

What is interesting about the KB is the list of issues that may occur when Windows Server 2003 SNP is turned on!

  • You cannot create a Remote Desktop Protocol (RDP) connection to the server.
  • You cannot connect to the Exchange server from a computer that is running Microsoft Outlook.
  • Inactive Outlook connections to the Exchange server may not be cleaned up
  • You experience slow network performance.
  • You experience intermittent RPC communications failures.
  • The server stops responding.
  • The server runs low on nonpaged pool memory

Not to serious then!
 

945684: Description of Update Rollup 1 for Microsoft Exchange Server 2007 Service Pack 1: v2.1

Humm, very crafty, the following articles have been added as “fixed” to this KB!

Article ID: 945684
Last Review: March 5, 2008
Revision: 2.1

  • 946958 (http://support.microsoft.com/kb/946958/) The Restore-Mailbox cmdlet is not successful and you receive an error message in Exchange Server 2007 S946958
    • In a Microsoft Exchange Server 2007 Service Pack 1 (SP1) environment, you run the Restore-Mailbox cmdlet. When you do this, the operation is not successful.
  • 945318 (http://support.microsoft.com/kb/945318/) An Exchange Server 2007 edge server does not rewrite the sender address for externally bound messages in an Exchange Server 2007 Service Pack 1 environment
    • In a Microsoft Exchange Server 2007 Service Pack 1 (SP1) environment, you set an AddressRewrite entry on two Microsoft Exchange Server 2007 edge servers. After you do this, one Exchange Server 2007 edge server does not rewrite the sender address for externally bound messages.
  • 947014 (http://support.microsoft.com/kb/947014/) An Exchange Server 2007 mailbox server randomly generates many transaction logs in an Exchange Server 2007 Service Pack 1 environment
    • In a Microsoft Exchange Server 2007 Service Pack 1 (SP1) environment, an Exchange Server 2007 mailbox server randomly generates many transaction logs.
  • 945938 (http://support.microsoft.com/kb/945938/) The Information Store service intermittently stops responding after you apply Microsoft Exchange Server 2007 Service Pack 1 on an Exchange Server 2007-based server
    • After you apply Microsoft Exchange Server 2007 Service Pack 1 (SP1) on an Exchange Server 2007-based server, the Information Store service intermittently stops responding
  • 944333 (http://support.microsoft.com/kb/944333/) The store event sink does not run as expected in an Exchange Server 2007 environment
    • In a Microsoft Exchange Server 2007 environment, the store event sink does not run as expected. The event is triggered, but the registered script is not executed.
  • 943808 (http://support.microsoft.com/kb/943808/) An attachment incorrectly appears as the body of an e-mail message in Exchange Server 2007
    • In a Microsoft Exchange Server 2007 organization, a user receives an empty e-mail message that has an attachment. However, the attachment incorrectly appears as the body of the e-mail message.
  • 943937 (http://support.microsoft.com/kb/943937/) An application cannot impersonate a user and then run Windows PowerShell commands in an Exchange Server 2007 environment
    • When an application tries to impersonate a user programmatically and then run Windows PowerShell commands in a Microsoft Exchange Server 2007 environment, Exchange Server 2007 blocks the call.
  • 941704 (http://support.microsoft.com/kb/941704/) The Microsoft Exchange Information Store service stops responding on an Exchange Server 2007 server
    • The Microsoft Exchange Information Store service stops responding on a server that is running Microsoft Exchange Server 2007. Additionally, clients cannot connect to the Exchange store. When this problem occurs, you cannot stop the Microsoft Exchange Information Store service. Additionally, the RPC Requests counter in the MSExchangeIS object in the Performance console reaches its highest value.
  • 943394 (http://support.microsoft.com/kb/943394/) Some e-mail messages become stuck in the submission queue in Exchange Server 2007
    • In a Microsoft Exchange Server 2007 environment, some e-mail messages become stuck in the submission queue and take a long time to be delivered.

945684: Description of Update Rollup 1 for Microsoft Exchange Server 2007 Service Pack 1

Holy sh1t have you read the fixes that are in this!

925252: The Store.exe process uses almost 100 percent of CPU resources, and the size of the public folder store increases quickly in Micorosoft Exchange Server 2007
View products that this article applies to.
Consider the following scenario. You create a Contacts folder in public folder tree that is located in a Microsoft Exchange Server 2007 environment. Additionally, you add some contacts in the Contacts folder. A user opens the properties of the Contacts folder in Microsoft Office Outlook. Then, the user clicks to select the Show this folder as an e-mail Address book check box in the Outlook address book, opens the Outlook address book, and then browses to the Contacts folder. In this scenario, the Store.exe process on the Exchange Server 2007 server uses almost 100 percent of CPU resources. Additionally, the size of the public folder store increases quickly.

941655: The Store.exe process stops responding, and event ID 9659 is logged on a Microsoft Exchange Server 2007 server
The Store.exe process stops responding on a server that is running Microsoft Exchange Server 2007

942424: On an Exchange Server 2007-based computer, the Microsoft Exchange Information Store service stops unexpectedly when you start the service or when you mount a database store
On a Microsoft Exchange Server 2007-based computer, the Microsoft Exchange Information Store service stops unexpectedly when you start the service or when you mount a database store.

943371: Event IDs 8206, 8213, and 8199 are logged in a Microsoft Exchange Server 2007 environment
…many transaction logs are created. This situation causes the hard disk drive to become full, the stores to unmount, and cluster continuous replication (CCR) to stop functioning.

943479: Some source mailboxes are merged into one target mailbox after you use a Move-Mailbox cmdlet to migrate the mailboxes from a Microsoft Exchange Server 2003 organization to a Microsoft Exchange Server 2007 organization
You use a Move-Mailbox cmdlet to migrate the mailboxes from a Microsoft Exchange Server 2003 organization to a Microsoft Exchange Server 2007 organization. To speed up the migration process, you run a migration script that executes multiple parallel processes with the Move-Mailbox cmdlets on the Exchange servers. However, duplicate aliases exist after the migration process. Additionally, multiple source mailboxes are merged into one target mailbox.

944451: Only the entries in the MailSubmission log are returned when you run the Get-MessageTrackingLog cmdlet against a Microsoft Exchange Server 2007 server that hosts both the Hub Transport role and the Mailbox role
You run the Get-MessageTrackingLog cmdlet to search the message tracking logs against a Microsoft Exchange Server 2007 server that hosts both the Hub Transport role and the Mailbox role. However, the results that are returned include only the entries in the MailSubmission log.

945428: An e-mail message is in disorder and is unreadable in a Microsoft Exchange Server 2007 environment
In a Microsoft Exchange Server 2007 environment, an e-mail message is in disorder and is unreadable. However, the same e-mail message is readable if it is received by a user in a Microsoft Exchange Server 2003 environment.

942647: The display name of an e-mail address is not encoded correctly according to RFC 2047 when you use extended characters in Microsoft Exchange Server 2007
In a Microsoft Exchange Server 2007 environment, you send an e-mail message to an external user. However, the e-mail address is not correctly encoded according to RFC 2047

  • The display name of the recipient or of the sender is in the Lastname, Firstname format.
  • The display name of the recipient or of the sender contains an umlaut

937194: The product service strategy for Exchange Server 2007

Any another one .. interesting how you could never find them when you want them

 


Source: http://support.microsoft.com/kb/937194/ 

This article describes the product service strategy that Microsoft uses to help support Microsoft Exchange Server 2007.

The way that we service Exchange 2007 differs from the way that we service earlier versions of Exchange. This new service method offers many advantages over earlier methods. This method differs from earlier methods with regard to the following:

  • Update contents
  • Installer technology
  • Fixes that are included

This article describes these differences. Additionally, this article contains information about how you can best deploy updates for Exchange 2007.

 
 

937052: How to obtain the latest update rollup for Exchange 2007

Interesting KB! and to keep an eye on!


Source: http://support.microsoft.com/?kbid=937052 

This article describes how to obtain the latest update rollup for Microsoft Exchange Server 2007. Update rollups are a common way to distribute Exchange 2007 fixes and Exchange 2007 modifications. You can install the latest update rollup to help keep the product up-to-date.

Windows 2003 SP2 & Exchange 2003 – Part II

Okay so came back with this:

  1. Please Update storport.sys to the latest version (946448), and Hp storport drivers (this can be easily accomplish by
  2. Update Broadcom nics
  3. Turnoff TCP Chimney per kb912222 (I believe It’s already turned off)
  4. Disable Checksum Offloading. 

Additional information:
http://www.broadcom.com/drivers/faq_drivers.php#33
http://www.broadcom.com/drivers/oemsupportlinks.php

Yeah okay, so we have done, 2,3 and 4.  The storport update didn’t make much difference, but this did 


So comparing two identical clusters 01 and 03.  Both are ProLiant DL585 G2  with Windows 2003 R2 SP2 x86, Exchange 2003 with the latest patches and have four storage groups each.  They also have /3GB /USERVA=3030 /BASEVIDEO added to boot.ini

01 is using one HP NC364T PCIe Quad Port Gigabit Server Adapter
03 is using one HP NC380T PCIe DP Multifunc Gig Server Adapter and the onboard HP NC371i Multifunction Gigabit Server Adapter

The NC371i & NC380T are Broadcom NICs while the NC364T are Intel

03 Nonpaged from Task Manager: 88,252
01 Nonpaged from Task Manager: 61,192

As you can see, the Intel cards are much better on Nonpaged memory … now lets see if HP will swap these out! 

 


BTW, the latest Exchange 2003 patches I applied are:

  • 887580 When you set a rule to autoforward a double-byte character set e-mail message in Exchange Server 2003, the original DBCS subject line in the header of the message is corrupted
  • 908259 Error message when you run the Eseutil command to determine the amount of free space in a database file in Exchange Server 2003 Service Pack 2 or in Exchange Server 2003 Service Pack 1: “Usage error: Source database has no streaming file”
  • 909068 A meeting request acceptance message from a Lotus Notes user generates an NDR, and the acceptance message is stuck in the local delivery queue in Exchange Server 2003
  • 909989 Error message when you log on to Outlook Web Access on an Exchange Server 2003 front-end server: “401”
  • 910035 When you generate a Mailbox Manager report in Exchange Server 2003 Service Pack 2, the report displays incorrect mailbox size information and “null”
  • 910268 Meetings are unexpectedly moved one hour ahead in the last week of October in Exchange Server 2003
  • 910272 The “Sender ID Filtering” feature does not work correctly in an Exchange Server 2003 SP2 server
  • 912480 An Exchange Server 2003 server that hosts many Outlook client sessions may run out of paged pool memory
  • 914148 Event ID: 1080 occurs every three seconds when you are using Exchange Server 2003 SP2 in a clustered environment
  • 940012 A stub object is left behind in the source database for certain users after a move mailbox operation is complete in Exchange 2003 Service Pack 2
    • This is a great one.  We saw this went we move mailboxes from Exchange 2007 to Exchange 2003 and then back again!

Microsoft Exchange 2007- Error There is a Problem with the Proxy Servers Security Certificate. Outlook Client Can Not Connect to an Exchange 2007 Server

Remember this? http://blogs.flaphead.dns2go.com/archive/2007/11/13/exchange-2007-msexchangeis-9646.aspx

Interesting how HP has hidden this .. I like the final words .. “The real fix is to make sure the network card supports the new featured offered in SP1 and SP2 of Windows Server 2003. Consult the manufacture of the network card for updated drivers. ” BUT THAT IS YOU HP!

Source: http://h10025.www1.hp.com/ewfrf/wc/genericDocument?lc=en&cc=us&docname=c01141389&dlc=en&printable=yes&encodeUrl=true&

ISSUE:
Exchange 2007 Standard. No service pack. Window 2003 Standard SP1

Outlook 2007
Windows XP

Customer had a single user that can not connect to the Exchange 2007 server using Outlook. He could use OWA and connect successfully. He tried using OL 2003 and 2007 with the same error. When trying to use auto discovery after he is prompted for credentials he would get error:

There is a problem with the proxy server’s security certificate. The name on the security certificate is invalid or does not match the name of the target site Outlook is unable to connect to the proxy server (Error code:0)

When he manually configures Outlook and gave credentials he would get error: Cannot open your default email folders. You must connect to Microsoft exchange with the current profile before you can synchronize your folders with you offline folder file.

Troubleshooting:
Customer moved the mailbox to another server. This broke OWA. We then removed the exchange attributes of the mailbox by doing a remove in Exchange 2007 console. After reconnecting the mailbox OWA worked again but we still had the same problem as before. We also notice this error in the event log:
Event Type: Error   
Event Source: MSExchangeIS   
Event Category: General   
Event ID: 9646   
Description:   Closing Mapi session “/o=Organization/ou=Administrative Group/cn=Recipients/cn=Recipient” because it exceeded the maximum of 32 objects of type “session”. 

This would suggest a third party program making too many connections but this was not the case. The problem was with the network card and is described in this article although the errors we got were not documented.

http://msexchangeteam.com/archive/2007/07/18/446400.aspx

With the release of the Scalable Networking Pack that is included with Windows 2003 SP2, we in Exchange support have been seeing some connectivity issues once the new networking features are enabled. These new features are enabled by default and are only used if your network card driver supports them. Some of the new architectural additions that were introduced with the Scalable Networking Pack are TCP Chimney Offload, Receive-side Scaling

SOLUTION:
Resolution:
To Disable TCP Chimney, Navigate to the following registry key and set the value to 0. Note: You have to reboot the server after this registry change.

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters]
“EnableTCPChimney”=dword:00000000

The real fix is to make sure the network card supports the new featured offered in SP1 and SP2 of Windows Server 2003. Consult the manufacture of the network card for updated drivers.

947282: Error message when you prepare an Active Directory forest for Exchange Server 2007: “Schema update failed”

January 25, 2008

947282: Error message when you prepare an Active Directory forest for Exchange Server 2007: “Schema update failed”

You run the ForestPrep operation by using the setup.exe /prepareschema command in a Microsoft Windows Server 2003 domain. You do this to prepare a Windows Server 2003 Active Directory directory service forest for Microsoft Exchange Server 2007.

When you do this, you receive the following error message:
Schema update failed: An attribute with the same link identifier already exists