Installing SharePoint in Microsoft Office

Printer QR Code JIS X 0510 in Microsoft Office Installing SharePoint

g To set the connection string for the server, click the Edit Global Configuration button to modify just for the site, click the Edit Configuration button h On the ASPNET Configuration Settings window, click the General tab i In the Connection String Manager pane, you should see the default connection string (LocalSqlServer); click on the row to select it and click the Edit button, modify the Connection parameter string accordingly, and then click OK to save j If LocalSqlServer is not shown, create a new entry by clicking the Add button, then enter Name as LocalSqlServer and the connection string to use in the Connection parameter field, and click OK to save k Click OK to close the settings window l Click OK to close the Properties window m Exit IIS Manager via File | Exit

Workflow Extensions (part of NET 30) are required for SharePoint and are necessary to enable using work flow tools within Visual Studio The extensions provide you with tools to work directly with the Windows Workflow Foundation and include the ability to create complex workflows in Visual Studio Assuming you already installed the 30 Framework and SDK, you must also download the latest version from the Microsoft site and install the Visual Studio 2005 Extensions for Windows Workflow for NET Framework 30

Apply the Visual Studio Service Packs 1 & 2

There is nothing remarkable about the service packs, but I do have a few suggestions for working with them: Copy the entire service pack installation package to the PC or server you want to update; do not try to apply the service pack over the network or use a file share During the installation (which can take quite some time), you may encounter Error 1718, File <file> was rejected by digital signature policy message and the installation will quit In order to correct this issue, refer to the instructions in Microsoft KB925336, which can be found below (after this fix, reboot and reapply)

http://supportmicrosoftcom/kb/925336

To work with SharePoint, you will need to download the Visual Studio 2005 Extensions for Windows SharePoint Services 30 from the Microsoft Download site to ensure you obtain the latest version Note that you cannot install these until after WSS/MOSS and Visual Studio have been installed

Step 10: Install Microsoft Office (Development or QA)

Project Task This task covers the installation of the Microsoft Office Products needed for both development and testing; this task follows installation of the server and Operating System software and should be accomplished before installing any SharePoint software While this step can be considered optional, much of SharePoint s functionality is extended through the tight integration with Office applications and in both development and QA, it is highly likely that testing features will need to utilize these applications While the full suite is suggested, the minimal applications should include Word 2007, Excel 2007, PowerPoint 2007, and Outlook 2007

Project Task This task covers the installation of the software packages for both Windows SharePoint Services platform and Microsoft Office SharePoint Server This task follows installation of the server and operating system software The installation Windows SharePoint Services and Microsoft Office SharePoint Server is nearly identical using either the Basic or the Advanced methods Again, this is because the install process in either WSS or MOSS is installing the platform In fact, the only noticeable difference in the installation is that MOSS requires you to enter a serial number to install (this is usually printed on the DVD jewel case or available from the MSDN Site for MSDN subscribers); the real differences between the two are not evident until configuring the products for use Troubleshooting Note In some installations, it is possible that when attempting to install

Office 12 products, you may receive an error that says The language of this installation package is not supported by your system There are two possible fixes for this issue The first is caused if using an ISO image and the files have been extracted; if using ISO Buster, you must be sure to select the normal extract indicated by the >\>> button to extract all of the files individually; do not extract the files as an ISO The second is by adding a few keys and a string value to the registry, which can be done by hand or by using a text file If using a file, create a new text file and enter the following:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\120\ServerLanguage] "1033"=""