Ravendra's Blog

April 28, 2010

Explorer view of MOSS 2007 site not working on IE8

Filed under: Sharepoint — Ravendra Mishra @ 11:13 am

Explorer view of MOSS 2007 site not working on IE8

when I’m working in shared documents, I’m trying to use the explorer view. It says ” Please wait while Explorer View is loaded. If Explorer View does not appear, your browser may not support it. ”

 


 

This seems a known issue; If you are not able to carry out your work without explorer view then you may try following options to make it work:

 

 

  • If still not working then try below (Make sure Web Client Network Protocol is installed in your client machine)

1. Go to START > RUN

2. Type _services.msc_

3. Locate the _WebClient_ service

4. Open the service and make sure startup is set to _Automatic_. If service is already stopped, you’ll have to hit _START_ after setting to Automatic.

 

  • Try deleting all the temp files in the following locations:

    c:\documents and settings\[Username]\nethood
    c:\documents and settings\[Username]\application data\microsoft\web server extensions\cache

    Then try running these commands in sequence

    net stop webclient
    net stop mrxdav
    net start webclient

 

  • Actions -> Open With Windows Explorer this will open a new Windows Explorer window that is in reality a web folder to the Document Library.
Advertisements

February 2, 2010

SSRS Report on TFS 2010 Portal


Sometimes default reports which comes out of the box with process templates are not enough and custom reports are required. These reports can be put together on SharePoint team portal to create a dashboard or part of existing pages/ dashboards. If using SSRS on SharePoint integrated mode than rdl files of these reports can be copied directly on document libraries. Sometimes SSRS is not running on SharePoint integrated mode specially when SSRS is deployed in different box then SharePoint box. In such cases using Web page view web part can be quite useful.

Let’s say there is project collection called “PCollection” contains a project called “PProject” contains a report called “PReport” then URL for this report on page viewer web part will be something like

/PCollection/PProject/_layouts/tfsredirect.aspx?IsReport=1&ReportName=PReport

If report is located within folders let’s say “Dashboards” then URL will be

/PCollection/PProject/_layouts/tfsredirect.aspx?IsReport=1&ReportName=Dashboards/PReport

If report name of folder name contains multiple words then space between these words should be replaced by ‘+’ symbol. For example in above examples folder name is “Project dashboards” and report name is “Burn up report” then URL will be something like

/PCollection/PProject/_layouts/tfsredirect.aspx?IsReport=1&ReportName=Project+dashboards/Burn+up+report

December 31, 2009

Sharepoint 2010 New Features

Filed under: Sharepoint — Ravendra Mishra @ 5:38 pm
Tags: , , ,

Sharepoint 2010 New Features

Terms WSS is replaced by SharePoint foundation server and MOSS is replaced by SharePoint server. New hardware requirement is 64bit server however it will work on x86 servers as well. OS requirement is x64 edition of either windows server 2008 or server 2008 R2. It also requires 64 bit version of MS SQL Server 2008 or 2005.

The most prominent change to the visual interface is the introduction of the Ribbon which looks same way as it does in Office 2007 and Office 2010

  1. Browser Support

SharePoint 2010 will support a wider range of browsers. Out of the box, SharePoint

will support IE 7 and newer, Firefox, and Safari as Tier 1 browsers. This means that

all features will work in these browsers.

  1. Lists

Lists in SharePoint 2010 get an overhaul,

XSL Lists?

SharePoint 2010 does allow you to use XSL for your list views rather than the dreaded CAML View schema. In this case, the list view is stored in an out-of-the-box XSL file called main.xsl, which in turn references other XSL files to render the output of a view.

XSL is a much more usable standard for rendering content than the CAML View

schema, and since it’s an open standard, you get much better tool support as well. More details on MSDN blog:

http://blogs.msdn.com/sharepointdesigner/archive/2009/11/16/sharepoint-2010-listview-blog-series-part-1-introduction-to-the-new-list-view.aspx

List View Joins

This is definitely one of the best features in Sharepoint 2010. You can now join data from multiple lists into a single view. This includes any external lists as well, so you can now put your legacy data sources into SharePoint and utilize parts of that data in pure SharePoint list views as well.

The list join feature works much in the same way as SQL views, although the

syntax is very different. These joined views are defined in CAML code in the view

itself.

List Throttling

In MOSS 2007 there was Microsoft recommendation to restrict view items by 2000 but there was no way to enforce it. In SharePoint 2010, administrators may enforce the limit of items in a view. By default, this limit is set to 5,000 items, but administrators can change this for any list or set of users or disable the feature completely.

List Validation

SharePoint 2010 allows to do validation of the input to a list, enforcing either business or technical rules for what kind of data should be accepted. If you have worked with calculated columns, the format of these validation rules is very similar,

For example, you can disable the editing of items using a simple validation rule such as [Modified]<[Created]. This will disallow editing if the Modified date is later than the Created date, which it will be for any subsequent edits after item creation. In previous version of SharePoint, this required .NET code.

External Lists

BCS replaces Business Data Catalog from SharePoint 2007. BCS allows to connect any data source and work with the data in that data source almost as if it were a standard SharePoint list. This is what is known as an external list.

There are a few limitations, but you can work with the normal CRUD operations

(Create, Read, Update, Delete), and you can use external lists as part of a joined

view.

  1. User Solutions

You may have heard about something called the Solution Sandbox. In short, the

Solution Sandbox allows you to deploy solutions to a single site collection rather

than to a web application. But it gets a lot better.

These site collection solutions are user uploadable, so end users can create or

download solution packages and deploy them to their sites without requiring web

application permissions. This includes .NET code for certain operations as well.

This may sound very scary, allowing users to run code. This is where the Solution

Sandbox comes into play.

The Solution Sandbox runs the .NET code in a limited environment to protect both

the performance and the security of your farm. You can limit these user solutions to

prevent that one faulty solution from consuming too many resources, and you can

even block solutions that you do not want running in your environment.

  1. Client Object Model

For developers, the new Microsoft.SharePoint.Client namespace offers an easy way

of creating client applications for use against SharePoint sites. This includes both

regular applications and Silverlight applications, as well as web-based applications.

The client object model provides a subset of the full SharePoint object model,

enough to work with major components such as lists, users, content types, sites, and

so on.

Ton Stegeman has written a blog post showing how to use the client object model in

JavaScript (or ECMAScript, really):

http://www.tonstegeman.com/Blog/Lists/Posts/Post.aspx?ID=118

What is cool with the client object model is that you as a developer do not need to

learn a completely new object model. The client object model has more or less the

same objects as the regular object model, and the behavior is also very similar.

  1. Search

There are also improvements to search in SharePoint 2010. Search in SharePoint is

now served by three products: Search Server 2010, SharePoint Search, and FAST

Search for SharePoint 2010. Licensing is available from free (Search Server 2010)

to expensive (FAST Search for SharePoint 2010).

All the search engines offer improved search over previous versions, such as

relevance and query completion. Of course, the feature set increases with the more

expensive editions, but for most smaller organizations, the free Search Server 2010

will do a great job.

FAST Search

After Microsoft purchased FAST Search and Transfer, everyone has been looking

forward to seeing what Redmond was going to do with the company. To us as

SharePoint people, perhaps the biggest news is that SharePoint gets a special FAST

search engine, titled FAST Search for SharePoint 2010.

FAST has been a market leader for enterprise search for many years, but unless you

had a wallet the size of Egypt, you were unlikely to be able to share in the goodness.

However, the new engine promises both cheaper and easier access to FAST for

SharePoint sites.

  1. Business Intelligence

You find further new features in the Business Intelligence category, dubbed

Insights. Excel Services and the dashboards are still with us, but there are several

new features as well.

Related to Excel Services is SQL Server PowerPivot, a web-based service

previously known as Gemini. In short, users can now navigate and query massive

datasets in their browsers in microseconds. An Excel spreadsheet with tens of

millions of rows would take quite literally forever to download, but PowerPivot

makes filtering and working with data such as this very fast.

For enterprise license holders, Performance Point is now included. Performance

Point prior to SharePoint 2010 was a stand-alone SharePoint-based business

intelligence tool that Microsoft decided to include in the package for SharePoint

2010. Performance Point is great for setting up dashboards and getting insights into

business data, including drilling down into details in the browser.

The previously mentioned BCS improves Insights even more, allowing you to

expose other business data in SharePoint and utilize it as part of KPI dashboards or

in other business intelligence solutions.

  1. Managed Metadata Services

WithManaged Metadata Services, you can define and manage a central set of

metadata throughout your farm. You can then use these sets of metadata as

metadata in lists or content types, as tags for tagging content, or for other uses.

These sets of metadata are stored in term sets. For each term set, you can set

permissions and optionally allow users to extend the set by providing custom

values.

One vast improvement served by the Managed Metadata Services is the optional

content types distribution. You can now centrally define and manage content types

and allow your site collections to subscribe to these content types.

On the next page, in Figure 14, you can see the overview of the various service

applications that ship out of the box with SharePoint 2010.

  1. Service Applications

A major change in architecture, however, is that of service applications. Out is the

old Shared Services Provider, and in is the new method for sharing data and

services across an organization.

Service applications are individual services such as search, user profiles, Excel

Services, and others. However, rather than being part of one monolithic application

as was the case for Shared Services, the service applications are individual services

that can be turned on and off as needed.

Further, these service applications can expose themselves as WCF services to any

location anywhere. If you have no idea what that means, think of it like software as

a service where you can expose services in your SharePoint farm to someone else

either in your organization or on the Internet.

Companies may, for example, expose their user profile services to each other to

allow for cross-company people search. Other organizations may want to build a

giant Excel services rendering farm and allow other farms to utilize that service so

they do not have to implement it themselves.

Developers can also create new service applications and harness the power of

SharePoint to create completely new features either locally or globally.

  1. SharePoint Best Practices Analyzer

With the SharePoint 2010 release, SharePoint Best Practices Analyzer will be incorporated as part of the base SharePoint product. This tool provides Microsoft’s guidance for SharePoint implementation and troubleshooting. A Problems and Solutions page in the analyzer helps you solve common implementation problems.

  1. Usage reporting and logging

SharePoint 2010 includes a new database designed to support usage reporting and logging. The usage database is extensible, allowing third-party vendors to create custom reports based on the information it contains.

  1. Visio Services

Visio Services in SharePoint 2010 lets users share and collaborate on Visio diagrams. A built-in viewer lets SharePoint users view Visio files in their browser without having Visio installed on their system. Visio Services also retrieves and renders any external data used in the Visio diagrams.

  1. Enhanced collaboration features

SharePoint 2010 supports tagging content as well as providing enhanced blog authoring capabilities. There’s a new group authentication feature that’s based on distribution list or organization and a new rich text editor for creating wikis. In addition, calendars from Microsoft Exchange Server can be merged with SharePoint calendars.

Blog at WordPress.com.