Installation/Update
Problem:	The Groove upgrade installer does not warn licensed users about losing licensed functionality when upgrading to Groove 3.x (from Groove 2.x) without first activating a 3.x license.
Explanation:	Licensed 2.x users may unintentionally upgrade to 3.x without realizing that their accounts will be downgraded. If the user has not activated a Groove 3.x license prior to upgrading to Groove 3.x (from Groove 2.x), then Trial Edition limits and restrictions will be applied.
Workaround:	None, if these users don't intend to obtain and activate a Groove 3.x license. Activating an equivalent Groove 3.x license will restore all features.
Problem:	For an account on multiple computers, data stops being synchronized after 60 days unless all computers that have the account are using the same version of Groove.
Explanation:	When users upgrade an account, Groove automatically prompts them to upgrade on all other computers that have the account. If the user fails to complete the upgrade on the other computers, synchronization will stop after 60 days.
Workaround:	If the prompted account upgrade has failed for some reason, and the 60-day period has not expired, the user can go to http://www.groove.net/downloads to run the full installation. If the 60-day period has expired, the user must delete the account on the computer on which it's no longer being synchronized, and then add it again using the Groove Account Activation Wizard. For information, see Using your account on another computer in the Groove User's Guide.
Groove and Jabber/XMPP Integration
Problem:	Changing a Jabber account password fails if the user logs off their Groove account and then logs on before before the change has taken effect on the XMPP Server.
Explanation:	When a user changes a Jabber password in Groove, the change does not take effect until the user logs off Groove and then logs on again (or works offline, and comes back online). However, typically, the user needs to be logged off (or offline) for at least one minute before the new password takes effect. If the user logs on (or goes online) before a minute has passed, an authorization failure notification will display.
Workaround:	The user can try logging off (or working offline) again, this time making sure to wait at least one minute before logging on (or working online) again.This should provide enough time for the new password to be recognized on the XMPP Server.
Problem:	Awareness may not be accurate for Jabber contacts derived via MSN Messenger.
Explanation:	Jabber users can a gateways to add contacts from MSN Messenger to contact lists in a Jabber client. These "gateway" contacts are automatically added to the user's Groove contact list when the Jabber account is associated with their Groove identity. However, awareness indicators for these contacts may not always be accurate. Note that this is a known issue originating within the Jabber infrastructure.
Workaround:	None.
Problem:	An online alert displays for Jabber contact who status has changed to idle.
Explanation:	If you set the alert level to "High" for a Jabber contact, an online alert displays when the Jabber contact becomes idle.
Workaround:	None.
Problem:	Messaging activities with Jabber contacts who are using "chat-only" Jabber clients may have unpredictable results.
Explanation:	Groove supports XMPP standards for awareness and instant messaging, but not for chat. As a result, messaging interactions with Jabber contacts who are using Jabber clients that only support chat may have unpredictable results.
Workaround:	None.
Groove Folder Synchronization
Problem:	On Systems running Windows 2000, when users open a file marked unread in a file sharing workspace, the file's application window sometimes opens behind Windows Explorer.
Workaround:	Reselect the application in the Windows status bar.
Problem:	Firewall software running on your computer may block the creation of file sharing workspaces.
Explanation:	If your firewall software application is set to block port 9080, this will also block the creation of Groove file sharing workspaces.
Workaround:	Change settings in your firewall software application so that it does not block port 9080.
Groove and Lotus Notes
Problem:	When exporting a Lotus Notes email thread to a Groove Discussion Tool, some messages in the Notes email thread are sometimes not transferred to the Discussion Tool.
Explanation:	This is a known Lotus Notes issue.
Workaround:	If a message in a Lotus Notes email thread is not exported as part of the thread to a Discussion Tool, manually select the message and export it to the Discussion Tool separately after exporting the rest of the email thread.
Groove and Microsoft Office
Problem:	When launching Outlook 2003 after installing Groove, you may receive the following error message:
Explanation:	The Windows registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Client\Extensions\Exchange Extensions has become corrupt.
Workaround:	Delete the  HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Client\Extensions\Exchange Extensions registry value and then restart Outlook.
Problem:	In the Document Review tool, merging Microsoft Word documents may fail under certain conditions.
Explanation:	Because of a limitation in Microsoft Word (except for Microsoft Word XP and later), Groove may fail to merge changes successfully.
Workaround:	If possible, upgrade to Office XP. Otherwise, merge the files manually.
Problem:	When attempting to co-view Microsoft PowerPoint presentation, the presentation opens in a new window and navigation fails.
Explanation:	You or your IT administrator may have set up PowerPoint to open presentation files in separate windows. Co-viewing does not function properly in separate presentation windows.
Workaround:	For operating systems other than Windows NT 4.0, select Tools - Folder Options in Windows Explorer and click the File Types tab. Select the PowerPoint file type (PPT), click Advanced, and make sure the "Browse in same window" option is checked. For Windows NT 4.0, see Microsoft Knowledgebase article Q148897.
Problem:	Email address for contact imported from Microsoft Outlook is incorrect in Groove contact list.
Explanation:	Under certain circumstances, Groove displays an invalid email address for a contact imported from Outlook.
Workaround:	From the Groove contact list tool, right-click the contact name and select Edit. Enter the correct email address.
Problem:	If Microsoft Outlook is not the default email client, an error message is displayed when trying to import Outlook contacts into Groove. When the error message is dismissed, Groove begins the import process, but the contacts are not imported.
Explanation:	This is a known issue.
Workaround:	Before importing contacts, use Windows' Internet Settings application (accessible from Start--Control Panel) to make Outlook your default email client.
Problem:	When using the Calendar or Meetings tool to synchronize with Outlook, entries sent to Outlook by Groove are titled "Groove Entry" followed by the name of the workspace from which they came. If a user changes the name of the shared workspace, synchronized entries in Outlook are not updated to reflect the new name of the workspace.
Explanation:	Changing a workspace name does not constitute a change in the entry's record, so this piece of data is not updated until the record itself changes.
Workaround:	This issue will be addressed in a future release.
Problem:	When synchronizing Groove data to Outlook with the same Exchange email account on two computer systems and the same Groove account on two systems, duplicate items are created.
Explanation:	This is a known synchronization issue.
Workaround:	To avoid duplicates in Outlook, disable synchronization (and keep it off) in Groove on one of the systems. This issue will be fixed in a future release.
Problem:	Data is not synchronized when Microsoft Outlook is not open, Groove detects multiple Outlook profiles, and "Prompt for a profile to be used" is selected.
Explanation:	This is a known issue.
Workaround:	Before attempting to synchronize your Groove data with Outlook, open Microsoft Outlook and select the profile with which you wish to synchronize your Groove data.
Problem:	When using the Calendar or Meeting tool to synchronize with Microsoft Outlook, Outlook entries that were edited by adding a file attachment are duplicated when further edited in the Calendar or Meetings tool. When the original entry is edited again in Groove, the changes are saved to the duplicate entry made by Outlook.
Explanation:	This is a known synchronization issue.
Workaround:	This issue will be fixed in a future release. However, the last entry made by Groove will always be the most up-to-date entry in Outlook.
Problem:	Import/export between the Groove Task Manager tool and Microsoft Project fails.
Explanation:	This is a known issue that has to do with Microsoft Project and/or script blocking and other features of Norton AntiVirus®.
Workaround:	Open Microsoft Project before using the Task Manager tool's import/export feature. If you use Norton AntiVirus, disable script blocking and/or the Norton AntiVirus Microsoft Office® plug-in and restart Groove before using the Task Manager tool's import/export feature. Instructions on disabling script blocking and the Microsoft Office plug-in can be found on Symantec's Web site.
Problem:	Microsoft Word does not work properly when trying to use the Files Tool's co-edit feature.
Explanation:	This is a known issue that has to do with your Microsoft Office installation or the Microsoft Office plug-in used by your version of Norton AntiVirus.
Workaround:	Try any of the following procedures: If you haven't activated Microsoft Office, complete the activation procedure before using the co-edit feature. If you haven't run Microsoft Word before using the co-edit feature, do so. When used for the first time, Microsoft Word may ask you to configure your installation by providing a user name and initials. Run Microsoft Word and provide this information (if required) before using the co-edit feature. Norton AntiVirus® is installed on your computer and the Microsoft Office plug-in is enabled. The plug-in prevents some applications from performing automated tasks in Microsoft Word. Instructions on disabling the plug-in can be found on Symantec's Web site. Run Microsoft Word's Detect and Repair feature by selecting Help-Detect and Repair (Microsoft Word 2000, XP). This Microsoft Office feature detects and repairs problems associated with Microsoft Office 2000 programs, such as missing files and registry settings. It does not repair personal files such as documents. Check to see if your installation of Microsoft Word needs any updates from Microsoft Office's Web site (http://office.microsoft.com). Reinstall Microsoft Word.
Problem:	While co-editing a Microsoft Word file, members are prompted to enter a password each time the editor makes a change to the file.
Explanation:	This is a known issue.
Workaround:	When co-editing a Microsoft Word file with the password feature enabled, disable it before beginning the co-edit session.
Problem:	When using Microsoft Office XP on a Windows XP system using Internet Explorer 6.0, attempting to start or join a Microsoft PowerPoint presentation fails.
Explanation:	Internet Explorer's default download file dialog option is set to Save, not Open.
Workaround:	In Windows Explorer, select Tools--Folder Options and click the File Types tab. Select the PowerPoint file type (PPT), click Advanced, and make sure the "Confirm open after Download" option is checked.
Problem:	When co-editing a Microsoft Word document in the Files Tool with Word's "Track changes while editing" feature enabled, changing and then saving the Word document turns off the "Track changes" feature.
Explanation:	This is a known issue.
Workaround:	After saving a Word document, re-enable Word's "Track changes" feature.
Problem:	During a co-edit session, if the active editor decides to work offline, no one else will be able to edit in the session until the active editor goes back online and clicks Done.
Explanation:	This is a known issue.
Workaround:	This issue will be fixed in a future release.
Problem:	When co-editing a Microsoft Word document, the cursor appears to "jump" to another location in the document when someone edits and then saves the document.
Explanation:	This is a known issue.
Workaround:	This issue will be fixed in a future release.
Mobile Workspace for Microsoft® SharePointTM
Problem:	When taking a SharePoint site offline to Groove, Groove users in different time zones may see different dates displayed for the same item.
Explanation:	This is a known issue.
Workaround:	There is no workaround at this time, however, the dates displayed will only be off by a maximum of one day. This issue will be fixed in a future release.
Problem:	When taking a SharePoint site offline to Groove, the Home tool in the Groove mobile workspace displays all announcements and events, even those that have expired.
Explanation:	This is a known issue.
Workaround:	Before taking a SharePoint site offline, change the layout of the home page so that Events and Announcements are separate columns. This way, the most recent entries can be seen without scrolling.
Problem:	When a member (non-creator) of a mobile workspace edits a list item, his or her name is not displayed on the SharePoint site. Instead, changes are always attributed to the workspace creator (this does not apply for Document Libraries).
Explanation:	This is a known issue.
Workaround:	Mobile Workspace for Microsoft SharePoint was designed to have only one synchronization point (the mobile workspace creator). Therefore, when the mobile workspace and the site are synchronized, changes are attributed to the workspace creator.
Problem:	When creating a mobile workspace from a SharePoint site or synchronizing a mobile workspace with a SharePoint site for the first time, a user may experience slow computer responsiveness due to an increase in virtual memory usage.
Explanation:	This is a known issue.
Workaround:	When synchronizing a mobile workspace with a SharePoint site for the first time, close all other Windows applications. This should improve performance, though it may still seem slow. This issue will be fixed in a future release.
Problem:	When a mobile workspace and a SharePoint site become disconnected due to network problems or network outages, synchronization may appear successful even though synchronization does not occur.
Explanation:	This is a known issue.
Workaround:	If a mobile workspace and a SharePoint site become disconnected due to network problems or network outages, shut down and restart Groove and resynchronize the mobile workspace and the SharePoint site.
Problem:	When attempting to retrieve data from a new SharePoint Team Services Web site that has never been taken offline to Groove, a user may receive <RENDER FAILED> messages. Likewise, when restoring a backup of a SharePoint Team Services Web site in order to return it to a pre-Groove State, users may receive <RENDER FAILED> as well.
Explanation:	Groove adds new columns to several SharePoint lists when a site is taken offline to Groove. Attempting to restore a backup of the site made prior to the addition of new columns will result in failure due to a caching issue with Internet Information Server (IIS). This will persist even if the SharePoint Web site is deleted and a new site is created in its place.
Workaround:	Stop and restart the World Wide Web Publishing Service on the Web Server.
Problem:	Fonts, page layouts, and hyperlink properties are different on the Groove Mobile Workspace for Microsoft® SharePointTM Home tool and the home page for the Mobile Workspace for Microsoft SharePoint Web site.
Explanation:	This is a known issue.
Workaround:	This issue does not affect Mobile Workspace for Microsoft SharePoint functionality or performance. It will be addressed in a future release.
Problem:	If you create a new InfoPath document from Groove, you will get a warning on exiting that indicates temporary files are still open, even if you've closed InfoPath.
Explanation:	Groove creates temporary files on your computer when you open a file from another application through Groove. Unlike most other applications, Infopath does not automatically delete these temporary files when the application is closed.
Workaround:	Dismiss the warning and Groove will exit normally.
Problem:	Last synchronization is displayed incorrectly for Groove 2.5 users.
Explanation:	If a Groove 3.0 user create a Mobile Workspace for SharePoint and then invites Groove 2.5 users to the workspace, the "Last Synchronization" time, as reported in the Status area of the Home tool displays incorrectly for Groove 2.5 users.
Workaround:	None, unless the Groove 2.5 user upgrades their Groove installation to Groove 3.0. The problem corrects itself after upgrading.
Tools
Problem:	Certain files (such as a file with an "idl" extension) do not open when added to the Document Review Tool.
Explanation:	When the Document Review Tool opens a file, the file is exported to a temporary area before being opened. While in the temporary area, the file's name has parentheses around it. Certain programs, such as Microsoft Developer Studio 6, cannot open files with parentheses in their name.
Workaround:	Change the default application for handling files of the problematic file type to an application that can open file names with parentheses.
Problem:	Microsoft Windows XP users of the Groove Files Tool cannot send a copy of a file to a floppy drive because the "Send to a Floppy" option does not appear on the menu.
Explanation:	This is a known Windows XP issue.
Workaround:	You can make the "Send to floppy" option appear on the menu by adding a new shortcut to your floppy drive in the Send To folder. To do this, click Start and select Run. In the Open box, type sendto and click OK. This opens your Send To folder. Click File-New Shortcut. Type "A:\" in the Type the location of the item: dialog box and click Next to continue. Type a name for your shortcut in the "Type a name for this shortcut:" dialog box and click Finish. To use the Send to floppy option with the Groove Files Tool, right-click on a file in the Groove Files Tool, select Send To, and select the icon you just created. For more information, read the following Microsoft technote: http://support.microsoft.com/default.aspx?scid=KB;en-us;310270&.
Problem:	Attachments opened in another application from a Groove tool may be left on your desktop, unencrypted, after you shut down Groove.
Explanation:	When Groove works with files, it creates unencrypted temporary files on your computer's disk which are erased when the application for the file is shut down properly.
Workaround:	If Groove is shut down while an application in which you're editing files is open, a dialog appears to allow you to remove the unencrypted temporary files left on your computer's disk. Close the application and click the dialog's Retry button to delete the temporary files.
Problem:	In the Groove Forms tool, data imported from another Forms tool does not display if field names are not exact matches.
Explanation:	If you export Forms records as XML, and then import these records into a new Forms tool in which you've added fields manually (that is, you have not also exported and imported the Form design from the original Forms tool), the imported data will not display unless field names are exact matches, including case. For example, if a field in the original Forms tool is named "CITY", the field name in the new Forms tool must also be "CITY", and not "City".
Workaround:	Use options to save the original Forms tool as a template, and then add the new Forms tool by selecting the saved template file. This will ensure that the design and field names match. If you're exporting from a 2.5 Forms tool, save the design as a database template in the Forms Manager. Then import the design (in a 3.0 Forms tool as Forms 2.5 XML or Binary).
Problem:	Groove Forms tool records exported from a 2.5 Forms tool created using Groove 3.0 cannot be imported into a 2.5 Forms tool created in Groove 2.5.
Explanation:	Groove 3.0 users can optionally select "Groove 2.5" as the Groove version when creating a new workspace and thereby add Groove 2.5 versions of tools to the workspace, including the Groove 2.5 Forms tool. However, records exported from this type of Groove 2.5 Forms tool cannot be imported into a Groove 2.5 Forms tool that's actually created in Groove 2.5.
Workaround:	None.
Problem:	In the Groove Forms tool, images in rich text fields may slow performance when records are viewed in the Forms preview window.
Explanation:	The Groove Forms tool allows users to view records in a preview window. This allows users to view the contents of records quickly by using the arrow keys. However, any record that includes an image pasted into a rich text field may take a long time to display in the preview window. The degree of performance degradation depends on the size of the image and the amount of memory available on the computer.
Workaround:	This problem will be fixed in a soon maintenance release.
Workspace
Problem:	Users must be running at least Groove version 3.0d to accept invitations to new workspaces that include a Forms tool.
Explanation:	If you create a new workspace that contains a Forms tool, any user you invite to this workspace must be running at least Groove version 3.0d in order to accept the invitation. Users running an earlier version of Groove will be prompted to upgrade to the latest version in order to accept your invitation. If you attempt to add a Forms tool to a workspace that already has users running an earlier Groove version as members, you'll be prompted to choose between adding the current version of Forms (and forcing an upgrade prompt for these users) or adding an earlier version of the Forms tool.
Workaround:	None.
Problem:	In the Meetings Tool, the Agenda Topics tab and the Action Items tab don't always refresh properly when deleting a contact.
Explanation:	This is a known issue.
Workaround:	If you make a change affecting the Agenda Topic tab or the Action Item tab and refresh does not work properly, select another tool in the workspace and then return to the Meetings Tool to refresh the Agenda Topics and Action Items tabs. This issue will be fixed in a future release.
Problem:	When using the Task Manager Tool to import or export data from or to Microsoft Project, the importing or exporting process may appear to hang or fail.
Explanation:	Dialog windows like "Tips" or "Project Information" that appear when Microsoft Project is launched by Groove may fall to the background or be hidden by Groove or by other open applications.
Workaround:	Configure Microsoft Project not to display these dialog windows when a project is opened. Switch to the Microsoft Project dialog window waiting for your input. Open Microsoft Project before exporting or importing data from Groove, dismiss any dialog windows, and then perform your import or export.
Problem:	Custom permissions in a workspace revert to the default (Manager) permissions in a workspace duplicated from it.
Explanation:	This is a known issue.
Workaround:	Reinstate the custom permission in the duplicate workspace. This issue will be fixed in a future release.