2007 Microsoft Office Servers Known Issues/ReadMe
Server Products
All known issues below are grouped by application.
Latest Installation Requirements
| Standalone Installation | Computer and Processor | Server with processor speed of 2.5 Gigahertz (GHz) or higher. , Dual processor, 3 GHz or higher recommended. |
| Memory | 1 Gigabyte (GB) RAM, 2 GB recommended | |
| Hard Disk | 3 Gigabyte (GB) of available hard disk | |
| Drive | DVD Drive, local or network accessible | |
| Display | 1024x768 or higher resolution monitor | |
| Operating system | Microsoft Windows Server 2003 Standard Edition SP1, Windows Server 2003 Enterprise Edition SP1, Windows Server 2003 Datacenter Edition SP1 or Windows Server 2003 Web Edition SP1 or later. Microsoft .NET Framework 2.0 and Microsoft Windows Workflow Foundation Runtime Components, or Microsoft .Net Framework 3.0. For more information about Microsoft .NET Framework 2.0 and 3.0, see the Microsoft .NET Framework Developer Center. | |
| Other | 56 Kilobits per second (Kbps) required for client to server connection. Internet Simple Mail Transfer Protocol/Post Office Protocol 3 (SMTP/POP3), Internet Message Access Protocol 4 (IMAP4), or MAPI-compliant messaging software required for e-mail notifications | |
| Browser | For Central Administration, the following are required: - Microsoft Windows with Microsoft Internet Explorer 6.0 or later. For basic functionality, including editing, Site Administration and Form Filing, one of the following configurations is required: - Microsoft Windows with Microsoft Internet Explorer 6.0 or later, FireFox 1.5 or later, Netscape 8.1 or later or Mozilla 1.7 or later. Note: Microsoft Office Project Server 2007 only supports Microsoft Internet Explorer 6.0 or later. - UNIX/Linux with FireFox 1.5 or later or Netscape 7.2 or later. - Mac OS-X with FireFox 1.5 or later or Safari 2.0 or later. | |
| Additional | Refer to the product Capacity Planning document for machine specific requirements. | |
| Farm Installation | Computer and Processor | Server with processor speed of 2.5 Gigahertz (GHz) processor or higher., Dual processor, 3 GHz or higher recommended. |
| Memory | 2 Gigabyte (GB) RAM, 4 GB recommended for SQL and Application Servers | |
| Hard Disk | 3 GB of available hard disk | |
| Drive | DVD Drive, local or network accessible | |
| Display | 1024x768 or higher resolution monitor | |
| Operating system | Microsoft Windows Server 2003 Standard Edition SP1, Windows Server 2003 Enterprise Edition SP1, Windows Server 2003 Datacenter Edition SP1 or Windows Server 2003 Web Edition SP1 or later. Microsoft Windows Workflow Foundation Runtime Components, and Microsoft .NET Framework 2.0, or Microsoft .Net Framework 3.0. For more information about Microsoft .NET Framework 2.0 and 3.0, see the Microsoft .NET Framework Developer Center. | |
| Other | 100 Megabits per second (Mbps) connection speed required for server to server connection, 56 Kilobytes per second (Kbps) required for client to server connection. Internet Simple Mail Transfer Protocol/Post Office Protocol 3 (SMTP/POP3), Internet Message Access Protocol 4 (IMAP4), or MAPI-compliant messaging software required for e-mail notifications. SQL Server 2000 SP3a or higher or SQL 2005 SP1 or later. SQL 2005 Analysis Services 2005 SP1 or later required for some advanced features. | |
| Browser | For Office SharePoint Server Central Administration, the following are required: - Microsoft Windows with Microsoft Internet Explorer 6.0 or later. For normal use, including editing, Site Administration and Form Filing, one of the following configurations are required: - Microsoft Windows with Microsoft Internet Explorer 6.0 or later, FireFox 1.5 or later, Netscape 8.1 or later or Mozilla 1.7 or later. Note: Microsoft Office Project Server 2007 only supports Microsoft Internet Explorer 6.0 or later. - UNIX/Linux with FireFox 1.5 or later or Netscape 7.2 or later. - Mac OS-X with FireFox 1.5 or later or Safari 2.0 or later. | |
| Additional | Refer to the product Capacity Planning document for machine specific requirements. |
Setup (server)
| Issue Type | Question or Issue | Answer |
| No issues at this time |
All Servers
| Issue Type | Question or Issue | Answer |
| Upgrade - Shared Services | After upgrading pre-B2TR builds to B2TR or RTM, the links to SSPs in the central administration navigation control takes user to OLD farm. | Run the following stsadm command: stsadm -o activatefeature -name OssNavigation -url <SSP admin site url> |
| Content Deployment | When creating a content deployment path which replicates a site collection to another site collection within the same farm, but on another managed path, the following error occurs: Value does not fall within the expected range. | The workaround is as follows: Stsadm -o deactivatefeature -name deploymentlinks -url <URL> Stsadm -o deactivatefeature -name migrationlinks -url <URL> Stsadm -o activatefeature -name deploymentlinks -url <URL> Stsadm -o activatefeature -name migrationlinks -url <URL> |
| Document Conversions | Document Conversions Launcher Service is always in "starting" state (specifically when trying to enable the Launcher Service on more than one Server in the farm). | The Document Conversions Launcher Service Admin UI is not functional for any Launcher that will run on a server that is not hosting the Central Administration web application. The UI will never reflect current state in this configuration. WORKAROUND To enable the Launcher Service you must specify the necessary Launcher information that the UI normally provides. This is done by updating two values in a registry key located on the machine on which you are trying to run the Launcher service. This includes the location of the Load Balancer and the Port to use for the connection. Key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\LauncherSettings]"LoadBalancerUrl"="http://server:port/HtmlTrLoadBalancer""Port"=dword:port LoadBalancerUrl: This is the full URL to the .NET Remoting channel that the Load Balancer opens. The scheme should be http://[please specify Load Balancer server]:[please specify Load Balancer port]/HtmlTrLoadBalancer and ensure they are accurate. Port: This is the port that the launcher service will open for incoming .NET Remoting requests to do Conversions, e.g. "8082". After changing either of these settings (initially or if future machines are added and require settings changes), you must stop and start the Launcher service (Office Document Conversions Launcher Service) in the Services control panel (Start|Control Panel|Administrative Tools|Services). The services should be set to Enabled and set to start automatically (Automatic) if not so already.Any future changes to the Load Balancer settings will require updating the Launcher settings on each machine to reflect those changes. The services will also have to be stopped and then started again to pick up the new changes once updated. |
Groove Server 2007
| Issue Type | Question or Issue | Answer |
| Groove Manager | In an LDAP environment, Groove users are not receiving Groove Manager e-mails. | If you are integrating Groove Manager with an LDAP directory server, particularly if you are using Lotus Domino directories, make sure that each user record includes a valid e-mail address. The Domino format automatically populates blank user e-mail addresses with default entries, usually preventing Groove Manager e-mails from reaching users. |
| Groove Manager | In an LDAP environment, imported members are showing directory status of Deleted. | If you are integrating Groove Manager with an LDAP directory server, you should access directory server member entries (for data synchronization, for example) using the same LDAP Login Name that was used to import members into the Groove Manager domain. Using a different LDAP Login Name can disrupt your directory entries on the Groove Manager when data synchronization occurs because different LDAP Login Names may have different access to the directory server. Under these conditions, the directory status of user accounts in Groove Manager will appear as Deleted. To update the member's directory status to Imported, change the LDAP Login Name back to the original name used to import members. |
| Groove Manager | Directory synchronization events (user updates and deletes) do not appear in management domain reports; they appear only in server-level reports. | If you have the role of Server Administrator, look for synchronization events at the application level. |
| Groove Manager | Communicator-Groove integration features do not function properly for managed Groove clients. | In environments where managed user contact information originates from an Active Directory (AD) database, a user's `mail' and `RTCSIP' addresses in AD must match (the AD default condition) in order for Groove-Communicator integration to function properly. Because Groove Manager uses AD `mail' addresses for user e-mail addresses, while Communicator's Live Communications Server (LCS), depends on AD RTCSIP addresses, if the two AD address fields do not match (if an administrator edited the `mail' address, for example) and you synchronize Groove Manager with AD, the resulting Groove contact e-mail address will conflict with the Communicator contact e-mail address and Groove-Communicator integration cannot occur. To avoid this condition, check with your Active Directory administrator to ensure that the RTCSIP address and mail address fields in Active Directory match. |
| Groove Manager | In an environment that includes Groove 3.1 (or earlier) users, trying to delete a license set fails. | Provisioned license sets cannot be deleted. Unprovision all the users from the license set. |
| Groove Manager | What steps are necessary to support Groove Manager e-mail? | In order to successfully send e-mail from the Groove Manager, be sure to grant permission to your local computer to relay e-mail through your SMTP server (via the Relay restrictions setting on the SMTP Virtual Server Properties/Access tab). |
| Groove Data Bridge | What prerequisites are necessary for running the Groove Data Bridge as a Windows service? | Before running the Groove Data Bridge as a Windows service, complete the Groove Data Bridge account setup configuration, as described in the Groove Data Bridge installation instructions (and in the Groove Data Bridge Administrator's Guide that accompanies the Data Bridge application). If the Data Bridge is started as a service before configuration is complete. The Data Bridge administrator will be unable to create the necessary directories in the file system. The Remember password option should be selected to prevent prompting for account password while performing automated restarts. This option is set during installation and can be reset whenever the password prompt appears. |
| Groove Data Bridge | What special steps are required for running external PKI on Groove Data Bridge? | When the management domain uses external PKI, the client authentication certificates for the Groove Data Bridge identities should be imported into the Local Machine Personal Store, not the Current User Personal Store. The recommended method is to use the Certificate Add-in the Microsoft Management Console (MMC), then choosing the `machine' option. When using external PKI for Groove Data Bridge on a Vista Server machine, export the certificate from the Vista Server certificate server, and import the certificate to the local Data Bridge machine. |
| Groove Data Bridge | What considerations should be made when choosing paths for Data Bridge account backups, space archives, and GFS workspaces? | The Groove Data Bridge proxy prompt does not function reliably in this Groove Data Bridge version. Specify all the proxy credentials on the Proxy Settings page (accessed from the Groove Data Bridge Options menu). If you are running Groove Data Bridge with a proxy device, configuring the proxy through the Proxy Settings page is recommended. |
| Groove Data Bridge | Available memory is declining noticeably. | Numerous Space Creation and Space Invitation requests can significantly deplete memory. Restart the Groove Data Bridge service when total memory in use exceeds the installed physical RAM. |
| Groove Data Bridge | The Groove Data Bridge intermittently terminates abnormally. | If the following message error appears: Abnormal termination: Groove has detected that a redundant database has become corrupt. This redundant database has been deleted and Groove must now shut down. A new redundant database will be created the next time Groove is started. This is a benign event and can be accommodated by going to the Recovery tab of the Windows Services applet and configuring the Microsoft Office Groove Data Bridge service to automatically restart. |
| Groove Data Bridge | When archiving Groove workspaces for a Groove Data Bridge identity, all workspaces are not archived. | If the archiving feature is not enabled while a Data Bridge identity is receiving workspaces, some spaces for may not be archived, due to the time required for the Groove Data Bridge to scan all workspaces. All spaces should be completely archived during the next 24-hour archive cycle. |
| Groove Data Bridge | The following error appears during installation: You cannot create a new folder here. Choose a different location, you clicked OK past the error, and now the Groove Data Bridge will not run. | Windows limits total path length to 250 characters. Your total path length was too long. To solve the problem and allow you to rerun the post install, follow these steps: 1. Run REGEDIT and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Groove 2. Delete the `PersistRoot' key. 3. Set the GDBInstallState key value to 0. |
| Groove Data Bridge | The Groove data Bridge server contains numerous orphaned workspaces (spaces with no other members than the Data Bridge identity). | You can configure Groove Data Bridge to automatically delete spaces when it becomes the last member of the space. To configure the Data Bridge to automatically delete any space that changes from multiple members to one member, follow these steps: 1. From the Start menu, run regedit and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Groove\ 2. Add the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Groove\EDB 3. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Groove\EDB 4. Add the following DWORD value: DeleteOrphanSpaces = 1 5. Restart the Data Bridge server. Note that any spaces that have made this transition prior to this change will not be automatically deleted. |
| Groove Data Bridge | In a managed environment, does the Groove Data Bridge server support identities from multiple Groove management domains? | No. All managed identities defined for a Groove Data Bridge account must be members of the same management domain. |
| Groove Manager | Auditing fails for management domain members on their managed devices after migrating from Groove 3.0 to Office Groove 2007. | The Groove 3.0 domain member should migrate to Groove 3.1, prior to upgrading to Office Groove 2007. |
| Groove Data Bridge | "The Event Viewer for Groove Data Bridge cannot be accessed." | You can correct this problem, by uninstalling, then reinstalling the Groove Data Bridge Windows service. To uninstall and reinstall the Groove Data Bridge service, follow these steps:
This issue will be addressed in future product versions. |
| Groove Data Bridge | The following message appears when an administrator tries to accept an invitation to an Archive Workspace: You cannot accept invitations from earlier Groove versions. Groove is configured to accept invitations to workspaces created in Groove version 2007 or later. | The administrator's Groove client can be configured to accept invitations from pre-2007 Groove versions as follows:
If the administrator is a managed Groove user, the management domain administrator should configure the workspace acceptance policy to allow pre-2007 versions, as follows:
|
| Groove Data Bridge | You have downloaded a device management key and used it to install and configure a managed Data Bridge account, but instead of displaying the administrative UI, the process hangs. | The password provided for account configuration does not pass the managed device policy governing password creation. Check the Groove Manager device policy for the Data Bridge management domain and use an eligible password to try the setup again. A pop-up message explaining this condition will be provided in future product releases." |
| Groove Data Bridge | What size limits exist for workspaces on a Groove Data Bridge server? | Groove Data Bridge does not archive workspaces greater than 2 gigabytes, so avoid supporting workspaces that exceed that size. You can check the size of any workspace of which a Data Bridge identity is a member by navigating to Workspaces in the Data Bridge administrative interface, selecting a workspace, and clicking Properties. |
Project Server 2007
| Issue Type | Question or Issue | Answer |
| Data Analysis views | You have installed the Microsoft Office Web Components, but you still cannot view data in Data Analysis views. | To view Data Analysis views when the database is on Analysis Services 2005, you need to have at least Microsoft Office Web Components 2003. To allow Microsoft Office Web Components to connect with Analysis Services 2005, you also need to install the Microsoft SQL Server 2005 Analysis Services Client Components. To install the client components, select the appropriate version from the list below. If you are unsure which version you have, select from the list based on your language preference and during the installation you will be notified if you should select the 64-bit one. 32-Bit Version:
64-Bit Version: English x64: http://go.microsoft.com/fwlink/?LinkID=72124&clcid=0x409 Traditional Chinese x64: http://go.microsoft.com/fwlink/?LinkID=72124&clcid=0x404 German x64: http://go.microsoft.com/fwlink/?LinkID=72124&clcid=0x407 French x64: http://go.microsoft.com/fwlink/?LinkID=72124&clcid=0x40C Italian x64: http://go.microsoft.com/fwlink/?LinkID=72124&clcid=0x410 Japanese x64: http://go.microsoft.com/fwlink/?LinkID=72124&clcid=0x411 Korean x64: http://go.microsoft.com/fwlink/?LinkID=72124&clcid=0x412 Simplified Chinese x64: http://go.microsoft.com/fwlink/?LinkID=72124&clcid=0x804 Spanish x64: http://go.microsoft.com/fwlink/?LinkID=72124&clcid=0xC0A |
| Cube Build Scheduling | Any scheduled cube build job set to be in the 30 minute mark (for example, 6:30pm) instead of the hour, is failing to build after the initial build request. | Schedule the cubes to be built at the hour mark (for example, 7:00pm) and the scheduling will work without any problems. |
SharePoint Server 2007
| Issue Type | Question or Issue | Answer |
| People | V2V upgrade server, the public page blog web part is not displaying blog posts. Returning the following error: Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator. | Workaround instructions: Option #1 (patches incorrectly upgraded page):
. Option #2 (new My Site host):
|
| People | V2V upgrade the memberships webpart title is: Displays your site and distribution list memberships. This stretches that left zone to be bigger than it should. | Change the web part title to Memberships. |
SharePoint 2007 "Excel Services"
| Issue Type | Question or Issue | Answer |
| Config | How do I enable Excel Services after performing a farm install? | If you have installed Office SharePoint Server as a farm, Excel Services will be disabled by default. To enable Excel Services, first open SharePoint 3.0 Central Administration. Click on your server name (or your application server name if you have installed separate application and web front-end servers). There you will see a list of services running on your server. To start Excel Services, click Start next to the Excel Calculation Services service. When the page refreshes the Status field should update to Started. If you have multiple application servers in your farm, you will need to start Excel Services on each application server you want to service Excel Services requests. |
| Workbook Loading | What configuration do I need to do in order to allow workbooks to be loaded by Excel Services? | Excel Services will only load workbooks from directories, or locations, that the administrator has specifically designated. These are known as trusted file locations for Excel Services. To add a trusted file location to Excel Services, open the SharePoint 3.0 Central Administration console. Click on the Shared Services Provider name from the left hand navigation bar. Under Excel Services Settings click Trusted file locations. On the next page, click New from the toolbar to create a new trusted file location. Trusted file locations give the administrator the ability to control workbook behavior at a granular level on the server. Each trusted file location has many different options that can be configured which can affect performance, security, and workbook functionality. For instance, the settings for a trusted file location control whether external data is enabled, how long sessions stay active on the server, how large workbooks loaded from that location can be, and more. All workbooks loaded from that location will respect those settings. For more information and guidance on how to configure and use trusted file locations see https://technet.microsoft.com/en-us/library/ff191194(v=office.14).aspx |
| External Data | How do I enable external data connectivity for workbooks loaded by Excel Services? | External data is a trusted file location setting, and it must be explicitly enabled on Excel Services. To enable external data connectivity open the SharePoint 3.0 Central Administration console. Click on the Shared Services Provider name from the left hand navigation bar. Under Excel Services Settings click Trusted file locations. On the next page, click the trusted file location that you want to enable data connectivity for. In the External Data section, under Allow External Data, choose the proper radio button selection to specify where data connections can be loaded from. Excel Services supports loading data connections that are embedded in workbooks, and it also supports loading connections from SharePoint Data Connection Libraries (DCLs), which can be linked to from workbooks. If DCLs are going to be used by the server, like trusted file locations, they must explicitly be designated as trusted data connection libraries. This can be done from the main Shared Services administration page, under the Excel Services Settings section. By default, Excel Services will attempt to use Windows integrated authentication to connect to external data sources. In most enterprise farm installs this requires Kerberos. If Kerberos isn't configured, then authentication to external data sources must be explicitly set for each data connection in a workbook loaded on the server. This can be specified by the properties dialog in Excel client's workbook connections UI. In a non Kerberos environment, another recommended option is to use Single Sign On (SSO) to provide credentials for connecting to external data from the server. For more information on configuring external data, including using DCLs, authentication, and configuring SSO, see https://technet.microsoft.com/en-us/library/ff191194(v=office.14).aspx. |
Other
| Issue Type | Question or Issue | Answer |
| No issues at this time. |
Downloads
| Issue Type | Question or Issue | Answer |
| No issues at this time. |
No comments:
Post a Comment