(These increase the file size limit to 100MB and timeouts to 10minutes.)

In the central administration screens do the following:

1. Get into the SharePoint Central Administration Site

2. Select “Application Management”

3. Under the “SharePoint Web Application Management” section select “Web Application General Settings”

4. Change the “Maximum Upload Size” to 100MB.

In IIS of the web front end server websites:

1. Go to the website, click advanced settings, then the connection limits expansion

2. Set Connection Timeout to 600.

In Program Files\Common Files\Microsoft Shared\Web server extensions\12\TEMPLATE\LAYOUTS
Adjust the upload.aspx setting to read:

<location path=”upload.aspx”>
<system.web>
<httpRuntime executionTimeout=”999999″ maxRequestLength=”2097151″ />
</system.web>
</location>

Adjust the virtual directory web.config to read:

<httpRuntime executionTimeout=”999999″ maxRequestLength=”51200″ />

ALSO:

Add this section in system.webserver

<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="104857600"/>
</requestFiltering>
</security>

“Revocation information for the security certificate for this site is not available. Do you wish to proceed?”

when they accessed a website.

After investigation it turned out that the certificate revocation list distribution point, which is found (in IE anyway), under:

Page properties, certificates button, look on the details tab for CRL distribution point.

Was no longer accessible, due to some interesting firewalls that had been put in place. On opening access to this appropriately, the message no longer appeared, as the revocation information was then available.

On returning to the first one, I got an error: “value does not fall within the expected range”

This turned out to be because I had changed the order of columns in a grid, so the xaml had two columns with the same index.

On moving them to be in the correct order, and removing the index attributes from the grid columns, all returned to normal nicely.

http://blog.tylerholmes.com/2008/02/troubleshooting-access-denied-errors-in.html

And here is a useful webpage for decoding url guid’s:

http://meyerweb.com/eric/tools/dencoder/

In my particular problem, a custom webpart was trying to enumerate permissions, and the user hadn’t been granted permission to do that.

Thus causing the whole site to fall over, with an access denied message.

1. http://blog.techgalaxy.net/archives/831
2. http://blogs.msdn.com/b/ifilter/archive/2007/03/29/indexing-pdf-documents-with-adobe-reader-v-8-and-moss-2007.aspx
3. http://www.moss2007.be/blogs/vandest/archive/2007/09/19/sharepoint-2007-and-pdf-indexing.aspx

Enjoy!

Remember to end XML with /> and change BOTH registry keys, restart everything, and then re-index in full.

http://grounding.co.za/blogs/neil/archive/2008/07/27/controlling-timer-jobs-in-sharepoint.aspx

You’re done. Remember, enable Web client, and use HTTP NOT HTTPS.

http://blog.techgalaxy.net/archives/761

Thanks Zubair

Unable to add selected webparts. Cannot import this webpart

I reviewed all the instructions and I had followed every step.

One of the steps mentioned adding a safecontrol entry to the web.config.

On changing the order of where this safecontrol entry was in web.config, to the top of the list, the webpart displayed perfectly.

My thinking is, that one of my other entries is causing an error, and stopping the rest from loading…

Anyway, next time you get this error, try moving the Safecontrol entry to the front of the list, and see if it resolves the problem.

In order to do this it was decided to split the company up to use different site collections, using the same URL to access them.

Thus we needed each site collection to use a seperate database, for easy restores, security, performance and other goodness.

Thus I began researching and found this link:

http://www.networkworld.com/community/node/19780?page=1

Which basically explained exactly what I wanted.

I went with the first approach, as I currently have full control over the system.

Thus I did the following:

1. Set the current content DB to offline.

2. Create a new one.

3. Create a site collection.

4. Switch the first content DB online.

Done.

One issue which arose on one of our environments was the site collection did not create correctly, and it appeared to fail at the end of the process, creating the top level site.

Restarting the timer service fixed this.

That was courtesy of this link: http://www.fftf.org/news/Apr09feed/Resolved__SharePoint_Profile_Sync_Problems.rss.html

Thanks for blogging guys.