Cannot uninstall Language Pack 0 because it is not deployed

SharePoint 2013 is really a good product w.r.t. functionality and awesome GUI to work with! But today’s article is based on the error that I faced while updating the solution.

IMP NOTE:

If you find a different solution, please report it as a comment to this post. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.

Here is the error message:

Cannot uninstall Language Pack 0 because it is not deployed when attempting to uninstall-spsolution

One thing we always need to understand is the logic would be same for the functionality irrespective of which SharePoint version you are working!

I have written one article in the past for SP2010 based on the same concept: http://sharepointknowledgebase.blogspot.com/2013/11/solution-deployment-stuck-on-deploying.html and today I am going to elaborate more on the same theory as I have resolved the above mentioned error message with the same funda.

What’s that funda? – Here we go:

If you are facing this error message then I would suggest checking the status of your solution in central administration. How to check this? Here are the details:

o   Central Administration

o   System Settings

o   Manage Farm Solutions

o   It will open the solution management

o   Here you can check the status of your solution

If your solution is showing updating, deploying or retracting status then first and top most check that you need to verify the status of your TIMER JOB across all WFE’s.  How to check this? – Here are the details:

o   Login to your web front end (WFE)

o   Start

o   Run

o   Type “services.msc” and hit enter

o   It will open the services console

o   Click on any service and press S

o   It will directly show you the SharePoint Services

o   Second service will be SharePoint Timer Service

o   Check the status across all your servers

Two outcomes will be there:

1.   Timer service will be stopped one of the server:

If this is the case then start the timer job on that specific server and check the results by executing the commands that you are using.

2.   Timer service is started on all the servers:

If this is the case then restart all the SharePoint Timer Services across all servers. Once this done then execute the commands that you are doing and check the results

If you are looking out command reference then please refer this link in which I have given the reference of add solution as well as update solution:

http://sharepointknowledgebase.blogspot.com/2013/11/solution-deployment-stuck-on-deploying.html

Details notes:

Add-SPSolution

Add-SPSolution -LiteralPath c:\nameofyoursolution.wsp

Install-SPSolution

Install-SPSolution -Identity nameofyoursolution.wsp –GACDeployment

Uninstall-SPSolution

Uninstall-SPSolution -Identity nameofyoursolution.wsp

Remove-SPSolution

Remove-SPSolution -Identity nameofyoursolution.wsp

Update-SPSolution

Update-SPSolution -Identity nameofyoursolution.wsp -LiteralPath c:\nameofyoursolution.wsp -GACDeployment

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.

Product Applies To:

o   SharePoint 2013

o   SharePoint 2010

o   SharePoint 2007

No Save Site As Template SharePoint 2013

‘Save site as template’ is a pretty useful feature which has been carried out from SharePoint 2007 version and it’s still there in SharePoint 2013. Useful functionality when we want to transfer the site structure from one location to another with small data as it has a size limitation. I don’t want to discuss about size limitation in this article as it altogether a different issue and needs a separate set of troubleshooting.

In the past, I have written some useful articles to share the knowledge based on the same topic. Please find the following references:

Mystery of save site as template in SharePoint 2010

http://sharepointknowledgebase.blogspot.com/2012/06/mystery-of-save-site-as-template.html

Save site as template using SharePoint Designer 2010

http://sharepointknowledgebase.blogspot.com/2012/01/saving-site-as-template.html

Save site as template is missing

http://sharepointknowledgebase.blogspot.com/2011/07/save-site-as-template-is-missing.html

How to activate the site template in the solution gallery

http://sharepointknowledgebase.blogspot.com/2012/01/activating-site-template-in-solution.html

Unexpected error has occurred while saving the site as template

http://sharepointknowledgebase.blogspot.com/2013/11/unable-to-save-site-as-template.html

IMP NOTE:
If you find a different solution, please report it as a comment to this post. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.

Problem description:

One user has reported an incident that he is not able to save the site as template. – That’s a plain description. Previously I thought that he might be facing some problem/error while saving the site as template but further probing revealed the fact that he is not able to see the option “save site as template”.

Error message:

There is no error message here as the link is missing so NA.

Let me tell you some facts which are useful to understand the logic behind this-

It’s been pretty clear that if you have the publishing feature activated on your site collection then ‘save site as template’ won’t be there.

Reference:

SharePoint Publishing feature does not support "Save Site as Template" option

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

But there is a tweak here for SharePoint 2007 and SharePoint 2010 versions as people can get this functionality / access that page by appending http://sitename/_layouts/savetmpl.aspx !

But this is a closed loop in SharePoint 2013 as you cannot browse that page by making the changes in the URL.

But after when I realized that it’s not possible using GUI so i started exploring SharePoint Designer 2013 and found the solution.

Resolution / Here are the complete details:

1.   Open the SharePoint Designer 2013

2.   Top Ribbon

3.   You will see the ‘site options’

4.   Click on it

5.   You will see 4 different tabs (Parameters, language, advanced and navigation)

6.   Click on parameters tab and you will see the option of “SaveSiteAsTemplateEnabled” is set to False

7.   Select the option ->click on Modify

8.   Set it true

9.   Click on Apply and OK

Please refer the following screenshot for better clarity.

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.

Product Applies To:

o   SharePoint 2013

Disabled accounts in AD show up in SharePoint as active profiles

Problem Description:

If the proper filer is not applied in import connections then it can lead to hundreds of unwanted / disabled profile in ssp database. Sometimes due to IT audits we want to get rid of those profiles from SharePoint.

Product Applies:

1.    MOSS2007 (Microsoft Office SharePoint Server 2007)

2.    WSS3.0 Windows SharePoint Services 3.0)

Error Message: N/A

What exactly I did? How exactly I configured and came to know about the issue?

1.    In AD, I have created lots of user and disabled few of them.

2.    Configured SSP to import user profile by using the default filter

(&(objectCategory=person)(objectClass=user).

3.    That’s it-Problem started and found lots of profiles in view user profile.

Resolution:

·         At first apply filter (&(objectCategory=person)(objectClass=user)(

!(userAccountControl:1.2.840.113556.1.4.803:=2))) to just import active profiles in

connection.

·         Run full profile import three times back to back.

·         After that you will find users in view user profile > Profile Missing from import.

·         You can manually delete these unwanted profile or wait till clean up job delete them.

If you have any queries/questions regarding the above mentioned information then please let me know, Thank you.

Integrating AD RMS and SharePoint

By preparing SharePoint infrastructure to store IRM-protected documents, where the protection capabilities are embedded in the document, it will make these protected documents unsearchable since they cannot be tagged or indexed while the document contents are encrypted.  This is no longer the case with AD RMS and SharePoint 2007 since the IRM policies are only applied when the documents are downloaded and they are stored unencrypted in the libraries, hence making them index able and later searchable.

With SharePoint, IRM protection is available for files that are located in document libraries. SharePoint uses the access control list (ACL) on the library or list to determine the permissions that it applies to a document for the user downloading it. Protection includes the following options with integration of SharePoint with AD RMS:

·         Whether or not users can print documents that are rights managed.

·         Whether the user can run Microsoft Visual Basic for Applications (VBA) and other custom code in the file.

·         The number of days for which the license is valid; after the specified number of days, the license expires and the user must download the file again from the document library.

·         Whether to let users upload file types that do not support IRM.

·         Optionally, the date to stop restricting permissions to the document library; after the specified date passes, Office SharePoint Server removes all rights-management restrictions from the documents in the library.

There are basically three simple steps to integrate AD RMS with SharePoint 2007 as follows:

(Notes: If we are using Windows Server 2008, as it already includes AD RMS client, there is no need to install a separate Windows RMS client as in Windows Server 2003)

Add permissions for the SharePoint server to the AD RMS certification pipeline

·         Log on to the AD RMS server as a local administrator

·         Click Start, and then click Computer

·         Navigate to c:\Inetpub\wwwroot\_wmcs\Certification

·         Right-click ServerCertification.asmx, click Properties, and then click the Security tab

·         Click Advanced, click Edit, select the Include inheritable permissions from this object's parent check box, and then click OK two times

·         Click Edit

·         Click Add

·         Click Object Types, select the Computers check box, and then click OK

·         Type the name of the SharePoint web front-end server, and then click OK twice.

·         Repeat the above three steps for other web front-end servers

·         Click OK to close the ServerCertification.asmx Properties sheet. By default the Read & Execute and the Read permissions are configured

·         Reset IIS

Specify RMS server location in SharePoint using Central Administration

·         Open SharePoint 3.0 Central Administration site

·         Click Operations, and then click Information Rights Management

·         Select Use the default RMS server specified in Active Directory.

·         Click OK

Before installation of Windows Rights Management Services Client.

After installation of Windows Rights Management Services Client

Note:  Ensure that Windows Rights Management Services Client (WindowsRightsManagementServicesSP2-KB917275-Client-ENU-X64.exe) is installed on the server. It is very small installation and takes less time. It will come by default with Windows server 2008.

Enable IRM policy to control access to the contents of a document library

1.       Open a SharePoint site and go to the document library where we want to enable the IRM policy

2.       Click Settings, and then click Document Library Settings

3.       Under Permissions and Management, click Information Rights Management

4.       Select the Restrict permission to documents in this library on download check box

5.       In the Permissions policy title box, type in the policy title

6.       In the Permission policy description box, type in the policy description

7.       Click OK

SharePoint will now automatically apply AD RMS rights to the document when it is downloaded from the document library. These rights are determined by the user permission for that library. For example, a user who has Read permission will not be able to modify the document when it is downloaded from the document library.

Notes: When AD RMS protected documents (created outside SharePoint environment) are uploaded to the library with IRM policy enabled, the original document protection policy will supersede the library protection policy when those documents are downloaded or accessed by users.  AD RMS end-to-end security prevents SharePoint from decrypting documents created outside of the SharePoint environment, hence applying the SharePoint library IRM policy to those documents.

Duplicate items appear when viewing items in Datasheet view in SharePoint

ISSUE:

Duplicate items appear when viewing items in Datasheet view in SharePoint.  This also happens when using the Export to Spreadsheet (Excel).  If duplicates appear in Datasheet view, they will also appear during Export to Spreadsheet and vice versa.

DESCRIPTION:

The list has got versioning switched off, and views fine in standard list view. However, when you switch to either datasheet view or Excel Export it shows the same rows up to three times in sequential rows.

WORAROUND/SOLUTION:

The affected lists have a REQUIRED lookup field which allows multiple values.

If you have a view that does NOT include this field and it is either a datasheet or you "Switch to Datasheet" then datasheet shows duplicate items depending on how many multi-values are selected. 

Our work-around was to create a specific Datasheet view with the field included.  The multi-value field does not show in datasheet, because multi-value lookup fields don't seem to work in datasheet.  However, it's important to include the field in the view to avoid duplicates.

Unfortunately, if you have a view that does not include the field and then "Switch to Datasheet" you will encounter the same problem.

The duplicates appear also when you try to Export to Excel.  If you have a view that would be affected by the "Switch to Datasheet" duplicates problem, when you try to Export to Excel, it will also appear.

Switching from SSRS Native Mode to SharePoint Integrated Mode

SharePoint integrated mode enables Reporting Services to integrate with the SharePoint(SP) databases and security model. These features become available when you configure a report server to run within a larger deployment of a SharePoint 3.0 product or technology.

In SP integrated mode, a report server must run within a SP server farm. A SP site provides the front-end access to report server content and operations with  all report processing and rendering. The advantage of integrated mode is a rich level of integration that allows you to access and manage report server content types using the application pages and data stores of a SP Web application.

Reports, data sources, and data models in a SP document library are stored as files in the SP content database for that SP document library. Files are stored in the .rdl, .rsds, and .smdl extensions.

Advantages of SharePoint Integrated Mode:

1)   Uniform UI to access reports – No need to access reports using SP and manage using the SSRS report manager. Everything will be done through SP UI.

2)   An ability to create and manage SSRS reports, SSRS data sources, and SSRS report models from the SP UI.

3)   Reports stored in the document libraries to enable versioning, workflow capabilities, collaboration, and document management features

4)   Shared Storage – Report Catalogs stored in the SP Content DBs

5)   Shared Security – No need to manage security at both SharePoint and Report Manager

6)   Inherited Governance Policy including SLA, Backup and Restore, Support, High Availability, Disaster Recovery, and Redundancy Policies

How to Switch from SSRS Native Mode to SharePoint Integrated Mode:

Steps to switch an existing SSRS server to SharePoint Integrated mode. This does not include any steps for migrating reports—we have to do them separately.

Switching to SSRS Integrated mode:

1.   Open SQL Reporting Services Configuration Manager on your SQL Server

·         Start

·         All Programs

·         Microsoft SQL Server 2008 R2

·         Configuration Tools

·         Reporting Services Configuration Manager

2.   Click on Databases, and note the current “Report Server Mode” is “Native”

3.   Select Change Database

4.   Select “Create a new report server database,” and click “Next”

5.   Enter your server name and credentials, and select “Next”

6.   Select a new “Database Name” and change “Report Server Mode” to “SharePoint Integrated Mode,” and click “Next”

7.   Enter authentication information, and click “Next”

8.   Verify Summary, and ensure “Report Server Mode” is set to SharePoint integrated

9.   Click next and ensure everything gives success status.

10.  In Reporting Services Configuration Manger, click on Web Service URL, and then click the URL link to open

11.  We should get an error that reads something like this:

12.   Reporting Services Error:

The report server has encountered a configuration error. If the report server is configured to use SharePoint integrated mode, verify that the server is joined to a SharePoint farm and that the Report Server service account has been granted access to the SharePoint farm. (rsServerConfigurationError)

13.  This error is expected, because we need to configure Reporting Services Integration in SharePoint.

14. Continue to next step.

15. Open up SharePoint Central Administration:

16. Go to “General Application Settings,” and click “Reporting Services Integration:”

17. Fill out “Report Server Web Service URL,” and your credentials:

18. Note that the Web Service URL should be what was specified in the Report Services Configuration Manager