November 2005 - Posts

So last week I set out to add the ability for my clients SharePoint search engine to index WordPerfect documents.  I figured this should be relatively easy to do and that a quick Google search would fetch me all of the information I would need.  WRONG ANSWER!  Turns out I couldn’t find a single person who had done this (and would admit to it) or had clue one about the process.  Not even in Corel’s newsgroups. 

 

Well, since the client needed it I was pretty much stuck figuring it out.  And now that I figured it out I guess I should share it with everyone.  Hopefully next time someone Googles for the answer they will find this article handy.  For those of you who are very familiar with the Adobe I-filter install you will find these instructions very similar just a couple of WordPerfect is “special” tweaks.

 

After a day of looking for the WordPerfect 12 I-filter I was kindly informed that their file format had not changed since version 8 so I gave up on the v12 I-filter (though I still think it exist somewhere) and downloaded the version 8 I-filter from here.  ftp://ftp.corel.com/pub/WordPerfect/wpwin/8/ You need to download the file WPIFilter.exe and WPIFilter.reg.

 

You can get the install instructions and all necessary files from here.  http://www.sharepoint911.com/Shared%20Documents/WordPerfect%20I-filter/SharePoint%20WordPerfect%20Ifilter%20install.zip

 

 

These instructions work for both SharePoint Portal Server 2003 and Windows SharePoint Services.

 

Note:  If you are using WSS only you can skip steps 16 through 22.

 

  1. Steps 2 through 15 need to be ran on all of your SharePoint Index servers and your SQL servers.
  2. Download WPIFilter.exe and WPIFilter.reg from ftp://ftp.corel.com/pub/WordPerfect/wpwin/8/
  3. Now execute wpifilter.exe
  4. Click Yes at the self extracting message
  5. Read and Accept the license agreement
  6. Click Next at the welcome screen
  7. Click Next at the ready to install screen
  8. Click Yes at the are you sure screen
  9. Click Ok at the update is successful screen
  10. Click Finish at the complete screen
  11. Click cancel if you are prompted to restart
  12. Now double click the wpifilter.reg file
  13. Click Yes at the are you sure screen
  14. Click Ok at the successful screen
  15. Now you have successfully updated your server.  If you have a multi server farm then you should rerun this part of the install on all of the index and SQL servers.
  16. On any of the SQL servers you have updated you need to restart the Microsoft Search service to allow the SQL full text indexes to index WPD files. 
  17. Now we are half way there.  We need to edit the portal search to allow the WPD file type.  We do this by opening our portal in the browser and clicking Site Settings.
  18. Now click configure search and indexing
  19. Now click include file types
  20. Click the button for New file type
  21. enter WPD and click Ok
  22. This will now allow your indexes to include WPD files the next time you perform an update. 
  23. Last thing is we need to setup SharePoint to use an icon for WPD files instead of the unknown icon.  We do this by going to the server and going to the folder c:\program files\common files\microsoft shared\web server extensions\60\template\images and copy the file wpd16.gif file to this directory.  I had to make my own.  You can get it from http://www.sharepoint911.com/Shared%20Documents/WordPerfect%20I-filter/wpd.gif
  24. Now we need to go to the folder c:\program files\common files\microsoft shared\web server extensions\60\template\xml and edit the file docicon.xml.  Look for the <byextension> section and add a new line <Mapping Key="WPD" Value="wpd16.gif" />
  25. Save the file.
  26. Now after an IISReset you should see the new icon when you view WPD files in document libraries and the search results.  Though on one occasion I did see a server who required a reboot first so your results may vary.
  27. If you have multiple web front end servers you need to repeat steps 23 - 26 on each server. 

 

I hope these instructions save someone else the time I spent banging my head on the table.  J

 

 

Shane Young

SharePoint Help

Posted by Shane | 14 comment(s)

My buddy Tony Bierman at SharePoint Solutions just put this together.

http://sharepointsolutions.blogspot.com/2005/11/sharepoint-portal-area-listings-rollup.html

 

Good Job Tony!

 

Shane

SharePoint Help

Posted by Shane | with no comments

http://andrewconnell.com/blog/articles/UseVirtualPCsDifferencingDisksToYourAdvantage.aspx

Andrew Connell, fellow MVP, has this great blog on using differencing disks to drastically cut down on the amount of storage you need for VHDs.  He also has some good tips on getting better performance and how to setup a base image.  Check it out if you get a chance.

Shane

Posted by Shane | 1 comment(s)

http://office.microsoft.com/en-us/assistance/HA100214291033.aspx

Nice little article on all of the new features like support for advanced proxy configs and a good explanation of how they work. 

Posted by Shane | with no comments

This is a WSS SP2 issue that causes some havoc in SPS.  The official KB is coming soon this is just a little preview. 

 

Applies To:  Windows SharePoint Services and SharePoint Portal Server 2003

 

 

Summary/Symptoms:

 

When you attempt to create a new area in SharePoint Portal Server 2003 after applying Windows SharePoint Services Service Pack 2 you receive the following error message:

 

An error has occurred in the portal site. Contact the portal site administrator for assistance.

 

 

Cause:

 

The file timestamps on the SharePoint SQL script files is incorrect.  These files are located in  <drive>:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\SQL.

 

Because the timestamps are incorrect WSS SP 2 did not update these files and subsequently the stored procedures for the content databases were not updated.

 

 

Resolution/Workaround:

 

1.  Remove the *.SQL files in location <drive>:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\SQL.

2.  Go to Add/Remove Programs, Windows SharePoint Services, Repair/Reinstall.

3.  Select ‘Detect and Repair errors in Microsoft Windows Sharepoint Services 2.0 installation’.

4.  After repair completes you will need to force an upgrade so the stored procedures on the content databases are updated.

 

To complete this step, use the Stsadm.exe command-line tool to force an upgrade of the content databases.

 

To do this, follow these steps:

 

1. Click Start, click Run, type cmd in the Open box, and then click OK.

2. At the command prompt, type the following lines, and then press ENTER after each line:

cd /d %commonprogramfiles%\Microsoft Shared\Web Server Extensions\60\Bin

stsadm -o upgrade -forceupgrade

3. Type exit to quit Command Prompt.

Posted by Shane | 1 comment(s)
There is a new WSS SP 2 issue that the product team identified with SharePoint virtual servers running ASP.NET 2.0.  The problem is that the Online Web Part Gallery will display (0) web parts.  If a customer had previously set the proxy settings in web.config for ASP.NET 1.1 and then moves to ASP.NET 2.0 the issue will appear.  For ASP.NET 2.0 there were some changes in this feature area.  This is a work in progress KB article with instructions for getting the Online Gallery working with ASP.NET 2.0.  The KB article should be out in a week or two.


Applies To:  Windows SharePoint Services

Summary/Symptoms:
 
When you attempt to add web parts to a page from the Online Gallery the number of web parts displayed is (0). 
 
If you click on the Online Gallery to view web parts the following message is displayed:
 
"Cannot open the Online Gallery. The site server has not been configured to support an online gallery. For more assistance, contact your site administrator."


Cause:
 
The proxy settings have not been configured for ASP.NET 1.1. 
 
If you have updated to ASP.NET 2.0 new settings are required to display the Online Gallery.
 

Resolution/Workaround:
 
For ASP.NET 1.1
 
Allowing Access to the Online Web Part Gallery from Behind a Proxy Server or Firewall
If your server is behind a proxy server or firewall, you must edit the web.config file for each virtual server for which you want to enable an online Web Part gallery that is implemented outside of your firewall. In a server farm environment, you must edit this file for each virtual server in every front-end Web server in the server farm.

On your Web front-end server computer, open Notepad, navigate to the folder containing the virtual server for which you want to enable the online Web Part gallery, and then open the web.config file under the following directory:

\Inetpub\wwwroot
 
In the web.config file, add the following lines to the very bottom of the web.config between the </system.web> and </configuration> tags.

<system.net> 
<defaultProxy> 
<proxy proxyaddress="http://Proxy_Server:port" bypassonlocal = "true"/> 
</defaultProxy>
</system.net>
 
Where Proxy_Server:port is the proxy server or firewall used for your environment.
 
Save and close the web.config file.
Repeat steps 1 through 3 for each virtual server for which you want to enable access to the online Web Part gallery.
 
For ASP.NET 2.0
 
ASP.NET 2.0 requires additional steps.  There are two options for configuring proxy settings.
 
Option 1:
 
Step 1:
 
On your Web front-end server computer, open Notepad, navigate to the folder containing the virtual server for which you want to enable the online Web Part gallery, and then open the web.config file under the following directory:

\Inetpub\wwwroot
 
In the web.config file, add the following lines to the very bottom of the web.config between the </system.web> and </configuration> tags.


<system.net> 
<defaultProxy> 
<proxy proxyaddress="http://Proxy_Server:port" bypassonlocal = "true"/> 
</defaultProxy>
</system.net>
 
Where Proxy_Server:port is the proxy server or firewall used for your environment.
 
Save and close the web.config file.
Repeat steps 1 through 3 for each virtual server for which you want to enable access to the online Web Part gallery.
 
Step 2:
 
On your Web front-end server computer, open Notepad, navigate to the folder <system drive>\program files\Common Files\Microsoft Shared\web server extensions\60\CONFIG and open the wss_minimaltrust.config file.


Add the following to the policy file wss_minimaltrust.config:
 
To the <SecurityClasses> node:
 
                        <SecurityClass Name="ReflectionPermission" Description="System.Security.Permissions.ReflectionPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>


To the <PermissionSet> node where Name=”Asp.Net”node:
 
                           <IPermission class="ReflectionPermission"
                                    version="1"
                                    Flags="Members"
                            />
 
After adding the new parameters save and close wss_minimaltrust.config.
 
 
Option 2:
 
Use the ASP.NET 2.0  Web Proxy Auto-Discovery solution.  For this option you do not need to make any edits to web.config or wss_minimaltrust.config.  Instead, you would configure the Internet Explorer proxy settings for the application pool account SharePoint is running as.  Or you could configure proxy settings per machine by setting a policy setting described in this article http://msdn.microsoft.com/msdnmag/issues/05/08/AutomaticProxyDetection/.

To set the proxy settings for the account SharePoint is running as, log into the web server as the application pool account.  In Internet Explorer choose Tools, Internet Options, Connections, LAN Settings.  Under Proxy Server choose to Use a proxy server for your LAN and specify the proxy settings.

After specifying the proxy settings in Internet Explorer the ASP.NET Web Proxy Auto-Discovery will enable the Online Gallery.

Posted by Shane | 2 comment(s)

Mike Walsh wrote a nice entry for the WSS faq that makes it easier to read exactly what was fixed in SP2 for WSS. 

http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=539

Now somebody needs to do the same for SPS SP2.  :) 

Posted by Shane | 3 comment(s)
SharePoint Portal Server SP 2 (Released 10/18)                           Most important KB articles for SP 2KB 887623 Description of Microsoft Office SharePoint Portal Server 2003 Service Pack 2KB 906337 Issues that are fixed in SharePoint Portal Server 2003 by SharePoint Portal Server 2003 Service Pack 2KB 907763 SPS requires ASP.NET 1.1 (although there was some initial confusion, the product team has clarified that SPS SP 2 and earlier must run on ASP.NET 1.1 – ASP.NET 2.0 is not supported for SPS virtual servers)KB 907308 How to address the case where SPS SP 2 does not updated the databases during service pack installation (Top support issue for SPS SP 2 and KB has been updated with more information based on research from our escalation engineers)KB 905229 How to update an evaluation version to SPS RTM if SPS if SPS SP 1 or SPS SP 2 has been installed on it.  (Updated KB article to be published soon)   Pending issue to be updated in KB 905854:  SharePoint Portal Server 2003 install on x64 fails if there is too much memory (4GB) on the server.  When this is the case, SPS SP 2 installer displays an OK button and silently fails.  A workaround that we are testing that seems to be working is to use the following switch in boot.ini to effectively reduce the memory to 1GB: /burnmemory=5054. Windows SharePoint Services SP 2 (Released 9/27) Most important KB articles for SP 2KB 906336 WSS SP 2 KB article listing all of the fixes KB 875358  Guidance for deploying WSS SP 2 including the new SP 2 version numberKB 841216  Steps for manually upgrading in case the databases do not get updated Pending issue that may require a KB article:  THAI and HEBREW web language template packs cannot be updated to SP 2 version.  When you attempt to update the THAI or HEBREW web language template pack to SP 2 version the update silently fails.  There may be other problems with these templates that we don't know about especially when running on ASP.NET 2.0.  Another problem that might occur is if you installed the THAI or HEBREW template packs and then try to install another language template pack SharePoint reports the following error: "Setup has detected Pre-Release or trial versions of Windows SharePoint Services products on this computer.  Pre-release versions must be removed before setup can continue" For a few days the incorrect version of these two language template packs were made available on the download center.  A number of customers may have downloaded these incorrect web language template packs.  The solution is to uninstall the incorrect version and install the republished version, http://www.microsoft.com/downloads/details.aspx?FamilyID=e7eec77d-4365-4b66-8e8d-9d079c509679&DisplayLang=en.   KB 909455 Document library event handlers that use object model code without explicit impersonation fail with the "Cannot complete this action" error message after Windows SharePoint Services Service Pack 2 is installed Pending KB article (number not available yet): An error occurs creating an SPS area after WSS SP 2 is installed.  When you attempt to create a new area in SharePoint Portal Server 2003 after applying Windows SharePoint Services Service Pack 2 you receive the following error message:

“An error has occurred in the portal site. Contact the portal site administrator for assistance.”

This can happen if the file timestamps on the SharePoint SQL script files is incorrect. These files are located in <drive>:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\SQL. Because the timestamps are incorrect WSS SP 2 did not update these files and subsequently the stored procedures for the content databases were not updated.  To work around the issue do the following:

1. Remove the *.SQL files in location <drive>:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\SQL.
2. Go to Add/Remove Programs, Windows SharePoint Services, Repair/Reinstall.
3. Select ‘Detect and Repair errors in Microsoft Windows Sharepoint Services 2.0 installation’.
4. After repair completes you will need to force an upgrade so the stored procedures on the content databases are updated.

To do this, follow these steps:

1. Click Start, click Run, type cmd in the Open box, and then click OK.
2. At the command prompt, type the following lines, and then press ENTER after each line:
cd /d %commonprogramfiles%\Microsoft Shared\Web Server Extensions\60\Bin stsadm -o upgrade -forceupgrade

Pending issue that may warrant a KB article:  SQL Server 2005 running as a domain account runs with Kerberos Authentication.  If the domain account SQL is running as is not registered as an SPN then SharePoint will not be able to connect to it to create databases (whether or not WSS is configured to use Kerberos).  A workaround is to run SQL Server as Local System. ASP.NET 2.0 and SQL Server 2005-         An updated WSS Administration Guide with instructions for using ASP.NET 2.0 and SQL 2005 will be released soon.  I don’t have a date yet exactly when it will get posted but you can check the date on http://www.microsoft.com/downloads/details.aspx?FamilyID=a637eff6-8224-4b19-a6a4-3e33fa13d230&DisplayLang=en.  When it shows greater than 10/7/2005 then the new version is posted. Microsoft Content Management Server 2002 SP2 is Available as of 11/8 Direct link to Download: Download details: Content Management Server 2002 Service Pack 2 (SP2)http://www.microsoft.com/downloads/details.aspx?FamilyId=3DE1E8F0-D660-4A2B-8B14-0FCE961E56FB&displaylang=en SP2 Additions: -      ·         Support for ASP.NET 2.0 (.NET Framework 2.0)-      ·         Support for Visual Studio 2005-      ·         Support for SQL 2005 (Yukon)-      ·         Support for running on 64-bit machines in 32-bit emulation mode Related KBs
  • 894691 - A list of the bugs that are fixed in Content Management Server 2002 Service Pack 2 (live)
  • 906142 - How to obtain the latest Microsoft Content Management Server 2002 service pack (live)
  • 906145 - Content Management Server 2002 Service Pack 2 installation information (not live as of 1PM PDT on 11/8)
  • 984691 - Description of the Content Management Server 2002 Service Pack 2 (not live as of 1PM PDT on 11/8
Supportability issue for CMS SP2:  CMS SP2 does not install the Developer Tools.  Developer Tools must be installed from SP1a, which doesn’t support Visual Studio 2005.  This has some interesting implications for customers and support.  For example, if a customer has installed Content Management Server 2002 SP2 on a machine without Developer Tools or Visual Studio installed, and they wish to install Developer Tools, they will need to take the following steps: 1.      Uninstall MCMS 2002 SP22.      Install Visual Studio 2003 (or Visual Studio 2002)3.      Run “Change/Remove” from Add/Remove Programs on MCMS 2002 SP1a (Using the SP1a CD to access required files)4.      Change the existing installation, and select Developer Tools as the feature to add5.      Re-install MCMS 2002 SP2 It should be noted that this essentially means that in order to use Visual Studio 2005 with MCMS 2002 SP2, customers must have at some point installed Developer Tools on Visual Studio 2003 (or Visual Studio 2002).  MCMS 2002 SP2 does update existing Developer Tools installations to support Visual Studio 2005.  See KB 906145 for more information. Supportability update for Database OrphansCurrently PSS has a number of support cases opened where we have orphans in the databases.  WSS took two fixes in SP 2 to prevent orphans from being created but those fixes do not retroactively clean orphans from the database.  The most common orphan is where there is an entry for a site in the sites table of the configuration database but no corresponding site entry in the content database sites table.  The product team is developing a solution where you can run an stsadm.exe command to detect and clean orphans.  The common issue we see is that a customer cannot restore an stsasdm backup because of orphaned entries.  The work for this is under way and we don’t have an estimate yet when it will be ready. Newly published content:Every month new content is published and made available on Office Online.  This is a great place to keep up to date with new content released by the product teams.-         SharePoint Portal Server, http://office.microsoft.com/en-us/FX010909721033.aspx-         Windows SharePoint Services, http://office.microsoft.com/en-us/FX011204871033.aspx  
Posted by Shane | 1 comment(s)

I guess all of these cute little critters that make up the search experience aren’t all that straight forward.  Of course if you already got them licked you can Mooooooove along.  This is just kind of a basic overview of how the pieces of the puzzle go together.  If you want some detail stuff on the gatherer and search check out the SharePoint Resource Kit starting with chapter 21.

 

Let’s start at the beginning.  The index is the file that holds all of the information that is collected during a crawl.  When you first create a portal you get a portal_content and non_portal_content index.  If you enable advanced search administration mode you can create other indexes if that makes sense in your environment.  A couple of things to consider when you are creating indexes is you can not create an index with a space in the name and you can specify an alternate location on the file system for the new index.

 

Just as a couple of side notes if you want to move the default indexes you can use this blog entry http://bes.xs4all.nl/blog/archive/2004/07/18/258.aspx from Berry Schreuder.  With catutil.exe you can also move the property store and log files.  More information from Microsoft at http://support.microsoft.com/?kbid=825484. 

 

The index is filled with data by the crawl which is run against all of the content sources that you specify for that index.  Content sources can be SharePoint sites or portals, regular web sites, file shares, & even exchange public folders.  The relationship between indexes and content sources is one index can have multiple content sources but a content source can only belong to one index.  So anytime you create a new content source you must choose the index that will hold the data.

 

Now that you have chosen an index and your options for the crawl configuration (we are skipping that part) you need to choose a source group to put your content source in.  Once again the relationship here is 1 content source can only belong to 1 source group but a source group can contain multiple content sources.  Now you will notice when you fill out the address for the content source it automatically fills in the description and the source group with information from your address (both fields are editable).  You can choose to use this as a new source group (which will be created when you click finish), change this default name to anything you like (creating a new source group also) or choose one of the existing source groups from the list. 

 

Ok now we have these indexes filled up with data from our content sources and divided up into source groups.  Why did we go through all of that effort?  Well, now we are going to create search scopes.  Search scopes are basically a way of defining a subset of sources you want to search.  If you look at your fresh portal you will see next to the search box you have your search scopes.  And if you haven’t added a search scope yet you will only see “All Sources” in that box.  This search scope does what it says and returns results from all of your indexes.  Now to build our own search scope we go to Manage Search Scopes and click New Search Scope at the top of the screen.  Here we will give the scope a name and we will either choose Include No Topic Or Area In This Scope or Limit The Search Scope To Items In The Following Topics Or Areas.  If we select either of these options you will the bottom section become available to choose content sources.  Now we can either choose to include none or all of our content sources in the scope or we can take what is behind door number three and choose to limit our scope to any of the source groups we would like.  Once last tidbit on search scopes.  Sometimes they will appear right away in the drop down box where you execute searches other times you have to do an IISreset to get them to show up.  So before you start banging your head on the desk when you create one and nothing happens try the IISreset first.  J  Those few brain cells you have left will thank you.

 

Now this kind of makes sense, right?  Well let’s do a quick example to drive it home.

 

My client wants to index 3 large file shares and make the results available in SharePoint through a search scope called Network Drives.  Here is a quick run down of what I would do.

 
  1. Enable advance administration search mode
  2. Create a new index name file_shares_index (this isn’t possible without advanced mode)
  3. Now I would create a new content source called File Share 1 and put it in the files_shares_index
  4. I would also create a new source group called File Share Source Group and put the content source in there
  5. I would now repeat step 3 for File Share 2 and File Share 3
  6. I would add both of those source groups to the File Share Source Group
  7. Now I would create a new search scope called Network Drives and I would choose to Include no topic or area in this scope
  8. I would also choose to Limit the scope to the following groups of content sources and would only select File Share Source Group
  9. Now I would do an IISreset (when no body was on of course) and my search scope would appear
  10. Also, so my search scope could have something to return I would run a full update on my file_shares_index from the manage indexes screen.
 

I hope this makes everything a little less fuzzy for people trying to get a handle on search config in SharePoint.

 

Can you guess what I did at my client today?  J

  

Shane – The Farmer on the Dell

Posted by Shane | 3 comment(s)

Lawrence Liu is the Senior Technical Product Manager and Community Lead for Microsoft Office "12" SharePoint Servers.  His blog “Report From The Inside” at http://blogs.technet.com/lliu/ is a wealth of Office 12 information so check it out.

 

Shane

Posted by Shane | with no comments

Do you ever want to recover a document directly from the database?

Here is a utility that I have used to recover documents from the database.

Sorry, but it's all in French :)

http://www.sharepoint-france.com

The product information page:
http://www.sharepoint-france.com/Products/DocumentRecovery/Default.aspx

The actual download link:
http://www.sharepoint-france.com/Products/DocumentRecovery/Release.zip

Posted by Shane | 3 comment(s)

I installed this for one of my clients the other day and I liked it so I thought I would post a link to here. 

(Yes I do teach for these guys but I am only posting this here because I liked the product.)

(Wait maybe I should be asking for a kickback.  ;)  LOL  )

As a SharePoint administrator have you ever wanted to assign alerts to users?  How about do it all at once for all the users?  SharePoint Solutions has released this great add on.  Lots more information here. 

http://sharepointsolutions.blogspot.com/2005/11/wss-alert-manager-v1-released.html

 

Shane

Posted by Shane | with no comments

Ok.  I know I said a technical article was coming next but whoops.  This is quazi technical so get over it.  :)

SharePoint Links and Common Questions

This is a handy little page full of questions I see a lot in the newsgroups.  There is also an RSS feed for the “How do I” list.  So if you want to have the latest how do I's show up feel free to subscribe to it.

 

Shane

Posted by Shane | with no comments

Well since the bandwagon has came and gone and these crazy blogs are still going strong I figured it was time for me to hop on. 

 

Since I am sure the first question you will have is “Why is it called the SharePoint Farmer’s Almanac?” I figured I would answer that one right off the bat.  I have always been a network admin type.  So in doing that I got to play with all types of server farms.  When I made the transition to SharePoint I was already comfortable with networks and servers so I figured I would learn the infrastructure side of SPS and grow from there.  So as I was moseying down that road I was asked to create a training course for SPS admins.  In the process of naming that class I came up with calling it SharePoint farmers (which got vetoed) so to help sell it I themed all of my modules with a farm overtone.  A great example was the Shared Services modules.  It had a great picture of a dancing cow and it was called “Your Local Coop” then the following module was called “SharePoint Farmers Market (or Now that I have turned on SharePoint what have I produced)”.  So good or bad that is kind of where the whole farm theme came from.  J

 

Here is a quick link to the course.  http://www.sharepointsolutions.com/advinfrastructure.html

 

Ok. I guess question #2 is who am I?  Well, my name is Shane Young.  I am the owner of http://www.sharepoint911.com.  We specialize in quick support on SharePoint.  I am a SharePoint Portal Server MVP and my profile out here has lots of bio information on my technical stuff so I will skip the rest of that.

 

Alright that is blah blah blah for now.  Time to write a technical article. 

Posted by Shane | 2 comment(s)

I had a client yesterday who could no longer edit any of the columns in her document library.  Very strange behavior.  I figured the large library was corrupt so I created a new library on her server and had the same behavior.  So I started scratching my head. Turns out that Automatic updates had ran and installed WSS SP2 for her.  Apparently when it installed it did not update the virtual servers.  So if you went to WSS central admin and clicked Configure Virtual Settings you would see Upgrade and you couldn’t get into the screens to edit the settings. 

 

I tried to manually install WSS SP2 to correct the issues but it said nope because it was already installed.  So then from the command prompt I ran

 

stsadm.exe –o upgrade –forceupgrade

 

That fixes it! 

 

This is a Microsoft KB article that covers the issue also.  http://support.microsoft.com/?id=907308

 

Some other symptoms I have heard for this problem is that you can not edit document or list properties and you can not apply new themes or templates.  Just FYI.

 

HTH (Hope This Helps)

 

 

Shane

 

SharePoint Help

Posted by Shane | 5 comment(s)