Feeds:
Posts
Comments

Archive for the ‘Web Applications’ Category

Dear all,

this is a quick one.

 

The Problem.

Recently I had the problem of not being able to create a page based on a custom master page and page layout. The error shown was:

image

“List does not exist”

“The page you selected contains a list that does not exist”

When clicking on “Site Actions”-> “Create Page”, it simply wouldn’t show the insertion mask for title and URL, but issue the above shown error. The solution for this is easy and quick.

The Solution.

It is quite easy to solve this problem. The authenticated users just don’t have the permissions to read the master page gallery – or in other words: No masterpage access, no new page (which makes sense). Hence, you can go to:

Site Actions –> Site Settings –> Master pages and page layouts –> Settings –> Document library settings –> Permissions

and add there the group NT AUTHORITY\authenticated users (Read, Restricted Read), just like in the screenshot given below:

image

Return to the site or page where you initially wanted to create a page, and you will see it is going to create the page without problems.

 

I hope this was of some help!

Have a good time and stay tuned to the next blog post!

Best regards,

Martin

Advertisements

Read Full Post »

Dear all,

 

a recent study of AIIM has revealed a few interesting statistics about the adoption of SharePoint 2010 for Enterprise Content Management, among the following, in my opinion most interesting ones:

 

  • 70% of 5000+ employees sized firms: Already implemented SP
  • 30% of 10-500 employees sized firms: No intention to implement SP
  • 13% are first-time SP2010 users
  • 27% performed an upgrade from MOSS 2007 -> SP2010
  • 49% plan to integrate SP w/ their existing or new ECM
  • 4% throw away existing ECMs to replace them with SP2010

 

While 76% of the participating companies are from the US, an estimated 18% are from Europe.

 

Here’s the statistics about which SharePoint versions are spread:

 

  • 6%: SharePoint 2010 production system
  • 13%: SharePoint 2003 production system
  • 36%: MOSS 2007 production system

 

… which was expectable: Most of the hitherto known installations are still on 2007. However, I’d expect number of SP2010 production systems to increase in the next months and years, while existing MOSS 2007 production systems would decrease. After all, it is some effort to upgrade from MOSS 2007 -> SharePoint 2010, but certainly it is worth the effort, as SP2010 is offering some nice additional functionality, such as the integrated PerformancePoint Services.

 

Many different industry sectors were participating in the surveys which lead to the above statistics, among them government, social businesses, . The total number of participating companies is 583.

 

What is really interesting to see is that the main business driver for adopting an ECM at all is the improvement of communication, namely an „Increased collaboration within and between teams“ (60% of the companies named this reason).

 

Most Frequently Used Features of ECM Systems

Moreover, the most frequently used features of ECM systems are concurrent document editing and wikis (58%) and blogs (53%). Another indicator that companies do value the inter-communication and knowledge sharing of their staff.

 

Let’s see how long it takes for smaller companies to recognize this value. After all, there are free editions of ECM systems, one of them being SharePoint Foundation 2010.

 

Stay tuned till next time!

 

Best regards,

Martin

Read Full Post »

Dear all,

 

An error I ran recently across was the following. After creating a new SharePoint Server 2010 web application, I tried to activate the PerformancePoint Site Features. At first sight, everything seemed to be done in the correct order:

 

  • PerformancePoint Service Application running
  • Secure Store Service Application running
  • Connection for PPS and SSS to my web application
  • Site Collection created

 

I went on to my web application, then under:

Site Actions –> Site Settings –> Site Actions –> Manage site features

There I tried to activate the PerformancePoint Services Site Features. Tried. And failed. It failed with the following error messages:

 

image

 

So, the first message gave already a good hint. Off I went for the site collection features:

 

Site Actions –> Site Settings –> Site Collection Administration–> Site Collection Features

 

There, I had to enable both:

  • SharePoint Server Publishing Infrastructure and
  • PerformancePoint Services Site Collection Features

 

That did the trick! Now, returning to the site features, I was able to enable the PerformancePoint Services Site Features, and finally could create also KPIs, Scorecards and Dashboards.

 

image

More options for content creation after PerformancePoint Services have been enabled.

 

I hope this helps some of you with the same problem!

Best regards,

Martin

Read Full Post »

Hi folks,

While working through my current SP2010 lecture, I found an exercise which explained how to set up a document center and how to establish a connection to a web site. The goal of this set up? Simple: When working with a web application and working on documents, at a certain point you may want to have this information centralized. And here comes the document center into play. You can use it as a central access point for your documents without really caring how to upload and complete you document library there. In the end, while working in your web application, the “Send To” context menu of a document should contain an entry for sending the document to the document center. That’s all – simple but effective.

The exercise showed how to create a document center (just create a new site collection and select under “Enterprise” the “Document Center” template). So far, so good. The explanation went further and explained the need of setting up a “Send To” connection  (from the side of the web application). So far, everything made sense. As suggested, in Central Administration I went to “General Application Settings” | “Configure send to connection”. There, I had to choose the web application (http://sp2010:25001), specify a display name, and, most important, define the Send To URL. Which one to choose? I knew the URL of the document center, but this wasn’t verified as a valid URL. A bit of browsing on the internet told me that I should append _vti_bin/officialfile.asmx as a default to the URL.

image

 

After confirming, surprisingly I received the following error message:

 

image

 

Still not valid? Something must have been missing. So back to searching, and finally I could find it. After choosing the document center web application, choosing “Site Actions” | “Site Settings” | “Manage Site Features”, I arrived at the following mask:

 

image

 

There, I needed to activate the Content Organizer Feature – done! Now, one  could expect I needed to verify that the feature was really enabled. Still being in the document center, under “Site Administration”, there was the “Content Organizer Settings” menu entry enabled.

 

image

 

A click on it revealed a mask where different options could be set – but most important: The Web service URL I needed!

 

image

 

A little copy & paste, and the job was done! I hopped back to step 1 and set up the “send to connection” using the now valid URL. It worked.

 

image

 

As you can see in the screen above, in the web application containing the send to connection, the new “Doc Connection Center” is available and ready for use!

 

Stay tuned till the next time!

Best regards,

Martin

Read Full Post »