KWSupport : Sharepoint

Hot Fixes for Outlook 2007 Now Available

kwsupport — Thu, 26 Feb 2009 12:49:00 GMT

For those using Outlook2007, two new hotfixes are now available that address specific speed and performance issues as well as a variety of other issues. Hotfixes, by nature, come with some warnings on their use. Hot fix 961752 and Hot fix 967688

Note #1: If you have never requested a hot fix from Microsoft, or it has been years since you have, you will be pleased to find that the process is quite fast and efficient. No longer do you need to even call Microsoft to request a hot fix!

Simply click on the links above to open up a new window with information on the hot fix. In the upper left of the window will be a clickable link" 'View and request hotfix downloads'. Click on the link, enter your email address twice plus a security code and within five minutes you will receive an email containing a link to download the hotfix and a required password. The password is only good for a certain number of days (7 days maximum), so it is best that you download the hotfix as soon as you receive the email from Microsoft.

DCOM 10016 Event Error

kwsupport — Sun, 15 Feb 2009 14:07:00 GMT

After installing SBS 2008, you may begin to see DCOM 10016 event errors being reported in your SBS Monitoring reports as soon as users begin to use Sharepoint/Companyweb. This error is also identified if you run the SBS 2008 Best Practices Analyzer. There have been several posts on how to fix this error, but the instruction always were vague in one specific step.

First, here is the DCOM error as reported in the event log and within the SBS Monitoring report:

Event Source: DCOM Event Id: 10016
Event Details: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

And here is the error as reported in the SBS BPA report:
Local activation permission to the IIS WAMREG Admin Service required

To fix this issue, perform the following steps:

* From the SBS console, click Administrative Tools > Component Services
(or, if you prefer: click Run > comexp.msc)
* Expand down Component Services > Computers > My Computer > DCOM Config
* Right click on IIS WAMREG Admin Service, then click Properties
* Click on the Security tab
* Click the Edit... button within the Launch and Activation Permissions section
* Click Add and add the user named: 'Network Service'
(NB: this is the step that confuses people. Most instructions simply tell you to add the appropriate user, but do not make it clear which user to add!)
* Click on the checkbox to Allow (enable) the Local Activation rights option for this user
* Click OK twice, and close Component Services
* Finally reboot the server for good measure and to ensure the change takes effect

Hope this helps!

SBS 2008 and Sharepoint Log file

kwsupport — Thu, 11 Dec 2008 04:04:00 GMT

If using SBS 2008, one of the things you want to do is to install and run the SBS 2008 Best Practices Analyzer (BPA) on a regular basis. At my first SBS 2008 installation, BPA recenlty reported that my Sharepoint log file was larger than 1gb in size. Strange, I thought, since this customer had not even started using sharepoint. Beyond that, BPA did not offer any suggestions for resolving this issue.

So, here are the instructions (from the SBS BPA team) on what to do:

Step 1: start up command prompt in administrator mode. You do this by clicking on Start, then right clicking on Command Prompt, then clicking 'run as Administrator'

Step 2: From the command prompt:
1. Type: sqlcmd –E –S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query and press Enter
2. From the 1> prompt, type: select name from sys.databases and press Enter
3. From the 2> prompt, type: go and press Enter
This will display a list of all databases know to SQL server. One of them will look something like this:
SharePoint_Config_29c26fca….

Step 3: Now, with the actual name of the Sharepoint database, you will want to enter the following commands, replacing dbname with the actual name of the Sharepoint database. Be sure to leave the brackets [ ], parens ( ), and _log, as noted:

1> BACKUP LOG [dbname] WITH TRUNCATE_ONLY
2> Go
1> Use [dbname]
2> Go
1> DBCC SHRINKFILE([dbname_log],2)
2> Go
1> Exit

For example, if your Sharepoint database was named SharePoint_Config_12345, then you would type in:

1> BACKUP LOG [SharePoint_Config_12345] WITH TRUNCATE_ONLY
2> Go
1> Use [SharePoint_Config_12345]
2> Go
1> DBCC SHRINKFILE([SharePoint_Config_12345_log],2)
2> Go
1> Exit

Hope this helps!

SBS2008 and Sharepoint

kwsupport — Fri, 22 Aug 2008 17:51:00 GMT

I've listened to three live web training sessions on SBS2008 recently. On all three sessions, they had Microsoft Partners share their "real world" customer experiences with the early betas of SBS2008. I was interested (perhaps surprised?) to hear all three Microsoft Partners rank Sharepoint 3.0 as being one of the major hot topics for their customers.

One of the partners emphasized that we should NOT view Sharepoint as an optional extra, just as most of us do not view Exchange as an option to SBs, but an integral part.

If your only experience with Sharepoint ahs been with version 1.x/2.x, perhaps it's time to take a look at Sharepoint 3.0! Did you know it now supports Blogs and Wikis? Or take a Demo tour of Sharepoint 3.0!

Enjoy!

SBS and the 3GB switch

kwsupport — Sun, 25 Nov 2007 17:41:00 GMT

For several years, there has been an on going discussion on whether or not to enable the /3GB switch in the boot.ini file for an SBS server. By and far, the consensus of opinion has been to NOT use the /3GB option - especially considering that WSS 2.0...(read more)

Publishing multiple web or sharepoint sites in SBS

kwsupport — Sat, 21 Oct 2006 15:03:00 GMT

Here are some links to frequently asked questions about hosting multiple websites or sharepoint sites on an SBS server, and hosting multiple mail domains (with thanks toi the M&M ladies, Sean and Vlad)

How to publish websites with ISA 2004:
http://www.smallbizserver.net/tabid/266/ArticleType/ArticleView/ArticleID/134/Default.aspx

Hosting a website on your SBS 2000 & 2003:
http://www.smallbizserver.net/tabid/266/ArticleType/ArticleView/ArticleID/89/Default.aspx

Publishing multiple sharepoint web sites:
http://www.vladville.com/2005/08/sbs-web-sharepoint-hosting-guide.html

Hosting multiple domains on an SBS Server:
Part 1: http://seanda.blogspot.com/2004/10/hosting-multiple-domains-on-sbs-2003.html
Part 2: http://seanda.blogspot.com/2004/10/hosting-multiple-domains-on-sbs-2003_22.html
Part 3: http://seanda.blogspot.com/2004/10/hosting-multiple-domains-on-sbs-2003_25.html

Sharepoint and Full Text Indexing and Searching

kwsupport — Sat, 08 Oct 2005 23:42:00 GMT

With SBS2003 Standard, Sharepoint uses WMSDE. But if you have SBS2003 Premium, and have installed SQL you should consider upgrading your Sharepoint site to SQL. Besides better performance as you add more users, you also gain the ability to enable full text indexing and searching!

Instructions for upgrading Sharepoint to SQL and enabling fulltext search can be found in KB article 837367: http://support.microsoft.com/?kbid=837367

HTTP 500 error after updating Sharepoint

kwsupport — Thu, 30 Jun 2005 01:47:00 GMT

If you have received "0x80040E14" or "HTTP 500" error message when you connect to your Windows SharePoint Services Web site after you install a Windows SharePoint Services service pack or a security update, see the following KB article 841216:

http://support.microsoft.com/default.aspx?scid=kb;en-us;841216

How to Reinstall Sharepoint

kwsupport — Thu, 30 Jun 2005 01:35:00 GMT

I have not had to do this myself, but as I routinely see questions about removing and reinstalling Sharepoint , I thought posting instructions provided by Microsoft CSS may be helpful to someone down the road!

Generally speaking, if you want to completely reinstall companyweb on SBS 2003 SP1, you need to follow the article KB829114 below, but it might ask you to insert the SBS SP1 CD3, so you need to extract SBS SP1 installation folders, and then point the SBS Integrated setup program to the folder for the 'SP1 CD3' contents.

The extraction process is listed below, please do follow the exact steps or the extracted files will be removed:
1. Start a cmd prompt and change directory to the SP1 download folder (or the SBS03_SP1 folder on PKG_CD2).
2. Then type "<path>\SBS2003-KB885918-SP1-X86-ENU.EXE /x" (with no quotation marks) and press Enter.
3. Specifying a path for the extracted files (such as C:\SBSSP1)
4. Run the SBS Integrated setup, and when the setup program prompts for the CD3, point it to the folder created above.

829114 How to remove and how to install the Windows Small Business Server 2003
http://support.microsoft.com/?id=829114

As I know, we are able to keep the original SharePoint database and connect it to the new installation. If the original database is not corrupted, you may manually backup the files and then reconnect the database after reinstalling the components:

829113 How to restore a Windows SharePoint Services CompanyWeb database after
http://support.microsoft.com/?id=829113

827701 How to perform a disaster recovery operation of SharePoint Services
http://support.microsoft.com/?id=827701

As I know, on SBS 2003 we have a document which can make a full backup and restore for the whole system. It might be useful to you, I suggest you have a look at it:

Backup and restore SBS 2003:
http://download.microsoft.com/download/b/d/8/bd8e1a40-d202-429a-8eb7-26300d62bcc9/BKU_BkupRstr.doc

Best regards,
Charles Yang (MSFT)
Microsoft CSS Online Newsgroup Support

Index PDF documents within Sharepoint

kwsupport — Thu, 30 Jun 2005 01:27:00 GMT

Chad Gross, once again, is the Sharepoint man of the day for coming up with this method for indexing and searching through PDF documents within Sharepoint:

To get full text search capability on SBS, the best method is to follow the instructions on the SBS Premium Technologies CD. Now, to get full-text search of PDFs (including content) will require a few extra steps:

1) Install the PDF iFilter from Adobe on your SBS:
http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611

2) Verify the Indexing service is started & set to start automatically.

3) Add the PDF icon to your docicon.xml file so your Document Libraries show the correct icons for your PDFs:
http://msmvps.com/cgross/archive/2004/10/26/16679.aspx

Another thing to realize is that not all PDFs are created equal, and some require additional handling in order to be able to search their contents. Basically, if you create a PDF locally from a Windows application (Word, Excel, QuickBooks, etc.) using Adobe's Acrobat Distiller or PDFWriter, then the PDF will include text that the iFilter will detect when the PDF is uploaded to your Sharepoint site.

As a result, you'll be able to search the contents of these files from Sharepoint. However, if you're scanning documents to a PDF format - then what you have is an image dumped into a PDF. As a result, these scanned documents are not able to have their contents searched without extra handling.

So what's the extra handling? If you're scanning documents, you'll want to make sure you run your scans through an OCR application and then create a dual-layer PDF (image + OCR text). Then when you upload this dual-layer PDF to your Sharepoint site, the iFilter detects the OCR text allowing you to search the contents.

For low to medium volume jobs, I would recommend ScanSoft's OmniPage Pro - it works with most scanners and is one of the most accurate OCR engines I've used. It also allows for workflow creation to help automate the scan / ocr / save process, and natively supports creating dual-layer PDFs. If you're looking at medium to large volumes of scanning, I would recommend
taking a look at leasing a new copier / printer / scanner / fax unit. Gestetner has several newer units that include the ability to scan to a PDF + OCR right at the unit.

Sharepoint Search not working

kwsupport — Sat, 13 Nov 2004 01:36:00 GMT

If you are running Sharepoint with SQL (not WMSDE), you're supposed to be able to perform full text searchies. If searching is not working for you, make sure it's enabled. Here's how:

1. Click Start > Administrative Tools > Sharepoint Central Administration.
2. Scroll down to the Component Configuration section
3. Click on the Configure full text search link
4. Click the box to enable full text search
5. Click OK, and then wait several seconds while it updates.

SBS2003 - Required Ports

kwsupport — Sun, 31 Oct 2004 13:36:00 GMT

This information comes from the Microsoft “Securing your SBS2003 Network” document, which can be found at: http://download.microsoft.com/download/1/f/1/1f15a874-f696-4992-b5ad-b1e7b258de1c/SecuringSBSnetwork.doc

Services and TCP Port Numbers

Service	TCP Port Number	Inbound Access Recommendations
E-mail	25	Allow if you are using Exchange to receive Internet e-mail.
Web server	80 (required for HTTP requests for your site) and 443 (required for HTTPS requests using Secure Sockets Layer (SSL), which secures communications from your server and a Web browser)	Allow if users on the Internet need to access specific Web-site services on your server. Web-site services that use port 80 and/or port 443 include the following: -Microsoft® Office Outlook® Web Access (OWA) -Windows Small Business Server 2003 server performance and usage reports -Outlook Mobile Access (OMA). -Business Web site (wwwroot), which allows users to access the company's Internet Web site from the Internet. -Outlook via the Internet (RPC over HTTP) feature of Outlook 2003.
Windows SharePoint Services intranet site	444	Allow if users securely access the intranet Web site created by Microsoft® Windows® SharePoint™ Services from the Internet.
Remote Web Workplace	4125 and 443	Allow if users securely access Remote Web Workplace to: -Connect to the local network from OWA -Create a direct Remote Desktop Web (RWW) Connection to client computers on the local network. -Use the Windows SharePoint Services intranet site (this also requires port 444, as noted above). -Download Connection Manager to configure the remote client computer for remote access (using remote access also requires that port 1723 be open, as noted below).
Virtual private network (VPN)	1723	Allow if remote clients connect securely to the network using a VPN connection to use resources as if the client was connected locally.
Terminal Services	3389	Allow if remote clients connect to the computer running Windows Small Business Server 2003 using Terminal Services.
File transfer protocol (FTP)	21	Allow if remote clients use file transfer protocol (FTP) to connect to the computer running Windows Small Business Server 2003.

Generating web cert for other sites on the server

kwsupport — Thu, 28 Oct 2004 16:38:00 GMT

DonDinCT asked this great question on the NG:

“When I generate a certificate for my server during installation, does it only work for the default web site ? Do I need to create a seperate certificate for each web site that I add ?”

And John gave this equally great response:

The certificate is automatically added to the companyweb and default web sites. You can manually add it to others if you would like. If you want to add the existing one:

Right click on the site and go to properties
Go to security tab
Click the server certificate button
Click next and choose assign an existing certificate
The SBS created cert should be in the list. Just pick that cert and click Next
Set the SSL port and finish the wizard.

Best Regards,
John Bay, MCSE 2003
Microsoft Support Engineer

Recreate Virtual IIS directories

kwsupport — Sat, 02 Oct 2004 14:33:00 GMT

This post comes via Ray and Damian at Microsoft, via Les!

Sometimes, things just get so screwed up that you want to re-create the virtual directories. I know the feeling. Thanks to Ray Fong and Damian Leibaschoff (both MS) for previous posts, here is how to do it.

In IIS, expand Default Web site and remove the following virtual directories:
- EXCHANGE
- EXCHWEB
- PUBLIC
- OMA
- EXADMIN
- (Do not remove EXCHANGE-OMA)

Then, enable real time editing of the metabase in IIS admin, for this:
1. Open properties on the server object.
2. Check the box 'Enable direct metabase edit'
3. After this, open windows explorer and navigate to the following directory: windows\system32\inetsrv
4. Edit metabase.xml (make a backup first) with notepad and navigate to the following section: /LM/DS2MB/HighWaterMarks
5. Set the Value="207778" to zero or delete it. This value will be located in a string value like the following (The value may be different):

/LM/DS2MB/HighWaterMarks/{79F81D41-A652-4375-85F0-41A16037CC85} >
<Custom
Name="UnknownName_61472"
ID="61472"
Value="207778" <----- Set this to "0"
Type="STRING"
UserType="IIS_MD_UT_SERVER"
Attributes="NO_ATTRIBUTES"

6. Alternatively, you can use Metaedit to make these changes.
7. Save the file.
8. Run IISRESET and then re-start the MsExchangeSA service.

The deleted virtual directories should get re-created after a few minutes from the information that Exchange keeps in Active Directory.
--
Les Connor [SBS Community Member]
-------------------------------------
SBS Rocks !

Discrepancy with configuring SSL & Sharepoint

kwsupport — Wed, 28 Jul 2004 12:38:00 GMT

Issue: In the midst of religiously following "Publishing a SharePoint Web Site Accessible to External Users" (Microsoft, October 2003), I ran into a conundrum. The instructions state at one point:

103. In the Web Server Certificate Wizard, complete the following: z. On the Server Certificate page, select Assign an existing certificate.

The problem is that there is no choice for "Assign an existing certificate".

Resolution: According to post by Les Connor, there may be a discrepancy in the KB:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=e9qlUtB5DHA.2300%40TK2MSFTNGP10.phx.gbl&rnum=1

Before:

***********************************************************************
7. On the "Server Certificate" page, click "Assign an existing certificate", and then click "Next".
***********************************************************************

Correction:

7. On the "Server Certificate" page, click "Replace the current certificate", then click "Next".

How to restore a Sharepoint site

kwsupport — Sat, 24 Jul 2004 04:18:00 GMT

Check out Microsoft's article on the subject:
829113 HOW TO: Restore a SharePoint CompanyWeb Database After the Intranet
http://support.microsoft.com/?id=829113

Frontpage Extensions on SBS2003

kwsupport — Fri, 02 Jul 2004 10:24:00 GMT

To configure your front page extension in SBS 2k3, you can find the admin site by clicking:
Start -> All Programs -> Administration Tools -> Microsoft SharePoint Administrator

Then you will find the FrontPage Server Extensions 2002 Server Administration page open.

If you want to manage a certain website such as default website, please just open the server management, expand IIS, expand website and right click the Default web site. And then, point to 'All Tasks' and now, you will find 'Check Server Extensions', Recalculate Server Extensions 2002 Web, Remove Server Extensions 2002 and SharePoint Central Administration options. You can click any of them to manage your site according to your requirements.

In addition, please do not install standard FPSE on your SBS server. It will damage your intranet site and cause lots of problems.

Thanks for your time and have a good day!

Best Regards,

Eric Sun,
MCSE2000 / MSCA / MCDBA
Microsoft Partner Support Professional

Relocate Sharepoint Database

kwsupport — Sun, 14 Mar 2004 21:32:00 GMT

These instructions to relocate your Companyweb / Sharepoint database comes from David Copeland at Microsoft.

Stop the Companyweb site as well as any other web sites that have been extended with Windows SharePoint Services (WSS).

Create the new directory/drive where the databases will be moved to (in the example below is e:\newlocation)

I would suggest that the directory have the same permissions as the
\program files\microsoft sql server\mssql$sharepoint\data directory has

Replace "servername" with the name of your server.

The following section will detatch (the WSS config and content databases)
c:> OSQL -E -S servername\sharepoint <Enter>
sp_detach_db 'STS_Config' <Enter>
go <Enter>
sp_detach_db 'STS_servername_1' <Enter>
go <Enter>
Once the databases are detached, then using Explorer or another command prompt you should be able to copy the databases to their new location. (would suggest copying instead of moving just in case there is any kind of problem)
sp_attach_db @dbname = 'STS_Config', @filename1= 'E:\new location\STS_config.mdf', @filename2 = 'E:\new
location\STS_Config_log.ldf' <Enter>
go <Enter>
sp_attach_db @dbname = 'STS_servername_1', @filename1= 'E:\new location\STS_servername_1.mdf', @filename2 = 'E:\new location\STS_servername_1_log.ldf' <Enter>
go <Enter>
exit
Restart any of the web sites that had been stopped previously

Hope that helps,
David Copeland
Microsoft Small Business Server Support

Companyweb slow to open

kwsupport — Sun, 14 Mar 2004 19:30:00 GMT

You can speed up the launching of the Companyweb site by changing the IIS Application Pool.

Go to IIS Manager
Open the Application Pools
Right click on the DefaultAppPool and go to properties
Go to the Performance Tab
Uncheck the top box - shutdown worker processes after being idle.

http://www.sbslinks.com/AppPool.htm