Groove Virtual Office 3.0 Project Edition
| 1 ). | The TeamDirection tools are blank after you uninstall and then reinstall Groove |
| Describes a problem in which the TeamDirection tools are blank after you reinstall Groove Virtual Office over data from a previous installation. | |
| 2 ). | How to export, to print, or to e-mail a meeting or a project that has attached notes by using the TeamDirection Project tool |
| How to export, to print, or to e-mail a meeting or a project that has attached notes by using the TeamDirection Project tool | |
| 3 ). | You may receive an error message when you try to add TeamDirection tools to Groove Virtual Office |
| Explains that when you add TeamDirection tools to Groove Virtual Office, you may receive an error message. | |
| 4 ). | A mobile workspace that you created by using Groove Mobile Workspace for SharePoint no longer displays Rich Text fields after you upgrade to Groove Virtual Office 3.1 |
| A mobile workspace that you created by using Groove Mobile Workspace for SharePoint no longer displays Rich Text fields after you upgrade to Groove Virtual Office 3.1 | |
| 5 ). | Duplicate names appear in the task resources of a TeamDirection Project tool in Groove |
| Describes an issue that may occur when someone creates a non-Groove resource that is duplicated by a Groove resource. Provides a resolution. | |
| 6 ). | Error message when you try to add the Project Manager to a Workspace: "Cannot add tool" |
| Describes that You uninstall Groove Workspace 2, and then you install Groove Virtual Office 3 Project Edition. When you try to add the Project Manager to a Workspace, you receive an error. | |
| 7 ). | You receive an error message after you upgrade to Groove Virtual Office 3.x |
| Describes an issue in which you receive a "The procedure entry point ?SetThreadName@@YGXPBGK@Z could not be located in the dynamic link library GrooveUtil.DLL" error message when you try to upgrade to Groove Virtual Office 3.x. | |
| 8 ). | How to view the release notes for Groove Virtual Office after you close the installation program |
| Describes how to view the release notes for Groove Virtual Office after you close the installation program. | |
| 9 ). | You must upgrade all computers when you upgrade to Groove Virtual Office 3.0f if you use your Groove account on multiple computers |
| Describes issues that may occur because the password reset feature in Groove Virtual Office 3.0f requires changes to the way that Groove stores your account. | |
| 10 ). | How to print a Groove discussion topic and all its responses without having to print each item |
| Describes how to print a Groove discussion topic and all its responses without having to print each item. | |
| 11 ). | Error message when you log on to an account that is created in Groove Virtual Office 3.x and imported into a Groove Workspace 2.0 installation over a managed Groove 2.0 account: "Linked binary document not found" |
| Error message when you log on to an account that is created in Groove Virtual Office 3.x and imported into a Groove Workspace 2.0 installation over a managed Groove 2.0 account: "Linked binary document not found" | |
| 12 ). | You cannot import combined Microsoft Project files to the TeamDirection Project tool in Groove |
| Describes an issue that occurs because the TeamDirection Project tool does not examine tasks in the master project. Provides a workaround. | |
| 13 ). | Error message when you try to select a tool in Groove: "This tool has been disabled on this computer due to device policy" |
| Error message when you try to select a tool in Groove: "This tool has been disabled on this computer due to device policy" | |
| 14 ). | Error message when you try to add a Form Heading field to a Form view in Groove Virtual Office: "Invalid Column Selection" |
| Error message when you try to add a Form Heading field to a Form view in Groove Virtual Office: "Invalid Column Selection" | |
| 15 ). | Sections in the Dashboard tool may be overwritten by another manager in Groove |
| Describes an issue that occurs because the sections in the Dashboard tool were designed to be owned by a single manager. Provides a workaround. | |
Page 1 of 29
Next Page
