• When you attempt to move mailbox from/to Exchange Online, you receive the error "The call to Microsoft.Exchange.MailboxReplicationService timed out"

    Symptom:

    When you attempt to move mailbox from/to Exchange Online, you receive the error:

    The call to 'net.tcp://server name/Microsoft.Exchange.MailboxReplicationService server name' timed out. Error details: This request operation sent to net.tcp:// server name//Microsoft.Exchange.MailboxReplicationService did not receive a reply within the configured timeout (00:01:00).  The time allotted to this operation may have been a portion of a longer timeout.  This may be because the service is still processing the operation or because the service was unable to send a reply message.  Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

     

     

    Cause:

    The DataImportTimeout property may be set too low.

     

    Resolution:

    To isolate the issue, you may check how it works if you increase the timeout with the following steps:

     

    1. On the Client Access server, open the following file with a text editor such as Notepad:

    \ExchWeb\EWS\web.config

    1. Locate the following section in the web.config file:

    <!-- Mailbox Replication Proxy Server configuration -->

    <MRSProxyConfiguration

    IsEnabled="true"

    MaxMRSConnections="100"

    DataImportTimeout="00:01:00" />

    1. Make sure value of the IsEnabled property is set to true.
    2. Check the value of the DataImportTimeout property. The minimum value is one minute (00:01:00), and the maximum value is 30 minutes (00:30:00).
    3. Set a higher value, but make sure the value is less than 30 minutes.
    4. The recommended value for this field should be 00:20:00 (20 minutes).
    5. After the values are configured correctly, save and close the web.config file.

     

     

    More information and documentations for your reference:

     

    Troubleshooting Mailbox Moves

    http://64.4.11.252/en-us/library/dd638094.aspx

  • Disabling offline files removes pinned items from Windows 7 task bar?

    When I review the forum threads, I found an interesting issue about offline files and pinned items.

    Symptom:

    Users may not be able to pin items to their taskbar or Start menu, or pinned items may disappear the next time the user logs in if desktop is redirected to a network file server and offline files are disabled.

    But if offline files are enabled and re-login, the pinned items will re-appear on the task bar.

    Cause:

    This occurs becuase Explorer needs permission to read from user shell folders when adding items to the taskbar. The SMB read permissions are more restrictive than NTFS read permissions, so Explorer is not able to access the folders and cannot load the pinned items.

    Solution:

    To resolve this issue, set the share permissions to Read and Change or Full Control. The folder can be restricted to read only using file system (NTFS) permissions on the file server, but the share permissions must be at least Read and Change.

    Reference:

    http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/53a6a7f1-8fb6-47e8-bf8d-c1b03e8d4575/

    http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/3c60c3f6-6682-4ab4-9369-b3ecac62fcf2

  • Outgoing mails stuck in the Outlook and cannot be delivered when you have cached mode enabled to connect with BPOS account

    Symptom:

    You cannot send mail in Outlook with BPOS account connected. Mail items stuck in the Outlook Outbox folder. Other symptoms that you may experience:

     

    1. OWA/ActiveSync works well and the issue happen only in Outlook.
    2. Sometimes it works fine and sometime don't.
    3. If you disable the cache mode, it can connect and send mail without problem.
    4. Closing then reopening Outlook helps sending stucked mails.

     

    Cause:

    The issue results from the disconnection between your corporate network and BPOS. It may indicates that there is network communication issues with you internet connection which triggers the connection timeout unexpected.

     

    Workaround:

    As a workaround, you may check how it works if increasing the timeout value to 60s (30s by default) with the steps following:

     

    1. Click File menu, select Info page and click account settings.
    2. In the Account settings window, navigate to E-mail page, double click the account that you experience the issue.
    3. In the Change Account windows, click More settings and change the value to 60s to increase the timeout interval.

     

     

  • The error 0X80070490(Element not found) when you are installing a service pack or update

    Symptom:

    When you are installing a service pack or update for Windows 7 or 2008 R2, the update may fail to install with an error 0X80070490.

    You have tried the following contents, but still can not resolve the problem:

    1. KB977893

    2. KB947821

    3. http://windows.microsoft.com/en-US/windows7/Windows-Update-error-80070490

    When you examine the setupapi.dev.log, you may find the followings were logged:

         inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\scanners.inf_amd64_neutral_08717035d84064b6\scanners.inf' ([strings])
         sig: {_VERIFY_FILE_SIGNATURE} 08:56:21.210
         sig:      Key      = scanners.inf
         sig:      FilePath = C:\Windows\System32\DriverStore\FileRepository\scanners.inf_amd64_neutral_08717035d84064b6\scanners.inf
    !    sig:      No installed catalogs matching catalog name '' were found that validated the file.
    !    sig:      Error 1168: Element not found.
         sig: {_VERIFY_FILE_SIGNATURE exit(0x00000490)} 08:56:21.226

    *note*: the missing inf file could be different in your computer.

    Cause:

    Error 0x80070490 is "Element not found". there is a consistent error to the specific drivers.

    Resolution:

    To resolve the issue please try the following

    1. Run the checksur.exe (System Update Readiness Tool) tool.
    2. Run System File Checker. From the command line run the command sfc /scannow
    3. Review the cbs logs and uninstall the patches which were missing assemblies and reboot the server.
    4. Reinstall the update.

    For advanced customers, you can maunally fix it:

    From an elevated command prompt:

    pnputil - a <Inf File Path>

    e.g.: C:\Windows\System32\DriverStore\FileRepository\scanners.inf_amd64_neutral_08717035d84064b6\scanners.inf

    Well, the repair install is the last choice but worth a try befor you give up. :-)

    More information:

    Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2
    http://support.microsoft.com/kb/947821

  • How to resolve the error 0x80073701(ERROR_SXS_ASSEMBLY_MISSING) when you are installing a service pack or update

    Symptom:

    When you are installing a service pack or update for Windows 7 or 2008 R2, the update may fail to install with an error 0x80073701.

    When you examine the CBS.log, you may find the followings were logged:

    2011-03-01 10:31:14, Error CSI 00000010 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #396746# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = 9e12b49121d141c9a55e48800acbaadd, Version = 8.0.7600.20820, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, cb = (null), s = (null), rid = [77]"Package_1_for_KB2447568~31bf3856ad364e35~amd64~~6.1.1.0.2447568-1_neutral_LDR", rah = [1]"3", manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
    2011-03-01 10:31:14, Info CBS Failed to pin deployment while resolving Update: 2447568-1_neutral_LDR from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2011-03-01 10:31:14, Info CBS Failed to resolve item[0] in Package: Package_1_for_KB2447568~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2447568-1_neutral_LDR [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

    Cause:

    Error 0x80073701 is ERROR_SXS_ASSEMBLY_MISSING, it means there are some system files are missing, which caused the update installation failure.

    Resolution:

    To resolve the issue please try the following

    1. Run the checksur.exe (System Update Readiness Tool) tool.
    2. Run System File Checker. From the command line run the command sfc /scannow
    3. Examine the language packs installed on the system. Uninstall the unnecessary language packs.
    4. Review the cbs logs and uninstall the patches which were missing assemblies and reboot the server.
    5. Reinstall Service Pack 1.

    For advanced customer, you can manually examine which files are missing. For example, in the above CBS log, you can see the files for update KB2447568 are missing. To resolve this issue, you can either:

    1. Copy the missing files from a good machine.

    2. Download and install KB2447568 again.

    Well, the repair install is the last choice but worth a try befor you give up. :-)

    More information:

    Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2
    http://support.microsoft.com/kb/947821