Microsoft Knowledge Base Wiki

Consider the following scenario. An Office 365 user uses Windows Internet Explorer 8 to connect to Outlook Web App to access email messages or to sign in to a Secure Sockets Layer (SSL) website that requires authentication. When the user opens a new tab or a new window in the website, the user is prompted to reauthenticate.

This issue occurs when Internet Explorer 8 creates a new process for a new tab or a new window. In this case, the SSL session state of the new tab or of the new window isn’t shared, and an additional authentication dialog box appears.

To fix this issue, install the hotfix that’s referenced in the following Microsoft Knowledge Base article:

Prerequisites

To apply this hotfix, you must have Internet Explorer 8 installed on a computer that’s running one of the following operating systems:

• Windows Vista Service Pack 1
• Windows Server 2008
• Windows 7
• Windows Server 2008 R2

Article ID: 2486120 – Last Review: May 17, 2013 – Revision: 8.0

This article describes how to troubleshoot the following Offline Address Book issues in Microsoft Outlook in a Microsoft Office 365 environment:

• Users can’t download the Offline Address Book.
• Synchronization errors occur in the Offline Address Book.
• You receive nondelivery report (NDR) messages when you use the Offline Address Book to send email messages to users.

To troubleshoot these issues, follow these steps. After you follow each step, test to see whether the Offline Address Book issue is resolved. If the issue is resolved, you don’t have to continue to the next step. If the issue isn’t resolved, go to the next step.

Step 1: Make sure that the global address list (GAL) is up to date

Check whether the GAL is up to date. To do this, make sure that you can view any changes in the GAL by using Microsoft Outlook Web App. If the expected changes aren’t present in the GAL, the changes will not be replicated to the Offline Address Book.

Note If you change your on-premises Active Directory schema and the Windows Azure Active Directory Sync Tool still doesn’t synchronize these changes correctly, go to the following Microsoft website for more info about how to troubleshoot this issue:

If the Online Address Book is correct but the Offline Address Book is still incorrect, go to the next step.

Step 2: Manually download the Offline Address Book and then make sure that Cached Exchange Mode is enabled

Manually download the Offline Address Book in Outlook. This may also resolve nondelivery report issues if you’re using an outdated version of the Offline Address Book. For more information about how to manually download the latest copy of the Offline Address Book, click the following article number to view the article in the Microsoft Knowledge Base:

Then, make sure that Outlook is set up to use Cached Exchange Mode. To do this follow these steps:

1. Take one of the following actions:
   • If you’re running Outlook 2007, click Tools, and then click Account Settings.
   • If you’re running Outlook 2010, click File on the Office ribbon, click Account Settings, and then click Account Settings.
2. In the E-mail Settings dialog box, select the Microsoft Exchange account that you want, and then click Change.
3. In the Microsoft Exchange Settings dialog box, make sure that the Use Cached Exchange Mode check box is selected.

Step 3: Check that the Background Intelligence Transfer Service (BITS) service is running

Check that BITS is started on the computer. Outlook uses BITS to connect to the URL that is provided by the Autodiscover service. To determine whether BITS is started, follow these steps:

1. Click Start, click Control Panel, click Administrative Tools, and then click Services.
2. In the list of services, click Background Intelligence Transfer Service, and then make sure that the status of this service is set to Started.
3. If BITS can’t be started, reinstall it. For more information about how to install BITS, click the following article number to view the article in the Microsoft Knowledge Base:
   968929

   (http://support.microsoft.com/kb/968929/
   )

   Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0)

Step 4: Install the latest updates for Office and for Office 365 Desktop

1. Make sure that the latest Microsoft Office service pack is installed.

   Note If you’re using Microsoft Office Outlook 2007, you must, at a minimum, have the 2007 Microsoft Office system Service Pack 1 installed on the computer.

2. Make sure that the latest version of Office 365 Desktop Setup is installed. To install the latest version of Office 365 Desktop Setup, go to the following Microsoft website:

Step 5: Re-create the Outlook profile

If the existing Outlook profile is corrupted, this corruption could be the cause of the issue. Corruption may have occurred if Outlook stopped responding. For more information about how to create and to set up an email profile in Outlook, see the E-mail Setup Help Wizard at the following Microsoft website:

Step 6: Determine whether the Autodiscover service is working, and check access to the Offline Address Book

Note If the Offline Address Book issue wasn’t resolved by using steps 1 through 5, follow this step for validation before you call Support.

Check whether Outlook and the computer can access the Offline Address Book file on the server. This action is typically done by Outlook in the background or when you force a download of the Offline Address Book in Outlook. To do this check, sign in to the Office 365 portal, and then follow these steps:

1. Start Outlook.
2. Hold down the CTRL key, right-click the Outlook icon in the notification area on the right side of the taskbar, and then click Test E-mail AutoConfiguration.
3. Click to clear the Use Guessmart check box, and then click to clear the Secure Guessmart Authentication check box.
4. Click to select the Use AutoDiscover check box.
5. Type the email address and password, and then click Test.
6. On the Results tab, note the path of OAB URL.
7. Click the XML tab, locate the and tags, and then copy the path that is displayed between the tags. Paste the path into the address box in Windows Internet Explorer, add /OAB.xml to the end of the path, and then press Enter.

   The following is an example of what the URL may resemble:

   https://autodiscover.contoso.com/OAB/93179f28-4b4d-4e58-aec1-07bb493be4f4/OAB.xml

8. Note the information that is displayed in the webpage in Internet Explorer. The webpage should contain lots of XML data. The following is an example of the information that should be displayed in Internet Explorer:

   Collapse this imageExpand this image

Article ID: 2429946 – Last Review: May 17, 2013 – Revision: 40.0

Purchase Orders are missing from Analysis Cubes for Dynamics GP.

This is caused by a bug in the PurchaseOrderDetail SSIS package that runs during the data load from Dynamics GP to the Analysis Cubes Data Warehouse database. The bug occurs due to a timestamp comparison on the LastUpdated timestamp and LSTEDTDT/CREATDDT/DOCDATE of the Purchase Order detail line in the Dynamics GP database. The timestamp in the LastUpdated value includes HH:MM:SS whereas the LSTEDTDT/CREATDDT/DOCDATE does not. This difference can cause Purchase Orders to not be included in Analysis Cubes.

Please use the following steps to resolve this issue:

1. Open SQL Server Business Intelligence Development Studio (BIDS).
2. Click File, point to New, and then select Project….
3. Click OK.
4. Right-click SSIS Packages folder in the Solution Explorer pane and then select Add Existing Package.
5. Choose SSIS Package Store for the Package Location.
6. Type in the SQL server name where the Analysis Cubes SSIS packages reside into the Server field.
7. Choose the Authentication type and type in a user if required.
8. Click the ellipses button next to the Package path field.
9. Expand MSDB.
10. Expand your Analysis Cubes SSIS folder.
11. Locate the SSIS package that ends with “PurchaseOrderDetail”. Select it and then click OK.
12. Click OK.
13. Double-click the PurchaseOrderDetail SSIS package in the Solution Explorer pane.
14. Double-click the icon inside the Copy Data from Results to PendingPurchaseOrders Task to open that task.
15. Double-click the icon inside the OLE DB Source entity.
16. Copy the contents of the SQL command text section into a text editor, such as Notepad.
17. In the text editor, use the Replace function to replace ”select @lastdate = DateUpdated from DynamicsGPWarehouse.dbo.LastUpdated where CompanyID = @CompID and TableName = ‘PurchaseOrderDetail’” with “select @lastdate = convert(char(12),DateUpdated,101) from DynamicsGPWarehouse.dbo.LastUpdated where CompanyID = @CompID and TableName = ‘PurchaseOrderDetail’”
18. Go back to BIDS and select all of the text inside the SQL command text section and then press the Delete key to remove the text.
19. Copy the updated text from the text editor into the SQL command text section.
20. Click the Parse Query button. If the query was not parsed successfully, the text was not updated correctly or copied back correctly. Click Cancel on the OLE DB Source Editor window and retry steps 15-20.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2851158 – Last Review: May 17, 2013 – Revision: 1.0

You have a hybrid deployment of on-premises Microsoft Exchange Server and Microsoft Exchange Online in Microsoft Office 365 in which the following conditions are true:

• The on-premises environment consists of both Exchange 2010 and Exchange 2003 servers.
• The Exchange 2003 public folder is set up to use a custom list instead of routing groups for public folder referrals.

In this scenario, on-premises users who have a mailbox on Exchange 2003 or who are using Outlook 2003 can’t view free/busy information of Office 365 users. However, they can view free/busy information of other on-premises users. Additionally, on-premises users who have a mailbox on Exchange 2010 can view free/busy information of Office 365 users.

This issue occurs if the Exchange 2003 server is unable to refer Outlook to the Exchange 2010 public folder server that contains the replica. Although an Exchange 2010 server is specified in the custom list for public folder referrals, the cost calculation fails. When the Exchange 2010 server is selected in the public folder referral custom list from the Exchange 2003 Management System, the public folder database is displayed instead of the server.

Exchange 2003 incorrectly resolves the Exchange 2010 server in the list of public folder referrals to the GUID of the Exchange 2010 public folder database instead of the GUID of the Exchange 2010 public folder server. When Exchange 2003 looks up the database GUID to assign cost, it’s not a valid server path. Therefore, it’s marked with an infinite cost. Because the cost is infinite, it doesn’t refer the client to the Exchange 2010 server.

To resolve this issue, use Active Directory Service Interfaces Editor (ADSI Edit) to modify the msExchfolderAffinityList attribute on the Exchange 2003 server. Specifically, replace the GUID of the Exchange 2010 public folder database with the GUID of the Exchange 2010 public folder server.

To do this, follow these steps on the Exchange 2003 server.

1. Open Exchange Management Shell, and then follow these steps:
   1. Identify the GUID of the Exchange 2010 public folder database. To do this, run the following command:

      get-publicfolderdatabase |fl name, guid

   2. Identify the GUID of the Exchange 2010 public folder server. To do this, run the following command:

      get-exchangeserver |fl name,guid

2. Use ADSI Edit to locate the msExchfolderAffinityList attribute, and then specify the GUID of the Exchange 2010 public folder server.
   1. Open ADSI Edit, and then connect to the Configuration context.
   2. Expand the domain, and then locate the server.

      The path of the server is Configuration/Services/Microsoft Exchange//Administrative groups/Servers/.

   3. Right-click the server, and then click Properties.
   4. Click the Attribute Editor tab, locate and then select the msExchfolderAffinityListattribute.
   5. Click Edit, and then based on the information that you obtained in step 1, replace the GUID of the Exchange 2010 public folder database with the GUID of the Exchange 2010 public folder server.
3. Restart the Microsoft Exchange Information Store service. For more info about how to do this, go to the following Microsoft website:

After you follow this procedure, the Exchange 2010 public folder server name will show in the custom list for public folder referrals. Note that you can modify the other servers in the custom list without affecting the updated GUID in the msExchFolderAffinityList attribute.

The msExchfolderAffinityList attribute is the Active Directory property that resolves the custom list for public folder referrals to server GUIDs. 

For more information, see the following Microsoft resources:

Article ID: 2847591 – Last Review: May 17, 2013 – Revision: 1.0

A current Deployment Administrator may be unable to add a new Deployment Administrator from a trusted domain

When adding a user from another domain as a Deployment Administrator, you are able to find that user in the UserPickerForm, but only after the current signed in Deployment Administrator enters credentials to be able to browse the object in the trusted domain. Once the user is chosen and we retrieve the user properties with an LDAP call, the credentials are lost and reverted back to the CRM domain credentials (local deployment administrator credentials without access to the trusted domain). This causes the LDAP call to not find any users and a null value is returned for the user. This simulates that the user cancelled out of the wizard.

1. Create a two-way trust between the domains in order to add the user as a new Deployment Administrator.

2. Manage the username and password prior to assigning it as a Deployment Administrator. To do this:

a. Go to Manage your Network Passwords on the server and have the current Deployment Administrator add the Domain Controller and credentials from the trusted domain. This allows the credentials to be automatically passed for the LDAP query and not dropped.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2842571 – Last Review: May 17, 2013 – Revision: 3.0

Errors when configuring the Microsoft Dynamics CRM for Outlook client, “There is a problem communicating with the Microsoft Dynamics CRM server. The server might be unavailable. 10″  

Trying to open Credential Manager in the Control Panel will result in the following error.  

Unable to save credentials. To save credentials in the vault, check your computer configuration.

Error Code: 0×80070520

Error Message: A Specified login session does not exist. It may already have been terminated.

A Registry item implemented to the domain had tried to disable the Credential Manager  

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsa

ValueName: DisableCredMan

Value Data: 1

Changing the value Data from 1 to 0, or removing the Value Name entirely will allow the Outlook client to configure correctly as well as allowing the successful opening of the Credential Manager.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2736267 – Last Review: May 17, 2013 – Revision: 2.0

When installing Update Rollups for the Microsoft Dynamics CRM Client for Outlook, you get the below error: 

“The type initializer for ‘Microsoft.Crm.LocatorService’ threw an exception.
Cannot load Counter Name data because an invalid index ” was read from the registry.”

The performance counters have been corrupted on the client machine and they must be rebuilt.

1. Go to Start, type”cmd”.

2. Right-click on cmd.exe and choose ‘Run as administrator’.

3. Type “lodctr /r” and press enter.

You will then get the message ‘Info: Successfully rebuilt performance counter setting from system backup store’.

4. Check if there are providers that are disabled, write “lodctr /q” and press enter

5. You will then get a long list of providers, make sure that the CRM Client is Enabled, see below

If not, write “lodctr /e:CRM Client” and press enter.

6. Install the Microsoft Dynamics CRM for Outlook client Update Rollup

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2832079 – Last Review: May 17, 2013 – Revision: 2.0

An error message may occur when trying to access Microsoft Dynamics CRM 2011 with Claims Based Authentication. “404-File or Directory Not Found”

The following error stack can be found in the event viewer after enabling the AD FS trace log on the AD FS server:

Log Name: AD FS 2.0 Tracing/Debug
Source: AD FS 2.0 Tracing
Date: mm/dd/yyyy 00:00:00 PM
Event ID: 67
Task Category: None
Level: Error
Keywords: ADFSProtocol
User: NETWORK SERVICE
Computer: SERVER
Description:
Failed to process the Web request because the request is not valid. Cannot get protocol message from HTTP query. The following errors occurred when trying to parse incoming HTTP request:

Microsoft.IdentityServer.Protocols.Saml.HttpSamlMessageException: MSIS7015: This request does not contain the expected protocol message or incorrect protocol parameters were found according to the HTTP SAML protocol bindings.
   at Microsoft.IdentityServer.Web.HttpSamlMessageFactory.CreateMessage(HttpContext httpContext)
   at Microsoft.IdentityServer.Web.FederationPassiveContext.EnsureCurrent(HttpContext context)

IIS Applicationhost.config is incomplete. This could be caused by a corrupt or incomplete installation of AD FS. One or all of the following location paths and their settings have been removed:

In order to fix this issue, you must follow the steps below:

1. Stop the IIS service on the AD FS server

2. Stop the AD FS service on the AD FS server

3. Make a copy of the applicationhost.config file and then open the applicationhost.config file located: c:windowssystem32inetsrv.

4. Review this file for any missing file location paths. Update this file to include all file location paths as displayed below.

       
           
           
               
               
                   
                       
                   
                   
                   
                   
                   
               
           
           
           
               
                   
                   
               
           
       
   
   
       
           
           
               
               
                   
                       
                   
                   
                   
                   
                   
               
           
       
   
   
       
           
               
                   
                   
                   
                   
                   
               
           
       
   
   
       
           
           
               
                   
                   
                   
                   
                   
               
           
       
   
   
       
           
           
               
               
                   
                   
                   
                   
                   
               
           
       
   
   
       
           
           
               
                   
                   
                   
                   
                   
               
           
       
   

4. Start the IIS service on the AD FS server

5. Start the AD FS service on the AD FS server

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2847921 – Last Review: May 17, 2013 – Revision: 3.0

In Microsoft Office Live Communications Server 2003 and in Live Communications Server 2005 you may experience the following symptoms:

• A Microsoft Windows Messenger user, “User A,” can successfully transfer files to or send audio or video to another Windows Messenger user, “User B.” (This behavior occurs when no users are behind a network address translation (NAT) device)
• “User A” cannot receive file transfers, audio, or video from “User B” when any one of the users is behind a NAT device.

This issue occurs if one of the Windows Messenger 5.x users or one of the Live Communications Server 2005 users is behind a NAT device. In this case, the user who is behind the NAT device receives a private IP address from that device.

When “User A” starts a session, such as a file transfer session, with “User B,” IP address information is sent between computers from “User A” to “User B.” However, if “User A” is behind a NAT device, this IP address information is a private IP address. When “User B” tries to connect to this private IP address to send a file or to start an audio or video session, “User B” is not successful. Therefore, file transfer traffic or audio and video traffic, only travels in one direction between these two users.

If you have a UPnP-enabled NAT device that is configured between the Windows Messenger 5.x users or the Live Communications Server 2005 users, all the Windows Messenger features work as expected.

Note Transfers of audio, video, and data files is peer-to-peer traffic that occurs between computers that are running Windows Messenger 5.x or Live Communications Server 2005. This traffic does not pass through the Live Communications Server computer.

For more information about Windows Messenger, visit the following Microsoft Web site:

Article ID: 889937 – Last Review: May 17, 2013 – Revision: 5.0

Microsoft has released an update to Microsoft Excel 2002.
This update includes several security updates and other issues that are
corrected in the update.

This article describes how to download and
install the Excel 2002 Update: June 19, 2002.

NOTE: This Public Update is part of the Microsoft Office XP Service
Pack 2 (SP-2), but for your convenience the Public Update also is available
individually, as described in the “More Information” section of this article.
If you already applied Office XP SP-2, you do not have to apply this Public
Update.
For additional information, click the article
number below to view the article in the Microsoft Knowledge Base:

How to Download and Install the Update

Client Update

If you installed Office XP from a CD-ROM, you have two
options:

• Use the Office Product Updates Web site to automatically
  install all of the latest updates that includes all available Service Packs and
  Public Updates.

  -or-

• Install only the Public Update
  by using the steps described later.

Both options require that you have your Office XP CD-ROM
available throughout the installation process.

Office Product Updates

To have the Office Product Updates Web site detect the required
updates that you must install on your computer, visit the following Microsoft
Web site: After detection is complete, you receive a list of recommended
updates for your approval. Click Start Installation to
complete the process.

Install Only Excel 2002 Update

This update requires that Microsoft Office XP Service Pack 1
(SP-1) be installed.
For
additional information about obtaining and installing Microsoft Office XP
Service Pack 1 (SP-1), click the article number below to view the article in
the Microsoft Knowledge Base:

Follow these steps to download and
install the client update:

1. Visit the following Microsoft Web site:

   Click
   here to download the Client Update

   (http://download.microsoft.com/download/Excel2002/Patch/exc1002/W982KMeXP/EN-US/exc1002.exe)

2. Click Download Now. Click Save this program to disk, and then click
   OK.
3. Click Save to save the Exc1002.exe file to the selected folder.
4. In Windows Explorer, double-click Exc1002.exe.
5. If you are prompted to install the update, click Yes.
6. Click Yes to accept the License Agreement.
7. Insert your Office XP CD-ROM when you are prompted to do
   so, and then click OK.
8. When you receive a message that indicates the installation
   was successful, click OK.

NOTE: After you install the public update, you cannot remove
it.

For more information about the Client Patch, click the link below
for the Office Tools on the Web article.

Administrative Update

If you installed Microsoft Excel 2002 from a server location, the
server administrator must update the server location with the administrative
public update and deploy that update to your computer.

If you are the
server administrator, follow these steps to download the administrative update:

1. Visit the following Microsoft Web site:

   Click
   here to download the Administrative Update

   (http://download.microsoft.com/download/Excel2002/Patch/exc1002/W982KMeXP/EN-US/exc1002a.exe)

2. Download the file to your desktop.
3. In Windows Explorer, double-click the Exc1002a.exe file.
4. Click Yes to accept the License Agreement.
5. In the Please type the location where you want to
   place the extracted files box, type
   C:exc1002a, and then click OK.
6. Click Yes when you are prompted to create the folder.
7. Click Start and then click Run. Type the following command in the Open box:

   start msiexec /p pathname of update
   MSP file /a pathname of MSI file SHORTFILENAMES=TRUE /qb /L*v pathname of
   log file

8. To deploy the update to the client workstations, click Start and then click Run. Type the following command in the Open box:

   start msiexec /i path to updated .msi
   file on the administrative image REINSTALL=EXCELFiles REINSTALLMODE=vomus
   /q

For additional
information about how to update your administrative installation and deploy to
client workstations, click the following article number to view the article in
the Microsoft Knowledge Base:

This article contains standard instructions for installing an
administrative public update.
 

How to Determine Whether the Public Update Is Installed

Excel 2002 Update: June 19, 2002 affects the Excel.exe file.
Excel 2002 Update: June 19, 2002 updates the version of Microsoft Excel 2002 to
version 10.0.4109.0. In Excel, click About Microsoft Excel on the Help menu to determine the version that is on your computer.

NOTE: If Excel 2002 Update: June 19, 2002 is already applied to your
computer, you receive the following message when you try to install Excel 2002
Update: June 19, 2002:

This update has already been applied or is included in an update that has already been applied.

Issues Fixed by the Update

The update fixes the following issues that were previously not
documented in the Microsoft Knowledge Base.