vivi's SharePoint Space: FrontPage Tips

Error message when you try to edit an Office document in a document library: "'Edit Document' requires a Windows SharePoint Services-compatible application"

Wed, 02 Jan 2008 21:41:22 GMT

http://support.microsoft.com/kb/833714

SYMPTOMS

When you try to edit a Microsoft Office document that is stored in a document library of a Microsoft Windows SharePoint Services Web site, you may receive one of the following error messages, depending on the version of Office that you are running.

2007 Microsoft Office suites

'Edit Document' requires a Windows SharePoint Services-compatible application and Microsoft Internet Explorer 6.0 or greater.

Microsoft Office 2003 and earlier versions of Office

'Edit Document' requires a Windows SharePoint Services-compatible application and Microsoft Internet Explorer 5.0 or greater.

For example, you experience these symptoms if you click a Microsoft Word document in the document library, and then click Edit in Microsoft Office Word.

Additionally, when you click New Document in the document library, you may receive the following error message:

The document could not be created. The required application may not be installed properly, or the template for this Document Library cannot be opened. Please try the following: 1. Check the General Settings for this Document Library for the name of the template, and install the application necessary for opening the template. If the application was set to install on first use, run the application and then try creating a new document again. 2. If you have permission to modify this Document Library, go to General Settings for the library and configure a new template.

CAUSE

This issue may occur if one or more of the following conditions are true:

•	Microsoft Office XP or later is not installed on the computer.
•	Office XP or a later version of Office is installed on the computer. However, the SharePoint support component that is included in Office Tools is not installed on the computer. That is, either Microsoft SharePoint Support or Windows SharePoint Services Support (as appropriate to your version of Office) is not installed on the computer.
•	The Owssupp.dll file is not registered correctly in Microsoft Windows.

RESOLUTION

To resolve this issue, use one of the following methods, as appropriate for your situation.

Method 1: Install Office XP or a later version of Office

Install Office XP or a later version of Office on your computer. When you install Office, make sure that you also install the SharePoint support component that is included in Office Tools in the Setup program. In Office XP, this component is named Microsoft SharePoint Support. In Office 2003 and in later versions of Office, this component is named Windows SharePoint Services Support.

For more information about how to install the SharePoint support component that is included in Office Tools, see the "Method 2: Install SharePoint support" section.

Method 2: Install SharePoint support

To install SharePoint support, do one of the following, as appropriate to the version of Office that is installed on your computer.

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

If Office XP is installed on the computer, follow these steps:

1.	Click Start, and then click Control Panel.
2.	Click Add or Remove Programs.
3.	In the list of currently installed programs, click Microsoft Office XP, and then click Change.
4.	Click Add or Remove Features - Change which features are installed or remove specific features, and then click Next.
5.	In the Features to install box, expand Office Tools, click the down arrow next to Microsoft SharePoint Support, and then click Run from My Computer.
6.	Click Update.

If Office 2003 is installed on the computer, follow these steps:

1.	Click Start, and then click Control Panel.
2.	Click Add or Remove Programs.
3.	In the list of currently installed programs, click Microsoft Office 2003, and then click Change.
4.	Click Add or Remove Features, and then click Next.
5.	Click to select the Choose advanced customization of application check box, and then click Next.
6.	In the Choose update options for applications and tools box, expand Office Tools, click the down arrow next to Windows SharePoint Services Support, and then click Run from My Computer.
7.	Click Update.

If a 2007 Office suite is installed on the computer, follow these steps:

1.	Click Start, and then click Control Panel.
2.	Click Add or Remove Programs.
3.	In the list of currently installed programs, click Microsoft Office suite 2007, and then click Change.
4.	Click Add or Remove Features, and then click Continue.
5.	Expand Office Tools.
6.	Click the down arrow next to Windows SharePoint Services Support, and then click Run from My Computer.
7.	Click Continue.

Method 3: Register the Owssupp.dll file

To register the Owssupp.dll file, follow these steps:

Click Start, and then click Run.

In the Open box, type cmd, and then click OK.

At the command prompt, switch to the folder that contains the Owssupp.dll file.

By default, the Owssupp.dll file is located in one the following folders, as appropriate for your version of Office:

•	If Office XP is installed on the computer: Drive:\Program Files\Microsoft Office\Office10
•	If Office 2003 is installed on the computer: Drive:\Program Files\Microsoft Office\Office11
•	If a 2007 Office suite is installed on the computer: Drive:\Program Files\Microsoft Office\Office12

Type the following line, and then press ENTER:

regsvr32 -u owssupp.dll

Click OK when you receive the message that states that the operation was successful.

Type the following line, and then press ENTER:

regsvr32 owssupp.dll

Click OK when you receive the message that states that the operation was successful.

Type exit to exit Command Prompt.

In my case, just simply Run Repair Office and problem solved.

SharePoint - Firefox and NTLM authentication

Tue, 04 Dec 2007 17:43:17 GMT

From Kathy Hughes, MVP

Note: Assumes internal SharePoint deployment using NTLM authentication where client machine is a member of the same domain where SharePoint is deployed

I discovered this browser workaround several years back and thought I’d post here for reference. Here is the original source:- http://www.cauldwell.net/patrick/blog/PermaLink,guid,c7f1e799-c4ae-4758-9de7-5c3e7a16f3da.aspx.

When using Firefox, avoid being prompted for logon when browsing to SharePoint sites by making the following configuration changes to your Firefox browser:

In the Firefox address bar, type about:config then press <return>
On the subsequent about:config page, scroll down until you locate the key named network.automatic-ntlm-auth.trusted-uris.
Right-click the network.automatic-ntlm-auth.trusted-uris key and click Modify. Enter the name of the SharePoint site (see below) and then click OK. For multiple sites, separate each name by a comma.

Unpacking and repacking files in themes in FrontPage

Wed, 12 Apr 2006 21:24:26 GMT

Via Microsoft:

SUMMARY

This article provides sample Windows Script Host (WSH) scripts that can be used to unpack and repack files used in FrontPage themes.

MORE INFORMATION

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

FrontPage Themes

FrontPage installs themes to the following folder by default:

C:\Program Files\Common Files\Microsoft Shared\Themes

All themes created by you are saved in the following folder:

%USERPROFILE%\Application Data\Microsoft\Themes

Individual themes are saved in a folder named after the theme. For example, the Artsy theme is saved in the Artsy folder. In each theme folder is a file with a .inf file extension and a file with a .elm file extension. The file names match the name of the folder. For example, the Artsy folder contains the Artsy.inf and the Artsy.elm files.

The .inf file contains descriptive information about the theme. The .elm file is a self-defining file list for the theme. It contains an uncompressed concatenation of all the files that compose the theme. The following list shows the basic file format of a .elm file:

•	Line 1: VVV (where VVV is the version number of the .elm file format)
•	Line 2: NNN (where NNN is the number of individual files packed in the .elm file)
•	Line 3 to Line (NNN + 2): filename,filelength
•	Line (NNN + 2) to EOF: "<==MS-Theme==>" & filedata

FrontPage 2000 integrates theme editing functionality so that you can create or modify FrontPage themes. It does not allow you to easily manipulate all of the files in the theme. The WSH code samples provided in this article either unpack all the files in a .elm file or repack the individual files back into a .elm file.

IMPORTANT NOTES

•	If you incorrectly modify a theme, the theme may become unusable and you may need to reinstall it to use it again. Therefore, if you modify a theme, save the theme under a different file name by clicking Save As in the FrontPage 2000 Themes dialog box.
•	Save the WSH code samples as Unpack_elm.vbs and Repack_elm.vbs. If you don't they will not work correctly.
•	Run the scripts listed in this article from a theme's folder; if you run them from a different folder, you may receive errors.
•	The WSH code sample for repacking the .elm file builds the .elm file from all files that are in the folder excluding the .elm file, the inf file, the Unpack_elm.vbs file, and the Repack_elm.vbs file. Because it packs all other files found in the theme's folder into the .elm file, some unused files may be stored in the .elm file.

Unpacking a .elm File

The following WSH script sample unpacks a .elm file into the individual files used in the theme.

Save the following WSH code as Unpack_elm.vbs on your desktop:

Option Explicit

' Declare all variables.
Dim objFSO,objFolder
Dim objInputFile
Dim objOutputFile
Dim strELM
Dim lngFileCount
Dim strFileName
Dim strFileLength
Dim strFileVersion
Dim strFileArray()
Dim X

' Create constants for the .elm version and Theme string.
Const strELMVersion = "4.0.2.4022"
Const strThemeString = "<==MS-Theme==>"

' Create object for file I/O.
Set objFSO = WScript.CreateObject("Scripting.FileSystemObject")

' Get object for current folder.
Set objFolder = objFSO.GetFolder(".")

' Create variable for .elm file.
strELM = LCase(objFolder.Name & ".elm")

' Open the .elm file.
Set objInputFile = objFSO.OpenTextFile(strELM)

' Get the .elm file's version.
strFileVersion = objInputFile.ReadLine

' Get the file count.
lngFileCount = CLng(objInputFile.ReadLine)

' Create an array for file information.
ReDim strFileArray(lngFileCount)

' Create array from the file name/size list in the .elm file.
For X = 1 to lngFileCount
strFileArray(X) = objInputFile.ReadLine
Next

' Loop through the array of files.
For X = 1 to lngFileCount
' Get the file name.
strFileName = Left(strFileArray(X),InStrRev(strFileArray(X),",")-1)
' Get the file size.
strFileLength = Mid(strFileArray(X),Len(strFileName) + 2)
' Create a file object for the output file.
Set objOutputFile = objFSO.CreateTextFile(strFileName)
' Skip past the MS Theme text.
objInputFile.Read Len(strThemeString)
' Extract the packed file data from the .elm file.
objOutputFile.Write objInputFile.Read(strFileLength)
' Close the output file.
objOutputFile.Close
Next

Set objFolder = Nothing
Set objFSO = Nothing

2. Copy the Unpack_elm.vbs file to the folder containing a packed theme. For example, if you want to unpack the Artsy theme files, copy the Unpack_elm.vbs file to the Artsy folder:

C:\Program Files\Common Files\Microsoft Shared\Themes\artsy

3. Double-click the Unpack_elm.vbs script to run it.

4. When the script is finished, the graphics and text files that make up the theme will be unpacked in the folder.

Repacking a .elm File

The following sample WSH script sample repacks the individual files used in the theme into a .elm file.

1. Save the following WSH code as Repack_elm.vbs on your desktop:

Option Explicit

' Declare all variables.
Dim objFSO,objFile,objFolder
Dim objInputFile
Dim objOutputFile
Dim strELM,strINF
Dim strPACK,strUNPACK
Dim strName,strFileNames
Dim strFileArray,lngFileCount
Dim X

' Create constants for the .elm version and the theme string.
Const strELMVersion = "4.0.2.4022"
Const strThemeString = "<==MS-Theme==>"

' Create object for file I/O.
Set objFSO = WScript.CreateObject("Scripting.FileSystemObject")
' get object for current folder
Set objFolder = objFSO.GetFolder(".")

' Create variables for ignored file names.
strELM    = LCase(objFolder.Name & ".elm")
strINF    = LCase(objFolder.Name & ".inf")
strPACK   = "repack_elm.vbs"
strUNPACK = "unpack_elm.vbs"

' Loop through the files collection.
For Each objFile in objFolder.Files
' Get a file name.
strName = objFile.Name
' Is the file name an ignored file name?
If (LCase(strName) <> strELM) And _
     (LCase(strName) <> strINF) And _
     (LCase(strName) <> strPACK) And _
     (LCase(strName) <> strUNPACK) Then
    strFileNames = strFileNames & ":" & strName
End If
Next

' Create an array of file names.
strFileArray = Split(strFileNames,":")
lngFileCount = UBound(strFileArray)

If lngFileCount > 0 Then
' Open the .elm file.
Set objOutputFile = objFSO.CreateTextFile(strELM,-1,0)

' Output the .elm version and file count.
objOutputFile.Write strELMVersion & vbLf
objOutputFile.Write lngFileCount & vbLf

' Loop through the files.
For X = 1 To lngFileCount
    Set objFile = objFSO.GetFile(strFileArray(X))
    objOutputFile.Write objFile.Name & "," & objFile.Size & vbLf
Next

' Loop through the files.
For X = 1 To lngFileCount
    Set objFile = objFSO.GetFile(strFileArray(X))
    objOutputFile.Write strThemeString
    Set objInputFile = objFSO.OpenTextFile(objFile.Name,1)
    objOutputFile.Write objInputFile.Read(objFile.Size)
    objInputFile.Close
Next

objOutputFile.Close
End If

Set objFolder = Nothing
Set objFSO = Nothing

2. Copy the Repack_elm.vbs file to the folder containing an unpacked theme. For example, if you unpacked the Artsy theme, copy the Repack_elm.vbs file to the following folder:

C:\Program Files\Common Files\Microsoft Shared\Themes\artsy

3. Double-click the Repack_elm.vbs script to run it.

4. When the script is finished, the graphics and text files will be repacked in the .elm file for the theme.