daumkr: octubre 2010

martes, 26 de octubre de 2010

How to Create a MOSS 2007 VPC Image: The Whole 9 Yards

http://www.pptspaces.com/sharepointreporterblog/Lists/Posts/Post.aspx?List=7537e639-b4e5-48b6-97c0-a75e44ee9be3&ID=28&Source=http://www.pptspaces.com/sharepointreporterblog/Lists/Posts/AllPosts.aspx

How to Create a MOSS 2007 VPC Image: The Whole 9 Yards

Now that I've finally completed my series of posts describing how to build a Microsoft Office SharePoint Server (MOSS) 2007 Virtual PC image for demos and development work, here is a one-stop-shopping index of all 20 posts:

Part 1: Getting Started, Installing IIS, and Installing .NET Framework 2.0

Part 2: Installing and Configuring POP3 Email

Part 3: Installing and Configuring Outlook 2007

Part 4: Installing and Configuring the .NET Framework

Part 5: Installing SQL Server 2005

Part 6: Configuring SQL Server 2005

Part 7: Installing SQL Server 2005 SP1

Part 8: Creating the MOSS Accounts

Part 9: Installing and Configuring the MOSS 2007 Application

Part 10: Setting Up Internet Explorer Web Browser Security

Part 11: Starting Services

Part 12: Creating a Shared Services Provider

Part 13: Configuring Search Settings

Part 14: Configuring Outgoing E-mail

Part 15: Creating the Portal

Part 16: Installing SharePoint Designer 2007

Part 17: Installing Office 2007 Applications

Part 18: Installing Warm-up Scripts

Part 19: Optimizing the MOSS 2007 VPC Image

Part 20: Creating a Virtual PC Differencing Disk

viernes, 15 de octubre de 2010

Campo de búsqueda filtrado (Nuevo tipo de dato): webpart

Project Description
Porting of the "SharePoint Filtered Lookup Field" project to SharePoint 2010.

This project is the porting for SharePoint 2010 of the "SharePoint Filtered Lookup Field".
You can find the list of available features here: http://filteredlookup.codeplex.com/. Now available also for SharePoint Foundation 2010 and SharePoint Server 2010.

Addictional informations about the lookup field are available here:
- English project description
- Italian project description

http://sp2010filteredlookup.codeplex.com/

http://surpoint.blogspot.com/2010/06/sharepoint-lookup-filter-2007-y-2010.html

http://surpoint.blogspot.com/2010/04/u2u-caml-query-builder.html

Organizador de contenido

http://www.gavd.net/servers/sharepointv4/spsv4_item.aspx?top=art&itm=1126

problema con document information panel

Ambiente: panel personalizado creado con Infopath 2010. Sobre MOSS 2010, y usando MS Office 2007.
Aún desconozco el problema del error.
Se probó todos los foros a quienes les resultó.
Instalación de hotfix.
Modificación archivo xsn, compilación con makecab.exe.
Con MS Office 2010, no resultó, ni muestra el panel personalizado.

http://www.howtofixcomputers.com/forums/microsoft-office/document-information-panel-word-2007-excel-2007-powerpoint-2-a-91637.html
http://support.microsoft.com/kb/954571/en-us#appliesto
http://www.eggheadcafe.com/software/aspnet/32445525/excel-2007-the-document-information-panel-was-unable-to-load.aspx
http://mossytips.blogspot.com/2009/12/form-template-associated-with-this-form.html
http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/2a4d6d10-d1d5-4d6a-a22b-62dfb6b60685/
http://social.msdn.microsoft.com/Forums/en-US/sharepointinfopath/thread/243b4852-3f17-4a3a-b6d7-187d65a5f088
http://www.infopathdev.com/blogs/matt/archive/2006/02/02/Setup-Namespaces-for-a-Secondary-Data-Source.aspx
Si alguien encontró la solución..

Posibles soluciones, que no he probado:
http://geeks.ms/blogs/gortigosa/archive/2010/04/22/automatizar-documentos-office-2010-con-datos-de-sharepoint-2010.aspx

Otras informaciones:
http://msdn.microsoft.com/en-us/magazine/cc500578.aspx

¿Por qué no inicia el WF Personalizado que colocamos en autostart?

No usar system account, editar el wf con una cuenta distinta. SHAREPOINT\SYSTEM.

http://blogs.technet.com/b/victorbutuza/archive/2009/03/14/workflows-do-not-start.aspx

You are of course aware of the fact that starting with Service Pack 1 the workflows created in SharePoint designer that should launch under the credentials of the system account will no longer start automatically.
You know what the resolution is for this problem: simply do not to use the system account.
You implemented all the steps written here http://support.microsoft.com/kb/947284 ,but the workflow still does not start.
More interesting, if you email-enable a document library and attach a workflow to it, and set the workflow to start on Item creation, this workflow will never start.
This usually happens because the e-mail is saved into the document library using the sharepoint services timer service account credentials. If an e-mail was created by the system account then the workflow will attempt to start using the system account which is no longer permitted.
As you cannot change the credentials for the for the timer service, what should you do?
The answer is pretty simple: install Infrastructure Update http://support.microsoft.com/kb/953749/(and of course if you are at it, you can update the whole farm to the latest patch level (FEB CU) ) and pay close attention to one small line (made bigger here because of it’s importance) written in the notes part of the knowledgebase article:
To prevent the declarative workflows from impersonating the system account, the workflows will now impersonate the user who created the workflow association.
This basically means that you should create a special account not SHAREPOINT\SYSTEM, that is a site collection owner on the site collection where the workflow is hosted, open the workflow in SharePoint Designer while logged on as this new account and simply save the workflow without modifying anything.
It will effectively change the account that associated the workflow, which will allow it to start.
A !
you should also run
stsadm -o setproperty -pn declarativeworkflowautostartonemailenabled -pv true
to enable workflows to start using the impersonation scheme
http://support.microsoft.com/kb/953289/

más info:http://social.msdn.microsoft.com/Forums/en-US/sharepointworkflow/thread/376ed7ef-4dcd-4633-ba53-5cf06626a1ff
http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010customization/thread/5fd8aefc-81c6-4ea1-acd0-ab82339f6c2a

Incluir filtros de tipo Elección en la búsqueda avanzada (webpart)

http://spadvancedsearch.codeplex.com/

también funciona para MOSS2010.

Personalizar página de resultados de búsqueda

http://www.sharepointdevwiki.com/display/sp2010/Removing+metadata+from+SharePoint+2010+search+results
http://sharepointfoundation2010.blogspot.com/2010/08/customize-search-results-in-sharepoint.html

http://www.sharepointer.es/2010/01/moss-2007-personalizar-resultados-de.html

Este link: http://www.zimmergren.net/archive/2007/10/28/moss-2007-customize-the-search-result-using-xslt-part-3-customize-using-sharepoint-designer-2007.aspx

http://blog.jesskim.com/kb/420

http://www.wssdemo.com/Blog/archive/2006/12/22/customising-sharepoint-search-moss-only.aspx

http://www.google.cl/#q=sharepoint+2010+metadata+search+result+custom&hl=es&safe=active&biw=1280&bih=907&ei=JXq4TMWwIMP58Abnrey4Dw&start=30&sa=N&fp=d344f3e1a11fda42

martes, 5 de octubre de 2010

Plantillas de sitio nativas MOSS2007

http://blah.winsmarts.com/2007-7-All_you_ever_wanted_to_know_about_SharePoint_2007_Site_Templates.aspx

What are site templates?

Sometimes, you need to create the cutter for sites, so you can create cookie cutter sites easily. SharePoint comes with a few such cookie cutters out of the box. You might have seen this cookie cutter picker when creating a site/site collection etc. as shown below:

Those are usually site definitions (not Site Templates). I have covered the process of registering custom site definitions over here.

The obvious Q here is, How are Site Templates different from Site Definitions?

Site Templates vs. Site Definitions

Site Templates are a LOT easier to create than Site Definitions. You can create a site template using point and click. Creating a site definition requires hand-coding a lot of XML files and other supporting files.
Site templates serve a customized version of pages, i.e. low performance. Site definitions serve uncustomized pages, i.e. high performance. Thus you should choose site definitions over site templates, if a large number of sites will be created based on this cookie cutter.
It is fairly easy to move around a site template. It is a tad bit (but not horribly more) complex to move around site definitions.

How to export a site to a site template?

Pretty darned easy. Go to http://<yoursiteaddress>/_layouts/savetmpl.aspx . Note: There is no UI point and click that takes you to this URL for a site, so note this URL down.

You are presented with the following form.

Fill it out, and hit "OK". The template file (.stp) gets saved under the Site Template Gallery, which can be accessed by going to the Site Collection, Site Actions --> Site Settings --> Modify All Site Settings, and clicking on the "Site Templates" link under the "Galleries" section. As you can see, the entire site got squeezed into a single .stp file (which is really a cab file). Quite impressive. :-)

How to register a site template inside a site?
AND
How to restrict certain sites to use only certain site templates?

Okay, so now you have created a cookie cutter for your site. The next obvious question is, "How can I use this cookie cutter?".

EASY!

a) You need to make sure that the site template exists on the site collection. This can be done by uploading an existing site template to the site template gallery. As mentioned above, the site template gallery can be found by going to the top level site in the site collection, then going to Site Actions --> Site Settings --> Modify All Site Settings, and clicking on the "Site Templates" link under the "Galleries" section. Alternatively, you may also use the stsadm -o addtemplate command.

b) The next step is that you need to make this template uploaded in the gallery available to individual sites. So that is basically saying that Site A can use template X, but Site http://A/B can use only template Y. You would note for instance that out of the box, a publishing site lets you choose only "Publishing site with workflow" definition based sites as child sies. Well you can change that.

1. Just go to http://<yoursiteurl>/_Layouts/AreaTemplateSettings.aspx NOTE: Note down this URL :-), there is no point and click way of getting to at the site level. At a site collection level, you may use Site Settings -> Modify all Site Settings -> Page Layouts and Site Templates to reach the same page.

2. Pick the templates you'd rather have available as shown below:

.. and hit "OK". Now the appropriate site templates will show up in the cookie-cutter-picker. :-) w00t!

Ummm .. thats about it as far as site templates go. Anything I missed re: Site Templates? Leave a comment or send me a message.

Registrar definición de sitio personalizado en MOSS2007 (site template)

http://blah.winsmarts.com/2006-12-Registering_your_custom_site_definitions_in_SharePoint_2007.aspx

Last night, Carl and I did end up recording the sequel to the first SharePoint 2007 DNRTV show we did earlier. In this episode, I had a chance to talk more about content types, and then I ran through a full-fledged example demonstrating an InfoPath Forms Services based solution solving a real life problem. And then after that I demonstrated creating KPI (key performance indicator) reports based on data collected via infopath forms running in a web browser.

All in all, the show I think, turned out quite well. I will blog about it when it is online.

But, that is not what this blog post is about. When Carl and I were recording, based on a conversation, I had alluded to the fact that you can create your own site definitions and register them within SharePoint 2007. How you ask? It’s a question of twiddling with a bunch of XML files. To which, of course the developer world comes to a screeching halt.

Yes, SharePoint does suffer from XMLITIS, but I have blogged about that as one of the criticisms, and let us get over that.

The real Q is, how can you, register your own site definitions. Well here is how.

First you need a custom site definition. As you may be aware, a custom site definition is nothing but a logical grouping of features, lists, web parts, and a whole bunch of other things, that together make a site. For instance, I could create a custom site definition for a “Blog reader” application. (Speaking of which, in a week or two, the next issue of code-magazine will contain an article from me, demonstrating exactly how to create a blog-reader application a.k.a. bloglines/newsgator etc in SharePoint). All site definitions reside as a bunch of files at the following location.

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\SiteTemplates

(Note: I am almost done reviewing Scot Hilier’s upcoming Apress book on SharePoint 2007. He explains this very well in Chapter 11, and I strongly recommend you picking a copy of it – the book is simply excellent, and yes I will post a full review later).

Now in that directory, there are a bunch of site definitions already created. You can create one of your own, but since this blogpost doesn’t talk about that – go ahead and copy paste, “BLANKINTERNET” to a directory called “Sahil”

Now ideally, the directory “Sahil” which contains the details of your site definition, should contain something meaningful in it – so a blogreader site definition will contain the necessary lists, features etc. But ignoring that, let us next look at, how you can register this new Site definition, in SharePoint.

Now at this path –

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\

You would note a curiously named directory called “1033”. 1033 is the culture number for en-us (US English). Under 1033\Xml, there are a bunch of XML files. Strangely enough, many of them are named as “WebTemp*.xml”. That is where you need to put this new site definition’s information, so SharePoint will understand it. Go ahead and copy paste webtempsps.xml and call the new file webtempsahil.xml. The name is important, since SharePoint will look for all files that match “WebTemp*.xml”.

Now go ahead and edit the webtempsahil.xml file to look like as below.

<?xml version="1.0" encoding="utf-8"?>


<Templates xmlns:ows="Microsoft SharePoint">
<Template Name="Sahil" ID="10001">
<Configuration ID="0" Title="Sahil's site" Hidden="FALSE" ImageUrl="/_layouts/1033/images/IPPT.gif" Description="This is the custom site I was talking about." SubWebOnly="FALSE" DisplayCategory="Winsmarts"> </Configuration>
</Template>
</Templates>

A few things that will jump out at you from the above XML file.

- ID must be greater than 10000, so your IDs don’t screw up SharePoint’s.
- You have a whole bunch of other control from the various possible elements, I think the above are self-explanatory.

Now go ahead, and do an iisreset, and try creating a site collection under SCAW (SharePoint Central Web Administration), or a site under a site collection through various means. You should see something like the following in the page that prompts you to create new sites:

Note that the text, the image, and everything else has been picked from WebTempSahil.xml.

Now how cool is that J!!? Now you can merrily create your custom site definitions, register them, and create them on a per-demand basis.

In further blog posts, I will cover various other aspects of Site Definitions. Until then, Rock On!!

Video Streaming in SharePoint 2007/Media Player in SharePoint 2007

http://csharptalk.blogspot.com/2008/09/video-streaming-in-sharepoint-2007media.html

The idea came that I need to do video streaming in SharePoint 2007, I did small research and found 2 ways to do such a thing:

Method1:

1. Add Content Editor Web Part into your page.
2. Edit the properties of the web part.
3. Click the “Source Editor”
4. Simply copy and paste this code:

<\OBJECT id="VIDEO" CLASSID="CLSID:6BF52A52-394A-11d3-B153-00C04F79FAA6" type="application/x-oleobject">
<\PARAM NAME="URL" VALUE="http://sitename:42875/Documents/CocaCola-Jump.wmv">
<\PARAM NAME="animationatStart" VALUE="true">
<\PARAM NAME="transparentatStart" VALUE="true">
<\PARAM NAME="SendPlayStateChangeEvents" VALUE="True">
<\PARAM NAME="AutoStart" VALUE="false">
<\PARAM name="uiMode" value="mini">
<\PARAM name="AutoRewind" value="true">
<\param name=enableContextMenu value=false>
<\OBJECT>
Explanation: the idea behind this code is simply you create an object with a classid that indicates windows media player version 7. This code will create an embedded instance of windows media player and plays the video you uploaded in your document library.
Method2: Media Player Web Part

It’s a readymade media player web part that runs an instance of windows media player and plays all the type of files the player can play, and the credit for this web part goes to the owner who built it as you will see in the link.

1. Download the web part from this link:http://www.sharepointblogs.com/files/folders/ajp/entry3059.aspx
2. Copy the mediaplayerwebpart.dll to the bin folder of your MOSS web site.
3. Open the web.config of your site and add SafeControl entry like this: <\SafeControl Assembly="MediaPlayerWebPart, version=1.0.0.0, Culture=neutral, PublicKeyToken=4907dffeafb11512" Namespace="NFWebParts" TypeName="*" Safe="True" />
4. Inside your site, go to Site Actions > Site Settings > Modify All Site Settings > Gallery > Web Parts
5. Click New > select the media player web part > populate gallery
6. Now your web part is there, you can use it in any page and play videos
Hope this article was useful for all.

SharePoint kill process

En la base de datos master, abrir New query. Ejecutar lo siguiente:

SELECT spid from master..sysprocesses
WHERE blocked = 0
AND spid in (select blocked from master..sysprocesses)

Ver a qué proceso corresponde, ejecutar lo siguiente:

SP_WHO2

Para matar algun proceso, ejecutar kill + SPID. Ejemplo:
kill 189
kill 120