Microsoft Reduce Customer Effort Center

Our team drives product feedback based on solid data, it drives proactive issue prevention and ultimately, drives improvements around products based on customer feedback.

June, 2011

  • 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

  • Error message "Your client does not support opening this list with Windows Explorer" when you try to "Open with Explorer" on a SharePoint document library in Office 365 site

    [Symptoms]

    When you log on to the SharePoint online site by using your Office 365 account, navigate to a document library and click “Open with Explorer” button on the ribbon, you receive the following error message:

    Your client does not support opening this list with Windows Explorer

    [Resolution]

    To successfully make “Open with Explorer” work, we need ensure the following:

    1.  WebClient service is started 

    WebClient service which the WebDav protocol enables Windows-based programs such as Windows Explorer to create, access and modify Internet-based files.


    Important Note: 
    If you are running a server type Windows OS, for example, you use Window Server 2008, install Desktop Experience feature first to get  WebClient service installed.

      1. From the Start menu, point to Administrative Tools, and click Services.
      2. Scroll down, right-click WebClient, and click Properties.
      3. In the Startup type list box, click Automatic.
      4. Click Apply.
      5. In the Service status section, click Start.
      6. Click OK.

     

      2.    You have supported Web browser

    For a list of supported Web browsers and support level information, please visit:
    Plan browser support
    From the page you can see it’s recommended to use 32-bit Internet Explorer 7,8,9.

    Note: “Open with Explorer” may not work if you have 64-bit Internet Explorer and 64-bit Microsoft Office installed.

     

    3. Add https://*.sharepoint.com to Local intranet site

    To configure Web browser, open “Internet Options” menu, navigate to the “Security Tab”, and add https://*.sharepoint.com to Local intranet site.

     

    Then restart the browser and try it again.

    =======

    > If you have tried the above methods, however “Open with Explorer” still does not work, try to make sure you have applied the latest updates on the system.

    > In addition, you can also try to enable Basic authentication on the client computer, by setting the BasicAuthLevel registry entry of the following key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters

    For detailed steps, visit the following KB page.

    You cannot connect to a document library in Windows SharePoint Services 3.0 or Windows SharePoint Services 2.0 by using Windows shell commands or by using Explorer View
    http://support.microsoft.com/kb/841215

     

    If none of the above resolves your issue,  you can open a post for discussion in Office 365 community or contact Microsoft Support. 

    http://community.office365.com/en-us/f/154.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

  • 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

  • Recommended articles for resolving printing issues in Internet Explorer 9(IE9)

    Some customers reported that when printing or viewing the print preview of a webpage in Internet Explorer 9, the webpage may not print or preview correctly.

    There are some known issues, you can reference below articles to resolve it:

    Errors occur when using Canon printer drivers to print from Windows Internet Explorer 9

    http://support.microsoft.com/kb/2522071/en-us

    Cannot print from Internet Explorer 9 using some Canon printers

    http://support.microsoft.com/kb/2522422/en-us

    Error message: “Canon Easy-WebPrint EX isn’t compatible with Internet Explorer”

    http://support.microsoft.com/kb/2518296/en-us

    Unable to print or view the print preview of a webpage in Internet Explorer 9

    http://support.microsoft.com/kb/2409656/en-us

    You cannot print or print preview Web pages in Internet Explorer on Windows Vista or on Windows 7

    http://support.microsoft.com/kb/973479/en-us

    Compatibility issues with HP Smart Web Printing and Internet Explorer 8

    http://support.microsoft.com/kb/2519416/en-us

    Printing webpages in Internet Explorer 9: frequently asked questions

    http://windows.microsoft.com/en-US/windows7/Printing-webpages-in-Internet-Explorer-9-frequently-asked-questions

     

  • You cannot connect two Office 365 accounts in one Outlook profile at the same time

    [Symptoms]

    Some customers find that if they try to configure two or more Office 365 accounts in one Outlook profile, these accounts cannot all connect to the Exchange Online Server at the same time, even though you have configured them correctly. For example, you have name1@domain.com (default account) and name2@domain.com configured, when name1@domain.com is connected to the server, you cannot get name2@domain.com connected.

    This issue may occur intermittently.

    [Resolution]

    To resolve this issue, use the Add-RecipientPermission cmdlet to add SendAs permission to the default account. To do so, use the following steps:

    1. Connect Windows PowerShell to the Office 365 Online Service

     


    For detailed steps, visit Use Windows PowerShell in Exchange Online .

     

          2.  Run the cmdlet that resembles the following. Please be noted that name1@domain.com is the default account in Outlook.

     

    $target_giving = 'name1@domain.com'

    $user_getting = 'name2@domain.com'

    Add-MailboxPermission –Identity $target_giving -User $user_getting -AccessRights FullAccess -InheritanceType All
    Add-RecipientPermission $target_giving -Trustee $user_getting -AccessRights SendAs

    Note:  More details about Add-RecipientPermission cmdlet
    http://technet.microsoft.com/en-us/library/ff935839.aspx

     

    IF this method does not resolve this issue, welcome to leave a comment here, or follow up on the original post http://community.office365.com/en-us/f/160/t/3505.aspx .

  • Error message when you try to configure Office 365 account in Outlook: "The security certificate was issued by a company you have not chose to trust"

    [Symptoms]

    When you configure a Microsoft Exchange Online account (Office 365 account) in Outlook client application, you receive a security alert after you enter your account credentials: 

    The security certificate was issued by a company you have not chose to trust. View the certificate to determine whether you want to trust the certifying authority.

    Note: The issue typically occurs in an environment where Microsoft Exchange Online coexisting on-premise deployment. 

    [Cause]

    The issue occurs because the network incorrectly redirects external auto-discover calls back to your Client Access Server(CAS) that are deployed on-premise. In a normal configuration, Office 365 domain autodiscover calls will simply hit the internet looking for the Microsoft Online DNS address.  Since this call hits your CAS instead, and probably because the certificate that is installed on the CAS is not valid, you receive certificate authority (CA) validation errors.

    [Resolution]

    To resolve this issue, manually configure Outlook client with the following settings:

    1. First log on to the Office 365 Outlook Web Access(OWA). Inside of OWA, go to help/about. Make a note of the first part of the "Host Name" entry (For example, SN1PRD0202) which is the server name and well as the first part of the external POP setting (ex. POD51008) which is the proxy name.

    2. Log into Outlook and manually configure an Exchange connection with the following settings:

    SERVER: the server name attached to .mailbox.outlook.com (ex. SN1PRD0202.mailbox.outlook.com)

    CACHED MODE: Checked.

    USER NAME: The full O365 email address of the account.  Don't click "check name", click "more settings"

    Go to the SECURITY tab.

    Make sure the first box is checked, and security is set to "negotiate authentication"

    

    Go to the CONNECTION tab.

    Check "connect to Microsoft Exchange using HTTP" then click the "Exchange Proxy Settings" button

    In the connection settings box, enter the proxy name attached to .outlook.com(ex. POD51008.outlook.com)

    In the 2nd box enter msstd: outlook.com

    All four checks should be selected

    Under "Proxy Authentication Settings" make sure that "Basic Authentication" is checked.

    OK all the way back out to the first page (server name and user name) and hit next.

  • Messages are not delivered after you send messages to a large number of recipients by using an Office 365 account

    [Issue]

    When you try to send emails by using an Office 365 account, the email messages are not delivered. Additionally, you receive the following non-delivery report messages:

    Your message did not reach some or all of the intended recipients.

                This message could not be sent. Try sending the message again later, or contact your network administrator.  Error is [0x80004005-00000000-00000000].

    The issue typically occurs if you have sent messages to a large number of recipients during the past 24 hours.  

    [Cause]

    The issue because there is a limit in Office 365 that a mailbox is not allowed sending messages to more than 1500 recipients in one day.  You can check out the details by visiting the following page:

    Message and Recipient Limits

    Note: If a message is sent to a distribution group in the Global Address List (GAL), the distribution group is counted as 1 recipient; If a message is sent to a group of in the contacts folder of Outlook, each member of the group is counted as a recipient.

     [Resolution]

    To successfully deliver the email messages, resume sending them later.

    [More Information]

    For on=premise deployment of Exchange Server 2010 environment, administrators can query all recipients by using the Get-MessageTrackingLog cmdlet as below:   

    Get-MessageTrackingLog -Start "06/09/2011 9:00AM" -End "06/10/2011 9:00AM" -Sender "john@contoso.com" | Select-Object Timestamp,Sender, {$_.recipients}, MessageSubject | export-csv c:\QueryAllRecipients.csv

    However, Get-MessageTrackingLog cmdlet is not available to Office 365 users. For a list of PowerShell Cmdlets, visit the following Microsoft Web site:

    Reference to Available PowerShell Cmdlets

  • Online service SSO client issues series 2/2: Receive the message that "Outlook cannot be configured in the Single Sign In application" when you try to configure Outlook by Single Sign In application

    [Symptoms]
    When you try to configure Outlook by Online Service Single Sign In application, you receive the following error message:
    Outlook cannot be configured in the Single Sign In application.
    [Resolution]
    The issue may be result from the dis-match of user principal name (UPN) and the Default SMTP Address. If they do not match, Microsoft Online Single Sign In application cannot complete the configuration of Outlook. To make sure that the UPN and the Default SMTP Address match, follow these steps:
    a. Sign in to the Microsoft Online Administration Console.
    b. Under Actions, click View User List.
    c. In the All enabled users list, click a user's display name.
    d. In the Edit User box, compare the text in the User Name and Domain boxes to the default address in the Alternate E-Mail Addresses box, and make sure that they are the same.
    If you have other questions on this issue, please open a post for discussion in BPOS forum or contact Microsoft Support to ask for help.
  • Online service SSO client issues series 2/1: After successfully sign in to Microsoft Online Services by using the Microsoft Online Services Sign In client, you are repeatedly prompted for credentials when you open Outlook.

    [Symptoms]
    1. This occurs when the computer was in Sleep mode , Hibernation mode, or Standby mode and then weak up.
    2. Microsoft Office Communicator/Lync is asking for credentials.
    [Resolution]
    1. If Office Outlook wakes up before the Microsoft Online Services Sign In client successfully signs in, Outlook will prompt you for credentials before you can successfully connect to Microsoft Exchange Online. Please enter your credentials in the dialog box. This forces the Sign In client to automatically pass the credentials and the credentials prompts no longer appear.
    2. Please follow the step below to disable the automatically start of Communicator/Lync.
    a. In communicator click Tools, and then click Options.
    b. Uncheck the box Automatically start Communicator when I log into Windows, and then click OK.
    c. Quit Communicator.
    d. Quit Office Outlook.
    e. Quit the Sign In client.
    f. Start the Sign In client, and then sign in.
    g. Start Office Outlook from the Sign In client.
    h. Start Communicator.
     
  • 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.

     

     

  • 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