Errors Uploading Files to SharePoint After SP1

We have 2 different MOSS farms (internal and external) and most of our users upload files ranging in size from under 1 MB to over 100 MB. In the past we had the typical SharePoint issues with users uploading large files when they were in remote locations with a slow upload speed.

We installed WSS and MOSS SP1 on our external farm first and immediately received reports of problems uploading files over 2 MB. About a month later we upgraded our internal farm to SP1 and, again, immediately had reports of problems uploading files.

After much digging and not seeing anyone else with this problem, I ran across a Microsoft KB article that eventually solved my problem. I tried several things before I found the magic fix.

So what’s the fix?
Modify the web.config in your SharePoint site to include the following:

Look for this line:
<httpRuntime maxRequestLength=51200 />

Change it to this
<httpRuntime executionTimeout=999999 maxRequestLength=51200 />

The Microsoft KB article is here

This small change fixed the problem on both of our farms.

Datasheet View Errors With Office 2007

We recently started upgrading all of our employees to Office 2007 (from 2003). We’ve seen a lot of different errors but nothing pandemic. One of the errors is related to the datasheet view. I started doing some research and this blog has everything you need…

SharePoint HTTP to HTTPS Redirection

The scenario is a MOSS site with HTTP and HTTPS enabled but you want all traffic to go to HTTPS. I thought this would be a fairly simple using IIS but apparently not…

Here’s a good description of the problem and fix

Basically you just change your public URL in Alternate Access Mappings to HTTPS.
Then you go to the properties on your site in IIS and change the TCP port to something other than port 80. I changed mine to port 8001.
Now create a new web site and select the same IP as your SharePoint site and enter the host name as the “host header”. (I’m not sure this is required or why it would be…)
Now go to the “Home Directory” tab of your new site on port 80 and select “A redirection to a URL” and enter the HTTPS address of the SharePoint site.
Now go to your SharePoint site using HTTPS and open the properties. Select the Directory Security tab and click Edit in the Secure Communications section. Check the “Require SSL” and “Require 128-bit encryption”.

You should now be able to go to any address on your site using HTTP and it will automatically forward the browser to the same address using HTTPS.

MOSS SEO – 302 Pages Redirect

When you create a public facing MOSS site using the publishing feature, all of the pages are stored in a “Pages” document library. MOSS will automatically redirect the user to the page designated as the default page in the Pages library when they go to the site URL.
(http://www.mosssite.com redirects to http://www.mosssite.com/pages/default.aspx)

This redirection is a 302 temporary server-side redirection. Redirecting URLs using 302-Temporary redirection is a non-search-engine-friendly technique. To resolve this issue it is recommended changing the server side redirection from a 302-Temporary Redirection to a 301-Permanent Redirection. A 301 redirect is the most efficient and search engine friendly method for web page redirection.

There are several ways to change the 302 to a 301 redirection (just Google it.)  I solved this problem with a simple utility that was already installed on the web server called “ISAPI Rewrite”. ISAPI Rewrite is a free utility used to “rewrite” URLs at the IIS level, before the request is returned to the client. This utility can be used to solve many different issues (we use it to forward old URLs to the new location.) In this case we use it to create a permanent redirect to the default page on the site.

After you install ISAPI Rewrite Lite on the web server you can modify the “httpd.ini” to configure the 301 redirect. Just add the following in red to your configuration file.

This adds a trailing slash to all URLs that don’t have a page at the end
# Fix missing trailing slash
RewriteRule ^([^.?]+[^.?/])$ $1/ [R]

This looks for the correct host site and then redirects if the URL is just the host name
# Pages Redirect – Change 302 to 301 redirect
RewriteCond  Host:  (www\.)?mosssite\.com
RewriteRule  / http\://www.mosssite.com/pages/default.aspx [I,RP]

Note: ISAPI Rewrite runs it’s rules on ALL incoming traffic on your server so make sure the rules work for all of your sites! As always, TEST IT FIRST!

Want to test it? Go to http://www.urivalet.com and enter your site URL without the http://. Test it using HTTP/1.0 and HTTP/1.1. The Object Details will show you what type of redirection is used on your site.

MOSS SEO – Robots.txt

It’s fairly easy to add a robots.txt file to your public anonymous MOSS site. Just open up your root site in SharePoint Designer. Right-click the top folder with your site URL and select New – SharePoint Content. Click the Page tab, select Text File and click OK.

Add the robots.txt file content and save it as “robots.txt”. That’s it!

Make sure the file is accessible to search engines by going to your site URL with a “/robots.txt” at the end. You should see the contents of your robots.txt file in the browser.

CSsoResourceManagerCache MOSS Log File Entries

After installing SP1 on my MOSS server farm I noticed the MOSS logs full of the errors below.
I found out that the during the SP1 upgrade the SSO service was started on the server. I’m not using SSO so I turned it off and made sure it was set to “manual”. That got rid of the errors in the MOSS log.

CSsoResourceManagerCache cannot find SSO connection string value in the registry!    

Error code is: -2147418113           

CSsoResourceManagerCache has set SSO connection string value to be empty …  SSO is not configured any more.          

Error code is: -2147418113           

IResourceManager::Refresh() failed      

Error code is: -2147024809           

ForceRefreshOfSPSResMgr() failed.  This may be ok if SSO has not been configured yet and the run-as service gets an access denied   

Error code is: -2147024809           

CSsoResourceManagerCache cannot find SSO connection string value in the registry!    

Error code is: -2147418113           

CSsoResourceManagerCache has set SSO connection string value to be empty …  SSO is not configured any more.          

Error code is: -2147418113           

CSsoResourceManagerCache::Refresh Failed!  

Error code is: -2147024809           

CSsoResourceManager failed to get Connection String from the cache!

Error code is: -2147024809           

IResourceManager::CreateSession() failed, we will call IResourceManager::Refresh() to refresh and try again   

Error code is: -2147024809