KB Articles

Page 1 of 97212345...102030...Last »

The Lync window stays on top when you click another application window

A Microsoft Lync window stays on top of other application windows after you click another window to try to make it active. This problem occurs when two or more of the following conditions are true:
  • Lync 2010 is installed.
  • Lync 2013 64-bit is installed.
  • A third-party application that uses Lync is installed.
To work around this problem, use one of the following methods:
  • If you have both the Lync 2010 client and the Lync 2013 64-bit client installed on the same computer, remove the Lync 2010 client.
  • If you have a third-party application installed that uses the Lync client, remove the third-party application, and then verify that the problem is resolved. If the problem is resolved, contact the vendor of the third-party application for a resolution.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

Article ID: 3038350 – Last Review: March 4, 2015 – Revision: 3.0


Applies to
  • Microsoft Lync 2013
  • Microsoft Lync 2010
kbsurveynew kbexpertiseinter kbprb KB3038350

Read More:
The Lync window stays on top when you click another application window

Custom messages in NDRs are replaced by default system messages in Office 365

You set up a transport rule in Office 365 to return a non-delivery report (NDR) that displays a custom message. However, the custom message in the NDR is overwritten by the standard NDR message. This occurs in either of the following scenarios:
  • The sender and recipient belong to different Office 365 organizations.
  • The sender has an Office 365 mailbox and the recipient belongs to an external Exchange Server organization.
Use the Set-TransportConfig cmdlet to set the DSNConversionMode parameter to the value of PreserveDSNBody. This transport configuration setting must be changed at the organization that receives the NDR.

To do this, follow these steps:

  1. Connect to Exchange Online by using remote PowerShell. For more info about how to do this, see Connect to Exchange Online using remote PowerShell

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

    .

  2. Run the following command:
    Set-TransportConfig -DSNConversionMode PreserveDSNBody
The DSNConversionMode parameter determines the format to use for delivery status notifications (DSNs). The parameter can be set to one of the following values:
  • UseExchangeDSNs
    Exchange converts the DSNs to the Exchange 2013 DSN format, which is the same as the Exchange 2010 DSN format. However, any customized text or attachments that were associated with the original DSN are overwritten if the DSN is delivered from another Office 365 organization or from an external organization.
  • PreserveDNSBody
    Exchange converts the DSNs to the Exchange 2013 DSN format, and the text in the body of the DSN message is retained.
  • DoNotConvert
    Exchange does not modify the DSN message. Instead, Exchange delivers the message as a standard message.

Article ID: 3044155 – Last Review: March 3, 2015 – Revision: 1.0


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

Visit site:
Custom messages in NDRs are replaced by default system messages in Office 365

Google Chrome showModalDialog API deprecation requires update for Microsoft Dynamics CRM

Google Chrome has removed support for the showModalDialog API with Chrome 37 and above. Microsoft Dynamics CRM will require an update to continue using Google Chrome. More information on the deprecation of this API can be found here:

Disabling showModalDialog

(http://blog.chromium.org/2014/07/disabling-showmodaldialog.html)

There is a workaround available to continue using this API, which expires at the end of April 2015. This information is also documented in the link above. Once this API and workaround have been fully deprecated, Microsoft Dynamics CRM will require an update for users to continue using Google Chrome.
  • Microsoft Dynamics CRM 2011, a Critical On-Demand fix will be available for Update Rollup 18 through support.
  • Microsoft Dynamics CRM 2013, a Critical On-Demand fix will be available for Update Rollup 3 through support.
  • Microsoft Dynamics CRM 2013 Service Pack 1, the fix will be included in the Update Rollup 3 for Service Pack 1 release.
  • Microsoft Dynamics CRM 2015, the fix will be included in the Update Rollup 1 release. 

The release of these updates is scheduled for April 2015.

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: 3045631 – Last Review: March 3, 2015 – Revision: 1.0


Applies to
  • Microsoft Dynamics CRM 2011
  • Microsoft Dynamics CRM 2013
  • Microsoft Dynamics CRM 2015
kbmbsmigrate kbsurveynew KB3045631

Continued here:
Google Chrome showModalDialog API deprecation requires update for Microsoft Dynamics CRM

Revised February 2015 anti-malware platform update Endpoint Protection clients

This article describes an anti-malware platform update package for clients of the following Endpoint Protection platforms:
  • Microsoft System Center 2012 R2 Configuration Manager Endpoint Protection
  • System Center 2012 Endpoint Protection Service Pack 1 (SP1)
  • Microsoft Forefront Endpoint Protection 2010

This package updates System Center 2012 Endpoint Protection (SCEP) client services, drivers, and UI components, and it replaces the following update:

3036437

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

February 2015 anti-malware platform update for Endpoint Protection clients

Update information

In addition to the changes that were made in update 3036437, this revision also contains the following updates:

  • Removes potential incompatibilities between System Center Endpoint Protection and Windows Defender when both are installed on a Windows 8.1-based computer. This resolves an issue that was previously discovered and referenced in the following TechNet blog post:
  • Prompts the user to restart the computer if affected files are in use during the installation process.

Microsoft regularly releases anti-malware platform updates to guarantee consistency in protection, performance, robustness, and usability in a malware landscape that is constantly changing. This update package is dated February 2015.

How to obtain this update

This update is available from Microsoft Update

(http://update.microsoft.com/microsoftupdate/v6/vistadefault.aspx?ln=en-US)

.

Anti-malware platform updates for System Center 2012 R2 clients, System Center 2012 clients, and Forefront Endpoint Protection 2010 clients are available from Microsoft Update.

Update replacement information

This update replaces update 3036437

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

, the February 2015 anti-malware platform update for Endpoint Protection clients.

Version information

This update brings the anti-malware client version to 4.7.209.0. To find the version information, click About on the Help menu of the Endpoint Protection client UI.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

System Center 2012 and System Center 2012 R2 Endpoint Protection

Collapse this tableExpand this table

File name File version File size Date Time
Scepinstall.exe 4.7.209.0 28,265,576 21-Feb-2015 15:22

Forefront Endpoint Protection 2010

Collapse this tableExpand this table

File name File version File size Date Time
Fepinstall.exe 4.7.209.0 28,489,320 21-Feb-2015 15:22

Article ID: 3041687 – Last Review: March 2, 2015 – Revision: 3.0


Applies to
  • Microsoft System Center 2012 R2 Configuration Manager
  • Microsoft Forefront Endpoint Protection 2010

View article:
Revised February 2015 anti-malware platform update Endpoint Protection clients

How to retrieve archived conversations from Lync Online in Office 365 dedicated

Microsoft Lync Online archiving retrieval is a procedure that retrieves Microsoft Lync and Microsoft Office Communications Server (OCS) conversations from the content archiving server.

Assumption

The requesters must be authorized by using the Authorized Requestors process.

Note If you are unsure whether the requester is a member of the Authorized Requestors list, contact your Service Delivery Manager (SDM).

Procedure

  1. Microsoft Online Services Support (MOSSUP or MOSSFED) receives an escalation that requests retrieval of Lync or OCS archiving content.
  2. MOSSUP or MOSSFED verifies that the requester is authorized according to the Authorized Requesters list.

    Note If the requester is not authorized, the SR is rejected.

  3. MOSSUP or MOSSFED escalates the request to the Lync Operations team as a Severity C case, unless otherwise requested.
  4. If a higher severity is requested, provide the business justification for a higher severity.
  5. The Lync Operations team pulls the requested information if the information is available. Then, the Lync Operations team resolves the escalation back to support.
  6. The Lync Operations team communicates the Data Transfer and Management (DTM) information to the Authorized Requestor.
  7. After the customer confirms the receipt of the information, the SR is closed.

Article ID: 2649373 – Last Review: February 27, 2015 – Revision: 11.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal
  • Microsoft Lync Online

Original post:
How to retrieve archived conversations from Lync Online in Office 365 dedicated

Outlook connection issues with Exchange mailboxes because of the RPC encryption requirement

When you start Microsoft Office Outlook by using a profile that includes a mailbox on a server that is running Microsoft Exchange Server 2010 or Microsoft Exchange Server 2013, you may receive the following error messages:

Cannot start Microsoft Office Outlook. Unable to open the Outlook window. The set of folders could not be opened.

Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.

The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action.

Unable to open your default e-mail folders. The information store could not be opened.

Outlook could not log on. Check to make sure you are connected to the network and are using the proper server and mailbox name. The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action.

Also, if you are using a cached mode profile, Outlook does not display an error. Instead, you may experience the following symptoms:

  • Outlook starts in the Disconnected state (the lower-right corner of the Outlook windows displays “Disconnected”, the screen shot for the state is shown below).

    Collapse this imageExpand this image

  • Outlook starts and you can send and receive email messages. However, you only see two connections within the “Microsoft Exchange Connection Status” and you may see the Type Directory displayed as Disconnected/Connecting.

    Collapse this imageExpand this image

When you try to create a new Outlook profile for a mailbox on a server that is running Exchange 2010 or Microsoft Exchange Server 2013, you may receive the following error messages: 

The action could not be completed. The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action.

The name could not be resolved. The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action.

Outlook could not log on. Check to make sure you are connected to the network and are using the proper server and mailbox name. The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action.

The name could not be resolved. The action could not be completed.

Your Server or Mailbox names could not be resolved.

This problem can occur if you are using Microsoft Office Outlook and you disable the Encrypt data between Microsoft Office Outlook and Microsoft Exchange profile setting. The default configuration for Exchange Server 2013 requires RPC Encryption from the Outlook Client, this prevents the client from being able to connect.

Note The default Exchange Server 2010 Release to Manufacturing (RTM) configuration requires RPC encryption. This behavior is a change from Microsoft Exchange Server 2010 Service Pack 1 where the RPC encryption requirement is disabled by default. However, any CAS servers deployed prior to Service Pack 1, or upgraded to Service Pack 1, will retain the existing RPC encryption requirement setting which could still prevent the client from being able to connect.

To resolve this problem, use one of the following methods.

Note If you are using one of the automated methods (Group Policy or a .prf file), make sure that you fully test the method before you deploy it on a large scale.

Method 1: Disable the encryption requirement on all CAS servers

Collapse this imageExpand this image

Microsoft strongly recommends you leave the encryption requirement enabled on your server, and to utilize one of the other methods listed in this article. Method 1 is only provided in this article for situations where you cannot immediately deploy the necessary RPC encryption settings on your Outlook clients. If you utilize Method 1 to allow Outlook clients to connect without RPC encryption, please re-enable the RPC encryption requirement on your CAS servers as quickly as possible to maintain the highest level of client-to-server communication.

To disable the required encryption between Outlook and Exchange, follow these steps:

  1. On the server that is running Exchange 2010, run the following command in the Exchange Management Shell:
    Set-RpcClientAccess –Server Exchange_server_name –EncryptionRequired $False

    Note The Exchange_server_name placeholder represents the name of an Exchange Server 2010-based server that has the Client Access Server role.

    You must run this cmdlet for all Exchange 2010 Client Access servers.

  2. Rerun this command for each Exchange 2010-based server that has the Client Access Server role. The command also needs to be run on each Mailbox Server role that contains a Public Folder Store. Public Folder connections from the MAPI client go directly to the RPC Client Access Service on the Mailbox server.
  3. After your Outlook clients are updated with the setting to enable encrypted RPC communication with Exchange (see steps provided below), you can re-enable the RPC encryption requirement on your Exchange 2010 servers that have the Client Access Server role.

    To re-enable the RPC encryption requirement on your Exchange 2010-based servers that have the Client Access Server role, run the following command in the Exchange Management Shell:

    Set-RpcClientAccess –Server Exchange_server_name –EncryptionRequired $True

    Note The Exchange_server_name placeholder represents the name of an Exchange 2010-based server that has the Client Access Server role.

    This cmdlet must be run for all Exchange 2010 Client Access servers.

Collapse this imageExpand this image

Method 2: Manually update or create your Outlook profile with RPC encryption

Collapse this imageExpand this image

Outlook 2007

Collapse this imageExpand this image

To manually update an existing Outlook 2007 profile so that it uses RPC encryption with Exchange 2010, follow these steps:

  1. In Control Panel, open the Mail item.
  2. Click Show Profiles.
  3. Select your profile, and then click Properties.
  4. Click E-mail Accounts.
  5. Select the Microsoft Exchange Server account, and then click Change.
  6. In the dialog box that contains your mailbox server and user name, click More Settings.
  7. In the Microsoft Exchange dialog box, click the Security tab.
  8. Click to select the Encrypt data between Microsoft Office Outlook and Microsoft Exchange check box, and then click OK (A screen shot for this step can be seen here).

    Collapse this imageExpand this image

  9. Click Next,and then click Finish.
  10. Click Close, click Close, and then click OK.

Collapse this imageExpand this image

Outlook 2010

Collapse this imageExpand this image

To manually update an existing Outlook 2010 profile so that it uses RPC encryption with Exchange 2010, follow these steps:

  1. In Control Panel, open the User Accounts item.
  2. In User Accounts, open the Mail (32 bit) item.
  3. Click Show Profiles.
  4. Select your profile, and then click Properties.
  5. Click E-mail Accounts.
  6. Select the Microsoft Exchange Server account, and then click Change.
  7. In the dialog box that contains your mailbox server and user name, click More Settings.
  8. In the Microsoft Exchange dialog box, click the Security tab.
  9. Click to select the Encrypt data between Microsoft Office Outlook and Microsoft Exchange check box, and then click OK (A screen shot for this step can be seen here).

    Collapse this imageExpand this image

  10. Click Next, and then click Finish.
  11. Click Close, click Close again, and then click OK.

Collapse this imageExpand this image

Outlook 2013

Collapse this imageExpand this image

To manually update an existing Outlook 2013 profile so that it uses RPC encryption with Exchange 2010, follow these steps:

  1. In Control Panel, open the User Accounts item.
  2. In User Accounts, open the Mail (32 bit) item.
  3. Click Show Profiles.
  4. Select your profile, and then click Properties.
  5. Click E-mail Accounts.
  6. Select the Microsoft Exchange Server account, and then click Change.
  7. In the dialog box that contains your mailbox server and user name, click More Settings.
  8. In the Microsoft Exchange dialog box, click the Security tab.
  9. Click to select the Encrypt data between Microsoft Office Outlook and Microsoft Exchange check box, and then click OK (A screen shot for this step can be seen here).

    Collapse this imageExpand this image

  10. Click Next, and then click Finish.
  11. Click Close, click Close again, and then click OK.

Collapse this imageExpand this image

Collapse this imageExpand this image

Method 3: Deploy a Group Policy setting to update existing Outlook profiles with RPC encryption

Collapse this imageExpand this image

From a client perspective, deploying the Outlook-Exchange encryption setting is probably the simplest solution for organizations that have many Outlook clients. This solution involves a single change on a server (domain controller), and your clients are automatically updated after the policy is downloaded to the client.

Outlook 2007

Collapse this imageExpand this image

By default, the RPC encryption setting is enabled in Outlook 2007. Therefore, you should only deploy this setting by using Group Policy for either of the following reasons:

  • Your original Outlook 2007 deployment disabled RPC encryption between Outlook and Exchange.
  • You want to prevent users from modifying the RPC encryption setting in their Outlook profile.

The default Group Policy template for Outlook 2007 contains the Group Policy setting that controls Outlook-Exchange RPC encryption. Therefore, the process for updating Outlook 2007 profiles requires fewer steps than the process for Outlook 2003.

To update existing Outlook 2007 profiles by using Group Policy, follow these steps:

  1. Download the latest version of the Outlk12.adm Group Policy template

    (http://www.microsoft.com/downloads/details.aspx?FamilyId=92D8519A-E143-4AEE-8F7A-E4BBAEBA13E7&displaylang=en)

    .

  2. Add the .adm file to your domain controller.

    Note The steps to add the .adm file to a domain controller vary according to the version of Windows that you are running. Also, because you may be applying the policy to an organizational unit and not to the entire domain, the steps may also vary in this aspect of applying a policy. Therefore, check your Windows documentation for details.

    Continue with Step 3 after you add the .adm template to the Group Policy Editor.

  3. Under User Configuration, expand Classic Administrative Templates (ADM) to locate the policy node for your template. By using the Outlk12.adm template, this node will be named “Microsoft Office Outlook 2007.”
  4. Under Tools | Account Settings, select the Exchange node (A screen shot for this step can be seen here).

    Collapse this imageExpand this image

  5. Double-click the Enable RPC encryption policy setting.
  6. On the Setting tab, click Enabled.
  7. Click OK.

At this point, the policy setting will be applied on your Outlook client workstations when the Group Policy update is replicated. To test this change, run the following command at a command prompt on a client: After you run this command, start Registry Editor on the workstation to make sure that the following registry data exists on the client:

Key: HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice12.0OutlookRPC
DWORD: EnableRPCEncryption
Value: 1

If you see this registry data in the registry, the Group Policy setting has been applied to this client. Start Outlook to verify that the change resolves the problem.

Collapse this imageExpand this image

Outlook 2010

Collapse this imageExpand this image

By default, the RPC encryption setting is enabled in Outlook 2010. Therefore, you should only deploy this setting by using Group Policy for either of the following reasons:

  • Your original Outlook 2010 deployment disabled RPC encryption between Outlook and Exchange.
  • You want to prevent users from changing the RPC encryption setting in their Outlook profile.

The default Group Policy template for Outlook 2010 contains the Group Policy setting that controls Outlook-Exchange RPC encryption. To update existing Outlook 2010 profiles by using Group Policy, follow these steps:

  1. Download the latest version of the Outlk14.adm Group Policy template

    (http://www.microsoft.com/en-us/download/details.aspx?id=18968)

    .

  2. Add the .adm file to your domain controller.

    Note The steps to add the .adm file to a domain controller vary according to the version of Windows that you are running. In addition, because you may be applying the policy to an organizational unit and not to the domain, the steps may also vary for this aspect of applying a policy. Therefore, check your Windows documentation for detailed information.

    Go to step 3 after you add the .adm template to the Local Group Policy Editor.

  3. Under User Configuration, expand Administrative Templates (ADM) to locate the policy node for your template. By using the Outlk14.adm template, this node will be named Microsoft Outlook 2010.
  4. Under Account Settings, select the Exchange node (A screen shot for this step can be seen here).

    Collapse this imageExpand this image

  5. Double-click the Enable RPC encryption policy setting.
  6. On the Setting tab, click Enabled.
  7. Click OK.

At this point, the policy setting will be applied on your Outlook client workstations when the Group Policy update is replicated. To test this change, run the following command: After you run this command, start Registry Editor on the workstation to make sure that the following registry data exists on the client:

Key: HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice14.0OutlookRPC
DWORD: EnableRPCEncryption
Value: 1

If you see this registry data in the registry, the Group Policy setting is applied to this client. Start Outlook to verify that the change resolves the problem.

Collapse this imageExpand this image

Outlook 2013

Collapse this imageExpand this image

By default, the RPC encryption setting is enabled in Outlook 2013. Therefore, you should only deploy this setting by using Group Policy for either of the following reasons:

  • Your original Outlook 2013 deployment disabled RPC encryption between Outlook and Exchange.
  • You want to prevent users from changing the RPC encryption setting in their Outlook profile.

The default Group Policy template for Outlook 2013 contains the Group Policy setting that controls Outlook-Exchange RPC encryption. To update existing Outlook 2013 profiles by using Group Policy, follow these steps:

  1. Download the Office 2013 ADM templates

    (http://www.microsoft.com/en-us/download/details.aspx?id=35554)

    .

  2. Add the .admx and .adml files to your domain controller. This adds the Outlook ADM template to make it available in the Local Group Policy Editor.

    Note The steps to add the .admx and adml files to a domain controller vary according to the version of Windows that you are running. In addition, because you may be applying the policy to an organizational unit and not to the domain, the steps may also vary for this aspect of policy application. Therefore, check your Windows documentation

    (https://technet.microsoft.com/en-us/library/cc179081)

    for detailed information. (This article is labeled for Office 2010. However, it also applies to Office 2013.)

  3. Start the Local Group Policy Editor.
  4. Under User Configuration, expand Administrative Templates (ADM) to locate the policy node for your template. When you use the Outlk15.admx template, this node will be named Microsoft Outlook 2013.
  5. Under Account Settings, select the Exchange node (A screen shot for this step can be seen here).

    Collapse this imageExpand this image

  6. Double-click the Enable RPC encryption policy setting.
  7. On the Setting tab, click Enabled.
  8. Click OK.

At this point, the policy setting will be applied on your Outlook client workstations when the Group Policy update is replicated. To test this change, run the following command on a workstation:After you run this command, start Registry Editor on the workstation to make sure that the following registry data exists on the client:

Key: HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice15.0OutlookRPC
DWORD: EnableRPCEncryption
Value: 1

If you see this registry data in the registry, the Group Policy setting is applied to this client. Start Outlook to verify that the change resolves the problem.

Collapse this imageExpand this image

Collapse this imageExpand this image

Read More:
Outlook connection issues with Exchange mailboxes because of the RPC encryption requirement

"451 4.4.0 DNS query failed" Exchange Server error in message queue when you send email to remote domains

This problem may occur because the remote DNS servers ignore the AAAA query or return an unexpected response.

To work around this issue, create send connectors for the affected remote domains. (Create a send connector for each domain). Then, configure the send connectors to use the mail server in the remote domain as a smart host. To do this, follow these steps:

  1. Check the IP address of the MX record (mail server) for the affected remote domain. To do this, use nslookup or MX Record lookup tool

    (http://www.bing.com/search?q=mx+lookup+tool&FORM=AWRE)

    .

  2. Create a new send connector for this domain. Make sure that you configure the following settings:
    1. In the Address space section, add the affected remote domain such as contoso.com.
    2. In the Network setting section, select Route mail through the following smart hosts. Add the IP address of the MX record that you checked in step 1.
    3. Set Smart host authentication settings to None.

    For other settings, you can use the default value. For more information, see Configure a Dedicated Send Connector for a Specific Domain

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

    .

When Exchange Server sends email to this remote domain, it will now bypass the DNS query and connect the mail server in the remote domain by using the IP address directly. 

This problem may occur because the DNS server that Microsoft Exchange Server uses is not working. By default, Exchange Server uses network adapter DNS settings for outgoing remote mail routing.

To resolve this issue, fix the issues in your local DNS server, or configure the external DNS server for remote mail routing. To configure the external DNS server for remote mail routing, follow these steps:

  1. Open the Proprieties page of the Exchange server that hosts the send connector, and then add the IP address of public DNS servers

    (http://www.bing.com/search?q=public+dns+server&go=Submit+Query&qs=bs&form=QBRE)

    in the External DNS Lookups setting.

  2. Select the Use the external DNS lookup settings on servers with the transport roles option in the send connector that is responsible for remote mail routing.

Article ID: 3038746 – Last Review: February 26, 2015 – Revision: 9.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
kbsurveynew kbtshoot kbexpertiseinter KB3038746

View article:
"451 4.4.0 DNS query failed" Exchange Server error in message queue when you send email to remote domains

"MigrationPermanentException: Cannot find a recipient that has mailbox GUID <GUID>" error message when you try to move a mailbox in an Exchange hybrid deployment

Assume that you have a hybrid deployment of on-premises Microsoft Exchange Server and Exchange Online. When you try to “offboard” or move a mailbox that was created in Exchange Online to the on-premises organization, you receive the following error message:

Error: MigrationPermanentException: Cannot find a recipient that has mailbox GUID ‘‘. –> Cannot find a recipient that has mailbox GUID ‘<‎GUID>‘

This behavior occurs because the value of the mailbox GUID isn’t stamped on the associated mailbox in the on-premises organization.

Note The mailbox value is stored in the ExchangeGUID property (also known as the msExchMailboxGUID attribute).

This situation occurs because the value of the property isn’t synced to the associated remote mailbox in the on-premises organization when a mailbox is created in Exchange Online.

To move a mailbox, the value of the ExchangeGUID property must be the same in the Exchange Online mailbox and in the associated on-premises remote mailbox.

Set the ExchangeGUID property on the associated on-premises remote mailbox before you move the mailbox to the on-premises organization. To do this, follow these steps:
  1. Open the Exchange Management Shell on the on-premises server, and then run the following command to check whether the ExchangeGUID property of the on-premises remote mailbox is set:
    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. Open Windows PowerShell (don’t use the Exchange Management Shell), and then connect to Exchange Online. For more info about how to do this, see Connect to Exchange Online Using Remote PowerShell

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

    .

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

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

    .

To prevent this scenario from occurring, create the mailbox in the on-premises organization, and then move the mailbox to
Exchange Online. This stamps the value of the ExchangeGUID property on the mailbox, and then syncs the value to Exchange Online. After you do this, you can return the mailbox to the on-premises organization.

For more information, see Move mailboxes between on-premises and Exchange Online organizations in 2013 hybrid deployments

(https://technet.microsoft.com/en-us/library/jj906432%28v=exchg.150%29.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: 2956029 – Last Review: February 26, 2015 – Revision: 6.0


Applies to
  • Microsoft Exchange Online
o365e o365m o365022013 o365 o365a hybrid kbbug kbfix KB2956029

View article:
"MigrationPermanentException: Cannot find a recipient that has mailbox GUID <GUID>" error message when you try to move a mailbox in an Exchange hybrid deployment

Exchange Server error "451 4.4.0 DNS query failed" in Message Queue when you send email to remote domains

This problem may occur because the remote DNS servers ignore the AAAA query or return an unexpected response.

To work around this issue, create Send Connectors for the affected remote domains (Create Send Connector for each domain). Then, configure the Send Connectors to use the mail server in the remote domain as smart host. To do this, follow these steps:

  1. Check the IP address of the MX record (mail server) for the affected remote domain. To do this, use nslookup or MX Record lookup tool

    (http://www.bing.com/search?q=mx+lookup+tool&FORM=AWRE)

    .

  2. Create a new Send Connector for this domain. Make sure that you configure the following settings:
    1. In the Address space section, add the affected remote domain such as contoso.com.
    2. In the Network setting section, select Route mail through the following smart hosts. Add the IP address of the MX record that you checked in step 1.
    3. Set Smart host authentication settings to None.

    For other settings, you can use the default value. For more information, see Configure a Dedicated Send Connector for a Specific Domain

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

    .

When Exchange Server sends email to this remote domain, it will now bypass the DNS query and connect the mail server in the remote domain by using the IP address directly. 

This problem may occur because the DNS server that Microsoft Exchange Server uses is not working. By default, Exchange Server uses network adapter DNS settings for outgoing remote mail routing.

To resolve this issue, fix the issues in your local DNS server, or configure the external DNS server for remote mail routing. To configure the external DNS server for remote mail routing, follow these steps:

  1. Open the Proprieties page of the Exchange server that hosts the send connector, add the IP address of public DNS servers

    (http://www.bing.com/search?q=public+dns+server&go=Submit+Query&qs=bs&form=QBRE)

    in the External DNS Lookups setting.

  2. Select the Use the external DNS lookup settings on servers with the transport roles option in the send connector that is responsible for remote mail routing.

Article ID: 3038746 – Last Review: February 26, 2015 – Revision: 8.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
kbsurveynew kbtshoot kbexpertiseinter KB3038746

Read more here:
Exchange Server error "451 4.4.0 DNS query failed" in Message Queue when you send email to remote domains

System crashes or hangs when you try to duplicate an Advanced Financial report in General Ledger in Microsoft Dynamics GP

Microsoft Dynamics GP crashes or hangs when you try to copy or duplicate Advanced Financial (AFA) Reports.
This issue is usually caused by a corrupt dictionary such as the Reports.dic or Forms.dic.
Use the steps below to test if the dictionaries are corrupt: 

1. Ask all users to exit Microsoft Dynamics GP and make a current restorable backup.

2. Rename both dictionaries to determine if one or both of these is causing the issue. Navigate to the GP code folder and right-click on the Reports.dic and rename it to ReportsOld.dic and right-click on the Forms.dic and rename it to FormsOld.dic

Note: The default installation path is: C:Program FilesMicrosoft DynamicsGP

*More detailed steps are provided in the KB articles More detailed steps are provided in the KB articles below:

KB Article (850465) – How to re-create the Reports.dic file in Microsoft Dynamics GP 
http://support.microsoft.com/kb/850465

(https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;en-us;860545)

KB Article (951767) – How to re-create the Forms.dic file in Microsoft Dynamics GP
http://support.microsoft.com/kb/951767

(https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;en-us;860545)

3. Now test duplicating the AFA report again to see if the issue still happens. If Microsoft Dynamics GP continues to crash or hang, then one or both of these dictionaries is corrupt. (If one of the dictionaries is not causing the issue, you can put it back.)

5. If the issue still persists, you can also test to see if the Dynamics.dic is corrupt. To do this, rename the Dynamics.dic to DynamicsOld.dic and then copy over the Dynamics.dic from a different workstation, or install a new Microsoft Dynamics GP code folder to test with.

For more information on how to troubleshoot AFA reporting issues, see KB 866341:

KB Article (866341) – How to troubleshoot the reports in Advanced Financial Analysis in Microsoft Dynamics GP
http://support.microsoft.com/kb/866341

(https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb;en-us;866341)

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: 2472399 – Last Review: February 25, 2015 – Revision: 7.0


Applies to
  • Microsoft Dynamics GP 2013
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0, when used with:
    • Financials General Ledger
    • General Ledger
    • General Ledger
kbmbsmigrate kbsurveynew KB2472399

Read More:
System crashes or hangs when you try to duplicate an Advanced Financial report in General Ledger in Microsoft Dynamics GP

Page 1 of 97212345...102030...Last »

Recent Comments

    Archives

    Categories