Page 322 of 734« First...102030...320321322323324...330340350...Last »

You experience slow performance when you perform RetrieveMultiple queries on large datasets in Microsoft Dynamics CRM 2011

When you perform RetrieveMultiple queries on large datasets in Microsoft Dynamics CRM 2011, you experience slow performance.
This problem occurs because large datasets cache the Microsoft SQL query plans for the RetrieveMultiple queries. The RetrieveMultiple optimization for the basic depth is required for the “local depth” read privilege and for the “deep depth” read privilege.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756

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

How to back up and restore the registry in Windows

This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 2011. For more information about the latest cumulative update rollup for Microsoft Dynamics CRM 2011, click the following article number to view the article in the Microsoft Knowledge Base:

2466086

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

Update Rollup 2 for Microsoft Dynamics CRM 2011 is available

If Update Rollup 8 or an earlier upudate rollup is installed, follow these steps to enable this hotfix on the computer that is running Microsoft Dynamics CRM 2011:  

  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSCRM

  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Name the newly created DWORD registry entry by typing EnableRetrieveMultipleOptimization.
  5. Right-click EnableRetrieveMultipleOptimization, and then click Modify.
  6. In the Value data box, type 2, and then click OK.

    Note
    The default value is 0.
  7. On the File menu, click Exit.

If Update Rollup 10 or a later update rollup is installed, see the ”Optimizing the Performance of Queries against Large Datasets” section of the ”Optimizing and Maintaining the Performance of a Microsoft Dynamics CRM 2011 Server Infrastructure” white paper. To download the white paper, go to the following Microsoft Download Center website: 

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/
)

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

For more information about Microsoft Business Solutions CRM software hotfix and update package terminology, click the following article number to view the article in the Microsoft Knowledge Base:

887283

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

Microsoft Business Solutions CRM software hotfix and update package naming standards

Article ID: 2535245 – Last Review: August 15, 2012 – Revision: 2.0


Applies to
  • Microsoft Dynamics CRM 2011
kbqfe kbfix kbmbsmigrate kbexpertiseinter kbsurveynew KB2535245

Continue Reading:
You experience slow performance when you perform RetrieveMultiple queries on large datasets in Microsoft Dynamics CRM 2011

How to remove duplicate folders in Outlook when connected to an Exchange Server mailbox

In Microsoft Outlook, you see duplicate folders in your Microsoft Exchange Server mailbox when you view the Outlook folder list in Online mode or in Cached Exchange mode, or when you access the list by using either Outlook Web Access (OWA) or Outlook Web App (OWA).
A mobile device or a third-party server application that synchronizes with the Exchange Server mailbox may unexpectedly introduce the duplication. Or, the unexpected duplication may be the result of Exchange Server mailbox maintenance or of other changes that are performed on the computer that is running Exchange Server. Other factors could also contribute to the issue described in the Symptoms section of this article.

The following steps may result in data loss if you do not follow them exactly as written. We recommend that you back up Outlook data or make sure that the Exchange Server mailbox has been backed up before you proceed with these steps.

To delete the duplicate items, follow these steps:

1. Exit Outlook and close OWA on all workstations that are connected to the user mailbox.

2. Use MFCMapi to identify the duplicate folders. To do this, follow these steps:

    1. Download MFCMAPI from http://mfcmapi.codeplex.com
    2. Run MFCMAPI.exe.
    3. Click on the Tools menu, then click Options.
    4. Click to enable the following option:
  • Use MDB_ONLINE when calling OpenMsgStore
  • On the Session menu, click Logon.
  • If you are prompted for a profile, select your profile name, and then click OK.
  • In the top pane, locate the line that corresponds to your mailbox, and double-click it. 
  • In the navigation pane (left-side pane), expand Root Container then expand Top of Information Store.
  • To identify the duplicate folder, click one of the duplicate folders on the left pane. In the right pane, locate the Value column for the PR_CREATION_TIME property. Compare this value to the duplicate folder with the same name. The duplicate folder will have a newer creation date and time. Work with one pair of folders at a time (for example, start with the two Calendar folders that appear).
  • 3. Use MFCMAPI to copy any items from the duplicate folder to the original folder. These are items created after the duplicate folders were created. This can include email that was received in the Inbox, Contacts that were created, Calendar appointments that you scheduled and meetings that you accepted.

      1. In the left pane of MFCMAPI, double-click on the duplicate folder, which has the newer creation date and time.
      2. On the window that opens, click on the top pane, then press CTRL + A to select all items.
        If no items appear in the top pane, the folder is already empty; skip to step 7.
      3. Click on the Actions menu, then click the Copy Messages command.
      4. Close the folder window, then double-click on the original folder, which has the older creation date and time.
      5. Click on the Actions menu, then click the Paste Messages command.
      6. Click to enable the MESSAGE_MOVE checkbox, then click OK.
      7. Close the folder window.

    4. In MFCMAPI, switch back to the duplicate folder, which is now empty. Use MFCMAPI to delete it.

      1. To delete the duplicate folder, right-click the folder and select Delete Folder.

    5. Repeat steps 2 through 4 for other common Outlook folders (Contacts, Deleted Items, Drafts, Inbox, Journal, Junk E-mail, Notes, Sent Items, and Tasks).

    6. Close MFCMAPI.

      7. Start Outlook with the resetfolders switch:

        • Windows 7 and Windows Vista
          • Click the Start button, point to All Programs, click Accessories, and then click Run.
          • In the Run dialog box, type a quotation mark, enter the full path for the outlook.exe file, and then type another quotation mark. Alternatively, click Browse to locate and select the file. In this case, the quotation marks are supplied automatically.
          • After the closing quotation mark, type a space, and then type the switch. For example, if you have Outlook 2010 installed, you might type:

            “c:program filesmicrosoft officeoffice14outlook.exe” /resetfolders

            For Outlook 2007, use Office12.
            For Outlook 2003, use Office11.

        • Windows XP
          • Click the Windows Start button, and then click Run.
          • In the Run dialog box, type a quotation mark, enter the full path for the outlook.exe file, and then type another quotation mark. Alternatively, click Browse to locate and select the file. In this case, the quotation marks are supplied automatically.
          • After the closing quotation mark, type a space, and then type the switch. For example, if you have Outlook 2010 installed, you might type:

            “c:program filesmicrosoft officeoffice14outlook.exe” /resetfolders

            For Outlook 2007, use Office12.
            For Outlook 2003, use Office11.

        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: 2509983 – Last Review: August 15, 2012 – Revision: 11.0


        Applies to
        • Microsoft Office Outlook 2003
        • Microsoft Office Outlook 2007
        • Microsoft Outlook 2010
        • Microsoft Business Productivity Online Suite Federal
        • Microsoft Business Productivity Online Dedicated

        Other Support Sites

        Community

        Get Help Now

        Excerpt from:
        How to remove duplicate folders in Outlook when connected to an Exchange Server mailbox

        MRM cannot process retention policies on a cloud-based archive mailbox if the primary mailbox is in an on-premises Exchange Server 2010 organization

        Consider the following scenario:
        • You configure Microsoft Exchange Online Archiving on your on-premises Microsoft Exchange Server 2010 organization that has Exchange Server 2010 Service Pack 1 or a later-version update rollup installed.
        • You create a retention policy, and then apply the policy to a user’s primary mailbox in the on-premises Exchange organization.
        • You enforce the retention policy to be processed on the on-premises primary mailbox by running the Start-ManagedFolderAssistant cmdlet.
        • You try to enforce the retention policy to be processed on the cloud-based archive mailbox by running the Start-ManagedFolderAssistant cmdlet in a remote Windows PowerShell session.

        In this scenario, the cmdlet fails. Additionally, you receive the following error message:

        WARNING: An unexpected error has occurred and a Watson dump is being generated: Value cannot be null.
        Parameter name: entryId

        This issue occurs because messaging records management (MRM) cannot detect the folder associated information (FAI) message objects in the primary mailbox. Therefore, MRM stops processing the mailbox.
        To resolve this issue, install the following update rollup:
        2706690

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

        Description of Update Rollup 4 for Exchange Server 2010 Service Pack 2

        Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
        For more information about Exchange Online Archiving, go to the following Microsoft website:For more information about retention policy tags and retention policies, go to the following Microsoft website:For more information about the Start-ManagedFolderAssistant cmdlet, go to the following Microsoft website:For more information about MRM, go to the following Microsoft website:

        Article ID: 2677727 – Last Review: August 14, 2012 – Revision: 1.0


        Applies to
        • Microsoft Exchange Online
        • Microsoft Exchange Server 2010 Service Pack 2, when used with:
          • Microsoft Exchange Server 2010 Enterprise
          • Microsoft Exchange Server 2010 Standard
        kbqfe kbfix kbsurveynew kbexpertiseinter KB2677727

        See more here:
        MRM cannot process retention policies on a cloud-based archive mailbox if the primary mailbox is in an on-premises Exchange Server 2010 organization

        Troubleshooting basics for Lync Online and Office Communicator in a dedicated Office 365 environment

        oneMscomBlade,oneMsomNav,oneMscomFooter,

        Visit site:
        Troubleshooting basics for Lync Online and Office Communicator in a dedicated Office 365 environment

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

        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. MOSSUP or MOSSFED must attach the escalation template to the escalation.
        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 Secure File Transfer (SFT) information to the Authorized Requestor.
        7. After the customer confirms the receipt of the information, the SR is closed.

        Article ID: 2649373 – Last Review: August 13, 2012 – Revision: 6.0


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

        View article:
        How to retrieve archived conversations from Lync Online in a dedicated Office 365 environment

        How to manually remove the Microsoft Dynamics CRM 4.0 server

        This article describes how to manually remove the Microsoft Dynamics CRM 4.0 server.
        Typically, you can use Add or Remove Programs in Control Panel to remove the Microsoft Dynamics CRM server. You can also run the Microsoft Dynamics CRM server installation program to remove the Microsoft Dynamics CRM server.

        Note You can run the ServerSetup.exe file to run the Microsoft Dynamics CRM server installation program.

        However, if a problem occurs when you use one of these methods to remove the Microsoft Dynamics CRM server, you must manually remove the Microsoft Dynamics CRM server.

        Note The Microsoft Dynamics CRM server contains many components. These components are related to many applications and to many technologies. For example, the components are related to Windows Server, to Internet Information Services (IIS), to Microsoft SQL Server, to SQL Server Reporting Services (SSRS), and to the Microsoft .NET Framework. Therefore, if you must completely remove the Microsoft Dynamics CRM server, consider completely rebuilding the computer instead of manually removing the Microsoft Dynamics CRM server.

        To manually remove the Microsoft Dynamics CRM server, follow these steps.

        Note The following steps describe how to remove the applications that are installed in a Full Server configuration. You can use similar steps to remove specific server roles. Additionally, the following steps do not remove all the components that are installed when you install the Microsoft Dynamics CRM server. However, after you follow these steps, you can reinstall the Microsoft Dynamics CRM server.

        Step 1: Stop the Microsoft Dynamics CRM Asynchronous Processing service

        1. Click Start, point to All Programs, point to Administrative Tools, and then click Services.
        2. Right-click Microsoft Dynamics CRM Asynchronous Processing Service, and then click Stop.

        Step 2: Stop the Indexing service

        1. Click Start, point to All Programs, point to Administrative Tools, and then click Services.
        2. Right-click Indexing Service, and then click Stop.

        Step 3: Configure the Web site and the application pool

        1. Log on to the computer that is running Internet Information Services (IIS). This computer has the Microsoft Dynamics CRM 4.0 Web site installed.
        2. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
        3. Expand the computer name, and then expand Web Sites.
        4. Right-click the Microsoft Dynamics CRM 4.0 Web site, click Stop, and then click Yes.

          Note By default, the name of the Microsoft Dynamics CRM 4.0 Web site is Microsoft Dynamics CRM.

        5. Right-click the Microsoft Dynamics CRM 4.0 Web site, and then click Properties. Click the Home Directory tab, click DefaultAppPool in the Application pool list, and then click Remove.
        6. Click the ISAPI Filters tab, click CRM.Default.Addon isapi, and then click Remove.
        7. Click OK.
        8. Expand Application Pools, right-click the Microsoft Dynamics CRM 4.0 application pool, click Delete, and then click Yes.

          Note By default, the name of the application pool is CRMAppPool.

        9. Close IIS Manager.

        Step 4: Delete the Microsoft Dynamics CRM program files and the Microsoft Dynamics CRM folders

        To do this, delete the following folder:

        Drive :P rogram FilesMicrosoft Dynamics CRM

        Notes

        Step 5: Delete the Active Directory security groups

        1. Log on to a domain controller as a user who has rights to delete the security groups.
        2. Click Start, point to All Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
        3. Expand the domain node.
        4. Expand the node of the organizational unit (OU) on which you install the Microsoft Dynamics CRM 4.0 server.
        5. Delete the following security groups:
          • PrivReportingGroup
          • PrivUserGroup
          • ReportingGroup
          • SQLAccessGroup
          • UserGroup

          To delete a security group, right-click the security group that you want to delete, and then click Delete.

        Note If there is more than one deployment of Microsoft Dynamics CRM 4.0 in the domain, you may have many security groups. To find the correct security group, follow these steps:

        1. Open SQL Server Management Studio, and then click New Query.
        2. Run the following statement against the MSCRM_Config database.
          select Id, DatabaseName, FriendlyName from Organization

        3. Note the ID of the first organization. The ID is used in the name of the security group.
        4. Find the security group in the Active Directory directory service. The name of the security group for the deployment contains the ID that you noted in step c earlier in this section.

        Step 6: Remove the SQL Server logins

        1. Log on to the computer that is running the instance of SQL Server 2005.
        2. Click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
        3. Expand the computer name, expand Security, and then expand Logins.
        4. Locate the following logins:
          • DomainNamePrivReportingGroup
          • DomainNameReportingGroup
          • DomainNameSQLAccessGroup

          Notes

          • The DomainName placeholder represents the actual name of the domain in which the logins are located.

          • To determine the groups that belong to the Microsoft Dynamics CRM deployment that you want to delete, compare the complete names of these groups to the names of the groups that exist in the Active Directory. By default, the Active Directory groups exist in the OU that was created by the Microsoft Dynamics CRM server installation program. The group names in the Logins folder of SQL Server Management Studio contain the name and a GUID.
        5. Delete the logins. To do this, right-click the login, click Delete, and then click OK.
        6. Close SQL Server Management Studio.

        Step 7: Remove the Microsoft Dynamics CRM subkeys

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

        322756

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

        How to back up and restore the registry in Windows

        1. Click Start, click Run, type regedit, and then click OK.
        2. Locate the following registry subkey:

          HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSCRM

        3. Right-click MSCRM, click Delete, and then click Yes.
        4. Locate the following registry subkey:

          HKEY_CLASSES_ROOTInstallerFeaturesC5D06E9536719E94DB7D0491EB205E22

        5. Right-click C5D06E9536719E94DB7D0491EB205E22, click Delete, and then click Yes.
        6. Locate the following registry subkey:

          HKEY_CLASSES_ROOTInstallerProductsC5D06E9536719E94DB7D0491EB205E22

        7. Right-click C5D06E9536719E94DB7D0491EB205E22, click Delete, and then click Yes.
        8. Locate the following registry subkey:

          HKEY_LOCAL_MACHINESOFTWAREClassesInstallerFeaturesC5D06E9536719E94DB7D0491EB205E22

        9. Right-click C5D06E9536719E94DB7D0491EB205E22, click Delete, and then click Yes.
        10. Locate the following registry subkey:

          HKEY_LOCAL_MACHINESOFTWAREClassesInstallerProductsC5D06E9536719E94DB7D0491EB205E22

        11. Right-click C5D06E9536719E94DB7D0491EB205E22, click Delete, and then click Yes.
        12. Locate the following registry subkey:

          HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerFolders

        13. Delete all the entries that begin with the following path:

          Drive :P rogram FilesMicrosoft Dynamics CRM

        14. Locate the following registry subkey:

          HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserData

        15. On the Edit menu, click Find.
        16. In the Find what box, type Microsoft Dynamics CRM, and then click Find Next.
        17. Right-click the GUID, and then click Delete. For example, the GUID may be C5D06E9536719E94DB7D0491EB205E22.
        18. To find the next entry to remove, press F3.
        19. Right-click the GUID, and then click Delete.
        20. Repeat steps 18 and 19 to delete all the entries that are in the components registry and in the products registry.
        21. Locate the following registry subkey:

          HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstallBC8DD950-8100-42F4-9EA9-26FCD41690AF

        22. Right-click BC8DD950-8100-42F4-9EA9-26FCD41690AF, click Delete, and then click Yes.

        Step 8: Use “Add or Remove Programs” to remove the application entry if the application entry still exists

        Note Although you cannot use Add or Remove Programs in Control Panel to uninstall the Microsoft Dynamics CRM 4.0 server, you can remove the entries from the Add or Remove Programs list.
        To do this, follow these steps:

        1. Click Start, point to All Programs, click Control Panel, and then click Add or Remove Programs.
        2. Click Microsoft Dynamics CRM 4.0 Server, click Remove, and then click Yes.

        Step 9: Delete the Microsoft Dynamics CRM server from the Start menu

        1. Start Windows Explorer, and then locate the following folder:

          Drive :D ocuments and SettingsAll UsersStart MenuPrograms

        2. Right-click the folder, and then click Delete.

        Step 10: Delete the Microsoft Dynamics CRM databases

        Warning After you complete this step, all the data that is maintained in Microsoft Dynamics CRM is removed. If you want to keep the data, you can skip this step.

        To delete the Microsoft Dynamics CRM databases, follow these steps:

        1. Log on to the server that is running SQL Server 2005 and on which the Microsoft Dynamics CRM 4.0 databases are installed.
        2. Click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click Microsoft SQL Server Management Studio.
        3. When you are prompted to connect to a server that is running SQL Server, enter the server on which the Microsoft Dynamics CRM 4.0 databases are installed in the Server name box, and then click Connect.
        4. Delete the configuration database.

          Note If you want to reinstall the Microsoft Dynamics CRM 4.0 server on this instance of SQL Server, you must delete this database.

          To delete the configuration database, expand Databases, right-click MSCRM_CONFIG, click Delete, and then click OK.

        5. Delete the organization database.

          Note If you want to use a different organization name when you reinstall the Microsoft Dynamics CRM 4.0 server, you do not have to do this step. After you reinstall the Microsoft Dynamics CRM server, you can use the Import Organization wizard in Deployment Manager to import the organization database.

          To delete the organization database, expand Databases, right-click OrganizationName_MSCRM, click Delete, and then click OK.

          Note The OrganizationName placeholder represents the actual organization name.

        6. Close SQL Server Management Studio.

        Step 11: Delete assemblies in the GAC

        1. Log on to the computer that has the Microsoft Dynamics CRM 4.0 server installed.
        2. Click Start, point to All Programs, point to Administrative Tools, and then click Microsoft .NET Framework 2.0 Configuration.
        3. In the Tasks area, click Manage the Assembly Cache, and then click View List of Assemblies in the Assembly Cache.
        4. In the Assembly Name pane, delete the following assemblies:
          • Microsoft.Crm
          • Microsoft.Crm.Admin.AdminService
          • Microsoft.Crm.ApplicationBuildUpgrade
          • Microsoft.Crm.DuplicateDetection
          • Microsoft.Crm.Faxes.FxsComWrapper
          • Microsoft.Crm.Entities
          • Microsoft.Crm.MetadataHelper
          • Microsoft.Crm.ObjectModel
          • Microsoft.Crm.Platform.Passport
          • Microsoft.Crm.Platform.Sdk
          • Microsoft.Crm.Platform.Server
          • Microsoft.Crm.Reporting
          • Microsoft.Crm.ReportingServices
          • Microsoft.Crm.Scheduling
          • Microsoft.Crm.Sdk
          • Microsoft.Crm.SdkProxy
          • Microsoft.Crm.SdkProxy.XmlSerializers
          • Microsoft.Crm.SdkTypeProxy
          • Microsoft.Crm.SdkTypeProxySerializers
          • Microsoft.Crm.SqlGovernor.Proxy
          • Microsoft.Crm.WebStore

          Note The names of these assemblies start with “Microsoft.Crm.”

          To delete the assemblies, click the assemblies that you want to delete, and then click Delete.

        After you complete these steps, you can reinstall the Microsoft Dynamics CRM 4.0 server.

        Note Before you reinstall the Microsoft Dynamics CRM 4.0 server, you must restart the Indexing service. Additionally, you must re-enable the Web site. Otherwise, you may receive an error message or a warning message in the Environment Diagnostics wizard when you reinstall the Microsoft Dynamics CRM server.

        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: 946980 – Last Review: August 10, 2012 – Revision: 5.0


        Applies to
        • Microsoft Dynamics CRM 4.0
        kbmbsinstallation kbexpertisebeginner kbmbsmigrate kbhowto kbexpertiseinter KB946980

        Other Support Sites

        Community

        Get Help Now

        Article Translations

        Read More:
        How to manually remove the Microsoft Dynamics CRM 4.0 server

        Users may receive and error importing a solution when an attribute’s length has been reduced in Microsoft Dynamics CRM 2011

        Users may receive the error below when importing a solution:

           ”Failure 0×80040203 Updating Attributename.subject.Length but it’s not valid for update. Original value:500. New value:400.”

        This is a built in feature that is designed to protect data integrity in the system. This is only enabled for fields that come out of the box.
        The steps below will resolve the issue:

        1. Within source environment for the customizations navigate to Settings, then click Customizations, then click Customize the System

        2. Select the entity where this attribute resides, and then select Fields

        3. Find the field in the list and double click to open the properties of the field

        4. Increase the length of the attribute to at least that of Original value from the error message

        5. Select Save on the attribute

        6. Select Save for the solution and then select Publish

        7. Export the customizations

        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: 2705886 – Last Review: August 10, 2012 – Revision: 2.0


        Applies to
        • Microsoft Dynamics CRM 2011

        More:
        Users may receive and error importing a solution when an attribute’s length has been reduced in Microsoft Dynamics CRM 2011

        How to use Access 2000 Upsizing Wizard

        This article shows you how to upsize a Microsoft Access
        database to the Microsoft SQL Server or to the Microsoft Data Engine (MSDE) by
        using the Access 2000 Upsizing Wizard. This article covers an introduction to
        the Upsizing Wizard, what to check before you upsize, design considerations,
        suggested troubleshooting techniques for common upsizing issues, and additional
        resources for information.

        Introduction

        You can use the Upsizing Wizard to convert an existing Access
        database (.mdb) to a client/server solution. The Upsizing Wizard creates a new
        SQL Server database structure (including indexes, validation rules, defaults,
        and relationships) and then copies your data to the new SQL Server database.
        Additionally, the Upsizing Wizard tries to re-create your queries as SQL Server
        views and as stored procedures.

        You can select to upsize only your
        database structure and your data, or, after you create the SQL Server back-end
        database, you can select to create an Access front-end client application. The
        Upsizing Wizard can create the front-end client application in either of two
        ways:

        • By keeping the current Access database file (.mdb) and then
          adding linked tables that connect to the upsized tables on the SQL
          Server.

          Your existing forms, reports, and data access pages use the
          newly linked tables as their data sources.

        • By creating a new Access project file (.adp) and then
          copying the forms, the reports, the data access pages, the macros, and the
          modules from the current Access database, and then connecting that Access
          project file to the upsized tables on the SQL Server.

          The copied
          forms, reports, and data access pages that refer to the local database are
          converted to use the newly upsized SQL Server tables, views, and stored
          procedures as their data sources through the connection of the ADP file to the
          server. Data access pages that refer to databases other than the current
          database are unchanged after upsizing.

        Note that when you run the Upsizing Wizard, this is not a
        perfect process. There are differences and potential incompatibilities between
        Access databases and SQL Server databases. Included are differences in SQL
        dialects and data types. Although the Wizard can handle many of these
        differences and still convert objects correctly, the Wizard cannot handle all
        differences. Therefore, you may experience problems while you create your new
        database and your new client application. If the Upsizing Wizard experiences a
        problem during the upsizing process, the Wizard does not stop the process. The
        Wizard records the error and then continues to work with the next object. After
        the upsizing process is complete, the Wizard displays a report. The report
        shows you the details of the process that include the name and the size of the
        new database, the selections that you made while you ran the Wizard, and any
        errors the Wizard experienced.

        For more information about how to run
        the Upsizing Wizard, follow these steps:

        1. Click Microsoft Access Help on the Help menu.
        2. Type Upsizing Wizard in the Office
          Assistant or the Answer Wizard.
        3. Click Search to view the topics that are returned.

        For more information about differences between Access syntax
        and SQL Server syntax and how the Upsizing Wizard handles these differences,
        follow these steps:

        1. Click Microsoft Access Help on the Help menu.
        2. Type Comparison of Microsoft Access and SQL
          Server syntax
          in the Office Assistant or the Answer
          Wizard.
        3. Click Search to view the Work with a Microsoft Access Project subtopic.

        What to Check Before You Upsize

        • Make sure that you have a backup copy of your Access
          database file (.mdb). The method that you select to upsize may change your
          existing application design.
        • Make sure that you know the name of the SQL Server or the
          computer that runs MSDE that you will connect to. Make sure that you know the
          logon information. For additional information about how to install MSDE, visit
          the “Installing MSDE” section of the MSDN Web site:
        • To make upsizing go as smoothly as possible, make sure that
          you have the appropriate access permissions on the SQL Server to which you want
          to upsize. At minimum, you must have CREATE TABLE permission. If you want to
          build a new database from scratch, you must have CREATE DATABASE
          permission.
        • To make sure that you have enough free space, calculate how
          much disk space upsizing will require by multiplying the size of your Microsoft
          Access database by two.
        • If you plan to upsize to SQL Server 2000, install the
          Office 2000 SR-1 Update and the Access 2000 and SQL Server 2000 Readiness
          Update before you start.

          For additional information about obtaining and
          about installing the Office 2000 SR-1 Update, click the following article number to view the article in the Microsoft Knowledge Base:

          245025

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

          How to obtain and install the Microsoft Office 2000 SR-1/SR-1a
          Update

           

        Database Design Considerations

        • You must follow server-based naming restrictions from the
          beginning. The Upsizing Wizard can correct many common mistakes, but not all
          mistakes. To make sure there is an easy migration to the back end, follow the
          SQL Server restrictions:
          • For SQL Server 6.5, names must be 30 characters or
            less. For SQL Server 7.0, this limit is expanded to a maximum of 128
            characters, and for SQL Server 2000 the limit is expanded to 249
            characters.
          • The first character must be a letter or the “at” sign
            (@). The remaining characters may be numbers, letters, the dollar sign ($), the
            number sign (#), or the underscore (_).
          • For SQL Server 6.5, no spaces are permitted. For SQL
            Server 7.0, spaces are permitted, but the name must be enclosed by quotation
            marks (“”) or by square brackets ([]).
          • The name must not be a Transact-SQL keyword. SQL Server
            reserves both the uppercase and the lowercase versions of keywords. For
            information about Transact-SQL keywords, see the SQL Server Books Online.
        • The Upsizing Wizard does not convert certain items. Other
          items are converted, but require verification after the Wizard has completed.
          When you use the Upsizing Wizard, you must review all changes made to tables,
          to views, to forms, and to reports.

          Specifically, the Upsizing Wizard
          uses the following rules when databases are converted:

          • Duplicate column names are given an alias.
          • Date delimiters are converted.
          • Boolean constants are converted to integers.
          • String concatenation is converted from an ampersand
            (&) to a plus sign (+).
          • Wildcard characters are converted to their appropriate
            Transact-SQL equivalents.
          • WITH TIES is added to all TOP queries that contain an
            ORDER BY clause.

          The following Access SQL syntax elements are not supported
          by MSDE and are not converted. The Upsizing Wizard removes these items from SQL
          statements:

          • DROP INDEX
          • DISTINCTROW
          • OWNERACCESS
          • Table in UNION
          • ORDER BY in Unions
          • TRANSFORM
          • PARAMETERS
        • The Upsizing Wizard does not convert your code of the
          Access solution. Code that works directly with Access objects may continue to
          work, but you must convert any Data Access Objects (DAO) code that works with
          tables and with queries to ActiveX Data Objects (ADO) code.

          For an
          overview of using ADO, visit the following MSDN Web site:

          For additional references about how you can use ADO, visit the
          following MSDN Web site:

        Troubleshooting Upsize Issues

        • Tables do not upsize.

          • Make sure that the default data file size for the Model
            database on the SQL Server is not larger than 1 MB.
          • Try to upsize just the table structure.
        • “Overflow” Error Message when trying to upsize to SQL
          Server 2000
        • Cannot upsize MDE to SQL Server or MSDE
        • Combo Box or List Box Empty after upsizeFor additional
          information about issues you may experience when you upsize to SQL Server 2000,
          click the article number below to view the article in the Microsoft Knowledge
          Base:
          269824

          (http://support.microsoft.com/kb/269824/EN-US/
          )

          ACC2000: Incompatibility Issues Between Access 2000 Projects and SQL Server 2000

        For additional information about upsizing, visit the
        following Microsoft Developer Network (MSDN) Web sites:

        For additional information about the Access 2000 Upsizing Tools White
        Paper, click the following article number to view the article in the Microsoft Knowledge Base:

        241743

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

        Access 2000 Upsizing Tools white paper available in Download
        Center

        For additional information about the Access
        2000 Upsizing Wizard, click the following article number to view the article in
        the Microsoft Knowledge Base:

        325019

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

        ACC2000: Issues with the Access 2000 Upsizing Wizard

        Article ID: 325017 – Last Review: August 10, 2012 – Revision: 4.0


        Applies to
        • Microsoft Access 2000 Standard Edition
        kbwizard kbfunctions kbdatabase kbdesign kbdownload kbhowtomaster KB325017

        View article:
        How to use Access 2000 Upsizing Wizard

        FIX: Incorrect HL7 ACK is generated when you use BizTalk Server 2010 Accelerator for HL7

        When you use Microsoft BizTalk Server 2010 Accelerator for HL7 (BTAHL7), the Acknowledgement (ACK) is generated is an incorrect format.

        For example, an ACK is generated in the following format:

        ERR||OBX_ObservationResult^9^23|HL7nnnn^Data type error^102|E||||||||^^^^^^^^^^^

        However, the correct format for an ACK is as follows:

        ERR||OBX ^9^23|102^Data type error^ HL70369|E||||||||^^^^^^^^^^^

        Notes

        • “OBX_ObservationResult” is an XML node name, not an HL7 identifier.
        • “HL7nnnn” should actually be the code “HL70369″.
        • The order of the fields in the ERR segment is incorrect. “HL7nnnn^Data type error^102″ should be “102^Data type error^ HL70369″.
        The issue occurs because of a product defect.
        This hotfix addresses the following three aspects of the issue:
        • The ACK has an HL7 identifier instead of an XML node name. For example, the ACK has “OBX” instead of “OBX_ObservationResult”.
        • The error information for the ERR segment is generated through the following guidelines:
        • The order of the fields in the ERR segment is incorrect. For example, “HL7nnnn^Data type error^102″ is changed to “102^Data type error^ HL7nnnn”.

        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.

        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, submit a request to 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 website:

        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

        You must have BTAHL7 installed to apply this hotfix. Additionally, you must apply the hotfixes that are described in the following Microsoft Knowledge Base (KB) articles:

        2564013

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

        FIX: A hotfix is available that provides additional Delivery Mode properties for the Minimal Lower Layer Protocol send and receive adapters in BizTalk Accelerator for HL7 in a BizTalk Server 2010 environment

        2607536

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

        FIX: Hotfix adds support to HL7 v2.5.1 message processing and fixes several issues in BizTalk Server 2010 Accelerator for HL7

        Restart requirement

        After you apply this hotfix, you may have to restart the computer. If you are not prompted to restart the computer, you must restart the BizTalk host instance services.

        Installation Instructions

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

        322756

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

        How to back up and restore the registry in Windows

        If the current hotfix is needed and BTAHL7 generates an ACK according to the modified schema, you must follow these steps in addition to installing the hotfix. If the hotfix is not needed, for example BTAHL7 generates an ACK that does not have the similar symptom that is described in the “Symptoms” section, you do not have to follow these steps.

        Note The following procedure requires setting a new registry key, rebuilding BTAHL7V2XCommon Project with the modified schemas, and then redeploying the project. If those schemas are referred to in any other projects, it also requires rebuilding and redeploying those projects.

        1. Stop the BizTalk Server host instances.
        2. Redeploy BTAHL7V2XCommon Project with the new modified schemas. To do this, perform the following actions:
          • Rename ACK_24_GLO_DEF_949029 in %Microsoft BizTalk 2010 Accelerator for HL7TemplatesSchemasV2.X2.4 as ACK_24_GLO_DEF
          • Rename ACK_25_GLO_DEF_949029 in %Microsoft BizTalk 2010 Accelerator for HL7TemplatesSchemasV2.X2.5 as ACK_25_GLO_DEF

          Notes

          • If BTAHL7V2XCommon Project is already deployed, undeploy the project, and then build and redeploy the project.
          • If these schemas are referred to in any other projects, the procedure also requires rebuilding and redeploying those projects with these modified schemas.
        3. Create a registry entry of type DWORD with the name “UseModifiedAck” in the following registry subkey:
        4. If the hotfix is needed and step 2 is finished, set the newly created registry key value to 1. If the registry key is not available or the value is set to a value other than 1, BTAHL7 will generate an ACK that does not have symptoms similar to what are described in the “Symptoms” section (this procedure is performed in order to make sure that the existing customer solutions are not disturbed). Therefore, in case the modified schemas are not deployed (step 2 is not finished), set the registry key value to another value that is not 1. If the modified schemas are deployed (step 2 is finished), make sure that you set the registry key to 1.
        5. Restart the BizTalk Server host instances.

        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 Platform
        Microsoft.solutions.btahl7.pipelinecommon.dll 3.9.559.2 90,528 13-Jul-2012 17:41 x86
        Microsoft.solutions.btahl7.pipelinemessagecore.dll 3.9.559.2 86,448 13-Jul-2012 17:41 x86
        Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
        For more information about BizTalk Server hot fixes, click the following article number to view the article in the Microsoft Knowledge Base:
        2003907

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

        Information about BizTalk hotfixes and service pack support

        Article ID: 2713884 – Last Review: August 10, 2012 – Revision: 1.0


        Applies to
        • Microsoft BizTalk Server Branch 2010
        • Microsoft BizTalk Server Developer 2010
        • Microsoft BizTalk Server Enterprise 2010
        • Microsoft BizTalk Server Standard 2010
        kbsurveynew kbexpertiseadvanced kbhotfixserver kbautohotfix kbqfe kbfix KB2713884

        Visit site:
        FIX: Incorrect HL7 ACK is generated when you use BizTalk Server 2010 Accelerator for HL7

        Full-file version update may request Office source files

        When you install a full-file version of a Microsoft Office service pack, hotfix, or update, you may be prompted to provide the source files from where you first installed your Office programs. When this problem occurs, you can either provide the source files, or you may be able to update the modified date of the Office files that is causing the Microsoft Windows Installer to prompt you for the source files.

        When you install a full-file version service pack, update,
        or hotfix to a Microsoft Office 2000 program, to a Microsoft Office XP program,
        or to a Microsoft Office 2003 program, you may be prompted to provide the
        original source media CD-ROM or the path of the administrative installation
        point (AIP) where you installed from. This behavior may occur so that the
        Office files that are not included in the update can be replaced on the client
        computer.

        During a typical update installation, if a file is
        determined to have changed, the Windows Installer program may present a dialog
        box to you that contains the following message:

        The
        feature you are trying to use is on a CD-ROM or other removable disk that is
        not available.

        This request for source files indicates that a valid
        source is not currently available to the computer that is being
        updated.

        Note For Office 2003, if a Local Install Source (LIS) is available,
        you do not receive a request to provide the source installation files during
        the update process because an LIS contains a compressed version of all the
        required files that Office 2003 requires.

        For more information about Local Install Source, click
        the following article number to view the article in the Microsoft Knowledge
        Base:

        825933

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

        Local Install Source
        (Msocache)

        There are several likely causes for original Office files
        that are installed on a client computer to be changed in some way. During the
        updating process, the Windows Installer tries to verify that existing Office
        files have not changed. The Windows Installer program uses the following
        criteria to verify existing files:

        • The file version.
        • The file modified date and size.
        • The Cyclical Redundancy Check (CRC).
        • The file hash for unversioned files.
        • The file language.

        If any one of the file criteria does not match what the Windows
        Installer program expects to find based on the information that is stored in
        the current Office Windows Installer database, a request for the Office source
        files may occur.

        Note See the “More Information” section for one known cause when
        multiple versions of Office are installed on the same
        computer.

        Possible reasons that the original Office source files may
        not be available include the following:

        • The original Office CD-ROM is not readily
          available.
        • The Office CD-ROM store keeping unit (SKU) does not match
          the installed product (such as Standard edition verses Professional
          edition).
        • The MSI package file name may be changed (such as Pro.msi
          may have been changed to Data1.msi).
        • The network file share (AIP) location may have
          changed.
        To work around this problem, use one of the following
        methods.

        Method 1: Provide the Office source files

        When you install an update to an Office program, you must provide
        the Office source files (CD-ROM or administrative installation point) from
        where you originally installed Microsoft Office to make sure that all Office
        files are complete.

        Note For Microsoft Office 2000, the update that is described in the
        following article in the Microsoft Knowledge Base will help reduce the need to
        provide source files during an Office update:

        835220

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

        Description of the Office 2000 Update: February 10,
        2004

        Method 2: Manually change the modified dates of certain Office files

        Sometimes you may be able to manually change the modified date of
        the file that the Windows Installer program has identified as changed. After
        you update the modified date of the file, the Windows Installer program will
        consider the file as ‘user data’. A file that is considered ‘user data’ will
        not cause the Windows Installer program to request the Office source
        files.

        A partial list of the shared files that may be considered ‘user
        data’ during typical use of an Office program include the following files:

        • Access9.mdb
        • Ctryinfo.txt
        • Excel9.xls
        • Outlook.hol
        • Pwrpnt9.pot
        • Pwrpnt10.pot
        • XL8Galry.xls
        • Winword8.doc
        • Readme.txt

        To determine the Office file that the Windows Installer has
        determined must be changed, you must review the verbose log of the update
        installation.

        There are two ways to turn on verbose logging before you
        start the update process for your Office programs.

        • Use Regedit. To use Regedit, follow these steps:

          1. Click Start, and then click
            Run.
          2. In the Open box, type
            regedit, and then click
            OK.
          3. In Registry Editor, locate, and then click the
            following key:

            HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftWindowsInstaller

          4. With Installer selected, point to New
            on the Edit menu, and then click String
            Value
            .
          5. Type Logging, and then press
            ENTER.
          6. With Logging selected, click
            Modify on the Edit menu.
          7. In the Value data box, type
            voicewarmup, and then click
            OK.
          8. With Installer selected, point to
            New on the Edit menu, and then click
            DWORD Value.
          9. Type Debug, and then press
            ENTER.
          10. With Debug selected, click
            Modify on the Edit menu.
          11. In the Value data box, type
            7, click Hexadecimal, and then click
            OK.
          12. On the File menu, click
            Exit to quit Registry Editor.
        • Use the Group Policy editor (Local Machine). To use the
          Group Policy editor, follow these steps:

          1. Click Start, and then click
            Run.
          2. In the Open box, type
            gpedit.msc, and then click OK.
          3. In the Group Policy editor, under Local
            Computer Policy
            , expand Computer
            Configuration
            .
          4. Expand Administrative
            Templates
            .
          5. Expand Windows Components.
          6. Select Windows Installer.
          7. In Windows Installer, select
            Logging.
          8. On the Action menu, click
            Properties.
          9. On the Settings tab of the
            Logging Properties dialog box, click
            Enabled.
          10. In the Logging box, type
            voicewarmup, and then click
            OK.
          11. On the File menu, click
            Exit to close the Group Policy editor dialog
            box.

        After you turn on verbose logging and you install an Office
        update, a log file may be created that identifies the Office files that have
        changed.

        To locate and to change the modified date of the files that
        the Windows Installer program has determined to have changed, follow these
        steps:

        1. Find the Office update verbose log file that is located in
          the user’s Temp folder. To find the user’s
          Temp folder, follow these steps:

          1. Click Start, and then click
            Run.
          2. In the Open box, type
            %temp%, and then click OK.

          The path of the user’s Temp
          folder should be similar to the following:

          C:Documents and SettingsusernameLocal SettingsTemp

          The Office update verbose logs will have file names that are
          similar to Msi#####.log, where the # (number
          sign) represents any alpha/numeric character. For example, a verbose log file
          could have the following file name:

          Msi7b3d5.log

          Note If the OHotfix.exe bootstrapping application utility is used for
          updates, the log files are stored in the following folder:

          C:Documents and SettingsusernameLocal SettingsTempOhotfix

          The update log files are created in two set pairs with a naming
          convention of OHotfix(00001).log and
          OHotfix(00001)_Msi.log.

          For more information about
          the OHotfix.exe utility, visit the following Microsoft Web site:

        2. Check the timestamp of the log file to make sure that you
          have found the correct log file that was created for the latest update attempt
          because there may be many log files in the folder. To check the timestamp of
          the log file, right-click the log file, and then click
          Properties.
        3. Double-click the log file to open the file in your default
          text editor (such as Notepad).
        4. On the Edit menu, click
          Find.
        5. In the Find what box, type
          Resolving source, and then click Find
          Next
          .
        6. The line in the log file immediately above the words
          “Resolving source” will show the Office file that the Windows Installer program
          has determined was changed.

          Note The following example shows that the file Readme.txt has changed
          and will cause the Windows Installer program to prompt you for the Office
          source files:

          MSI (s) (B0:2C): File: C:Program FilesCommon FilesMicrosoft
          SharedSnapshot ViewerREADME.TXT;  Overwrite;  No patch;
          Existing file is unversioned and unmodified - hash doesn't
          match source file
          MSI (s) (B0:2C): Resolving source.
        7. To change the modified date of the files listed in the log
          file, follow these steps:

          1. Click Start, and then click
            Search.
          2. Click All files and
            folders
            .
          3. In the All or part of the file name
            box, type the file name of the file that you found in the log file.
          4. In the Look in box, click your local
            hard disk drive.
          5. Click Search.
          6. Double-click the found file.
          7. After the file has opened, close the file without
            making any changes to the file.
          8. You may have to repeat steps 7a to 7g several
            times.

        After each files modified date is changed, the Windows Installer
        program will not prompt you for the source Office files because each file will
        be considered ‘user data’ by the Windows Installer program.

        Microsoft has also determined that when you have multiple
        versions of Office installed on a computer, some shared files such as
        Excel9.xls or Xl8galry.xls may be overwritten by older files, depending on the
        version of the Office program that was installed last.

        For example, if
        Office 2000 and Office XP are both installed, when you perform a repair of
        Excel 2000, the earlier Excel9.xls file may be copied to the
        C:WindirShellnew folder. When you try to install
        an update for an Office XP program, this earlier unversioned Office 2000 file
        may show to have a hash that does not match the correct file hash for the
        Excel9.xls file from the Office XP source files.

        For more information, click the following article number to
        view the article in the Microsoft Knowledge Base:
        297168

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

        How to programmatically update the source list for an installed Windows
        Installer package

        828451

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

        Service packs, updates, and security patches may require the Office XP
        CD-ROM

        828450

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

        Why service packs, updates, and security patches may require the Office 2000
        CD-ROM

        330043

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

        The “Microsoft Office XP Update Deployment” white paper is available at the Download
        Center

        830168

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

        Frequently
        asked questions about the Local Install Source feature in Office 2003

        For more information about file versioning, visit
        the following Microsoft Web site:

        Article ID: 840169 – Last Review: August 9, 2012 – Revision: 4.0


        Applies to
        • Microsoft Office Access 2003
        • Microsoft Access 2002 Standard Edition
        • Microsoft Access 2000 Standard Edition
        • Microsoft Excel 2002 Standard Edition
        • Microsoft Excel 2000 Standard Edition
        • Microsoft FrontPage 2002 Standard Edition
        • Microsoft FrontPage 2000 Standard Edition
        • Microsoft Office Outlook 2003
        • Microsoft Outlook 2002 Standard Edition
        • Microsoft Outlook 2000 Standard Edition
        • Microsoft Office PowerPoint 2003
        • Microsoft PowerPoint 2002 Standard Edition
        • Microsoft PowerPoint 2000 Standard Edition
        • Microsoft Office Publisher 2003
        • Microsoft Publisher 2002 Standard Edition
        • Microsoft Publisher 2000 Standard Edition
        • Microsoft Word 2002
        • Microsoft Word 2000
        • Microsoft Office Professional Edition 2003
        • Microsoft Office Basic Edition 2003
        • Microsoft Office Small Business Edition 2003
        • Microsoft Office 2000 Premium Edition
        • Microsoft Office 2000 Professional Edition
        • Microsoft Office 2000 Standard Edition
        • Microsoft Office 2000 Small Business Edition
        • Microsoft Office 2000 Developer Edition

        Other Support Sites

        Community

        Get Help Now

        Article Translations

        Related Office 2000 Web Sites

        Read more here:
        Full-file version update may request Office source files

        Page 322 of 734« First...102030...320321322323324...330340350...Last »

        Recent Comments

          Archives

          Categories