June 2005 - Posts
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
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
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.
If you are using Sunbelt Software's IHateSpam Exchange (Server) Edition v1.6, there should be hourly updates in the micro_updates subdirectory. If you are running ISA, you may discover that you are not getting the updates. Here's how I fixed the problem:
1.Go to C:.\Program Files\Sunbelt Software\IHateSpam Server Edition directory
2. Edit the file cartridge.cfg with Notepad
3. Go to the end of the file and look for the line that reads:
# http proxy = localhost:8800
4. Edit this line by first by deleting the pound (#) symbol, and then entering the ip address and proxy port as appropriate for your SBS server. In my case, my server's internal IP address is 10.0.0.2, so I changed the line to read:
http proxy = 10.0.0.2:8080
5. After saving this file, go to a command line on your SBS server and enter: iisreset /restart
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
Here's a response I provided to a recent post asking how to move an SBS server to new hardware. In this instance, the user wanted to both upgrade from SBS2000 to SBS2003, and they also wanted to move to new hardware:
There's more than one way to do a migration (moving SBS2000/2003 to new hardware), and a lot of things add into the mix --- like how many users you have on youre server, any specific applications, etc.
If it were me, given your scenario, I would SKIP any thoughts of upgrading to SBS2003 first on your current server, before migrating. Since your
current server is working fine, and you have new equipment, I might suggest taking a look at Jeff Middleton's SwingMigration approach at www.sbsmigration.com .
Here's why:
1. Your current server remains up and running thorughout the process, until the very end. That means minimal impact to your users
2. You install SBS2003 fresh on your new server. Shoot, install it 2 or 3 times to get a feel for it, test out your recovery process, etc.
3. Then once you are ready, you do a final swing, move over your Exchange database, and all user data files, etc.
4. The advantage is that there's virtually no impact to your users, or to their workstations. Literally you turn the workstations on, and sign in like
you did before. Users won't know anything has happened!
Now, the "gotcha" for all of this is two simple things:
1. You need another computer to act as an interim server. I simply used a spare laptop with 768mb of memory, for this process.
2. You've got to plow through all of Jeff's manuals, documentations and notes. ;-) Not that the process is hard, buy Jeff goes into a lot of detail so
you are not only aware of what's going on at each step of the migration, but also -- if you run into any problems, he's already addressed them!
My first swing migration was an SBS server with 20 users, and except for one printer and one shared folder permission I forgot to restore, it was completely painless to the end users. I migrated the server over a weekend. When the users came in the next week, they logged in and started working.
SBS 2003 SP1 Premium includes ISA 2004. After upgrading to SP1, I discovered that I could not do an FTP upload from any workstation - it was failing with a 500 access denied error.
Here's the fix:
On your SBS server, open up ISA Server Mgmt, click on Firewall Policy, and scroll down and locate the policy labeled 'SBS Internet Access Rule'. Right click on this rule, and then click on the option 'Configure FTP'.
In the popup window that opens, click to UNCHECK the 'read only' option, then click Apply, then OK.
THEN --- look towards the top of the ISA Firewall Policy window, and you will see two new buttons displayed: Apply and Discard. Be sure to click on Apply, otherwise the changes you just made will NOT be applied.
That's it.
Go back to your workstation, restart your FTP client utility and happy uploading!