Article ID: 875251
Article Last Modified on 12/18/2006
APPLIES TO
- Microsoft Office Information Bridge Framework
INTRODUCTION
This article contains the contents of the Microsoft Office Information Bridge Framework Readme file.
Microsoft Office Information Bridge Framework Readme File
Contents
- How to use this document
- Upgrading from a prerelease version of Information Bridge
- Information Bridge Metadata Designer issues
3.1 In Visual Studio .NET 2003, Information Bridge Metadata Projects does not appear in the Project Types box of the New Project dialog box.
3.2 Attempting to build and execute a Metadata Designer project might result in an error message that prompts the user to install Microsoft Office Professional Edition 2003 and Microsoft Office Information Bridge Framework Client 1.0.
3.3 Attempting to create a Metadata Designer project in Visual Studio results in a Microsoft development error stating that the application for the project type (.mdproj) is not installed.
3.4 Attempting to debug a Metadata Designer project in Visual Studio might result in Word quitting unexpectedly (crashing).
3.5 Attempting to publish or refresh a metadata project results in a duplicate artifact error message.
3.6 Attempting to open a metadata project results in a duplicate artifact error message.
3.7 Attempting to import metadata might cause Visual Studio to stop responding (freeze). - Information Bridge client issues
4.1 Copying smart tags from Word documents and then inserting them into Excel spreadsheets results in only the text being pasted, not the functionality.
4.2 Information Bridge... might not appear on the Tools menu for Microsoft Office applications.
4.3 Closing the host Office application might result in unexpected behavior if the implementation of the Information Bridge client includes an ActiveX control.
4.4 Registering multiple handlers for the same operation or for multiple services of the same type might result in the Information Bridge client exhibiting unexpected behavior.
4.5 In an Information Bridge solution for Excel that is running under Windows 2000, attempting to view a region that includes a graphics device interface (GDI) control might result in a .NET Framework unhandled exception error.
4.6 Information Bridge quits unexpectedly.
4.7 The Solution Accelerator for Proposals client might cease to function after the Information Bridge client is installed.
4.8 Users might not see new metadata if their roles in the organization are changed.
4.9 Information Bridge might not function for an application that is embedded within another application.
4.10 Page caption is erroneously titled "Caption Undefined."
1 How to Use This Document
Welcome to the Readme file for the Microsoft Office Information Bridge Framework. This file contains important information that was not available when the documentation for the product was written. Workarounds have been provided for known issues.
You can find additional information at the Information Bridge web site:
2 Upgrading from a pre-release version
Installing the Microsoft Office Information Bridge Framework 1.0 over a prerelease version of the product might result in unexpected behavior. To upgrade from a prerelease version of the product to version 1.0, use the following procedure:
- Uninstall the prerelease version of the Information Bridge Framework.
- Install Information Bridge Framework 1.0, as described in the Microsoft Office Information Bridge Framework Installation and Deployment Guide.
3 Information Bridge Metadata Designer Issues
The following issues concern the Metadata Designer tool.
back to top
3.1 In Visual Studio .NET 2003, "Information Bridge Metadata Projects" does not appear in the Project Types box of the New Project dialog box.
Description: The desktop shortcut icon that is created by the Visual Studio Integrator Program (VSIP) when you install the Microsoft Visual Studio .NET 2003 SDK passes a command-line argument ("/RootSuffix exp") that causes Information Bridge Metadata Projects to not appear in the Project Types box in the Microsoft Visual Studio New Project dialog box.
Workaround: Create a new desktop shortcut icon without the "/RootSuffix exp" command-line argument.
back to top
3.2 Attempting to build and execute a Metadata Designer project might result in an error message that prompts the user to install Microsoft Office Professional Edition 2003 and Microsoft Office Information Bridge Framework Client 1.0.
Description: This issue is caused by a discrepancy between the installed languages of Microsoft Office Professional Edition 2003 and the Microsoft Office Information Bridge Framework client component. For example, when an English version of Information Bridge is installed with a Spanish version of the Microsoft Office System.
Workaround: Add the following information to the entries under Project Properties in the Metadata Designer project:
Metadata Debugger Name = WINWORD.EXE
Metadata Debugger Path = C:\Program Files\Microsoft Office\OFFICE11
Metadata Working Directory = C:\Program Files\Microsoft Office\OFFICE11
Metadata Command Line Arguments = /Microsoft.Solutions.InformationWorker.Common.EnterpriseInstrumentation= "$(SetupPath)\Microsoft.InformationBridge.Tools.EngineHost.EnterpriseInstrumentation.config" /IWBridge.Engine.MetadataProviderAssemblyLocation= "$(SetupPath)\Microsoft.InformationBridge.Tools.MetadataDesigner.dll" /IWBridge.Engine.MetadataProviderAssemblyName=Microsoft.InformationBridge.Tools.MetadataDesigner /IWBridge.Engine.MetadataProviderClassName=Microsoft.InformationBridge.Tools.MetadataDesiger.MetadataEngineHost /IWBridge.Engine.DisableCache /IWBridge.MetadataTool.MetadataProjectLocation="$(ProjectPath)"
back to top
3.3 Attempting to create a Metadata Designer project in Visual Studio results in a Microsoft development error stating that the application for the project type (.mdproj) is not installed.
Description: Information Bridge requires Microsoft Visual Studio .NET 2003 Professional or later.
Workaround: Upgrade to Visual Studio .NET 2003 Professional or later.
back to top
3.4 Attempting to debug a Metadata Designer project in Visual Studio might result in Word quitting unexpectedly (crashing).
Description: See the following article in the Microsoft Knowledge Base Article:
823140 FIX: Managed Application That Makes COM to COM+ Calls May Experience an Access Violation Error
Workaround: If the operating system is Microsoft Windows XP Professional, install the associated update mentioned in the Knowledge Base article.
back to top
3.5 Attempting to publish or refresh a metadata project results in a duplicate artifact error message.
Description: This error might occur if you modify the MetadataSolutionName attribute of a Port element that has an associated PortInstance element.
Workaround: To recover your metadata, use the following procedure:
- Start a new Visual Studio session.
- Create a new Metadata Designer project, and then on the Project menu, click Import Metadata.
- In the Import Metadata dialog box, import the metadata scopes that were originally contained in the project.
- Delete the old Metadata Designer project.
Note: The published metadata is correct as of the last version you published. It is only the internal state of the Metadata Designer project that is invalid after you modify the MetadataSolutionName attribute of the Port element.
back to top
3.6 Attempting to open a metadata project results in a duplicate artifact error message.
Description: This error might occur if you modify the MetadataSolutionName attribute of a Port element that has an associated PortInstance element, save the metadata project, and then try to open it.
Workaround: To recover your metadata to the published state and fix the metadata project, use the following procedure:
- Click OK to finish loading the project.
- On the Project menu, click Publish metadata to save the metadata to a file.
- Start a new Visual Studio session.
- Import the metadata from the file in which you saved it in step 2.
back to top
3.7 Attempting to import metadata might cause Visual Studio to stop responding (freeze).
Description: This error might occur if you import a metadata scope, modify the MetadataSolutionName attribute of a Port element that has associated PortInstance elements, and then try to import the same metadata scopes.
Workaround: If you saved your Metadata Designer project before you re-imported the metadata, follow these steps to recover your metadata:
- Use Task Manager to end the Visual Studio process.
- Start a new Visual Studio session.
- Open the project again, and ignore the error about duplicate artifact.
- Publish the metadata to a file.
- Close the project, and create a new Metadata Designer project.
- Import the metadata from the file in which you saved it in step 4.
Note: The published metadata is correct as of the last version you published. It is only the internal state of the Metadata Designer project that is invalid after you modify the MetadataSolutionName attribute of the Port element.
back to top
4 Client Issues
The following issues concern the Information Bridge client.
back to top
4.1 Copying smart tags from Word documents and then inserting them into Excel spreadsheets results in only the text being pasted, not the functionality.
Description: When a user clicks Copy Smart Tag on the Information Bridge menu in Microsoft Office Word 2003 and then tries to insert the smart tag in a Microsoft Office Excel 2003 spreadsheet, only the text is copied; the smart tag's functionality is not available in Excel.
Workaround: Do not use the Copy Smart Tag menu item on the Information Bridge menu to copy a smart tag from Word to Excel. Instead, either use Information Bridge to create the smart tag in Excel, or use the following procedure:
- Insert the smart tag in your Word document.
- Highlight the smart tag.
- Copy the smart tag.
- In the Excel spreadsheet, insert the smart tag in the desired location.
back to top
4.2 Information Bridge... might not appear on the Tools menu for Microsoft Office applications.
Description: When a Microsoft Office application quits ungracefully (such as when you have to use Task Manager to end a task), Information Bridge might be disabled, and in subsequent sessions Information Bridge... might not appear on the Tools menu.
Workaround: Use the following procedure:
- Make sure the value for the following registry key is set to "3". Any other value will prevent the MSIBF.AddIn from being loaded.
(where
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\
application\Addins\MSIBF.AddIn\LoadBehaviorapplicationequals Word, Excel, or Outlook). - Delete the registry entry for OpusApp (for Word) or XLMAIN (for Excel) value for the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Common\Smart Tag\Actions\{B4576665-9DD8-11D7-B7B5-00022D8648FC}\
- On the application's Help menu, click About to open the About dialog box, and then click Disabled Items to open the Disabled Items dialog box. If Information Bridge is listed in the box, select it, and then click Enabled.
back to top
4.3 Closing the host Office application might result in unexpected behavior if the implementation of the Information Bridge client includes an ActiveX control.
Description: Information Bridge does not support the use of ActiveX controls within the information window. Implementing an ActiveX control in the information window might result in data loss, ActiveX problems, display irregularities, or other unexpected behavior.
Workaround: Remove the ActiveX control from the information window.
back to top
4.4 Registering multiple handlers for the same operation or for multiple services of the same type might result in the Information Bridge client exhibiting unexpected behavior.
Description: Registering multiple handlers for the same operation or for multiple services of the same type is not supported.
Workaround: Use unique values for the Name attribute of the OperationType and ServiceType elements.
back to top
4.5 In an Information Bridge solution in Excel on running on Windows 2000, attempting to view a region that includes a graphics device interface (GDI) control may result in an .NET Framework unhandled exception error
Description: When you try to view a region that includes a graphics device interface (GDI) control, a red "X" might appear instead of the GDI control. A Microsoft .NET Framework error dialog box also appears that states: "An unhandled exception has occurred in a component in your application. Click continue and application will ignore this error and attempt to continue. Invalid parameters used."
Workaround: Install the hotfix described in the following article in the Microsoft Knowledge Base Article:
831939 Description of the Office 2003 hotfix package: January 29, 2004
back to top
4.6 Information Bridge quits unexpectedly.
Workaround: Install the hotfix described in the following article in the Microsoft Knowledge Base:
833329 FIX: Error Message: System.ExecutionEngineException occurred in an unknown module
back to top
4.7 The Solution Accelerator for Proposals client might cease to function after the Information Bridge client is installed.
Workaround: Update the Accelerator for Proposals client by downloading it from the Microsoft Office Solution Accelerator for Proposals download center.
back to top
4.8 Users might not see new metadata if their roles in the organization are changed.
Description: If users' roles within an organization change, they could have access to a different set of metadata from what they had in their previous roles. However, the following conditions might result in this new metadata not appearing for the users:
- The time stamps for the metadata or metadata scope contain an entity that was not cached yet.
- The metadata service is not available at the time the cache was refreshed, or the metadata scope was created and deleted before a refresh of the cache occurred.
Workaround: The administrator must delete the user's local cache so that Information Bridge checks the metadata service for a new cache.
back to top
4.9 Information Bridge might not function for an application that is embedded within another application.
Description: Information Bridge functionality is not supported for an application that is embedded within another application, such as a Excel spreadsheet that is embedded in a Microsoft Office Outlook 2003 e-mail.
Workaround: Do not include Information Bridge functionality in an application that is embedded in another application.
back to top
4.10 Page caption is erroneously titled "Caption Undefined."
Description: If an action that was not called as a result of a previous ShowContext calls a ShowAssociations operation, the ShowAssociations operation will display the associations correctly, but the page caption and tooltip will not be displayed. "Caption Undefined" will be displayed.
Workaround: ShowAssociations should be called as a result of ShowContext.
back to top
Keywords: kbhowto kbinfo KB875251
