Microsoft Knowledge Base Wiki

Cause 1

The ODBC is set up incorrectly. See “Resolution 1” in the “Resolution” section.

Cause 2

The user is not assigned to the correct roles in SQL. See “Resolution 2” in the “Resolution” section.
Note This applies to FRx for Microsoft Dynamics AX only.

Cause 3

The OFSI dll file is the incorrect version. See “Resolution 3” in the “Resolution” section.
Note This file will have a different name depending on the accounting system you are using in FRx.

Microsoft Dynamics GP – FSGreatPlains61.dll

Microsoft Dynamics AX – FSAxapta40.dll

Microsoft Dynamics SL – FSSolIV451.dll

Microsoft Dynamics NAV – FSFDM70.dll

Microsoft Dynamics GP with Analytical Accounting – FSAA80.dll

Cause 4

The Sales Tax option is not enabled in Microsoft AX. See “Resolution 4” in the “Resolution” section.
Note This applies to FRx for Microsoft Dynamics AX only.

Resolution 1

Check the settings for the ODBC by completing the following steps.

1. Start FRx.
2. Click Company and then click Information.
3. Select your company.
4. Click the System Specific Information tab.
5. Click Define.
   In the ODBC Data Source Administrator window, click the System DSN tab.
6. Click the ODBC that you are using for FRx, and then click Configure.
7. Click Next.
8. Click With SQL Server authentication. Type the sa user ID and password. Click Next.
9. Clear both of the ANSI options, and then click Next.
10. Click Finish.
11. Click Test Data Source.
12. Click OK, and then close the ODBC configuration window.
13. Set the company as default.

Resolution 2

The user needs the correct access to the SQL database.

1. Start SQL Server Management Studio.
2. Expand Security and then expand Logins.
3. Right-click the user ID that you log on to FRx with, and then click Properties.
4. Click User Mapping.
5. Click the database that the FRx company is connected to.
6. In the Database role membership section, click the following:
   • FRx Role
   • public
   • db_datareader
7. Click OK.

Resolution 3

Reinstall or update to the latest FRx service pack.Download the latest service pack for Microsoft FRx 6.7. To do this, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Microsoft Dynamics GP

https://mbs.microsoft.com/partnersource/downloads/servicepack/frx67gpoverview.htm

(https://mbs.microsoft.com/partnersource/downloads/servicepack/frx67gpoverview.htm)

Microsoft Dynamics SL

https://mbs.microsoft.com/customersource/support/downloads/servicepacks/frx67soloverview.htm

(https://mbs.microsoft.com/customersource/support/downloads/servicepacks/frx67soloverview.htm)

https://mbs.microsoft.com/partnersource/downloads/servicepack/frx67soloverview.htm

(https://mbs.microsoft.com/partnersource/downloads/servicepack/frx67soloverview.htm)

Microsoft Dynamics AX

https://mbs.microsoft.com/partnersource/downloads/servicepack/frx67axaptaoverview.htm

(https://mbs.microsoft.com/partnersource/downloads/servicepack/frx67axaptaoverview.htm)

Microsoft Dynamics NAV

To obtain the latest service packs for Microsoft Dynamics NAV, customers must contact their partner.

https://mbs.microsoft.com/partnersource/downloads/servicepack/frx67navoverview_eng.htm

(https://mbs.microsoft.com/partnersource/downloads/servicepack/frx67navoverview_eng.htm)

Microsoft Small Business Financials

https://mbs.microsoft.com/customersource/support/downloads/servicepacks/frx67sbfoverview.htm

(https://mbs.microsoft.com/customersource/support/downloads/servicepacks/frx67sbfoverview.htm)

https://mbs.microsoft.com/partnersource/downloads/servicepack/frx67sbfoverview.htm

(https://mbs.microsoft.com/partnersource/downloads/servicepack/frx67sbfoverview.htm)

Resolution 4

Starting in FRx Service Pack 8, FRx reads from the following columns in the LedgerBalancesDimTrans table:

Debitoprmst

Creditoprmst

Debittaxmst

Credittaxmst

These columns are only included if the Sales Tax option is enabled. To enable this option, follow these steps:

1. Start Microsoft Dynamics AX.
2. Click Administration.
3. Click Setup, and then click System.
4. Click Configuration, and then click General Ledger.
5. Select Sales Tax.

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Article ID: 951783 – Last Review: January 29, 2013 – Revision: 3.0

1. Uninstall the FOPE Directory Sync Tool.
2. Locate the folder or the path of the location where the tool is installed. Then, manually delete all the folders and subfolders that are related to the installation of the tool.
3. Reinstall the tool, and then try again.

If the issue persists after you reinstall the tool, contact Technical Support. Information about how to contact Technical Support is located in the Resources area on the Information tab of the FOPE Administration Center.

Article ID: 2642716 – Last Review: January 29, 2013 – Revision: 7.0

Step 1: Prepare to replace the existing mailbox

Export the contents of existing mailbox to a .pst file for backup. To do this, follow these steps:

1. Ask the user to make sure that any items that are created on mobile devices or other mail clients are synchronized to the mailbox.
2. Export the whole contents of the mailbox to a .pst file for backup.

   Note This may take some time for larger mailboxes. The time that it takes varies based on mailbox size, network conditions, and local computer performance.

3. In Microsoft Outlook, on the File menu, click Account Settings, and then click the Data Files tab. Click the backup .pst file, and then click Remove.
4. Exit all Outlook clients that access the user’s mailbox.

Step 2: Rename the existing mailbox

Important These steps will not work if directory synchronization is enabled.

To rename the existing mailbox, follow these steps:

1. Sign in to the Office 365 portal (http://portal.microsoftonline.com

   (http://portal.microsoftonline.com)

   ) as an admin.

2. In the header, click Admin, and then under Management in the left navigation pane, click Users.
3. In the list of users, click the user whose mailbox you want to re-create, and then click Details. In this example, the user name is “John Smith”.
4. In the Display name box, change the display name of the user, and then click Save.

   For example, change “John Smith” to “John Smith2″. Changing the user name in the portal also changes all other values for the user except for the proxy email addresses.

5. Click More, and then click Change mailbox settings.
6. Expand E-Mail Options. In the Other e-mail addresses box, delete or change the other email addresses, as needed, and then click Save.
7. Click Save again to return to the Users page.

Step 3: Create a new mailbox

Create a new user account. This new user account replaces the existing user account. To do this, follow these steps:

1. In the header, click Admin, and then under Management in the left navigation pane, click Users.
2. On the Users page of the Office 3365 portal, click New, click User, and then follow the on-screen instructions to create a new user account.

   For example, create a new user account that’s named “John Smith”. This is considered a new user account because the original user account that was named “John Smith” was renamed to “John Smith2″ in step 2.

   Note You may get an “A user with this name already exists. Use a different name” error message. If you do get this error message, you have to wait for the changes that were made to the original account to replicate throughout the service before you can create the new user account. Also, check to make sure that the proxy addresses are updated because this error message can occur if there’s a conflict with a proxy address.

Step 4: Assign permissions to the new mailbox

To assign permissions to the new mailbox, follow these steps:

1. Connect to Exchange Online by using Windows PowerShell. For more info about how to do this, go to the following Microsoft website:
2. Assign the user Full Access permission to the new mailbox. For example, to assign John Smith Full Access to the John Smith2 mailbox, run the following command.

   Add-MailboxPermission -Identity "John Smith 2" -User "John Smith" -AccessRights FullAccess -InheritanceType All

Step 5: Copy the contents of the original mailbox to the new mailbox

To copy the contents of the original mailbox to the new mailbox, follow these steps:

1. Create a new Outlook profile that opens the new mailbox by using an Exchange (MAPI) account. 
2. Start Outlook and open the new mailbox.
3. Add the original mailbox as an IMAP email account to the profile. For more info about how to do this, go to the following Microsoft website:For example, add the John Smith 2 mailbox as an IMAP email account to the profile.
4. When Outlook is open and both mailboxes can be accessed, select all the messages in the Inbox folder of the IMAP account and copy them to the Inbox folder of the Exchange (MAPI) account.

   Note This performs a MIME-to-MAPI conversion, which should fix most item-level corruption of the messages.

5. Repeat step 4 for each folder in the mailbox.
6. When you finish copying all folders to Exchange (MAPI) account, remove the IMAP account from the profile.
7. In the same profile, open the original mailbox that was renamed in step 2  as an Exchange mailbox, and then drag the Calendar, Contact, Notes and any other non-mail items from the original mailbox to the new mailbox. 

   For example, open the John Smith 2 mailbox, and then drag non-mail items from the John Smith 2 mailbox to the John Smith mailbox.

Important Any recurring meeting request in the original mailbox could potentially become orphaned if it leaves the Exchange store and if it’s copied or moved to a .pst file. If the user has a large number of meeting requests in his or her Calendar, the user may want to test the process by using a few meetings and confirm that the meetings can be  updated correctly before proceeding further. If the links to the original meeting request are orphaned, an update from the organizer will create a new item in the recipient’s calendar. However, the original item remains at the original date and time.

Article ID: 2804607 – Last Review: January 29, 2013 – Revision: 2.0

For example, in Excel if you go to Insert, and then click on Hyperlink the user is prompted to select the file. If the user navigates to a file residing on a Network Mapped Drive, and inserts a hyperlink to that file, the hyperlink will be created to the file via its UNC path instead of its network mapped drive path. After the link has been inserted, the user can then hover over the link and see that the full UNC path has been used when creating the link to the file.

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

Description of link management and storage in Excel

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2808316 – Last Review: January 28, 2013 – Revision: 1.0

Symptom 1

You try to set up Enhanced Intrastat for a Belgian company in Microsoft Dynamics GP 9.0 or in Microsoft Business Solutions – Great Plains 8.0. To do this, you perform the following actions:

• On the Tools menu, you point to Setup, you point to Company, and then you click Intrastat Setup.
• In the Country Code field, you type BE.
• In the Tax Registration Number field, you type a valid VAT registration number for Belgium.
• You enter any other required details.
• You click Save.

When you do this, you receive the following error message:

Symptom 2

You try to enter Intrastat details for an European Union (EU) transaction in the Sales Transaction Entry window in the Sales Order Processing module in Microsoft Dynamics GP 9.0 or in Microsoft Business Solutions – Great Plains 8.0. To do this, you perform the following actions:

1. On the Transaction menu, you point to Sales, and then you click Sales Transaction Entry.
2. You enter the appropriate type transaction with Intrastat for a Belgian customer.
3. You click Intrastat to open the Sales Intrastat Entry window.
4. You complete all required information. This information includes a valid VAT registration number for a Belgian customer.
5. You click OK.

When you do this, you receive the following error message:

Symptom 3

You try to enter Intrastat details for an EU transaction in the Transaction Entry window in the Receivables Management module in Microsoft Dynamics GP 9.0 or in Microsoft Business Solutions – Great Plains 8.0. To do this, you perform the following actions:

1. On the Transactions menu, you point to Sales, and then you click Transaction Entry.
2. You enter the appropriate document type transaction with Intrastat for a Belgian customer.
3. You click to select the EU Transaction check box, and then you complete all other required information.
4. You click Intrastat, and then you enter all required information. This information includes a valid VAT registration number for a Belgian customer.
5. You click Save.

When you do this, you receive the following error message:

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Microsoft Dynamics GP 9.0. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Partners

Customers

Hotfix information

A supported hotfix is now available from Microsoft. The hotfix corrects the problem that is described in this article. Apply the hotfix only to systems that are experiencing this specific problem.

To resolve this problem immediately, contact your Microsoft Dynamics partner or Technical Support for Microsoft Dynamics and related products to obtain the hotfix. If you have access to online assisted support you can log on to the Microsoft Dynamics site and create a new support request. To do this, visit the following Microsoft Web site:

You can also contact Technical Support for Microsoft Dynamics and related products by telephone. To do this, visit the following Microsoft Web site:

Partners

CustomersIn special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

To apply this hotfix, you must have one of the following Enhanced Intrastat versions installed:

• Enhanced Intrastat release 9.00.0037
• Enhanced Intrastat release 8.0.11

Installation information

To apply this hotfix, follow these steps:

1. Copy the EnhIntra.cnk file to the Microsoft Dynamics GP or Microsoft Business Solutions – Great Plains installation folder on the computer.
2. Start Microsoft Dynamics GP 9.0 or Microsoft Business Solutions – Great Plains 8.0.
3. Click Yes when you are prompted to include new code.
4. Log on to Microsoft Dynamics GP 9.0 or Microsoft Business Solutions – Great Plains 8.0 as the sa user.

Removal information

You cannot remove this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix.

Article ID: 953281 – Last Review: January 28, 2013 – Revision: 4.0

Service pack information

Service packs are cumulative. This means that the problems that are fixed in a service pack are also fixed in later service packs. For example, Microsoft Dynamics GP 9.0 Service Pack 4 contains all the fixes that are included in Microsoft Dynamics GP 9.0 Service Pack 1, Service Pack 2, and Service Pack 3. You do not have to install an earlier service pack before you install Microsoft Dynamics GP 9.0 Service Pack 4. For more information about the fixes that are included and installation information that is not included in this article, refer to the Installation Guide that is included with this service pack.

Problems that are resolved in this service pack

The following is a list of some problems that are corrected and some updates in the English version of Microsoft Dynamics GP 9.0 Service Pack 4.

Service pack replacement information

For more information about the previous hotfix rollup packages, click the following article numbers to view the articles in the Microsoft Knowledge Base:

Installation information

To download Microsoft Dynamics GP 9.0 Service Pack 4, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Partners

Customers

For more information about how to obtain Microsoft Dynamics GP service packs, click the following article number to view the article in the Microsoft Knowledge Base:

For installation information, see the 9.0SP4_Installation_Guide_ENUS.pdf file that is included together with Service Pack 4.

If you have questions about the service pack installation, contact Technical Support for Microsoft Dynamics. Log on to the Microsoft Dynamics Support Web site, and then enter a new support request. To do this, visit the following Microsoft Web site:

As the subcategory selection, select INSTALL-SQL or INSTALL-MSDE.

You can also contact Technical Support for Microsoft Dynamics by telephone at (888) 477-7877. Use Quick Access Code 6762 for SQL Server Desktop Engine (also known as MSDE 2000). Or, use Quick Access Code 6731 for Microsoft SQL Server.

Prerequisites

Before you install a service pack, follow these steps:

1. Perform a SQL Server database backup of all Microsoft Dynamics GP 9.0 databases.
2. Back up all modified dictionary files, such as the Reports.dic file and the Forms.dic file.
3. Have all users exit Microsoft Dynamics GP 9.0.

Removal information

You cannot remove this service pack.

Restart information

No restart is required.

File information

The English version of this service pack 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.

Article ID: 955672 – Last Review: January 28, 2013 – Revision: 4.0

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

INFO: Roadmap for ADO.NET

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

INFO: Roadmap for XML Integration with ADO.NET

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

INFO: Roadmap for Using ADO in .NET

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

INFO: Roadmap for XML Serialization in the .NET Framework

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

HOW TO: Update Server Data Through a Web Service by Using ADO.NET and Visual Basic .NET

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

HOW TO: Use a Web Service as a Data Source for a Client Application in Visual Basic .NET

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

HOW TO: Create and Test an XML Web Service in Visual Basic .NET

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

HOW TO: Write a Simple Web Service by Using Visual C# .NET

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

HOW TO: Build and Use XML Web Services by Using Visual Studio .NET

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

HOW TO: Integrate an Apache SOAP 2.2 Client with a .NET XML Web Service

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

HOW TO: Write a Simple Web Service by Using Visual Basic .NET

Microsoft has released an update to Microsoft Office XP. This update contains important security and stability enhancements in the Microsoft Script Editor and may require that you restart your computer.

Note After you install this update, you must be a member of either the
Administrators group or of the Debugger Users group to perform script
debugging. This behavior is by design and is the result of a security
enhancement.

How to download and to install the update

Important Before you install this update, make sure that you meet the
following requirements:

• Microsoft Windows Installer 2.0
  Before you install this
  update, you must install Windows Installer 2.0 or later. For additional
  information about this requirement, see the “Windows Installer update
  requirements” section of this article.
• Office XP Service Pack 3 (SP3)
  Before you install this
  update, install Office XP SP-3.

  For additional information about how to install
  Office XP Service Pack 3, click the following article number to view the
  article in the Microsoft Knowledge Base:

  832671

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

  Description of Microsoft Office XP Service Pack 3

Client update

If you installed Microsoft Office from a CD-ROM, you have the
following two options:

• Use the Microsoft Office Update Web site to automatically
  install all the latest updates that include all available service packs and
  public updates.
• Install only the Office XP Update: KB833858 by following
  the steps that are described later in this article.

Note Microsoft recommends that you install the client update by using
the Office Update Web site. The Office Update Web site detects your particular
installation of Office and prompts you to install exactly what you must have to
make sure that your Office installation is completely up-to-date.

Office Update Web site

To have the Office Update Web site detect the required
updates that you must install on your computer, visit the following Microsoft
Web site:

Click Check for Updates. After detection is
complete, you receive a list of recommended updates for your approval. Click
Start Installation to complete the process.

Install only the Office XP Update: KB833858

To download and install the client update, follow these
steps:

1. The
   following file is available for download from the Microsoft Download
   Center:

   Collapse this imageExpand this image

   Download
   the English version of the Office XP Update: KB833858 client package
   now.

   (http://download.microsoft.com/download/2/5/7/25750DD8-E66E-4099-95B4-216C0542D2F1/officexp-kb833858-client-enu.exe)

   Release Date: March
   23, 2004

   For additional information about how to download Microsoft
   Support files, click the following article number to view the article in the
   Microsoft Knowledge Base:

   119591

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

   How to Obtain Microsoft Support Files from Online Services

   Microsoft scanned this file for viruses. Microsoft used the most
   current virus-detection software that was available on the date that the file
   was posted. The file is stored on security-enhanced servers that help to
   prevent any unauthorized changes to the file.
   
   Note To obtain a localized client version of the Office XP Update:
   KB834691, visit the following Microsoft Web site:

2. Click Open to start the download and
   installation of the Office XP Update: KB833858.
3. If you are prompted to install the update, click
   Yes.
4. Click Yes to accept the license
   agreement.
5. Insert your Office XP CD-ROM if you are prompted to do so,
   and then click OK.
6. When you receive a message that indicates the installation
   was successful, click OK.

Note After you install the update, you cannot remove it. To revert to
an installation before the update was installed, you must remove Office XP, and
then install it again from the original CD-ROM.

Administrative update

If you installed your Office XP product from a server location,
the server administrator must update the server location with the
administrative update and deploy that update to your computer.

If you
are the server administrator, follow these steps to download the administrative
update:

1. In Microsoft Windows Explorer, create a folder on drive C,
   and then name the folder kb833858.
2. The
   following file is available for download from the Microsoft Download
   Center:

   Collapse this imageExpand this image

   Download
   the English version of the Office XP Update: KB833858 full file package
   now.

   (http://download.microsoft.com/download/2/5/7/25750DD8-E66E-4099-95B4-216C0542D2F1/officexp-kb833858-fullfile-enu.exe)

   Release Date: March
   23, 2004

   For additional information about how to download Microsoft
   Support files, click the following article number to view the article in the
   Microsoft Knowledge Base:

   119591

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

   How to Obtain Microsoft Support Files from Online Services

   Microsoft scanned this file for viruses. Microsoft used the most
   current virus-detection software that was available on the date that the file
   was posted. The file is stored on security-enhanced servers that help to
   prevent any unauthorized changes to the file.
   

3. Click Save to save the update installation
   file (for example, Officexp-kb833858-fullfile-enu.exe) to the kb833858
   folder.
4. Click Start, and then click
   Run.
5. In the Open box, type
   cmd, and then click OK.
6. At the command prompt, type the following lines, and then
   press ENTER after each line:
   cd kb833858

   Officexp-kb833858-fullfile-enu.exe /c /t:c:kb833858

7. Click Yes to accept the license
   agreement.
8. If you are familiar with the procedure for updating your
   administrative installation, click Start, and then click
   Run. Type the following command in the Open
   box:

   msiexec /a AdminPathMSI File /p C:kb833858MSP FileSHORTFILENAMES=TRUE

   In this command, Admin Path is the path
   of your administrative installation point for Office XP (for example,
   C:OfficeXP), MSI File is the .msi database package
   for the Office XP product (for example, ProPlus.msi), and MSP
   File is the name of the administrative update.

   Note You can append the /qb+ switch to the command line so that the Office XP
   Administrative Installation dialog box and the End User
   License Agreement dialog box do not appear.

9. To deploy the update to the client workstations, click
   Start, and then click Run. Type the following
   command in the Open box:

   msiexec /i AdminPathMSI FileREINSTALL=Feature List REINSTALLMODE=vomu

   In this command, Admin Path is the path
   of your administrative installation point for Office XP (for example,
   C:OfficeXP), MSI File is the MSI database package
   for the Office XP product (for example, ProPlus.msi), and Feature
   List is the list of feature names (case sensitive) that have to
   be reinstalled for the update.

   To install all features, you can use REINSTALL=ALL, or you can install the following features:

   HTMLSourceEditing,WebDebugging

For additional information about how to update your
administrative installation and deploy to client workstations, click the
following article number to view the article in the Microsoft Knowledge Base:

How to determine whether the update is installed

The update contains updated versions of the following files:

File name      		Version
----------------------------------
Msdbg2.dll     		7.0.9466.0
Msenv.dll      		7.0.9064.9606
Pdm.dll        		7.0.9466.0
Vs7jit.exe     		7.0.9466.0
Vsdebug.dll    		7.0.9064.9593
Htmed.dll      		7.0.9064.9607
Mdm.exe        		7.0.9466.0
Mdmui.dll      		7.0.9466.0
Vsbrowsu.dll			7.0.9064.9595

Note Vsbrowsu.dll may also be named Vsbrowseui.dll.

To
determine the version of the files that are installed on your computer, follow
these steps.

Note Because there are several versions of Microsoft Windows, the
following steps may be different on your computer. If they are, see your
product documentation to complete these steps.

1. Click Start, and then click
   Search.
2. In the Search Results pane, under
   Search Companion, click All files and
   folders.
3. In the All or part of the file name box,
   type a file name, and then click Search.
4. In the list of files, right-click the found file, and then
   click Properties.
5. On the Version tab, determine the version
   of the file that is installed on your computer.

Note If the Office XP Update: KB833858 is already installed on your
computer, you receive the following error message when you try to install the
Office XP Update: KB833858:

Windows Installer update requirements

To install the update that is described in this article, you must
have Windows Installer 2.0 or later installed. Both Microsoft Windows XP and
Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or
later. To install the latest version of the Windows Installer, visit one of the
following Microsoft Web sites:

Windows Installer for Microsoft Windows
95, Microsoft Windows 98, and Microsoft Windows Millennium Edition (Me):

Windows Installer for Microsoft Windows NT 4.0 and Microsoft
Windows 2000:

List of issues fixed by the update

The Office XP Update: KB833858 fixes the following issues that
were previously not documented in the Microsoft Knowledge Base.

Default debugging permissions have been enhanced

Changes have been made to the Microsoft Visual Studio .NET
debugger that is included in Microsoft Office XP to make debugging permissions
more restrictive. As a security enhancement, users who are not part of the
Administrators group or the Debugger Users group will no longer be able to
debug scripts with the Microsoft Script Editor.

Article ID: 833858 – Last Review: January 28, 2013 – Revision: 5.0

After renewing the Microsoft Dynamics CRM Internet Facing Deployment (IFD) Certificate through the Microsoft Dynamics CRM Deployment Manager, an AD FS generic error message is shown when you try to log into CRM. Additionally, the following error message can be found in the Event Viewer on the AD FS server:

 Microsoft.IdentityServer.Web.RequestFailedException: MSIS7012: An error occurred while processing the request. Contact your administrator for details. —> Microsoft.IdentityServer.Protocols.WSTrust.StsConnectionException: MSIS7004: An exception occurred while connecting to the federation service. The service endpoint URL ‘net.tcp://localhost:1501/adfs/services/trusttcp/windows’ may be incorrect or the service is not running. —> System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.tcp://localhost:1501/adfs/services/trusttcp/windows that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

Configure the AD FS Server service to use the new or existing certificate. To do this, follow these steps:

1.  Open AD FS 2.0 Management.
2.  Browse to AD FS 2.0ServiceCertificates.
3.  Right-click Certificates, and then select Set Service Communications Certificate.
4.  Select the new certificate from the certificate selection UI.
5.  Click OK.

It is recommended to follow all the steps found in the KB 2504439 in order to check whether the ADFS settings are correct.

How to change the ADFS 2.0 service communications certificate after it expires
http://support.microsoft.com/kb/2504439/en-us

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2804284 – Last Review: January 25, 2013 – Revision: 2.0

When attempting to register a 32bit plugin assembly in a Microsoft Dynamics CRM 2011 deployment, users may encounter the following error:

“Unable to load the specified plug-in assembly”

If one enables platform tracing within Microsoft Dynamics CRM, additional information is provided:

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.Crm.Sdk, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35′ or one of its dependencies. The system cannot find the file specified.
   at System.Reflection.Assembly._GetExportedTypes()
   at PluginRegistrationTool.AssemblyReader.RetrievePluginsFromAssembly(String path) in C:Usersadministrator.DDCRMDesktopPluginRegistration 2.2AssemblyReader.cs:line 59
   at PluginRegistrationTool.AssemblyReader.RetrievePluginsFromAssembly(String path)
   at PluginRegistrationTool.RegistrationHelper.RetrievePluginsFromAssembly(String pathToAssembly) in C:Usersadministrator.DDCRMDesktopPluginRegistration 2.2RegistrationHelper.cs:line 49
   at PluginRegistrationTool.PluginRegistrationForm.btnLoadAssembly_Click(Object sender, EventArgs e) in C:Usersadministrator.DDCRMDesktopPluginRegistration 2.2PluginRegistrationForm.cs:line 127

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2804252 – Last Review: January 25, 2013 – Revision: 1.0