Page 22 of 764« First...10...2021222324...304050...Last »

How to collect ActiveSync device logs to troubleshoot sync issues between mobile devices and Exchange Online

This article describes how to use Outlook Web App to collect Exchange ActiveSync device logs to troubleshoot sync issues between mobile devices and Exchange Online in Microsoft Office 365. If you can’t sync your mobile device to your mailbox, you may be asked by Office 365 Support to collect logs for troubleshooting.
To capture log information for mobile devices by using Outlook Web App, follow these steps:
  1. Sign in to the Office 365 portal (http://portal.office.com/

    (http://portal.office.com/)

    ).

  2. Click Outlook to open Outlook Web App.
  3. In the upper-right area of the page, click Settings (

    Collapse this imageExpand this image

    ), and then click Options.

  4. In the navigation pane on the left, click Phone, and then click Mobile Phone or Mobile Devices.
  5. In the list of devices, select the device that you want to track, and then click Start Logging.
  6. In the Information dialog box, click Yes.
  7. Reproduce the behavior that you want to capture, and then click Retrieve Log.

    An email message that contains the log file (EASMailboxLog.txt) as an attachment is sent to your mailbox.

Article ID: 2461792 – Last Review: October 4, 2014 – Revision: 24.0


Applies to
  • Microsoft Exchange Online
o365 o365a o365e o365p o365022013 o365m kbgraphic KB2461792

Read the original post:
How to collect ActiveSync device logs to troubleshoot sync issues between mobile devices and Exchange Online

Lync 2010 requires additional software to sign into Lync Online

When you try to sign in to Lync Online by using Lync 2010, you receive the following message:

To sign in, additional software is required.

When you click Download and install now?, you’re prompted to download and install the Microsoft Online Services Sign-In Assistant.

Collapse this imageExpand this image

To work around this issue, install the Microsoft Online Services Sign-In Assistant, restart your computer, and then try to sign in to Lync Online by using Lync 2010. To install the Microsoft Online Services Sign-In Assistant, go to the following Microsoft website:
This issue occurs if you try to sign in to Lync Online by using Lync 2010 on an operating system that doesn’t have the Microsoft Online Services Sign-In Assistant. 

Article ID: 2459899 – Last Review: October 4, 2014 – Revision: 25.0

o365 o365e o365p o365a kbgraphxlink o365022013 o365m kbgraphic KB2459899

More here:
Lync 2010 requires additional software to sign into Lync Online

Video is unavailable in a Lync Online conference when you use the "call me" option

When you join a Microsoft Lync Online conference by using the Microsoft Lync client, you can’t see or connect to the video feed. This issue occurs if you use the call me option when you connect to the conference.
To work around this issue, don’t use the call me option when you join a conference in Lync. Instead, use a phone to dial in to the audio conference. Then, you can add video by using Lync.
  1. Click the link in the meeting invitation to join the Lync meeting.
  2. When the Join Meeting Audio window opens, select Do not join audio, and then click OK.

    Collapse this imageExpand this image

    Note  If you don’t see the Join Meeting Audio window, you must enable it in Options before you join the meeting. In Lync, click Options, and then click Phones. Select Prompt me before joining to confirm or select another audio source.

  3. Use your telephone to join the audio part of the meeting with the telephone number and ID or PIN that is provided by the audio conferencing provider in the meeting invitation.

The call me option phones you when the conference occurs by using an audio connection that’s set up by the Audio Conferencing Provider (ACP) Multipoint Conferencing Unit (MCU). To connect by using video, the Audio/Video (AV) MCU must link the audio and video connections. However, the audio connection is already used by the ACP MCU, and the client can only create a single audio connection.

Article ID: 2430277 – Last Review: October 4, 2014 – Revision: 26.0

o365 o365m o365022013 kbgraphxlink o365e o365p o365a kbgraphic KB2430277

Visit site:
Video is unavailable in a Lync Online conference when you use the "call me" option

How to troubleshoot issues in which Outlook crashes or stops responding (hangs) when it’s used with Office 365

This article describes how to troubleshoot the following kinds of issues in Microsoft Outlook 2013, Microsoft Outlook 2010, or Microsoft Office Outlook 2007 when Outlook is used with Office 365:  
  • Outlook stops responding (hangs).
  • Outlook crashes even though you aren’t actively using it.
  • Outlook crashes when you start it.
To help troubleshoot Outlook issues in an Office 365 environment, follow these steps.

Outlook 2013 and Outlook 2010

Step 1: Investigate possible issues with add-ins

  1. Do one of the following:
    • If you’re running Windows XP, click Start, and then click Run.
    • If you’re running Windows Vista or Windows 7, click Start.
  2. Type Outlook /safe, and then click OK.
  3. If the issue is fixed, on the File menu, click Options, and then click Add-Ins.
  4. Select COM Add-ins, and then click Go.
  5. Click to clear all the check boxes in the list, and then click OK.
  6. Restart Outlook. If the issue doesn’t occur, start adding the add-ins one at a time until the issue occurs.

Step 2: Run Outlook Diagnostics

  1. Open Control Panel, and then open Add or Remove Programs (if you’re running Windows XP) or Programs and Features (if you’re running Windows Vista or Windows 7).
  2. In the list of installed programs, right-click the entry for your Office installation, and then click Repair.

Step 3: Create a new user profile

  1. Open Control Panel, and then click the Mail item.
  2. Click Show Profiles.
  3. Select the profile that you want to remove, and then click Remove.
  4. Click Add.
  5. In the Profile Name box, type a name for the profile.
  6. Specify the user name, the primary SMTP address, and the password. Then, click Next.
  7. You may receive the following message:

    Allow this website to configure alias@domain server settings?

    In this message, click to select the Don’t ask me about this website again check box, and then click Allow.

  8. When you’re prompted, enter your logon credentials, and then click OK.
  9. When set up is finished, click Finish.

Outlook 2007

Step 1: Investigate possible issues with add-ins

  1. Do one of the following:
    • If you’re running Windows XP, click Start, and then click Run.
    • If you’re running Windows Vista or Windows 7, click Start.
  2. Type Outlook /safe, and then click OK.
  3. If the issue is resolved, on the Tools menu, click Trust Center, and then click Add-ins.
  4. Select COM Add-ins, and then click Go.
  5. Click to clear all the check boxes in the list, and then click OK.
  6. Restart Outlook. If the issue doesn’t occur, start adding the add-ins one at a time until the issue occurs.

Step 2: Run Outlook Diagnostics

  1. Start Outlook 2007.
  2. Click Help, and then click Office Diagnostics.
  3. Click Continue, and then click Run Diagnostics.
  4. If an issue is identified, Office Diagnostics may be able to repair the issue.

Step 3: Create a new user profile

  1. Open Control Panel, and then click the Mail item.
  2. Click Show Profiles.
  3. Select the profile that you want to remove, and then click Remove.
  4. Click Add.
  5. In the Profile Name box, type a name for the profile.
  6. Specify the user name, the primary SMTP address, and a password. Then, click Next.
  7. You may receive the following message:

    Allow this website to configure alias>@ server settings?

    In this message, click to select the Don’t ask me about this website again check box, and then click Allow.

  8. When you’re prompted, enter your logon credentials, and then click OK.
  9. When set up is finished, click Finish.

Troubleshoot Outlook profiles by using Microsoft Outlook Configuration Analyzer Tool (OCAT)

You can also use OCAT to troubleshoot Outlook issues. For more info about OCAT, see the following Microsoft Knowledge Base article:

2659007

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

Outlook Configuration Analyzer Tool information

For more info about command-line switches that are used together with Outlook 2013, go to the following Microsoft website: For more info about command-line switches that are used together with Outlook 2010, go to the following Microsoft website:For more info about command-line switches that are used together with Outlook 2007, go to the following Microsoft website:
Still need help? Go to the Office 365 Community

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

website.

Article ID: 2413813 – Last Review: October 4, 2014 – Revision: 29.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Home Edition
o365 o365a o365e o365p o365022013 o365m KB2413813

See original article:
How to troubleshoot issues in which Outlook crashes or stops responding (hangs) when it’s used with Office 365

Users receive Send/Receive error messages after they set up multiple accounts in Office 365 by using Outlook 2007

Consider the following scenario. A user sets up multiple accounts in Microsoft Office 365 by using Microsoft Office Outlook 2007. For example, the user sets up his or her Outlook profile to connect to one account through MAPI and another account through POP3. However, the user receives Send/Receive error messages.
Outlook 2007 returns a failure message when it tries to download the offline address book for the non-MAPI account.
To fix this issue, set up the All Accounts Send/Receive group in Outlook 2007 not to download the offline address book. To do this, follow these steps.
  1. In Outlook 2007, on the Tools menu, point to Send/Receive, point to Send/Receive Settings, and then click Define Send/Receive Groups.
  2. Select the group name that’s named All Accounts, and then click Edit.
  3. Click to clear the Download offline address book check box for all non-MAPI accounts, and then click OK.

Article ID: 2269971 – Last Review: October 4, 2014 – Revision: 25.0


Applies to
  • Microsoft Exchange Online
o365 o365a o365e o365p o365022013 o365m KB2269971

View article:
Users receive Send/Receive error messages after they set up multiple accounts in Office 365 by using Outlook 2007

How to troubleshoot issues that you may encounter when you use the Lync 2010 mobile client for Apple iOS

The Microsoft Lync 2010 mobile client for Apple iOS requires a Lync account from your company organization. If you aren’t sure whether you have a Lync account, contact your company system administrator or support team.

This article describes how to troubleshoot some common issues that you may encounter when you use the Lync 2010 mobile client for Apple iOS.

Note If you’re looking for help with Lync Mobile 2013 for iOS phones or tablets, go to the following Microsoft websites: 

Signing in to Lync 2010 on Apple iOS

Verify your password, account information, server settings, and client version

Collapse this imageExpand this image

  1. If can’t sign in to Lync Mobile 2010, visit the Lync Sign-In Troubleshooter for Users

    (http://support.microsoft.com/common/survey.aspx?scid=sw;en;3719&showpage=1)

    to be guided through a series of steps to help resolve the most common sign-in issues.

  2. Make sure that you can sign in to Lync from a desktop by using Lync 2010, Microsoft Lync 2013, or Microsoft Lync for Mac 2011. If you can’t sign in from a regular desktop client, you probably can’t sign in to a mobile client.
  3. Make sure that you enter the correct password. If the password is incorrect, you’ll have to change it. For more information, go to the following Microsoft website:
  4. Make sure that you enter the correct account information. Unless your administrator has told you otherwise, you probably use the same account information to sign in to Microsoft Outlook, Microsoft SharePoint, and your work computer. If you can sign in to Lync from a desktop computer, use the same information to sign in to your mobile device.

    The following table describes the sign-in fields that are required for iOS users, depending on where their Lync account is located and how their account information is set up.

    Collapse this tableExpand this table

    Lync account SIP address and UPN Required fields
    On-premises Lync server Same Sign-in address: SIP address
    User name: Blank
    On-premises Lync server Different Sign-in address: SIP address
    User name: UPN or domainusername
    Office 365 Same Sign-in address: SIP address
    User Name: Blank
    Office 365 Different Sign-in address: SIP address
    User name: UPN
  5. Verify whether Auto-detect server is On. Lync tries to determine your Lync server based on your sign-in address. If it can’t detect your Lync server, you may have to turn off Auto-detect server and specify the Lync server manually.

    If Auto-detect server is turned on but you still can’t sign in, try manually entering the internal and external discovery addresses. This doesn’t resolve the issue. However, if you can successfully sign in manually, this indicates that the Auto-detect server option isn’t set up correctly by your administrator.

    • For Lync Online users in Office 365:
      • Internal discovery address: https://webdir.online.lync.com/Autodiscover/autodiscoverservice.svc/Root
      • External discovery address: https://webdir.online.lync.com/Autodiscover/autodiscoverservice.svc/Root
    • For Lync on-premises users, contact your support team or system administrator for help to determine your internal and external discovery address. In most cases, the internal and external discovery address should resemble the following:
      • Internal discovery address: https://lyncdiscover.lyncFE01.contoso.local/Autodiscover/autodiscoverservice.svc/Root
      • External discovery address: https://lyncdiscover.contoso.com/Autodiscover/autodiscoverservice.svc/Root


      Note
      To access the User name, Domain, Internal discovery address, and External discovery address fields, click Server Settings on the sign-in screen.

  6. Make sure that you’re using the latest version of the Lync 2010 mobile client for Apple iOS. Download the latest version from the Apple App Store. If you receive a message that states the client version is blocked or not supported, contact your support team or administrator because the Lync server might not be set up yet for mobile clients.

Collapse this imageExpand this image

Connecting over Wi-Fi through an authenticating proxy

Collapse this imageExpand this image

If the Wi-Fi connection that’s used requires authentication before you connect, Lync may not connect because it can’t use the credentials to connect through a proxy. To work around this issue, connect through the mobile carrier’s data connection instead of through Wi-Fi.

Collapse this imageExpand this image

Connecting on a network that requires certificates

Collapse this imageExpand this image

If your organization requires certificates to connect to their Wi-Fi or corporate network, and you receive an error message from Lync about certificates being incorrect or missing, you may have to import certificates from your company. There are apps in the Google Play store for importing and managing certificates. Contact your support team or administrator for help.

Collapse this imageExpand this image

Additional help with specific features

Collapse this imageExpand this image

For guides, FAQ, and references to help you use the Lync 2010 mobile client on Apple iOS, go to the following Microsoft websites:

Collapse this imageExpand this image

Comparison with other mobile clients

Collapse this imageExpand this image

For a feature comparison of Lync 2010 mobile clients, go to the following Microsoft TechNet website:

Collapse this imageExpand this image

Sending logs to support

Collapse this imageExpand this image

When users experience an issue that affects the Lync 2010 mobile client for Apple iOS, they can send logs by email to the support team or administrator. To do this, follow these steps:

  1. Click Options, locate Logging in the My Info section, and then click Send Logs.
  2. An email message is automatically generated that contains the attached log files and client version information in the body of the message. Then, enter an email address to send the logs to. Users should send the logs to their IT administrator or directly to the support engineer.

Note Make sure that Logging is set to ON before you try to reproduce the issue and send logs.

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.

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Article ID: 2636320 – Last Review: October 3, 2014 – Revision: 29.0

o365 o365a o365e o365p kbgraphxlink o365022013 o365m kb3rdparty kbgraphic guided walk through gwt KB2636320

See the original article here:
How to troubleshoot issues that you may encounter when you use the Lync 2010 mobile client for Apple iOS

List of attributes that are synced by the Azure Active Directory Sync tool

For a list of attributes that are synchronized by the Azure Active Directory Sync tool, see the following wiki article:

Article ID: 2256198 – Last Review: October 3, 2014 – Revision: 32.0


Applies to
  • Microsoft Azure Active Directory
  • Microsoft Office 365
  • Microsoft Exchange Online
  • Windows Intune
  • CRM Online via Office 365 E Plans
  • Microsoft Azure Recovery Services
  • Office 365 Identity Management
o365 o365a o365e o365062013 hybrid o365m KB2256198

Read More:
List of attributes that are synced by the Azure Active Directory Sync tool

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

After a mailbox is moved in Microsoft Exchange Server 2003 Service Pack 2 (SP2), a stub object is left behind in the source database for certain users. If you start Exchange System Manager (ESM) and then locate the object, you find the mailbox in the destination mailbox store and also in the source mailbox store.
Although the mailbox is moved successfully from the source server to the destination server, this problem occurs because Exchange 2003 cannot delete the folder hierarchy of the mailbox on the source server during or after the Move Mailbox operation.
Note This hotfix does not resolve the stub mailbox issue. It adds additional events in the application logs that indicate that there was a failure during the Move Mailbox operation. For more information, see the “After you apply the hotfix” section.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Exchange 2003 SP2 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, the Microsoft Exchange Information Store service, the Microsoft Search service, the IIS Admin Service, and all dependent services are restarted when you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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.

Collapse this tableExpand this table

File name File version File size Date Time
Davex.dll 6.5.7653.18 1,131,520 22-Oct-2007 09:02
Exoledb.dll 6.5.7653.18 2,621,440 23-Oct-2007 00:02
Exosal.dll 6.5.7653.18 70,144 22-Oct-2007 23:39
Mdbmsg.dll 6.5.7653.18 3,381,248 23-Oct-2007 00:43
Store.exe 6.5.7653.18 5,266,432 22-Oct-2007 23:40


After you apply the hotfix

After you apply this hotfix, if Exchange 2003 cannot delete the folder hierarchy of the mailbox in the source server during the Move Mailbox operation, the following events are logged:

Event Type: Error
Event Source: MSExchangeIS Mailbox Store
Event Category: General
Event ID: 10001
Description: The folder with folder ID %1 could not be deleted. Additional information: %2. 

Event Type: Error
Event Source: MSExchangeIS Mailbox Store
Event Category: General
Event ID: 10002
Description: Failed to delete mailbox with error %1.

In this log entry, Event ID 10001 identifies the folder that could not be deleted, and Event ID 10002 identifies the partly deleted mailbox that cannot be removed from the source server. As soon as you determine the partly deleted mailbox, remove the mailbox manually. To do this, use one of the following methods.

WARNING There is a high risk of disconnecting the newly migrated Exchange 2010 mailboxes if these stubs are removed manually or are removed as part of an Exchange 2003 server decommissioning process. To avoid this problem, you must use one of the following methods before you decommission an Exchange 2003 Mailbox server:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684

(http://support.microsoft.com/kb/824684/LN/
)

Description of the standard terminology that is used to describe Microsoft software updates

For more information about the naming schema for Exchange Server software updates, click the following article number to view the article in the Microsoft Knowledge Base:

817903

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

New naming schema for Exchange Server software update packages

Article ID: 940012 – Last Review: October 2, 2014 – Revision: 7.0


Applies to
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange Server 2003 Enterprise Edition
kbautohotfix kbhotfixserver kbqfe KB940012

Link:
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

Integration between RED and AA in Microsoft Dynamics GP

There is limited compatibility between Revenue and Expense Deferrals (RED) and Analytical Accounting (AA) at this time in Microsoft Dynamics GP.  This article discusses how to get AA codes on your deferral entries.
Limited compatibility between AA and RED
You are not able to add/edit AA codes at time of entry for deferrals at this time. But as a work-around, you can use one of the options outlined below to go back and add/edit the AA data on the deferrals in a two-step process: 

Option 1 – Post the deferral in GL. Then click on Transactions, point to Financial, point to Analytical Accounting, and click on Edit Analysis. Select the Journal Entry of the deferral and proceed to add/edit the AA data.

Option 2 - Stop the batch in GL and add the AA codes to the transactions in the GL work batch.

Option 3 - Enter default AA codes in the Trx Dimension Code Default fields on the Accounting Class, and these codes will get automatically assigned to the deferral entries. However, you would still have to use one of the other options if you want to change any of the codes.

***If this is a product enhancement you would like see added to Microsoft Dynamics GP in the future, please click HERE

(https://connect.microsoft.com/dynamicssuggestions/Feedback/Details/989466)

 or use the link below to vote on this suggestion so it will be considered as a future enhancement: Your vote on this suggestion will help to push this up in priority!

https://connect.microsoft.com/dynamicssuggestions/Feedback/Details/989466

(https://connect.microsoft.com/dynamicssuggestions/Feedback/Details/989466)

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: 3006081 – Last Review: October 2, 2014 – Revision: 3.0


Applies to
  • Microsoft Dynamics GP 2013 R2
  • Microsoft Dynamics GP 2013
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0, when used with:
kbmbsmigrate kbsurveynew KB3006081

Read More:
Integration between RED and AA in Microsoft Dynamics GP

Microsoft Dynamics CRM for Outlook records do not synchronize or are missing Track and Set Regarding buttons with User Filters disabled

Microsoft Dynamics CRM for Outlook records do not synchronize or are missing Track and Set Regarding buttons with User Synchronization Filters disabled even though System Synchronization Filters exist and are enabled
Although System Synchronization Filters are enabled for a specific type of record, they will not track without User Synchronization Filters enabled. The System Synchronization Filters currently depend on User Synchronization Filters being enabled before the synchronization criteria is applied
User Synchronization Filters for the particular record type in question must exist and be enabled
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: 3006088 – Last Review: October 2, 2014 – Revision: 1.0


Applies to
  • Microsoft Dynamics CRM 2011
  • Microsoft Dynamics CRM 2013
  • Dynamics CRM Online
kbmbsmigrate kbsurveynew KB3006088

Read the article:
Microsoft Dynamics CRM for Outlook records do not synchronize or are missing Track and Set Regarding buttons with User Filters disabled

Page 22 of 764« First...10...2021222324...304050...Last »

Recent Comments

    Archives

    Categories