Modern Web Design Articles and Tutorials

One of the most common problems around the office seems to be the browser crashes when attempting to open files in a SharePoint document library.  Luckily, most of the time it is an easy fix. 

Problem: Internet Explorer crashes (stops responding) when you try to open an Office document in a SharePoint document library.

Scenario: You connect to a document library in a Microsoft Office SharePoint Server 2007 site or in a Microsoft Windows SharePoint Services 3.0 site by using Windows Internet Explorer 7 or Microsoft Internet Explorer 6. However, when you try to open a Microsoft Office document, Internet Explorer crashes (stops responding). 

This problem occurs if the following conditions are true, in the order in which they are presented:

• You install a Microsoft Office 2003 product on the computer.
• You install one or more 2007 Office system programs on the computer.
• You repair or update the installation of an Office 2003 product.

In this scenario, the older version of the Name.dll file becomes the registered version. When the Owssupp.dll file is used, it tries to use functionality that is not available. This condition causes Internet Explorer to crash (stop responding). 

Solution: Download and install Microsoft Hotfix Patch
http://support.microsoft.com/kb/938888

Accidents happen… If Sharepoint has crashed and your database needs to be restored, here is how you can do it; this is a high level overview.

1. Restore database to a new Database

2. Dismount content database from Site you are restoring by using the central administration admin utility from DOS on one of the Sharepoint Front-end’s or Index Server run the following command from the following location

3. C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

4. stsadm -o addcontentdb -url -databasename

5. Results should be something similar to the following:

“Upgrade completed with errors. Review the upgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\Upgrade.log”

The number of errors and warnings is listed at the end of the upgrade log file.

Problem description: If a site has a document library using the Datasheet view a user will receive the following error when trying to navigate to the site.

“The list is displayed in Standard view. It cannot be displayed in Datasheet view for one or more of the following reasons: A datasheet component compatible with Windows SharePoint Services is not installed, your browser does not support ActiveX controls, or support for ActiveX controls is disabled.”

There are three possible solutions:
1.  Active X Security levels are not properly set.  Although, this may be the problem most likely the properties are correct.  Double check to see that they are set properly.
 
2.  The installation of Microsoft Office 2003 is corrupt.  It will need to be repaired:

a. Click Start, and then click Control Panel.
b. Double-click Add or Remove Programs, click Microsoft Office 2003, and then click Change.
c. In the Microsoft Office 2003 Setup dialog box, click Reinstall or Repair, and then click Next.
d. Click Detect and Repair errors in my Office installation, and then click Install.

 3. The registry key may need to be deleted (if present) 

a. Close IE
b. Start > Run > type “regedit”
c. locate HKEY_local_machine\software\microsoft\internet explorer\ activex compatibility sub-key {65BCBEE4-7728-41A0-97BE-14E1CAE36AAE}
d. Delete the folder
e. Restart IE

Sometimes sites need to move from one location to another. Here is how you do that using the Sharepoint CLI utility stsadm.

Note: Always perform in a test environment. An empty site must be in place before a cabinet file can be imported

1. Use MOSS07’s sts_adm.exe tool on test server located in directory: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

2.Export Command:

stsadm -o export -url http://toplevelsite/subsite -filename c:\folder\sitename1.cab -version #

Version #: Any content that hasn’t been approved will not be exported by default.

3. Import Command:

stsadm -o import -url http://toplevelsite2/subsitelocation -filename c:\folder\sitename1.cab

Important: Do not use -backup/-restore commands to move sub-sites, this will cause the top level site and database to be overwritten.

Always perform in a test environment prior to running commands on a production server.

For moving a subsites or toplevel sites to subsites. etc.

SharePoint workflows are very useful for sending automated emails when a list item is created or changed. As well, a workflow can be manually started from an item. SharePoint time zones can get a bit tricky when your workflow e-mails are sending date and times. This can confuse some recipients and may cause some problems when time accuracy is required. The following is a very simple workaround that may seem obvious to some, but in any case it’s always good to share!

Read the rest of this entry »