I’m seeing this on multiple SharePoint 2010 installation when dealing with a publishing site. Colonel Forbin has posted this issue on social.msdn.com.
When adding a picture to a publishing page and navigating through the dialogs, there used to be an upload feature on this dialog. It seems that it’s not appearing for some reason. Anyone else seeing this?
I was doing a little monkeying around (read that "book editing") with SharePoint 2010 and decided to see if the similar post I read by Sameer Dhoot was still true in 2010. If you are missing the CQWP in SharePoint, you’ll find that activating the Publishing Infrastructure feature will fix the problem, as the CQWP is added/enabled as part of the Publishing Infrastructure. Well, what if you want to use it in a team site for some reason? Turns out you can still do it.
If you simply export the CQWP from the web part gallery of your publishing site and import it to the web part gallery on your collaboration site, you won’t run into any problems.
You can export the web part by clicking the Edit icon and selecting the Export function in the ribbon.
The problems will start to occur when you try and use it. You’ll get errors when your page on which you’ve added the CQWP attempts to render the web part.
In this version of SharePoint, there is a Style Library in both collaboration and publishing sites. The important difference is that the collaboration site Style Library is empty. This is where the problem resides. You can either copy the content out of the publishing site style library or, you can create a list template out of the publishing style library and save the content with the template.
Since the publishing site does not have a "Save document library as template" link, you’ll have to create one on your own. Navigate to the library settings on your Shared Documents library and select the "Save document library as template" link. You’ll notice that this is using the _layouts/savetmpl.aspx page and it is passing the List GUID as a parameter (/_layouts/savetmpl.aspx?List=%7B1C534D30%2D9F2F%2D41A5%2DAC98%2D51CD244F532D%7D).
Navigate to the publishing site’s Style Library settings page (_layouts/listedit.aspx). Now simply change the listedit.aspx to savetmpl.aspx and press enter. Fill out the form being sure to "Include Content" and save it.
You should get a successful save. Now navigate to the list template gallery.
Right-click and save the list template (STP) on your computer.
Now all you need do is navigate to your site template gallery on your collaboration site and upload the STP file. Then you can delete the existing Style Library and create a new list called Style Library from the template.
You should now feel the love the the CQWP in your collaboration site.
Further investigation shows that the CQWP needs these three style sheets in order to function correctly: ContentQueryMain, Header and ItemStyle. Removing any of these from the Style Library will cause the CQWP to throw an error. So, you could probably just export these styles and import them into your collaboration site’s Style Library and accomplish the same thing.
Thought this might be an interesting graph for some folks.
This shows the elapsed time for upgrading a content database using the database attach method. This was all done on a memory-starved, physical quad-core server with 4GB of memory that has SQL, SharePoint 2010 and Project Server 2010 on it. This is NOT a final production configuration…it is merely a test to see what issues we are going to encounter during the upgrade to 2010.
So far, it doesn’t look like Bamboo or SharePoint Solutions have their 2010 products in production yet, so we didn’t have all the binaries on the test box. But, that didn’t stop us from being able to successfully get through the database attach (mount) PowerShell command:
Mount-SPContentDatabase
Now we have to wade through the "not best practice" UI customizations that were done to our 2007 web apps. Looks like it’s time for an extreme makeover!
Note to self:
REBOOT THE CABLE MODEM!
If you find yourself missing lists and libraries on the create page in SharePoint and you’re wondering where where your WIKI library, contacts list, announcement list, calendar, and all the other goodies went, you’ll need to check to insure that the features are enabled on your site. Here’s a case where there are plenty of custom lists, but not many of the out-of-the-box lists.
It’s very possible you created your site with a publishing portal template and all the other goodies were not turned on by default. To correct this, you’ll need to navigate to the Site Features page under Site Administration.
From here, you can see that the standard features and team collaboration lists are not activated.
So, activate the standard site features and team collaboration lists.
You should be able to create all the lists and libraries you want!
I was getting this error when trying to extend SharePoint to another web application:
The Execute method of job definition Microsoft.SharePoint.Administration.SPWebApplicationProvisioningJobDefinition (ID 22631de2-0c21-4e1b-aa9c-12e4f60a18f6) threw an exception. More information is included below.
"SharePoint – eicomsp4:80" contains illegal character ‘:’.
Turns out that, somewhere along the way, SharePoint allowed a colon in the name of another extension that was now causing the timer job to fail. I also had to delete the "run once" timer job that was associated with the failed extension attempt. Weirdness.
Today I helped a client solve one of the many mysteries around the infamous "Render Failed" that so many people seem to get at some point in time on MOSS 2007. In this situation, the error started appearing on several list views and nothing had been changed for several weeks prior.
After some trial and error, I found the problem was tied to several site columns that were being displayed in the views. The site columns were lookup columns and were used many places throughout the site hierarchy. Of course, this happened on the same day that my son and daughter-in-law were having their first child (and our first grandchild), so I found myself troubleshooting from the waiting room at Medical City in Dallas. I know this doesn’t have anything to do with the problem, but my son’s a new father and I’m a new grandfather…so sue me! I’ve got a captive audience and I’m a proud grandpa. 
Cason Noble Wright 2010-05-19
Anyway, it was really weird that nothing had been changed and this started and was fairly widespread. After monkeying with filters, view styles, sorting, grouping to see if any of those things changed the outcome, I observed that, as I removed columns from the display, the views began to work. That’s how I determined that the problem was tied to the site columns that were of the type "lookup."
To make things worse, later during the day the SharePoint site completely quit. Now I suspected something was amiss on one of the servers.
This client has a simple two-server setup, so I VPN’d in to each server. When I got on the SQL Server, I found that AUTOMATIC UPDATES was on and the machine had been updated and was awaiting a reboot. Ah ha! Finally a potential root cause.
I quickly contacted the client and told them to reboot the SQL Server and the problem was solved. And, TURN OFF AUTOMATIC UPDATES ON A PRODUCTION MACHINE!!!
Now, back to the grandbaby…
Reference Links:
Not sure if anyone else is seeing this, but I’m trying to get to the MS SharePoint site for the launch and nothing is happening! I can get to microsoft.com just fine, but if I go to microsoft.com/sharepoint, it redirects me to http://sharepoint.microsoft.com and I get this:
Hope they aren’t running the site on SP2010 and this is indicative of things to come!
Maybe I’m just too early.
Hey, now it’s showing up at 10:31 central. I’m pretty sure it’s nothing I did.
Guess I won’t be watching the keynote live…
Well, I guess it wasn’t just me.
Yes, I love technology
But not as much as you, you see
But I still love technology
Always and forever…
Update 20100802: I’ve rewritten this post a couple of times, adding more detail as we find it. We think we might be on to finding "the recipe," but we’ll only know for sure when we repeat the process in the staging and production environments and get repeatable results. This post is "in-work."
Oh man, this has been driving us CRAZY (just ask Leslee)! We have a multi-valued column in SharePoint (Subject) and we couldn’t get all the values to show up in the search results. All we could get is the last value. See this post: Always returning last value.
We had different results before we upgraded to SP2. In SP1, we were getting some weird results with some of the values being returned as ;#Value;# or some such nonsense. We hope we don’t see that again.
Currently, we are on SharePoint 2007 SP2 with the February 2010 June 2010 cumulative update with the infrastructure updates installed.
There were a few hints from Ontolica (Surfray) from this post.
From this post by Michael Schau, we started to deduce a method to fix the problem. Here’s what we came up with.
Overview:
Let’s start with the ugly part first. You’re not going to like this but, if MS doesn’t have software that correctly updates the database, then we’ll do it manually. After all, it’s just a database!
Find your SSP database in SQL Server Management Studio.
Find the MSSManagedProperties table and open it for editing. Locate your managed property using its FriendlyName and change the HasMultipleValues column to "True" (or 1).
Now find the MSSCrawledProperties table and open it for editing. Locate your crawled property using its PropertyName and change the VariantType column to 4127. We found when you change the VariantType to 4127 the Multi-valued field changes to "Yes." All of the multi-valued fields we could find had this variant type.
The variant type for a text field is 31 (0000000011111). The variant type that shows up on a multi-valued text field is 4127 (1000000011111). Could it be that the leading bit identifies the field as multi-valued? Here’s an incomplete table for the crawled properties in the SharePoint category.
| Variant Type | Multi-valued | Decimal | Binary |
| Text | False | 31 | 0000000011111 |
| Text | True | 4127 | 1000000011111 |
| Binary | False | ||
| Binary | True | ||
| Integer | False | 20 | 0000000000010 |
| Integer | True | ||
| Yes/No | False | 11 | 0000000001011 |
| Yes/No | True | ||
| Decimal | False | 5 | 0000000000101 |
| Decimal | True | ||
| Date/Time | False | 64 | 0000001000000 |
| Date/Time | True |
You are done modifying the database. Great job! You’ve now voided your warranty.
Now we’re going back to Central Administration in the SSP where your search is located.
Remove the mapping for the crawled property from the crawled metadata store. You can get there from the Metadata Properties page by clicking on Crawled Properties.
Find and edit your crawled property. Remove the mapping and de-select the "Include values for the property in the search index" field.
Find your crawled property group (SharePoint in our case) and drill into it.
Click on Edit Category .
Select the checkbox to delete all unmapped crawled properties and click OK.
Reset all crawled content and perform a full crawl. I hope you don’t have too much data! Perhaps you should have thought to limit it before you started!
After the full crawl has completed, you need to add your property back. It should be in the crawled properties. You need to map it back to your managed property. After you have it added back, perform ANOTHER full crawl, after which, you should see the property is correctly classified as multi-valued.
What does this get you? Now, if you look at the raw XML search results for your managed property, you should see the multiple values returned. In this example, we’re looking at a managed property called owssubject.
And, if you apply your XSLT, you should get something that’s nice looking, like this!
Search terms:
Multivalue fields in SharePoint search not returning all values
Multivalued fields in SharePoint search returning single value
Multivalued fields SharePoint search not working – broken
Can’t get multivalue field to return more than one result in Sharepoint search
If you need to update a URL field in a links list (or any other list) from SharePoint Designer, you need to know this little trick. Create a string that contains the URL and description like this:
URL, Description
and then update the field with this string. Notice there is a comma AND A SPACE after the URL. There are no brackets, curly braces or octothorpes (# signs) involved in the string.
Using the string builder, you can see the "input" and the "output" of the workflow.
