Removing missing feature dependency on a STP file

When you have a missing feature in your SharePoint that refuses to go away inspite of deactivating it as well as uninstalling it by force, a site template (.stp) that depends on - fails to work... so how do you make this work?

Well, you have to manually delete the feature id reference from the manifest.xml that is present in the .stp file. As you know, .stp files are nothing but .cab (cabinet) files, so all you need to do is rename, change the extension, open in WinRar or any such cabinet handling program, extract the files out, modify the manifest.xml file  (just delete the xml tag that points to that missing feature) and then when you have to place it back - you have to be careful!

You have to make sure there are no sub folders that get created!

Check my another post on how you can use the makecab.exe utility to recreate the cabinet file. Once you create that, then you need to rename it back to .stp, upload it back to the Site Template Gallery - and start using it!!!

Comments

Post a Comment

Popular posts from this blog

Using External Content Types with Stored Procedures with Input Parameters

Image
You must have tried External Content Types - the exciting new feature in SharePoint 2010 to connect to an external SQL table and provide a list where it lists, creates, updates data straight into the SQL table. People always wonder, how do you get a ECT to work with a Stored Procedure, one that has input parameters. You could do it this way... Step 1: In your SharePoint Designer 2010, create a new external content type Step 2: Connect to your SQL Server and then make sure you see the Routines (your stored procedures must be listed here) Step 3: Rt Click on the Stored Procedure name and create operations for "Read Item" and "Read List" - both are required for the External Content Type's SharePoint list to be created. During both these wizards, in the Input Parameters, your SP's Input Parameter will be listed. Here, you need to create a filter, which sends out it's value to the SP's filter. For example, if your SP's Input Parameter is @Emp
Read more

NAV 2009 Issues in Role Tailored Client

Image
Role tailored client issue Changing stored procedure to 64 bit in NAV 2009 Did install Dynamics NAV 2009 on windows 2008 64 bit / Windows 7 65 bit. When trying to connect to the database in classic client I got this error. The following SQL server error or errors occurred: 17750,“42000”,[Microsoft][ODBC SQL Server Driver][SQL Server]Could not load the DLL C:\Program Files (x86)\Microsoft Dynamics NAV\60\Database\xp_ndo.dll, or one of the DLLs it references. Reason: 193(failed to retrieve text for this error. Reason: 15100). SQL: INSERT INTO [#$ndo$groups] {CALL [master]..[xp_ndo_enumusergroups](?,?)} The reason for this error is that the installed xp_ndo.dll is 32 bit and not 64 bit. My solution was simple to replace xp_ndo.dll with the 64 bit version. 1. Stop SQL server 2. Copy \\vedfssrv01\DynamicsNAV2009\W1\DVD\Sql_esp\x64\ xp_ndo_x64.dll to C:\Program Files (x86)\Microsoft Dynamics NAV\60\Database 3. Rename existing xp_ndo.dll to xp_ndo_x32.dll 4. Rename xp
Read more