08 September, 2013

Failed to start workflow. This server is not licensed + Nintex 2010 + SP2010

Problem description:
Some users reported that there are workflows with errors. This error occurs it looks like there is some issue with the license on a farm’s server.

Error message:
Failed to start workflow. This server is not licensed.



Probable Possibilities:
The server admins are incorrect; the Nintex licenses are not configured correctly.  If this were true, I would expect the error to occur more frequently, and not just when multiple workflows start.  For example, I would expect a workflow manual start to occasionally throw the error.

There is a problem with the way Nintex checks for licensing when workflows are distributed among front-end servers or queued up for execution.

Resolution:
If you are facing this error then request you to see the following thread and you will get the answers that you are looking for:

Thank you.

Product applies to:
1)   SharePoint Server 2010
2)   Nintex 2010
3)   SharePoint Foundation 2010

07 September, 2013

Your client does not support opening this list with Windows Explorer + IE10 + Windows 7



The title of this article itself suggesting the exact problem description, still here are the details:

The machine on which windows 7 is running along with internet explorer 10 throws an exception when you select “Open with Explorer” in SharePoint Server 2010.

Error Message#1: Your client does not support opening this list with Windows Explorer.

Error Message#2: We're having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again.

Another Symptom:
You try to map a network drive to the SharePoint Document Library and the operation fails with the following error:

The mapped network drive could not be created because the following error has occurred:
Access Denied. Before opening files in this location, you must first add the web site to your trusted sites list, browse to the web site, and select the option to login automatically.

Resolution:
Let me provide you some update on this / let me give you some good news as Microsoft has released a fix for this issue by means of KB: 2846960

Fix can be downloaded from: http://support.microsoft.com/kb/2846960

Millions thanks to Microsoft Windows team to find out the root cause behind this and comes up with a concrete fix.

Happy SharePoint to all of you…

How to Open PDF files in a web browser -SharePoint 2010

One of my clients has reported an issue that they are facing some problems while opening PDF files. Further probing reflected the fact that PDF files are opening but they are getting the prompt of Open, Save and Cancel. In contradictory, the actual requirement is PDF files has to open in browser mode directly rather than saving it to the desktop.


Problem description: SharePoint 2010 prompts to save PDF documents when opening.

Now the question is: Is there a way to open a PDF in a web browser, just like Office Web Apps?

This problem is quite annoying as every time we need to save the documents to the desktop!

Started my troubleshooting to explore the options in central administration
Let me tell you the fact why this is happening? In SharePoint 2010, browser handling has been classified into 2 types:
1)   Strict
2)   Permissive

So the next obvious question will be- what are the differences between these above mentioned types? Here are the details:

Strict specifies the MIME types which are not listed in a Web Application’s AllowedInlineDownloadedMimeTypes property (more on this in a bit) are forced to be downloaded.

Permissive specifies that the HTML and other content types which might contain script are allowed to be displayed directly in the browser. In other words, no matter what the type of content, if it lives within SharePoint, the file will open in your browser.

By default, the option is strict in Central administration so that’s why getting prompt is quite obvious.

Resolution#1 / now the question is how to change this?

1)   Open the central administration
2)   Application management
3)   Under web applications- Manage web applications
4)   Select the web application for which you want to change the settings
5)   General Settings (Top-Ribbon section)
6)   This will be open web application general settings
7)   There is a section named as ‘Browser File Handling’
8)   You will see two radio buttons as Strict and Permissive
9)   Change it to Permissive and Click OK

 No needs to do any iisreset so please go ahead and check the results!

-You should be able to open the PDF files directly in browser-

Resolution#2 – Same functionality as Resolution1, only thing is by means of Power Shell:
$webApp = Get-SPWebApplication http://webapplication_URL
$webApp.BrowserFileHandling = "permissive"
$webApp.update()

If you have some security concerns and don’t want to change the option from strict to permissive then here is the resolution:

By means of Powershell:
[System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.SharePoint”)
$webapp = [Microsoft.SharePoint.Administration.SPWebApplication]::Lookup(“http://web application_URL”)
If ($webApp.AllowedInlineDownloadedMimeTypes -notcontains “application/pdf”)
{
Write-Host -ForegroundColor White “Adding Pdf MIME Type…”
$webApp.AllowedInlineDownloadedMimeTypes.Add(“application/pdf”)
$webApp.Update()
Write-Host -ForegroundColor White “Added and saved.”
} Else {
Write-Host -ForegroundColor White “Pdf MIME type is already added.”
}

Now your PDF documents will be displayed in the browser even if Browser File Handling is set to Strict.

One last point, in fact important point is you may face the problem with the list or site templates. How? – We are all aware that site as well as list/libraries can be saved as templates to transfer from one location to another.

I would like to thanks to Nico Martens for publishing this article for all of us:

Thank you.

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues.

Happy SharePoint to all of you…

Product Applies to:
1)   SharePoint Server 2010
2)   SharePoint Foundation 2010

References:
Open PDF files in the browser from SharePoint: http://www.youtube.com/watch?v=ULfIEmoq-F0

05 September, 2013

Installing Windows 2012 from Windows 7 (32-bit) failed.

Problem:  The version of this file is not compatible with the version of windows you’re running. Check your computer system information to see whether you need an x86 (32-bit) or x64 (64-bit) versions of the program and then contact the software publisher. 



Background: I was trying to install windows 2012 on my Notebook the Dell Latitude Series E6230.   

However realized I came with the 32-bit Windows 7 operating system. As any normal IT Pro first I tried to run the setup.exe and then got the above error. Sooner or later I realized that 32 bit version O.S doesn't support 64 bit versions application. I was not having any DVD or CD drive where I can burn ISO of Windows 2012.

Resolution: I tried a new method; by converting my USB flash drive to bootable flash drive using Windows 7 USB DVD Download Tool downloaded from MS store for free.

You just need to run the set-up.exe and rest the tool do everything for you.
Go to BIOS by pressing F10 or F12 and boot your PC from the Flash/Thumb Drive your set-up will automatically launch.

Thanks for Mr Bob hunt for his reference below:


Other references:


Applies to: Windows 7, Windows Server 2008, and Windows Server 2012.

Unable to create a secure URL cache + site could not be created + Group cannot be found + Verify that the file exists in the Layouts directory - SharePoint 2010

Recently I worked on language packs requirement and faced some problems. I would like to share some reviews with all of you so that it would be beneficial to all of you. One of my business owner has requested me to install the language packs (French and German) so we have downloaded the language packs from the following links:

Plain language pack

Language pack with service pack1

So by this way we have successfully installed the language packs on every server of the farm i.e. on every app as well as on every WFE.

Note: Make sure you run the psconfig on every server of the farm.
till this point, we are good without any problems.

But the problem started after this- We start creating the site collection by using this installed language packs example French! and it failed with the following ERROR MESSAGE:

The site /sites/French could not be created.  The following exception occurred: Error adding custom access permissions. Group cannot be found. 
   at Microsoft.SharePoint.SPGroup.InitMember() 
at Microsoft.SharePoint.SPGroup..ctor(SPWeb web, SPSecurableObject scopeSPUser user, String GroupName, Object[,] arrGroupsData, UInt32 index, Int32 iByParamId, SPGroupCollectionType groupCollectionType)
at Microsoft.SharePoint.SPGroupCollection.get_Item(String name) 
 at amolsharepoint.CustomPermission.Features.amolspCustomPermission.amolsharepointCustomPermissionEventReceiver.FeatureActivated(SPFeatureReceiverProperties properties).

So the problem is: not able to create the site collection

Tried creating the site collection by means of central administration as well as by PowerShell but got the same error as mentioned above.

From the error message, it’s quite clear that the problem is with specific solution/event receiver. Let me tell you that we have custom permissions in our environment and separate solution for that.

Involved developer and reviewed the specific solution and he has stated that the solution has been created & deployed with respect to English locale only so we need to make provisions for the other language packs.

Developer has made that provision and we deployed the solution again!

Tried creating the site again and it works this time.

So now one issue has been resolved regarding site creation! After this, we tried browsing the site collection and got the following error:

Unable to create a secure URL cache "1036/styles/customCOREV10_0020.CSS", file not found. Verify that the file exists in the Layouts directory.

From the error message, its quite clear what will be the next action plan!

What we did?

Simple copy the above mentioned .css file from english folder i.e. 1033 to French folder i.e. 1036.

That’s it- Try browsing the site now and it will open without any issues…

Thank you.

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you once again.

Product applies to:
1)   SharePoint Server 2010
2)   SharePoint Foundation 2010

References:
Language Packs for SharePoint Server 2013
http://www.microsoft.com/en-in/download/details.aspx?id=37140

Language packs in SharePoint Server 2013
http://technet.microsoft.com/en-us/library/ff463597.aspx

Language Packs for SharePoint Foundation 2013
http://www.microsoft.com/en-us/download/details.aspx?id=35492