First let’s prepare. We’ll need two icons for the button – a 16×16 and 32×32 version. You can use samples below:

Now let’s open the site with SharePoint Designer and upload the two images to the site (either images folder in SharePoint designer or any document/picture library).

Next in SharePoint Designer select the Lists and Libraries option under Navigation and select the list you need to add your custom button to.

With the list open in SharePoint designer, click the Custom action button and select New Form Ribbon.

In the popup window fill in the name and if needed description of your new button:

In the Select type of action select Navigate to url and enter the following in the box below:

javascript:var d=document.location.href.replace(‘&IsDlg=1′,”);window.open(d);

Now all that remains is to select images for the button in the last section:

And leave the rest of settings to default.

Now you should see your newly created custom action in the Custom actions section

In some cases SharePoint designer won’t add this. In that case set the Navigate to url to some valid url (http://www.sharepointboris.net ), complete the process, then edit the custom action and replace link with your JavaScript.

Without any further ado you can immediately see results:

Why you might need a popout you might ask? simple… for bookmarking, linking,…

When? On 26th and 27th November 2012

Why? Good presentations, lots of knowlege to gain, lots of interesting topics.

Who? MVP, MVP, MVP, MVP and more and lots of other great presenters. I’ll be presenting thre this year again too.

Who again? Returning legends like Zlatan Džinič, Claudio Brotto, Toni Frankola, Michael Noel, Joel Oleson, Paul Swider, local heroes like me, Dejan Sarka, Uroš Žunič, Robi Vončina, along with new special guests. See us all here.

What about? Topics are still being selected. I’ still haven’t decided what my topic would be. Should it be “Enhancing SharePoint through JavaScript”? Or “Silverlight and SharePoint Reloaded”? Or perhaps Workflows in SharePoint. Maybe you can help me decide. I will also take the chance to unveil the successor of SPCD, which is already being tested.

Kranjska where? In Hotel Kompas in Kranjska Gora in Slovenija. More info about hotel here. How to find the hotel? You can check directions on hotel’s website or find the hotel on Bing Maps.

More information and reservations: Check Organizer’s (Kompas XNet) website.

<a href="http://your-sharepoint-url-address">your link name</a>

to

<a onclick="NewItem2(event, this.href); return false;" href="http://your-sharepoint-url-address">your link name</a>

This code ofcourse works in SharePoint designer and other areas in SharePoint where you have SP.UI loaded. It also doesn’t work in rich text fields in SharePoint as the JavaScript gets filtered out.

But after running the bookmarklet from favorites or favorites bar

Right click again and the desired options are there

The bookmarklet is available in my JavaScripts Library.

How to "install" the bookmarklet?

1. Navigate to my JavaScripts Library page.

2. Under Bookmarklets you will find a link. Drag it to your browser’s favorites bar or favorites.

How to use the script:

1. Open SharePoint List settings page. In this example we’ll open a Contacts list’s settings. Pay attention to the "Columns" table

2. Click the link you’ve added to your bookmarks:

3. See your Columns table again

This just temporarily modifies the page. The column will disappear with the next page refresh. But meanwhile you can even copy-paste.

I’ve tested it with IE 9, FireFox and Chrome.

If they were set to manual start after clicking the Start button on the workflow initiation form, nothing would happen.

In SharePoint logs I’d find the following message:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at System.ThrowHelper.ThrowKeyNotFoundException()     at System.Collections.Generic.Dictionary`2.get_Item(TKey key)     at Microsoft.SharePoint.Workflow.SPWorkflowManager.IsConfigForSite(SPSite site)     at Microsoft.SharePoint.Workflow.SPWorkflowManager.GetWorkflowConfurationSection(SPSite site, String section)     at Microsoft.SharePoint.Workflow.SPWinOeHostServices.EnsurePluggableServices(SPSite site, SPWorkflowExternalDataExchangeServiceCollection services, ExternalDataExchangeService existingServices)     at Microsoft.SharePoint.Workflow.SPWinOeHostServices..ctor(SPSite site, SPWeb web, SPWorkflowManager manager, SPWorkflowEngine engine)     --- End of inner exception stack trace ---     at System.RuntimeMethodHandle._InvokeConstructor(Object[] args, SignatureStruct& signature, IntPtr declaringType)     at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)     at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)     at Microsoft.SharePoint.Workflow.SPWorkflowManager.LoadPluggableClass(String classname, String assembly, Object[] parameters)     at Microsoft.SharePoint.Workflow.SPWorkflowManager.GetService(SPWorkflowAssociation association, SPWorkflowEngine engine)     at Microsoft.SharePointWorkflow.SPWorkflowManager.RunWorkflowElev(SPWorkflow workflow, Collection`1 events, SPWorkflowRunOptionsInternal runOptions)

On another site collection on the same server workflows were working normally.

I’ve tried to resolve the problem with the solution described here but unfortunately it didn’t work.

At the end what worked for me was to re-enable workflows on site.

In Central Administration select Application Management and Manage web applications

Next select the failing Web application

Now click arrow under General Settings in the ribbon and select Workflow

Select No for "Enable user-defined workflows…" and click OK.

Now reopen the Workflow settings dialog by clicking on General Settings –> Workflow again

and select Yes, to re-enable user defined workflows.

Confirm your selection by clicking on the OK button.

This got my workflows up and running again.

There is an update available – on the same place – CodePlex. The project is still a small console application.

How to use it? Run it and follow instructions.

Click here to download the latest release.

Now thanks to my friend’s solution, you can tell them to go see for themselves. Robi Vončina has prepared a solution to list AD group members directly on your SharePoint site. It’s a nice solution to see who’s messing around your site.

The solution can be found on CodePlex.

On the failing server open Server Manager, and under Roles select Application server. You will most probably find quite a lot of DCOM errors. Open one of those errors to see for which user and for which service the authentication is failing. In the open window copy the GUID of the failing service. It will help you identify the service.

Next open registry editor and select the root node. In Edit menu select Find, paste the GUID and click Find next.

You can find the service name in one of the registry’s values (as seen on the screenshot below, in my case it was IIS WAMREG).

Leave the registry editor open (you might still need it).

Next in Start menu under Administrative tools click Component Services. Expand the Computers node and My Computer. Select DCOM Confing. Now locate the service you identified in your registry, right click it and select Properties.

In the open dialog select Security tab and in the Launch and activation permissions group click the Edit button.

If you have this entire tab grayed out, you need to do the following (outlined in the gray, otherwise skip the gray part below):

In registry editor (which I hope you still have open), right click the node you found and select Permissions Click Advanced and select the Owner tab. Change the owner to the account you’re logged on or to the administrators group (which I presume your account is in) Click Apply and in the permissions dialog also give same user/group full control Now you should close and reopen Component services and find the DCOM service.

In the permissions dialog for the service grant the failing user (or group the account is in) Local Launch and Local Activation permissions. And in case the event log says it is failing remote launch, grant the user remote launch and service also.

Confirm all the changes and close registry editor and Component services window.

Update: If you use Microsoft Office 2010, you have to use other fix:

http://support.microsoft.com/kb/841215