Why didn’t I know about this before?
If you’re a Chrome user and wish to have very similar Fiddler functionality, it’s already built in. Just go to chrome://net-internals/ and you’ll see a large amount of data with the ability to export. It’s pretty nice!
This looks like it might be really good but I wonder what it costs. At the top it says “free” but at the bottom it states: You can activate and deactivate applications with a click of the mouse. You get billed only for what you use.
Feature list at a glance:
- Microblogging – Share anything with your team quickly and communicate with specific team members using @replies. Streamline your productivity by asking for feedback, tag content, and much much more.
- Team Feed – The team feed organizes all your team’s activities into one easy to digest page. Track documents, post links, videos, pics, ask questions, assign tasks and provide insight all in one place.
- Rich Profiles – Quickly explore what your team mates are up to with one click. Profiles allow you to keep tabs on your team, explore common topics, locate expertise, and communicate all in one simple page.
- Tagging – Tagging makes the chore of organizing data a breeze! You can tag your posts as you create them or allow your team to assign tags later. Your activity stream can be filtered by tag to make finding that proposal much easier or help subject matter experts discover your questions. With infinite tag context gain insight by discovering content that would ordinarily go unnoticed. Tagging is the fun way to stay organized!
- Bookmarks – Bookmarks make it easy to keep track of the information that’s important to you. You can store any number of bookmarks and locate items, docs, links, or any other activity by tag, keeping the information you need at your fingertips.
- Task Integration – The industry’s first social workflow engine makes social accountable and productive with inline task integration. Assign tasks to get questions answered, get projects moving, review documents, or anything else you can think of!
Microsoft has come out with application templates for those who work in academic medical centers or health organizations. See the list of the various templates below:
In upgrading from SharePoint 2007 to SharePoint 2010, one of my InfoPath forms would not return the XML data for a form field. The error I was getting was:
XML data that is required for this form to function correctly cannot be found
If I previewed the form in InfoPath 2010, I had no issues. It was only on the site that this error would occur.
Here is my original data connect XML link:
This worked fine in SharePoint 2007, no issues. In SharePoint 2010 apparently, it needs to look like this:
After that, it works fine.
Last night I attended a meeting of the Triangle SharePoint Users Group (aka TriSPUG) here in Raleigh where they had a presentation by Jason Medero of B&R Solutions on “Migrating from SharePoint 2007 to SharePoint 2010 – Tools and Options.” In the presentation, Jason presented four ways to migrate and upgrade your current SharePoint 2007 farm to SharePoint 2010. Those four approaches are:
- In-Place Upgrade – the easiest approach but has the least amount of flexibility in configuration and has the most downtime. Also, depending on your hardware, it updates all the databases simultaneously which slows down the process and can take days or even weeks if this is attempted on a site with large content databases. And there is no ability to pause or rollback the upgrade.
- Database Attach – this is where you detach your content databases, create a new installation of SharePoint 2010, recreate your configuration, and finally reattach the content databases. This method has your site down while you upgrade.
- Hybrid Read-Only Database Attach – This method has you put your current site in read-only mode as you use backups to do the database attach on the new farm. This allows for users to continue using the site as you set up the new one. Once complete, you do a DNS change and point everyone to the new farm.
- Hybrid Detach Database Upgrade – Here you detach your content databases first, do the in-place upgrade, then reattach those content databases. The advantage with this is that the configuration is upgraded without having to reconfigure.
Take a look at the video below to hear Jason discuss all of these options as well as the tools to use before you start any of these methods. WARNING: the audio in the video is very loud so adjust your speakers prior to hitting play.
Recently I noticed quite a few “There is no web named [link to specific aspx file like AllItems.aspx]” in my SharePoint 2007 logs. Most online boards say to ignore the error, it’s just “noise in the logs.” Well, it can be a lot of noise.
If you remove the item from the Quick Launch (List Settings > Title, description and navigation > Display this list on the Quick Launch?), the errors go away. If you add it back, so do those errors. Solution?
Nope, no solution, but you can at least workaround it. If you set “Display this list on the Quick Launch?” to “No” and then go into your site navigation and add a link back to that list, no more errors. It’s not a pleasant solution but the look is the same to the user and no more errors clogging up my logs.
Just some reminders to myself, the STS#0 template is the blank template. So if you get the “you cannot import because of STS#0 and STS#1 templates do not match”, you have to delete/create your Site Collection again but this time choose the blank template instead of the team site (which I assume is STS#1).
Also when doing an import, if you run into the “failed to read package” error that's likely because you don't have enough disk space on drive C even if you're importing cabs located on a different drive.