RJ Dudley

Remember FAST search engine?  Maybe this will ring a bell:

FAST Search and Transfer isn't known for stealth technology, but it should be. Its AllTheWeb.com search engine has snuck up on all of the major search engines with new features, speed and customization capabilities, and is now a viable challenger to pack-leader Google.

"There are four new technologies that will drive customers to the site," said Bob Thomas, spokesperson for FAST. These include dynamic clustering of results, real-time news search, a "pre-analysis" tool that helps refine search queries, and enhanced user interface and customization options, according to Thomas.

- http://searchenginewatch.com/2158181, Nov 13, 2001

This was written almost 9 years ago, and the 2001 concept of "real time news" seems almost charming with the increase in blogging and creation of Facebook and Twitter since then, but kudos to FAST for innovating on something we all take for granted today.

Reports of FAST challenging Google were rather optimistic, and as we sit here in 2010 we can guess how that worked out for FAST.  But what happened to them?  Well, in 2008, Microsoft consumed FAST and rebranded it Enterprise Search (http://www.microsoft.com/enterprisesearch/en/us/fast-customer.aspx).  Heard of it?  Yeah, me neither.  I'm not even sure I could find it in my MSDN DVDs going back to 2003.

Well, speaking of MSDN, when I logged in to grab Expression 4 (shiny new thing!!), something else was listed in the new downloads: FAST Search Server 2010 for SharePoint.  Heard of it?  Yeah, me neither.  One thing hasn't changed in 9 years--the stealth aspects.

BTW--AllTheWeb.com still exists, it's a Yahoo! property now.  And, I suspect, still challenging Google. 

After migrating to Windows 7 and IE8, our users were unable to open SharePoint 2007 document libraries in Explorer View.  There was not a problem with Windows XP and IE8.  We found two issuses involved here.

First was Urlscan Filter 3.0 was installed on our server.  The Windows 7/IE8 combination apparently sends header verbs not used by Windows XP/IE8, most of which are disallowed by rule.  If possible, the best thing to do is uninstall Urlscan from your SharePoint server.  In order to utilize Explorer view, you pretty much need to allow all the verbs.  If you need to keep Urlscan installed, you'll need to work through the logs, performing the different oprations in Explorer View, making sure you have all the needed verbs allowed.  We have up after 5 verbs and justuninstalled Urlscan.

The second issue we found is that IE8 on Win7 doesn't actually support Explorer View.  Instead, a Windows Explorer window will open, and you can work with the library that way, but yuo aren't actually in the IE browser.  To me, this is preferable than opening the Explorer View in the browser, as the Windows Explorer is faster and more fluid.

Questions? Comments?  Use the Contact Me form above.  Comments are disabled due to comment spamming scum.

After we began rolling out Windows 7 at the day job, we found our first issue--when people checked out documents from SharePoint 2007, the documents were opened as "Read Only", and the users could not save the edited document back to the portal.  The work-around was to save the document locally and re-upload.

After four months of working with Microsoft, we were able to find the solution.  The problem was in URLScan, and Windows 7's use of the OPTIONS verb.  By default, this verb is blocked.  If you look in the URLScan logs (by default, %WINDIR%\system32\inetsrv\urlscan\logs), you'll see an entry like the following (important parts are in bold):

2010-03-19 02:12:15 127.0.0.1 778810668 OPTIONS /<document library path>/ Rejected verb+not+allowed HTTP+method - -

All we need to do to fix this problem is edit urlscan.ini by default, (%WINDIR%\system32\inetsrv\urlscan), find the [AllowVerbs] section and add OPTIONS.  Then scroll down a little to the [DenyVerbs] section, and remove OPTIONS from that list.  Do an IISRESET and all is well.

For reference, our server platform is Windows Server 2008/IIS 7/SharePoint 2007, and clients are Windows 7 Professional using IE8.  This issue does not seem to affect Windows XP users with IE 8.

Questions/comments?  Please use the contact form.  Because of jackass comment spammers, I've had to turn off comments for a while.

We recently upgradedf from SPS 2003 to MOSS 2007.  In the old portal, I had a couple of user controls running via the SmartPart.  After installing Return of SmartPart and adding the controls, I got an error every time I tried to search.  Way back in the dusty cobwebs, I remember troubleshooting this, and it was a permissions issue.  Checking in the Applications log, I found the following error: "sharepoint Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.".

Here's the fix:

Cause: Anything that access database from SP requires at least the WSS_Medium security policy in the web.config file. If you receive a security message from the web part, it's usually the trust element in the web.config file.

1. Open wss_mediumtrust.config & wss_minimaltrust.config usually (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\config\) look in your web.config file for the exact path.
2. Find in wss_mediumtrust.config: <SecurityClass Name="SqlClientPermission" Description="System.Data.SqlClient.SqlClientPermis sion, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
3. Copy and paste it in to the <SecurityClasses> node of wss_minimaltrust.config.
4. In the PermissionSet section of this configuration file, add the following: (Find in wss_mediumtrust.config) <IPermission class="SqlClientPermission" version="1" Unrestricted="true"/>.  Copy and paste it in to the a <PermissionSet> node of wss_minimaltrust.config.
5. Save your wss_minimaltrust.config
6. Reload your site, and try again

Presto!  Original source is http://objectmix.com/sharepoint/297402-request-permission-type-system-data-sqlclient-sqlclientpermission-system-data-version-2-0-0-0-culture-neutral-publickeytoken-b77a5c561934e089-failed.html.

As part of Mindsharp's Premium Content, they now have four free SharePoint 2007 posters.  I received the SP 2003 posters, and they are fantastic.  Head over to www.mindsharp.com, and click on Premium Content.  Registration required, but worth it.

A SharePoint User Group is coming to the Pittsburgh area:

The Pittsburgh Area SharePoint User Group  is dedicated to providing educational  and informational resources for Microsoft SharePoint technologies and related products.  Its purpose is to bring the local SharePoint community together to network, and to share tips, tricks, and ideas on SharePoint technologies, as well as to provide a forum for people involved with SharePoint.  The target audience for this users group includes developers, designers, administrators, and power users. 

The first meeting of the SharePoint User Group will be held at the end of April or early May.  To help us define the format, content, and timing of this meeting, and to be notified of upcoming meetings, please help us by filling out a brief survey, at http://www.surveymonkey.com/s.asp?u=495253496362  This survey, which is being administered by the Pittsburgh Technology Council, will only take a few minutes to complete, and we hope to have all responses by March 31st. Your responses will be collected by the Council and kept completely confidential and, without your permission, no material that identifies your response will be distributed.

The Pittsburgh area User Groups have proved to be a great source of information and knowledge for users over the years--and we anticipate that the SharePoint Users Group will be as equally successful.

Additional comments and concerns are always welcome.

Bil Simser responded to Shaun Walker's DNN vs. Sharepoint Feature Matrix, and for some reason I can't get the Submit button to work on Bil's blog.  So I'm posting my comments here.  Two points to add to Bil's great list:

1) Unless there have been some changes made, storing files in the file system with DNN is not secure.  This is the only way to store files in DNN 3 (unless the newest release changes this), and one option in DNN 4.  Someone paying attention can access files by direct URL.  In SharePoint, files are stored in the database, and acceses to these files can be strinctly controlled at several levels.

2) It's actually far, far easier to develop and deploy SP webparts with the free SmartPart than it is to develop DNN PAs.  The distribution method of PAs is great, but development of DNN modules can be a pain.  The SmartPart allows any ASCX control to be used in SharePoint, and has found significant use in my SP installations.  Without the SmartPart, developing for either can be a miserable experience.

Full article at http://www.codeproject.com/useritems/authcontentpart.asp

A SharePoint Portal Server Webpart that can publish content depending on a user’s authentication.

I haven't had a chance to try this out yet, but could be useful.

In Mindsharp's SharePoint Discussions group, the following question was posted:

Does anyone have experience with both SharePoint and DotNetNuke to the point where they could comment on the benefits of each are compared to the other?  Is there a type of installation where you might use one vs. the other?

Here's the answer I posted in the group:

SP and DNN are very different beasts which offer some similar functionalities.  I'm using SP as a generic term for either WSS or SPS, which is a different decision.  DNN is really an easy website creation tool, while SP was designed to be an information repository and collaboration tool in a corporate environment.  The best way to summarize might be "Extranet vs. Intranet".  My thinking is Extranet=DNN, Intranet=SP.  DNN is designed to be used and maintained by persons with little IT experience.  SP is one of those things that will require having a decent IT person around.

First question would be whether or not you need tight integration with Office.  If so, then hands down your only choice is SP.  Another feature that DNN is lacking is a document library with version control, although one may appear down the road.  SP offers full-text indexing of the documents you store in it, and so you can search inside the documents in its libraries.  DNN doesn't offer this.  SP stores its documents very securely in the SQL database; DNN stores them as files, which means if someone knows the right path, the site's security could be bypassed and the documents downloaded directly.

If you don't need the tight Office integration, DNN is a very valid choice for a website.  A good use would be for a school's website.  DNN supports multiple child portals, just as SP does, and you can distribute administration, just as with SP.  The school could have its main portal, and each department or club could have its own child portal, each with their own radically different looks.  True, you could pull off the school's website with SP, but it wouldn't be so flexible, and you would put in a lot more effort to make it work.

Another consideration is what type of authentication you need to use.  WSS was designed to integrate with Active Directory, DNN was designed to work with anonymous users and Forms Authentication.  There are ways to make DNN work with AD, and WSS work with anonymous users, but anytime you make a change as significant as authentication scheme, you introduce adminsitrative overhead.  One point of using these tools is to simplyify your life, not create extra work.

Cost might also be a consideration.  True, if you have Windows 2K3, then WSS is essentially free; DNN is entirely free.  There are a lot of good web parts available for free and cheap for WSS, but many are very expensive.  DNN can also be extended with inexpensive or free modules, and even the ones you have to pay for are still pretty cheap.

One main difference I see is the amount of different things you can do with DNN.  DNN can also serve as an e-commerce platform, or host robust photo galleries (rather than the "list of photos" in SP).  There are some nice calendar modules for DNN that not only list events, but allow registrations and can accept payment for them.  In this case, it might seem like SP is lacking in some functionality, but SP was never designed to do these things--these are functions of a website, not a collaboration tool.

Skinning is a bazillion times easier with DNN.  The DNN core team did a great job with its skinning engine, and there are lots of skins available for free or cheap.  Changing the look of a single page, or entire portal is done with a simple package upload and a few mouse clicks.  With enough work, you can do some really nice skinning on SP (both SPS and WSS), but it takes some work.  I've done both, and DNN is by far easier and more powerful (mainly due to DNN's simplicity--features which are hidden or difficult really aren't features at all).

DNN runs very well in a shared hosting environment; SP, not so much.  Although DNN only ships with SQL Server provider, if you're handy enough, you would write one for MySQL, or Vista, etc.  You don't have that option with SP--it's SQL Server only.

<update 2006-02-01>

If you didn't come here from there, Bil Simser has a much more detailed post at http://weblogs.asp.net/bsimser/archive/2006/01/31/437023.aspx.  Bil also includes some of the features of SharePoint 'v-Next' (currently due to be released at the end of this year), and better breakdown of the OOTB functionalities.

spreskit

dnnbooks

I see this a lot, and it's easier than you might think:

1. Open the e-mail, and click File >> Save.
2. In the "File Name", enter the URL to the document library, and click Save.
3. A view of the document library will open in the folder list window.  Confirm the file name (which will be the e-mail subject), change it if you need to, and click Save again.
4. Your e-mail message is now saved in the document library!

Tip #1: You can get the URL of the document library by navigating to it, and copying everything up to the end of the library name.  For example, you'd use http://MyPortal/sites/TestSite/Document%20Library/.

Tip #2: If you need to save a lot of e-mails in the same document library, create a Network Place for the document library.  Open My Network Places and use the wizard to create a new network place for this library, using the URL as shown in Tip #1.  Then, you can choose this library by browsing My Network Places.

Teun Dynstee released his Gantt Chart Web Part today:

The part allows you to specify a list and view to render. You select the fields from the view that will indicate the start and end date of an item. The third required field is the title field. Because the part works with view fields, you can also use calculated fields to specify the start date, end date or title of the item.

Now playing: Dierks Bentley - Lot of Leavin' Left to Do

Bob Mixon has released a beta of his Quick Launch Web Part:

This Web Part can be used to replace the hard coded HTML in a Windows SharePoint Services (WSS) Site. The first advantage to this Web Part is simply being aware of the current users security permissions. Meaning, if a user does not have the permissions to view the items in a document library or list, even if it is marked to be displayed on the Quick Launch bar, it will not be displayed.

There are many additional features currently present in this Web Part, which include:

1. The ability to turn any set of lists on or off. So if you chose to not display Surveys, simply turn it off!
2. The ability to display separation lines below the grouping headers.
3. And, the best of all features, the ability to dynamically add any items to the quick launch bar through a standard SharePoint list.

Now playing: M - Popmuzik

This is for people who get the following error either immediately after you create a WSS site, or when you try to access a WSS site or SPS portal:

You are not authorized to view this page
You do not have permission to view this directory or page using the credentials that you supplied.
--------------------------------------------------------------------------------

Please try the following:

Contact the Web site administrator if you believe you should be able to view this directory or page.
Click the Refresh button to try again with different credentials.
HTTP Error 403 - Forbidden: Access is denied.
Internet Information Services (IIS)

--------------------------------------------------------------------------------

Technical Information (for support personnel)

Go to Microsoft Product Support Services and perform a title search for the words HTTP and 403.
Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled About Security, Authentication, and About Custom Error Messages.

If you are using SPS, try to access http://<portalname>/default.aspx instead of http://<portalname>/.  If you can access the URL with the pagename, then the problem may be in your application pool settings.  Likewise, if you try to access a WSS site and get this error, see if you can add default.aspx to the URL.  If that works, same problem.  You might also get this error immediatelyt after you create a WSS site, at the point where you are supposed to pick the site template.

Fortunately, the fix is really easy.  You need to open up the IIS manager on the server, and the open the properties for your virtual server.  On the Home Directory tab, you probably need to change the Application Pool the site is running under.  There's probably one named SpsAppPool or something like that.  If there are several and you're unsure, try choosing them one by one, and trying to access the URL (the one without the default.aspx) after each change.

For more technical information, I recommend

Now playing: The Calling - Wherever You Will Go

Leaving the easy ones aside, here's a few things Mike Drips might want to know before he writes another article:

1) Hello?  Java and JavaScript are two separate technologies.  JavaScript was independently developed by Netscape, Java was developed by Sun.  JavaScript was actually known as LiveScript until Netscape and Sun entered into a marketing agreement, and rebranded LiveScript as JavaScript.  Netscape's JavaScript was marketed as a lightweight complement to Sun's Java on both the server and client side.  That's right--the 'Java' part of 'JavaScript' is a marketing gimmick, not a technological bond between the two (however, since both are dreived from some C-variant, you'll find inevitable similarities).

Microsoft's JScript almost completely supports Netscape's JavaScript.  More importantly, both are considered an implementation of ECMAScript, so you can count on a very standard base between the two.  You could make an equal counterargument that Netscape's JavaScript almost completely supports JScript, but since only ECMAScript is the accepted standard, support for that is all that really matters.

Serious developers know there is more documentation available than just MSDN Library (while we're on the subject, MSDN Library is head, shoulders, sternum and probably naval above what Netscape and Sun provide for online knowledge).  There's these things called 'books', you see, and you can buy them fairly cheaply.  They are full of really good information.  If you insist on downloading something for free, MS provides a complete JScript reference in its Windows Script Documentation.  You'll find the latest version at http://www.microsoft.com/downloads/details.aspx?FamilyId=01592C48-207D-4BE1-8A76-1C4099D7BBB9&displaylang=en.  This download also includes a VBScript reference.

Here's the skinny on the lawsuits: they were never about JavaScript.  Not one.  Nor were they about the fact MS built a better Java VM for Windows than Sun did.  They were about the fact that MS called their product a Java Virtual Machine, and infringed on Sun's trademark.  And, MS wasn't including non-MS software with its OS, even though anyone who wanted or needed the Java VM could go download it for free whenever they wanted to.  Trademark and market exclusion, not technology.

In response to

Once you get past the shock and horror of encountering the alien JavaScript files, to professionally program SharePoint you also have to deal with CSS, HTML, XML, ASP.Net, Visual Studio.Net, and your choice of C# or VB.Net. That doesn't include dealing with Windows Server 2003, Active Directory, and the wonderful world of IIS.

All I can say is "OMG!  To program a website, you have to know how to program a website!"  Guess what--if you wanted to program for another platform, you'd still need to know HTML, CSS, XML, Apache and probably PHP and DreamWeaver.  BTW - You forgot FrontPage 2003, which is the recommended editor for SharePoint pages, and SQL Server 2000.  You only need VS if you want to build web parts.

Exactly how 'alien' should a technology be that has been around since 1995?  Hello?

2) The next release of SharePoint isn't timed for Longhorn, it's timed with Office Wave 12, which is scheduled for late 2006.  SharePoint doesn't rely on Windows APIs now (the WSS are extensions to the web server, not a native API), so the next OS release is irrelevant.  SPS v3 will run on Win2K3 servers.

3) WSS is not a subset of SPS.  SPS is a superset of technologies that adds functionality on top of WSS.  MS does clear this up at http://www.microsoft.com/sharepoint/overview.mspx#EDAA:

SharePoint Portal Server 2003 is a secure, scalable, enterprise portal server built upon Windows SharePoint Services that you can use to aggregate SharePoint sites, information, and applications in your organization into a single, easy-to-use portal. SharePoint Portal Server 2003 relies on Windows SharePoint Services to provide basic Web hosting and document storage functions, but extends it with additional functions for navigation, search, application integration, and personalization.

This particular page might be more recent than Mike's SP experience, but that explanation has been around for a long while.

4) You didn't start with the "Microsoft SharePoint Products and Technologies Resource Kit", did you?  I guess if you don't know how to program a website, then yeah, a lot of the SP books will be useless.  That web programming thing might have been something to look into before diving into a SP installation.

5) MS laid out a very solid plan for SharePoint in April at their strategy briefings for CIOs.  It was good.

After you've installed Windows Server 2003, you need to add the role of Application Server to your server.  This will configure IIS, SMTP, etc. and you can optionally choose to configure FrontPage 2002 Server Extensions and the ASP.NET Framework.  At this point, do configure the ASP.NET Framework, but do not configure FPSE 2002, even if you are going to use FrontPage to customize your portal!  You don't need the FPSEs on Win2K3 to customize SPS 2003.

If you did happen to install the FPSEs at this step, your Default Web Site will be extended with FPSEs, and appear to the SharePoint Central Administration to be a site already in production (which requires a different upgrade path).  You won't be able to extend the Default Web Site to use SharePoint unless you remove the FPSEs.  You'll know when you get this error message:

Setup has detected that your default virtual server is running FrontPage 2002 Server Extensions. To continue Setup and upgrade your default virtual server later, click OK. To exit Setup and move data from your default virtual server, click Cancel. For more information about moving data from FrontPage 2002 Server Extensions, see the Administrator's Guide for Windows SharePoint Services.

Chances are, clicking OK isn't going to do a darn thing.  There's a Microsoft KB article that deals with the problem if you've already caused it:

"Virtual Server Is Running FrontPage 2002 Server Extensions" Message When You Run Windows SharePoint Services Setup or When You Try to Extend the Virtual Server with Windows SharePoint Services