KB Articles

Page 1 of 99512345...102030...Last »

Prompted for credentials for proxy server office14client.microsoft.com when launching an Office 2010 application

When you launch an Office 2010 application (such as Excel 2010 or Word 2010), you may be prompted for credentials for a proxy server – office14client.microsoft.com – as shown in this image:

Collapse this imageExpand this image

The prompt may repeat after being dismissed.

This is a known issue with the update described in Knowledge Base article 2956191

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

.

Article ID: 3066062 – Last Review: May 28, 2015 – Revision: 2.0


Applies to
  • Microsoft Office 2010 Service Pack 2
  • Microsoft Excel 2010
  • Microsoft Word 2010
  • Microsoft PowerPoint 2010
  • Microsoft Outlook 2010
  • Microsoft OneNote 2010
  • Microsoft Access 2010

See original article:
Prompted for credentials for proxy server office14client.microsoft.com when launching an Office 2010 application

Members of a dynamic distribution group in an Exchange hybrid deployment don’t receive email messages

You have a hybrid deployment of Exchange Online in Office 365 and on-premises Exchange Server. In this environment, certain members of a dynamic distribution group do not receive email messages. Senders also do not receive a non-delivery report (NDR). However, if a sender manually adds the user to the To field of an email message instead of sending the message to the distribution group, the message is delivered to and received by the user.

Additionally, if you run a command such as the following to return a list of recipients in the dynamic distribution group, the user doesn’t appear in the list:

$list = Get-DynamicDistributionGroup sales@contoso.com
Get-Recipient -RecipientPreviewFilter $list.RecipientFilter
This problem occurs if the dynamic distribution group was set up before the environment became a hybrid deployment and if the dynamic distribution group uses filters to include only mailboxes. Mailboxes that are migrated to Office 365 become mail-enabled users in the on-premises directory.
Use the Set-DynamicDistributionGroup cmdlet to update the filters for the dynamic distribution group to include mail-enabled users. For example, run the following command:
Set-DynamicDistributionGroup -Identity sales@contoso.com -IncludedRecipients "MailboxUsers,MailContacts"
-RecipientFilter ((RecipientType -eq 'UserMailbox' -or 'MailUser' -or 'MailContact'))
For more information, see Set-DynamicDistributionGroup

(https://technet.microsoft.com/en-us/library/bb123796(v=exchg.150).aspx)

.

Still need help? Go to the Office 365 Community

(http://community.office365.com/)

website or the Exchange TechNet Forums

(http://social.technet.microsoft.com/Forums/exchange/en-us/home?category=exchange2010%2Cexchangeserver)

.

Article ID: 3061396 – Last Review: May 27, 2015 – Revision: 2.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2013 Enterprise
  • Microsoft Exchange Server 2013 Standard
o365022013 o365 o365a o365e o365m hybrid KB3061396

Continue reading here:
Members of a dynamic distribution group in an Exchange hybrid deployment don’t receive email messages

Calendar changes aren’t synchronized from an iOS 8.3 device in some time zones

Note: This issue does not apply to all time zones. Known regions include Lebanon, Egypt, and parts of Brazil.

Users of iOS 8.3 devices may experience issues in which changes to calendar items are not synchronized to their mailbox. Therefore, the updates are unavailable in Microsoft Outlook and Outlook Web App (OWA). These issues require changes to the iOS implementation of the Microsoft Exchange ActiveSync protocol.

The following exception is found during analysis of the Exchange ActiveSync mailbox log for this device:

SyncCommand_ConvertRequestsAndApply_Add_Exception :
Microsoft.Exchange.AirSync.SchemaConverter.Common.ConversionException: ExTimeZoneFromRegTimeZoneInfo failed: Specified argument was out of the range of valid values.
Parameter name: Hour
   at Microsoft.Exchange.AirSync.SchemaConverter.Common.TimeZoneConverter.GetExTimeZone(Byte[] timeZoneInformation)
   at Microsoft.Exchange.AirSync.SchemaConverter.XSO.XsoTimeZoneProperty.InternalCopyFromModified(IProperty srcProperty)
   at Microsoft.Exchange.AirSync.SchemaConverter.XSO.XsoDataObject.CopyFrom(IProperty srcRootProperty)
   at Microsoft.Exchange.AirSync.SyncCollection.ConvertClientToServerObjectAndSendIfNeeded(SyncCommandItem syncCommandItem, Boolean sendEnabled)
   at Microsoft.Exchange.AirSync.SyncCollection.ConvertClientToServerObjectAndSave(SyncCommandItem syncCommandItem, UInt32& maxWindowSize, Boolean& mergeToClient)
   at Microsoft.Exchange.AirSync.SyncCommand.ConvertRequestsAndApply(SyncCollection collection)

This issue occurs because the TimeZone value in the sync request contains an invalid value.

Resolution

Apple is aware of this problem, and customers who experience any of the issues that are described in the “Symptoms” section should contact Apple for help.

Third-party information disclaimer

Collapse this imageExpand this image

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Collapse this imageExpand this image

Article ID: 3064000 – Last Review: May 27, 2015 – Revision: 4.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2013 Enterprise
kbsurveynew kbmobility KB3064000

Read More:
Calendar changes aren’t synchronized from an iOS 8.3 device in some time zones

Office 365 users can reserve a meeting room even though it’s already reserved for another meeting

oneMscomBlade,oneMsomNav,oneMscomFooter,

Continued here:
Office 365 users can reserve a meeting room even though it’s already reserved for another meeting

FIX: MQSeries adapter for a receive port doesn’t maintain message order in BizTalk Server 2010

In Microsoft BizTalk Server 2010, you use the MQSeries adapter to receive and process a large volume of messages. However, you notice that the messages are not kept in the correct order, even though the Order Delivery option is enabled in the receive location. In this situation, no errors are logged in either the System log or the Application log on the BizTalk server.

Cumulative update information

BizTalk Server 2010

This issue was first fixed in the following cumulative update of BizTalk Server 2010:
Note MQSAgent.dll must be updated on the IBM WebSphere MQ server to Cumulative Update 7 (CU7). To do this, make sure that you use the same CU7 setup package. You may experience performance issues if you run mismatched versions. 

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

Article ID: 2951982 – Last Review: May 27, 2015 – Revision: 1.0


Applies to
  • Microsoft BizTalk Server Branch 2010
  • Microsoft BizTalk Server Developer 2010
  • Microsoft BizTalk Server Enterprise 2010
  • Microsoft BizTalk Server Standard 2010
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2951982

Visit site:
FIX: MQSeries adapter for a receive port doesn’t maintain message order in BizTalk Server 2010

Prompted for credentials for proxy server office14client.microsoft.com when launching and Office 2010 application

When you launch an Office 2010 application (such as Excel 2010 or Word 2010), you may be prompted for credentials for a proxy server – office14client.microsoft.com – as shown in this image:

Collapse this imageExpand this image

The prompt may repeat after being dismissed.

This is a known issue with the update described in Knowledge Base article 2956191

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

.

Microsoft is working to resolve this issue. In the meantime, if you want to work around the problem, remove update KB2956191.

Article ID: 3066062 – Last Review: May 26, 2015 – Revision: 1.0


Applies to
  • Microsoft Office 2010 Service Pack 2
  • Microsoft Excel 2010
  • Microsoft Word 2010
  • Microsoft PowerPoint 2010
  • Microsoft Outlook 2010
  • Microsoft OneNote 2010
  • Microsoft Access 2010

View article:
Prompted for credentials for proxy server office14client.microsoft.com when launching and Office 2010 application

“Remote server returned an Error 404” when you move a mailbox from on-premises Exchange Server to Exchange Online

When you try to move a mailbox from the on-premises Exchange Server environment to Exchange Online in Office 365, you receive an error message that resembles the following:
Error(s): the call to https://mail..com/ews/mrsproxy.svc failed because no service was listening on the specified endpoint

error details:
there was no endpoint listening at https://mail..com/ews/mrsproxy.svc that could accept the message this is often cause by an incorrect address of soap action. The remote server returned an error 404 not found.

However, you may still be able to move other mailboxes successfully. 

This problem may occur if the ExchangeGUID property of the Exchange Online MailUser object does not match the ExchangeGUID property of the on-premises mailbox. To successfully move a mailbox, the value of the ExchangeGUID property in the Exchange Online mailbox and in the associated on-premises remote mailbox must match.
Set the ExchangeGUID property of the associated on-premises remote mailbox before you move the mailbox to the on-premises organization. To do this, follow these steps:
  1. Check whether the ExchangeGUID property of the on-premises remote mailbox is set. To do this, open the Exchange Management Shell on the on-premises server, and then run the following command:
    Get-RemoteMailbox  | Format-List ExchangeGUID

    Note If the ExchangeGUID property returns all zeros, the value isn’t stamped on the on-premises remote mailbox.

  2. Connect to Exchange Online by using remote PowerShell. For more info, see Connect to Exchange Online using Remote PowerShell

    (http://technet.microsoft.com/en-us/library/jj984289(v=exchg.150).aspx)

    .

  3. Retrieve the value of ExchangeGUID property of the mailbox that you want to move. To do this, run the following command:
    Get-Mailbox  | Format-List ExchangeGUID
  4. Set the value of the ExchangeGUID property on the on-premises remote mailbox to the value that you retrieved in step 3. To do this, run the following command:
    Set-RemoteMailbox  -ExchangeGUID 
  5. Force directory synchronization. For more info, see the “Force directory synchronization” section of Synchronize your directories

    (http://technet.microsoft.com/en-us/library/jj151771.aspx#BKMK_SynchronizeDirectories)

    .

Still need help? Go to the Office 365 Community

(http://community.office365.com/)

website or the Exchange TechNet Forums

(http://social.technet.microsoft.com/Forums/exchange/en-us/home?category=exchange2010%2Cexchangeserver)

.

Article ID: 3065754 – Last Review: May 26, 2015 – Revision: 2.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2013 Enterprise
  • Microsoft Exchange Server 2013 Standard
o365e o365m o365022013 o365 o365a hybrid KB3065754

Continued here:
“Remote server returned an Error 404” when you move a mailbox from on-premises Exchange Server to Exchange Online

Outlook displays incorrect search results of the GAL in Exchange Server

When you use Microsoft Office Outlook 2007, Microsoft Outlook 2010, or Microsoft Outlook 2013 to search for users in a global address list (GAL) in Microsoft Exchange Server 2007, Microsoft Exchange Server 2010 or Microsoft Exchange Server 2013, the following issues may occur:
  • When you select the option that sorts the search results by using the Display Name field under Advanced Find of Outlook Address Book, the results are not sorted by using the Display Name column.
  • When you search for objects that have a user name or a distribution list name, the search operation does not return the correct object if the Name only option is enabled.

Note When the More columns option is enabled, the search operations return the correct results.

This issue occurs because Active Directory Domain Services (AD DS) uses furigana for indexing in Windows Server 2008.

When phonetic display names are set to user or distribution group objects in AD DS in Windows Server 2008, an index of the phonetic display name is generated on the global catalog server. The index is used for searching or arranging a search result of a GAL in the Japanese version of Outlook. When the objects in GAL do not have a phonetic display name, the display name is used for indexing. If the name only option is selected, the search scope is restricted to objects that have phonetic display names. Therefore, you receive incorrect results when you search an address book in Office Outlook if objects do not have phonetic display names.

For example, you search for a display name that differs from its phonetic display name in a GAL in which some objects do not have phonetic display names. In this scenario, the object that has the matching display name in the Display name column is not returned in the search results, and only the objects that have phonetic display names are returned.

If the phonetic display name of all the users and distribution lists on the GAL is not set, a search that uses the Name only option returns correct results. Correct results are returned because the index for phonetic display names includes only display names.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756

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

How to back up and restore the registry in Windows

To work around this issue, use one of the following methods:

To have us fix this problem by using method 1 for you, go to the “Fix it for me” section. If you prefer to fix this problem yourself, go to the “Let me fix it myself” section.

Fix it for me

To fix this problem automatically, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard.

Collapse this imageExpand this image

Fix this problem

(http://go.microsoft.com/?linkid=9775586)


Microsoft Fix it 50705

Collapse this imageExpand this image

Notes

  • This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
  • If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Then, go to the “Did this fix the problem?” section.

Let me fix it myself

  • Method 1
    1. Click Start

      Collapse this imageExpand this image

      , click Run, type Regedit, and then press OK.

    2. Locate and then click the DisableGALPhonetic registry entry in one of the following registry subkeys:
      Note If the DisableGALPhonetic registry entry does not exist, you must create this entry. To do this, follow these steps:
      1. On the Edit menu, click New, and then click DWORD(32-bit) Value.
      2. Type DisableGALPhonetic, and then press ENTER.
    3. Right-click DisableGALPhonetic, click Modify, type 1 in the Value data box, and then click OK.
    4. Exit Registry Editor, and then restart the computer to apply the change.
  • Method 2
    Use the More columns option instead of the Name only option when you search the GAL for objects that have furigana and for objects that do not have furigana.


Did this fix the problem?

  • Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support

    (http://support.microsoft.com/contactus)

    .

  • We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the “Fix it for me

    (http://blogs.technet.com/fixit4me/)

    ” blog or send us an email

    (mailto:fixit4me@microsoft.com?Subject=KB)

    .

Outlook clients connect to Client Access Server (CAS) in the Exchange Server 2010 organization. However, CAS does not support the index of furigana when you search or view the GAL in Outlook in Exchange Server 2010 RTM. When you use the not-cached mode to search the address list in Office Outlook, the matching users are not returned in the search result. However, the bottom objects of the address list are selected. To resolve this issue, install Exchange Server 2010 Service Pack 1 (SP1).

For more information about Exchange Server 2010 SP1, visit the following Microsoft website:

Exchange Server 2010 SP1

(http://www.microsoft.com/downloads/details.aspx?displaylang=ja&FamilyID=50b32685-4356-49cc-8b37-d9c9d4ea3f5b)

Article ID: 2497077 – Last Review: May 26, 2015 – Revision: 6.0


Applies to
  • Microsoft Exchange Server 2013 Enterprise
  • Microsoft Exchange Server 2013 Standard
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2007 Standard Edition
  • Microsoft Office Outlook 2007
  • Microsoft Outlook 2010
  • Microsoft Outlook 2013
kbexpertiseinter kbtshoot kbprb kbfixme kbmsifixme KB2497077

Continue reading here:
Outlook displays incorrect search results of the GAL in Exchange Server

Office 365 users can’t connect to Exchange Online because of incorrect service settings

Office 365 users in your organization who connect to Exchange Online by using incorrect hardcoded service settings (or IP addresses) will be unable to connect to the service after these outdated service settings are discontinued on June 26, 2015. 

The services for which users may be using incorrect settings include the following:

  • Autodiscover: A feature that’s used to automatically discover server names for connectivity
  • Exchange ActiveSync (EAS):A protocol that’s used by email client applications on mobile devices
  • POP3 and IMAP4: Protocols that are used by email client applications on desktop and mobile devices
  • SMTP: Protocol that’s used for sending email messages

If users continue to use the outdated, hardcoded service settings, they will be unable to connect to the service after June 26, 2015. Use the information that’s provided in this article to make sure that these settings are set correctly for users in your organization. 

The following table lists the features, protocols, and expected server settings that must be set and provides links to the articles that contain instructions for how to configure these settings. 

Collapse this tableExpand this table

Article ID: 3067822 – Last Review: May 22, 2015 – Revision: 3.0


Applies to
  • Microsoft Exchange Online
o365e o365m o365022013 o365 o365a KB3067822

Read More:
Office 365 users can’t connect to Exchange Online because of incorrect service settings

Calendar changes aren’t synchronized from an iOS 8.3 device in Exchange environment

Users of iOS 8.3 devices may experience issues in which changes to calendar items are not synchronized to their mailbox. Therefore, the updates are unavailable in Microsoft Outlook and Outlook Web App (OWA). These issues require changes to the iOS implementation of the Microsoft Exchange ActiveSync protocol.

The following exception is found during analysis of the Exchange ActiveSync mailbox log for this device:

SyncCommand_ConvertRequestsAndApply_Add_Exception :
Microsoft.Exchange.AirSync.SchemaConverter.Common.ConversionException: ExTimeZoneFromRegTimeZoneInfo failed: Specified argument was out of the range of valid values.
Parameter name: Hour
   at Microsoft.Exchange.AirSync.SchemaConverter.Common.TimeZoneConverter.GetExTimeZone(Byte[] timeZoneInformation)
   at Microsoft.Exchange.AirSync.SchemaConverter.XSO.XsoTimeZoneProperty.InternalCopyFromModified(IProperty srcProperty)
   at Microsoft.Exchange.AirSync.SchemaConverter.XSO.XsoDataObject.CopyFrom(IProperty srcRootProperty)
   at Microsoft.Exchange.AirSync.SyncCollection.ConvertClientToServerObjectAndSendIfNeeded(SyncCommandItem syncCommandItem, Boolean sendEnabled)
   at Microsoft.Exchange.AirSync.SyncCollection.ConvertClientToServerObjectAndSave(SyncCommandItem syncCommandItem, UInt32& maxWindowSize, Boolean& mergeToClient)
   at Microsoft.Exchange.AirSync.SyncCommand.ConvertRequestsAndApply(SyncCollection collection)

This issue occurs because the TimeZone value in the sync request contains an invalid value.

Resolution

Apple is aware of this problem, and customers who experience any of the issues that are described in the “Symptoms” section should contact Apple for help.

Third-party information disclaimer

Collapse this imageExpand this image

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Collapse this imageExpand this image

Article ID: 3064000 – Last Review: May 22, 2015 – Revision: 2.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2013 Enterprise
kbsurveynew kbmobility KB3064000

Read the article:
Calendar changes aren’t synchronized from an iOS 8.3 device in Exchange environment

Page 1 of 99512345...102030...Last »

Recent Comments

    Archives

    Categories