List of MOSS 2007 ActiveX Controls

 

Diagram Launcher

 

Server Files       :   TEMPLATE\LAYOUTS\1033\BFORM.JS, TEMPLATE\LAYOUTS\1033\CORE.JS,

                           TEMPLATE\LAYOUTS\1033\INIT.JS, TEMPLATE\LAYOUTS\1033\OWS.JS

Client File          :   DGRMLNCH.DLL

Function           :   Launch Microsoft Office Visio to open diagrams

Non-IE behavior  :  The browser will offer to save the file locally instead of launching the application. The option to

                           "Open with Visio" will not show.

 

Digital Signatures

 

Server Files       :  TEMPLATE\LAYOUTS\INC\1033\IntlCoreStrings.js, TEMPLATE\LAYOUTS\INC\Core.js,

                          TEMPLATE\LAYOUTS\INC\intlcorestrings.js, TEMPLATE\LAYOUTS\SignatureDetails.FormServer.aspx

Function           :  Digital Signature for Microsoft Office clients

Non-IE behavior :  You cannot sign documents, but you can view signatures.

 

Export Database

 

Server Files         :  TEMPLATE\LAYOUTS\1033\CORE.JS, TEMPLATE\LAYOUTS\viewtype.aspx,

                            TEMPLATE\LAYOUTS\1033\OWS.JS

Client File            :  OWSSUPP.DLL

Also Known As      :  SharePoint Export Database Launcher

Function              :  Export list to a Microsoft Office Access database

Non-IE behavior    :  Option to "Open with Access" will not show.

 

List Net

 

Server Files          :  TEMPLATE\LAYOUTS\1033\CORE.JS, TEMPLATE\LAYOUTS\1033\CORE.JS,

                             TEMPLATE\LAYOUTS\1033\OWS.JS, TEMPLATE\LAYOUTS\1033\OWS.JS

Client File            :  STSLIST.DLL

Also Known As      :  Microsoft Office List 12.0

Function              :  Edit list in Datasheet view

Reference            :  http://msdn2.microsoft.com/en-us/library/ms416795.aspx

Non-IE behavior     :  The option to "Edit in Datasheet" will not show.

 

Name Ctrl

 

Server Files        :  TEMPLATE\LAYOUTS\1033\INIT.JS, TEMPLATE\LAYOUTS\1033\OWS.JS

Client File           :  NAME.DLL

Also Known As    :  NameCtrl Class

Function            :  Display presence information for people, integrating with Outlook and Communicator

                          (Instant messaging)

Reference          :  http://msdn2.microsoft.com/en-us/library/ms455335.aspx

Non-IE behavior  :  Presence information will not show.

 

 

OISClientLauncher

 

Server Files        :        TEMPLATE\LAYOUTS\1033\IMGLIB.JS, TEMPLATE\LAYOUTS\upload.aspx

Client File           :        OISCTRL.DLL

Also Known As    :         OSIClientLauncher Class

Function            :         Integration with the Office Picture Manager

Reference             :            http://msdn2.microsoft.com/en-us/library/ms954038.aspx

Non-IE behavior  :         Integration with Picture Manager will not show.

 

OpenDocuments

 

Server Files               :  TEMPLATE\LAYOUTS\1033\HtmlEditor.js, TEMPLATE\XML\DOCICON.XML

Client File                  :  OWSSUPP.DLL

Also Known As           :  SharePoint OpenDocuments Class

Function                    :  Launch Office applications to open documents

Reference                  :  http://msdn2.microsoft.com/en-us/library/ms454230.aspx

Non-IE behavior         :  The browser will offer to save the file locally instead of launching the application.

                                    The option to "Edit In (Microsoft Office application)" will not show.

 

OpenXMLDocuments

 

Server Files          :  TEMPLATE\LAYOUTS\1033\HtmlEditor.js, TEMPLATE\LAYOUTS\INC\Core.js,

                             TEMPLATE\LAYOUTS\ctdmsettings.aspx, TEMPLATE\XML\DOCICON.XML

Client File             :  INLAUNCH.DLL

Also Known As      :  SharePointOpenXMLDocuments

Function              :  Launch InfoPath to open forms

Reference            :  http://msdn2.microsoft.com/en-us/library/ms452435.aspx

Non-IE behavior    :  The browser will offer to save the file locally instead of launching the application. The option to

                             "Open with InfoPath" will not show.

 

Personal Site

 

Server Files          :    None?

Client File             :    PORTAL~1.DLL

Also Known As      :    PersonalSite Class, PortalConnect.PersonalSite

Function              :    Adds your my site to a list of SharePoint sites maintained by the Office client

Non-IE behavior    :    No client-side knowledge of where your MySite is located.

 

Ppactivex

 

Server Files         :    TEMPLATE\CONTROLTEMPLATES\sldlibtemplates.ascx, TEMPLATE\LAYOUTS\1033\SLDLIB.JS,

                              TEMPLATE\FEATURES\SlideLibrary\SldLib\schema.xml,

Function             :    Integration with PowerPoint for Slide Library Templates

Non-IE behavior   :    The Slide Library integration with PowerPoint will not work.

 

RTEDialogHelper

 

Server Files          : TEMPLATE\LAYOUTS\1033\BFORM.JS, TEMPLATE\LAYOUTS\1033\FONTDLG.HTM,

                            TEMPLATE\LAYOUTS\1033\HtmlEditor.js

Client File            :  MSHTMLED.DLL

Also Known As      :  Rich Text Editor, DlgHelper, HtmlDldSafeHelper Class

Function              :  Rich Text Editor used to edit wikis, rich text web part

References           :  http://msdn2.microsoft.com/en-us/library/ms535238.aspx,
                             http://msdn.microsoft.com/workshop/author/editing/tutorials/html_editor.asp 

Non-IE behavior     :   A simpler multi-line text editor with no Rich Text capabilities will show. Consider using the Telerik

                              control, which is available for free download at http://www.telerik.com/sharepoint and works

                              with non-IE browsers.

 

SpreadsheetLauncher

 

Server Files           :    TEMPLATE\LAYOUTS\1033\BFORM.JS, TEMPLATE\LAYOUTS\1033\INIT.JS,

                                TEMPLATE\LAYOUTS\NewTranslationManagement.aspx, TEMPLATE\LAYOUTS\lstsetng.aspx,

                                TEMPLATE\LAYOUTS\new.aspx, TEMPLATE\LAYOUTS\sledit.aspx, TEMPLATE\LAYOUTS\slnew.aspx,

                                TEMPLATE\LAYOUTS\1033\INIT.JS

Client Files            :     OWSSUPP.DLL, OWSCLT.DLL

Also Known As       :     SharePoint SpreadSheet Launcher

Function               :     Integration with Excel to import and export lists

Reference             :     http://msdn2.microsoft.com/en-us/library/ms427792.aspx

Non-IE behavior     :     Options to Export to Excel and Import Spreadsheet will not show. If you register an application

                                 to handle the '.iqy' extension, you might be able to export spreadsheets.

 

Stssync

 

Server Files         :  TEMPLATE\LAYOUTS\1033\BFORM.JS, TEMPLATE\LAYOUTS\1033\INIT.JS

Client File            :  OWSSUPP.DLL

Also Known As     :  SharePoint Stssynch Handler

Function             :  Connect to Outlook to synchronize lists

Reference           :  http://msdn2.microsoft.com/en-us/library/ms456225.aspx

Non-IE behavior   :  Option to "Connect to Outlook" will not show. You should be able register a client application

                           to handle the Stssync:// protocol.

 

UploadCtl

 

Server Files        :    TEMPLATE\CONTROLTEMPLATES\DefaultTemplates.ascx, TEMPLATE\LAYOUTS\1033\BFORM.JS,

                             TEMPLATE\LAYOUTS\1033\INIT.JS, TEMPLATE\LAYOUTS\copy.aspx,

                             TEMPLATE\LAYOUTS\updatecopies.aspx, TEMPLATE\XML\FLDTYPES.XML
                             TEMPLATE\LAYOUTS\upload.aspx

Client File            :   STSUPLD.DLL

Also Known As     :    STSUpld UploadCtl Class

Function             :    Multiple File Upload

Reference           :    http://msdn2.microsoft.com/en-us/library/ms456628.aspx

Non-IE behavior   :    Only single file upload is available. Option for "Multiple File Upload" will not show.

 

Below is a set of PSConfig commands and their equivalent cmdlet in PowerShell

   

Configuring your SharePoint farm using PowerShell

During the SharePoint Installation, make sure you choose “Server Farm” and then “Complete” install. This will allow you to create a SharePoint farm rather than a standalone server.

After the install completes, the setup program will ask you if you want to run the SharePoint Technologies Configuration Wizard (default is checked). Uncheck the box to NOT run the wizard.

Under the Start Menu, browse to Microsoft SharePoint 2010 Products, Right-click on SharePoint 2010 Management Shell and choose 'Run as administrator'

There are seven cmdlets that you will need to provision your farm so that you can access it correctly. The cmdlets are listed below along with their descriptions provided by the Get-Help cmdlet.

1. New-SPConfigurationDatabase
                  The New-SPConfigurationDatabase cmdlet creates a new configuration database on the specified database server. This is the
                  central database for a new SharePoint farm.

* Create a new configuration database and central admin content database.

Note: One of the main reason why we use this method as against the configuration wizard UI is because we can specify the names for the central admin and content databases.

       New-SPConfigurationDatabase –DatabaseName “SharePoint2010_Config” –DatabaseServer “<Your DB Server>”
       –AdministrationContentDatabaseName “SharePoint2010_AdminContentDB” –Passphrase (ConvertTo-SecureString 
       “Password123” –AsPlaintext –Force) –FarmCredentials (Get-Credential)

Note: As you can see, we are having PowerShell prompt us for the farm credentials rather than hard coding it. You can also do this with the passphrase by accessing the “Password” property of the of the credential object: (Get-Credential).Password

After the operation completes, you can confirm that the server has been added to a farm, by reloading the PowerShell window. Close the shell and repeat the “Run as administrator” step followed earlier. It should load with out any warning message(s).

2. Install-SPHelpCollection
                 The Install-SPHelpCollection cmdlet installs the Help site collection files for SharePoint 2010 Products in the current farm. Use
                 the LiteralPath parameter to install specific custom Help collection files. If the LiteralPath parameter is not specified, all available
                 Help in the Help site collection is installed and existing Help collection files are overwritten.

* Install the help files:
                 Install-SPHelpCollection –All

3. Initialize-SPResourceSecurity
                 The Initialize-SPResourceSecurity cmdlet enforces resource security on the local server. This cmdlet enforces security for
                 all resources, including files, folders, and registry keys.

* Secure the files and registry entries (SecureResources in Psconfig):
                Initialize-SPResourceSecurity

4. Install-SPService
                 The Install-SPService cmdlet installs and optionally provisions services on a farm. This cmdlet installs all services, service 
                 instances, and service proxies specified in the registry on the local server computer. Use this cmdlet in a script that you build to
                 install and deploy a SharePoint farm or to install a custom developed service.

* Install and provision the services on to the farm
                 Install-SPService

Note : The above command is for Server farm installations Only. For standalone servers, run Install-SPService -Provision

5. Install-SPFeature
                The Install-SPFeature cmdlet installs a specific SPFeature object by providing in the Identity parameter the relative path from 
                the folder “%Program Files%\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\" to the feature. 
                The SharePoint Feature’s files must already be put in the proper directory, either manually or by using a solution installer. If the 
                AllExistingFeatures parameter is provided, the file system is scanned and any new features are installed. This is generally
                only used during deployment and upgrade.

* Install the features on the server
                 Install-SPFeature –AllExistingFeatures

6. New-SPCentralAdministration
                 The New-SPCentralAdministration cmdlet creates a new Central Administration Web application and starts the central 
                 administration service on the local machine. Central Administration is available only on computers where this service runs.

* Provisions the central admin web application which will also link it with the admin content database created earlier
                  New-SPCentralAdministration -Port 2010 -WindowsAuthProvider "NTLM"

7. Install-SPApplicationContent
                  The Install-SPApplicationContent cmdlet copies shared application data to existing Web application folders. This cmdlet does
                  not take any parameters.

* Install all of the application content
                  Install-SPApplicationContent

That's it!! ….Launch the Central Administration site from 'Start > All Programs > SharePoint 2010 Products > SharePoint Central Administration'. 

All in one place.

The Script

 

# Create a new SharePoint Configuration and Administration database, use “Password123” as the passphrase.

New-SPConfigurationDatabase –DatabaseName “SharePoint2010_Config” –DatabaseServer “<Your DB Server>”

–AdministrationContentDatabaseName “SharePoint2010_AdminContentDB” –Passphrase (ConvertTo-SecureString “Password123”

–AsPlaintext –Force) –FarmCredentials (Get-Credential)

# Installs the Help site collection files for SharePoint 2010 Products in the current farm

Install-SPHelpCollection -All

# Enforces resource security on the local server

Initialize-SPResourceSecurity

# Installs services on a farm

Install-SPService

# The file system is scanned and any new features are installed

Install-SPFeature –AllExistingFeatures

# Creates a new Central Administration Web application and starts the central administration service on the local machine

New-SPCentralAdministration -Port 2010 -WindowsAuthProvider "NTLM"

# Copies shared application data to existing Web application folders

Install-SPApplicationContent

 

Happy SharePointing……

In Windows SharePoint Services, the description field of a workflow history list is truncated when the number of characters used goes beyond 255.
       This behavior is a by-design limitation. Windows SharePoint Services implements a restriction on the number of characters that can be used in a multiline text box. The reason is that the OLE property stream doesn't support more than 255 characters. Having more than 255 characters would cause problems demoting properties into documents.

As a side note, this issue can be reproduced in other areas from within SharePoint with similar results. This means that this behavior is not limited to the description field of a workflow history list but other areas of SharePoint as well like multi-line text fields in columns in a document library, adding a new link through the SharePoint interface to an existing site etc..

 

Issue

In Microsoft SharePoint Foundation 2010 or Microsoft SharePoint Server 2010, you see the following error getting logged in the Application Event Log:

          

Log Name       :  Application

Source           :  Microsoft-SharePoint Products-SharePoint Foundation

Event ID         :  8311

Task Category :  Topology

Level              :  Error

Description      : 

 

 

An operation failed because the following certificate has validation errors:\n\n Subject Name: CN=SharePoint Security Token Service, OU=SharePoint, O=Microsoft, C=US \n Issuer Name: CN=SharePoint Root Authority, OU=SharePoint, O=Microsoft, C=US\nThumbprint: 7884622F8B800E7AFAAFD3DDF98BE8AC96D4F952\n\n

Errors:\n\n The root of the certificate chain is not a trusted root authority.

Additionally, other areas such as search, claims authentication also do not function correctly.

CAUSE

This problem occurs when an administrator deletes the "local" trust relationship of the farm from the "Security" section of the Central Administration web site (Central Administration > Security > Manage Trust)

RESOLUTION

It looks like the root certificate for STS is missing from the SharePoint certificate store. As a result, claims authentication in the environment may totally broken. You will need to export the certificate from the certificate store on the local computer and add it to the SharePoint certificate store. Use the certificate thumb print from the event log to locate the certificate that needs to be added.

In order to resolve this problem, the local trust relationship has to be created. This can be done using PowerShell commands or from the Central Admin site.

PowerShell

          

$rootCert = (Get-SPCertificateAuthority).RootCertificate

New-SPTrustedRootAuthority -Name "localNew" -Certificate $rootCert

After running the above commands, perform an IISReset on all servers in the farm.

Alternate Method (Central Administration site)

1. Export the certificate from the Computer’s certificate store 

1. Log on to the SharePoint server where you are seeing the certificate errors
2. Open Start à Run, type in “mmc”  and hit “Ok”
3. From the file menu, choose “Add/Remove Snap-in”
4. Double click “Certificates”

1. Select “Computer account” and walk through the rest of the wizard. Make sure you select “Local Computer”

1. Hit Finish and then “OK”

1. Go to “Certificates” à SharePoint à Certificates

1. Double click on each of the three certificates and look at their thumbprint (details tab). If the thumb print of the certificate matches the thumb print from the event log, this is the certificate you want to export
2. Export the certificate (right click, All Tasks à Export). Leave all default options selected and save it to the desktop.

 

2.  Add the certificate to the SharePoint certificate store

          

1. Go to Central Admin à Security à Manage Trust.

1. Click on “New”.

1. Specify any appropriate name, and select the certificate you exported earlier.
2. Click OK.

After running the above commands, perform an IISReset on all servers in the farm.