none
Cannot Save Site as Template in SharePoint 2010

    Question

  • Hi folks, we have quite a problem and hopefuly you can help us out.

    We had SharePoint 2007 server (SPS) with SQL 2005 SP3 running great with HelpDesk and Asset Tracking Management templates and then.... SharePoint 2010 came out.  In order to prevent nightmares we decided to setup a whole new server with Windows 2008 R2 and SQL 2008 R2 and then just simply move sites into new SharePoint 2010 server (SPSTEST).

    Well that did not work that great because apparently saving templates in 2007 and in 2010 are two different things now due to their extension. So someone suggested, just upgrade your current SharePoint 2007 to SharePoint 2010 and then either export or save as template or backup and restore your sites. So we did an In-Place upgrade to SharePoint 2010. Hooray! HelpDesk and Asset Tracking Mgmt templates worked fine after upgrade to SharePoint 2010 or at least appear to so far. So all we need to do now is move them over to the new server (SPSTEST) along with data/content.

    Well that proved to be a nightmare as well. Now we have two SharePoint 2010 servers and we cant find a way to move those two templates with its data. We tried backup and restore which works fine for everything but those two templates...we get the following error when we try to access them on our new SHarePoint server (SPSTEST):

     
    An unexpected error has occurred.

     

    Troubleshoot issues with Microsoft SharePoint Foundation.

    Correlation ID: 3ecd6e75-32d7-489a-809d-ae05c4b6d480

    Date and Time: 5/24/2010 2:02:20 PM

    If we try to go and Save Site as Template we pretty much same error on our upgraded SharePoint 2010 server (SPS).

    So I guess our question is how to get those templates and its content over to our new SharePoint 2010 box?

    Thursday, May 27, 2010 6:26 PM

Answers

  • The reason moving sites between farms is difficult is because farms can have different custom solutions, features, and templates installed.

    You need to ensure that your farms are 100% identical in order to backup/export  or restore/import a site or list.   This means make sure you have the same features activated at the farm, web, site collection and site level.   If you have SharePoint 2010 Enterprise in one farm and SharePoint 2010 standard in another you will have major problems moving content.

    If you installed any custom solution packages you need to install them on the new farm prior to restoring the sites or lists.

    Your specific error for feature '75a0fea7-625d-4b31-be9e-24cee53d0d72'  is caused by not having the ApplicationTemplateCore.wsp solution package installed in your farm.  Here is the catch...  that solution package is part of a template pack that Microsoft released for SharePoint 2007.   As far as I am aware that has not been updated for SharePoint 2010 yet.   You could try installing the ApplicationTemplateCore.wsp in your 2010 dev or test environment to see if you can get things to work.

     


    If you get your question answered, please come back and mark the reply as an answer.  
    If you are helped by an answer to someone else's question, please mark it as helpful.
    Mike Hacker | Blog: http://mphacker.spaces.live.com 

    • Marked as answer by Zgembo Friday, June 11, 2010 1:06 PM
    Friday, June 11, 2010 12:13 AM

All replies

  • Nobody?
    Friday, May 28, 2010 12:32 PM
  • I have a similar problem here. Newly installed sharepoint 2008 server, and i cannot save any templates. An unexpected error occurred. If i mage a new site collection the same teplate function works like a charm. I have checked the permissions and i can not fin anything wrong. I really need help here. I need this templates to be at the root site.

     

     
    An unexpected error has occurred.

    Monday, May 31, 2010 7:43 AM
  • Can you get all the entries with Correlation ID 3ecd6e75-32d7-489a-809d-ae05c4b6d480 from the ULS log files from 5/24/2010 2:02:20 PM? It's difficult to diagnose based on the info given here.

    Thanks,

    kims

    Wednesday, June 02, 2010 12:36 AM
  • I got the error as well. Here's the relevant info from the logs:

    w3wp.exe (0x04BC)                        0x0F1C SharePoint Foundation          Runtime                        tkau Unexpected System.InvalidOperationException: Error copying temporary solution file to solutions gallery: _catalogs/solutions/mysite.wsp    at Microsoft.SharePoint.SPSolutionExporter.ExportWebToGallery(SPWeb web, String solutionFileName, String title, String description, ExportMode exportMode, Boolean includeContent, String workflowTemplateName, String destinationListUrl)     at Microsoft.SharePoint.SPSolutionExporter.ExportWebToGallery(SPWeb web, String solutionFileName, String title, String description, ExportMode exportMode, Boolean includeContent)     at Microsoft.SharePoint.ApplicationPages.SaveAsTemplatePage.BtnSaveAsTemplate_Click(Object sender, EventArgs e)     at System.Web.UI.WebControls.Button.OnClick(EventArgs e)     at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)... d9279191-744d-4722-bad0-0bf921739853


    Studying system development. I always give credit to helpful posts!
    • Proposed as answer by David Dean Tuesday, January 04, 2011 5:22 PM
    • Unproposed as answer by David Dean Tuesday, June 14, 2011 5:28 PM
    Wednesday, June 02, 2010 7:44 AM
  • We just ran into the same problem.

    Were do I find the ULS-logfile?

    Wednesday, June 02, 2010 12:13 PM
  • The site is actually saved as a template in spite of the error.
    But the new template has to be activated manually.

    Is this the same behavior for you guys too?

    Wednesday, June 02, 2010 2:43 PM
  • Yep, where can we find the ULS log file?

    Also, I think I already know the answer to this question but here it goes:

    Can I save a list or site as a template from http://server1:12000/Inventory/ and use it on http://server2:33000/Inventory/?

    Different server name or path does not matter, right?

    Thursday, June 03, 2010 12:54 PM
  • If the site is saved, and you can manually activate wsp. Were you able to create a site from it (wether sub site or root site). If you can attach wsp, it would also help.

    Ghania,

    Msft.

     

     

    Thursday, June 03, 2010 4:08 PM
  • > where can we find the ULS log file?

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS

    The files are named: 

    yourservername-date-time.log

    TESTSERVER-20100603-0945.log


    Mike Smith TechTrainingNotes.blogspot.com
    Thursday, June 03, 2010 5:16 PM
  • I gave up and manually moved and configured each list using stsadm utility. I ran into a problem with inserting data into Person/Group field, how can I do this? Let's say in Datasheet View, how can I insert data from another list by just pasting it like in Excel?

    • Proposed as answer by holzmann Thursday, June 10, 2010 3:37 PM
    Thursday, June 03, 2010 8:02 PM
  • I am not sure if this issue has been resolved yet.

    I am in the same boat unfortunately I do not have access to the servers in the farm, but has anybody tried the free SharePoint Migration tool from Xavor at the following url  http://www.xavor.com/whatwedo/solutions/Sharepoint2010.aspx

    It seems that this tool will migrate a site from a previous version to SharePoint 2010.

    Just need to have access to install software on the server and then drag and drop.

    Thursday, June 10, 2010 3:42 PM
  • This is part of SharePoint that I really hate, why do they make it so hard to move things between different servers. You see Save as Template option or Export Site or List and you think...oh ok here is a great option but no, it does not freaking work that way.

    I cant even move custom list from one SharePoint 2010 to another SharePoint 2010. Custom is overstatement, its just a list with fields added using List Settings options. I mean how custom can it be if its build using their own options within SharePoint????? If I went out of my way and used java here, php there, added some non-sense code and math magic..then I would understand...but this makes no sense and its just plain STUPID!!!!

    if I export a site that has my custom lists using Central Admin -> Backup and Restore -> Export a site or list, and then go to my other server and then try to upload that export.cmp file using stsadm.exe tool...shouln't that work? I get the following error:

     Error: Feature '75a0fea7-625d-4b31-be9e-24cee53d0d72' for list template '1009' is not installed in this farm.  The operation could not be completed.

    Any ideas? My brain is fried!

    Thursday, June 10, 2010 6:26 PM
  • The reason moving sites between farms is difficult is because farms can have different custom solutions, features, and templates installed.

    You need to ensure that your farms are 100% identical in order to backup/export  or restore/import a site or list.   This means make sure you have the same features activated at the farm, web, site collection and site level.   If you have SharePoint 2010 Enterprise in one farm and SharePoint 2010 standard in another you will have major problems moving content.

    If you installed any custom solution packages you need to install them on the new farm prior to restoring the sites or lists.

    Your specific error for feature '75a0fea7-625d-4b31-be9e-24cee53d0d72'  is caused by not having the ApplicationTemplateCore.wsp solution package installed in your farm.  Here is the catch...  that solution package is part of a template pack that Microsoft released for SharePoint 2007.   As far as I am aware that has not been updated for SharePoint 2010 yet.   You could try installing the ApplicationTemplateCore.wsp in your 2010 dev or test environment to see if you can get things to work.

     


    If you get your question answered, please come back and mark the reply as an answer.  
    If you are helped by an answer to someone else's question, please mark it as helpful.
    Mike Hacker | Blog: http://mphacker.spaces.live.com 

    • Marked as answer by Zgembo Friday, June 11, 2010 1:06 PM
    Friday, June 11, 2010 12:13 AM
  • I've got the same problem. We've migrated moss2007 to sp2010. The database attach method.
    Some solutions didn't work anymore. After installing the ApplicationTemplateCore.wsp the problems seems to be disappeared.

    We want to use our old template (created in Moss2007), but the template is not visible in the list of templates when creating a new one.  I tried to save an old moss-site as a template, but got an error. Even when i create a new template, based on default settings and features, i can't save it as a template in sp2010. I also get the error:

    Error

    Error exporting the site field named "Asset".

     

    Troubleshoot issues with Microsoft SharePoint Foundation.

    Correlation ID: 2c83085a-c441-4761-9dd4-91bec96378ba

    Date and Time: 15-6-2010 9:33:25

    ===============================================

     First I thought it was one of the fantastic 40 templates that causes the problems, but i can't find a relation between the Solutions and my latest template.

    Anybody an idea?

    tnx,

    Robbert

    Tuesday, June 15, 2010 7:58 AM
  • I'm having the same issue.  Even deploying the ApplicationCore template didn't help.

    I'm having a hard time understanding why a blank site, with a few document libraries and lists should even touch that application template now.

    Recreating a template was obnoxious enough, but not letting me save because it can't find a feature it doesn't need is worse.  

     

     

    Wednesday, June 16, 2010 3:41 PM
  • Anybody?

     

    Thursday, June 24, 2010 2:30 PM
  • Does it mean that the sites built using Fab 40 templates in WSS 3.0 will not work in 2010 foundation?
    Wednesday, June 30, 2010 9:15 PM
  • Robbert I am have the exact same issue. Did you ever find a resolution?

     

    Microsoft.SharePoint.SPException: Error exporting the site field named "Asset".

    at Microsoft.SharePoint.SPSolutionExporter.ExportFields(SPFieldCollection fields, String partitionName)

    at Microsoft.SharePoint.SPSolutionExporter.ExportLists()

    at Microsoft.SharePoint.SPSolutionExporter.GenerateSolutionFiles()

    at Microsoft.SharePoint.SPSolutionExporter.ExportWebAsSolution()

    at Microsoft.SharePoint.SPSolutionExporter.ExportWebToGallery(SPWeb web, String solutionFileName, String title, String description, ExportMode exportMode, Boolean includeContent, String workflowTemplateName, String destinationListUrl)

    at Microsoft.SharePoint.SPSolutionExporter.ExportWebToGallery(SPWeb web, String solutionFileName, String title, String description, ExportMode exportMode, Boolean includeContent)

    at Microsoft.SharePoint.ApplicationPages.SaveAsTemplatePage.BtnSaveAsTemplate_Click(Object sender, EventArgs e)

    at System.Web.UI.WebControls.Button.OnClick(EventArgs e)

    at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)

    at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)

    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    Thursday, December 02, 2010 2:19 PM
  • We are encountering the same issue.  Attach upgrade from 2007 to 2010.

    We have a Content DB with 2 site collections and only one of those site collections has this issue.  The other site collection is working fine.

    We have tried removing the application templates with no success.  We have also tried installing the 2010 (wsp) versions of the WSS fab 40 with no success.

    Any help would be great!

    12/09/201010:35:40.47 w3wp.exe(0x2284) 0x21E4 SharePointFoundation General 9k30 Monitorable SPSolutionExporter:System.FormatException:Guidshouldcontain32digitswith4dashes(xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).atSystem.Guid..ctor(Stringg)atMicrosoft.SharePoint.SPSolutionExporter.GetFieldSchemaXml(SPFieldfield,SPWebweb,BooleanisFieldFromWeb,BooleanremoveSealedAttribute)atMicrosoft.SharePoint.SPSolutionExporter.ExportField(SPFieldfield,SPWebweb)atMicrosoft.SharePoint.SPSolutionExporter.ExportFields(SPFieldCollectionfields,StringpartitionName) e5e1318a-27ff-44b5-8b68-9e19df5e4450
    12/09/201010:35:40.48 w3wp.exe(0x2284) 0x21E4 SharePointFoundation General ev0l Monitorable SPSolutionExporter:Microsoft.SharePoint.SPException:Errorexportingthesitefieldnamed"Asset".atMicrosoft.SharePoint.SPSolutionExporter.ExportFields(SPFieldCollectionfields,StringpartitionName)atMicrosoft.SharePoint.SPSolutionExporter.ExportLists()atMicrosoft.SharePoint.SPSolutionExporter.GenerateSolutionFiles()atMicrosoft.SharePoint.SPSolutionExporter.ExportWebAsSolution() e5e1318a-27ff-44b5-8b68-9e19df5e4450
    12/09/201010:35:40.51 w3wp.exe(0x2284) 0x21E4 SharePointFoundation Runtime tkau Unexpected Microsoft.SharePoint.SPException:Errorexportingthesitefieldnamed"Asset".atMicrosoft.SharePoint.SPSolutionExporter.ExportFields(SPFieldCollectionfields,StringpartitionName)atMicrosoft.SharePoint.SPSolutionExporter.ExportLists()atMicrosoft.SharePoint.SPSolutionExporter.GenerateSolutionFiles()atMicrosoft.SharePoint.SPSolutionExporter.ExportWebAsSolution()atMicrosoft.SharePoint.SPSolutionExporter.ExportWebToGallery(SPWebweb,StringsolutionFileName,Stringtitle,Stringdescription,ExportModeexportMode,BooleanincludeContent,StringworkflowTemplateName,StringdestinationListUrl)atMicrosoft.SharePoint.SPSolutionExporter.ExportWebToGallery(SPWebweb,StringsolutionFileName,Stringtitle,Stringdescription,ExportModeexportMode,Booleaninclud... e5e1318a-27ff-44b5-8b68-9e19df5e4450
    12/09/201010:35:40.51* w3wp.exe(0x2284) 0x21E4 SharePointFoundation Runtime tkau Unexpected ...eContent)atMicrosoft.SharePoint.ApplicationPages.SaveAsTemplatePage.BtnSaveAsTemplate_Click(Objectsender,EventArgse)atSystem.Web.UI.WebControls.Button.OnClick(EventArgse)atSystem.Web.UI.WebControls.Button.RaisePostBackEvent(StringeventArgument)atSystem.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandlersourceControl,StringeventArgument)atSystem.Web.UI.Page.ProcessRequestMain(BooleanincludeStagesBeforeAsyncPoint,BooleanincludeStagesAfterAsyncPoint) e5e1318a-27ff-44b5-8b68-9e19df5e4450
    12/09/201010:35:40.51 w3wp.exe(0x2284) 0x21E4 SharePointFoundation Monitoring b4ly High LeavingMonitoredScope(Request(POST:http://DOMAINNAME/demo/ehs2/_layouts/savetmpl.aspx)).ExecutionTime=13717.5665252511 e5e1318a-27ff-44b5-8b68-9e19df5e4450
    12/09/201010:35:40.54 w3wp.exe(0x2284) 0x1110 SharePointFoundation Monitoring nasq Medium Enteringmonitoredscope(Request(GET:http://DOMAINNAME/demo/ehs2/_layouts/error.aspx?ErrorText=Error%20exporting%20the%20site%20field%20named%20%22Asset%22%2E&ErrorCorrelationId=e5e1318a%2D27ff%2D44b5%2D8b68%2D9e19df5e4450)) 
    12/09/201010:35:40.54 w3wp.exe(0x2284) 0x1110 SharePointFoundation Monitoring b4ly Medium LeavingMonitoredScope(Request(GET:http://DOMAINNAME/demo/ehs2/_layouts/error.aspx?ErrorText=Error%20exporting%20the%20site%20field%20named%20%22Asset%22%2E&ErrorCorrelationId=e5e1318a%2D27ff%2D44b5%2D8b68%2D9e19df5e4450)).ExecutionTime=9.33640579095225 d2adf178-2923-437a-947e-c4abe882dec1


    dolo
    Thursday, December 09, 2010 3:57 PM
  • EUREKA!

    The below STSADM commands appear to have solved this issue for us.  Thanks to Sushant at Microsoft ... he is the man!

    stsadm -o deactivatefeature -name tsatypes -url http://sitename
    stsadm -o activatefeature -name tsatypes -url http://sitename

     

     


    dolo
    Sunday, December 12, 2010 2:44 AM
  • I ran into the same error message and, after struggling with it for a couple of days, I discovered that my issue was being caused by changes to the Information management policy on a site content type.

    Here's the full set of messages from my log file after I turned on Verbose logging:

    01/04/2011 10:47:49.95  w3wp.exe (0x104C)                        0x127C SharePoint Foundation          General                        8h45 Verbose  SPSolutionExporter: Closing XmlWriter 'TestListInstances\ElementsContentType.xml'. 974b99e0-575c-4f60-a293-049f59b1c44a
    01/04/2011 10:47:49.95  w3wp.exe (0x104C)                        0x127C SharePoint Foundation          General                        c42u Monitorable SPSolutionExporter: System.InvalidOperationException: The Writer is closed or in error state.     at System.Xml.XmlWellFormedWriter.AdvanceState(Token token)     at System.Xml.XmlWellFormedWriter.WriteEndElement()     at Microsoft.SharePoint.ScopedXmlWriterElement.Closer(XmlWriter writer, ScopedObjectUsage`1 wrapper)     at Microsoft.SharePoint.ScopedObjectUsage`1.Dispose(Boolean isDisposing)     at Microsoft.SharePoint.ScopedObjectUsage`1.Dispose()     at Microsoft.SharePoint.SPSolutionExporter.ExportContentTypes(SPContentTypeCollection contentTypes, String partitionName)     at Microsoft.SharePoint.SPSolutionExporter.ExportLists()     at Microsoft.SharePoint.SPSolutionExporter.GenerateSolutionFiles()     at Microsoft.SharePoint.SPSolutionExporter.ExportWebAsSolution() 974b99e0-575c-4f60-a293-049f59b1c44a
    01/04/2011 10:47:49.95  w3wp.exe (0x104C)                        0x127C SharePoint Foundation          General                        8hc6 Verbose  Deleting temporary directory 'C:\Users\TEMP.XXXXXX\AppData\Local\Temp\SPSolutionExporter-45dbf6a8-334c-4ff2-b80a-db12ceb676aa' and its contents during execution of the Dispose method. 974b99e0-575c-4f60-a293-049f59b1c44a
    01/04/2011 10:47:49.96  w3wp.exe (0x104C)                        0x127C SharePoint Foundation          General                        8hca Unexpected Failed to delete temporary directory: C:\Users\TEMP.XXXXXX\AppData\Local\Temp\SPSolutionExporter-45dbf6a8-334c-4ff2-b80a-db12ceb676aa, System.UnauthorizedAccessException: Access to the path 'Elements.xml' is denied.     at System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive)     at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive)     at Microsoft.SharePoint.TemporaryDirectory.Dispose(Boolean isDisposing) 974b99e0-575c-4f60-a293-049f59b1c44a

    Looking into the temp folder, I saw that the file ElementsContentType.xml was incomplete and stopped in the middle of a <PolicyDirtyBag> element in the XmlDocuments collection. Here's the portion from the content type definition:

    <PolicyDirtyBag xmlns="microsoft.office.server.policy.changes"><Microsoft.Office.RecordsManagement.PolicyFeatures.Expiration op="Delete" xmlns="" /><Microsoft.Office.RecordsManagement.PolicyFeatures.PolicyAudit op="Change" xmlns="" /></PolicyDirtyBag>

    Once I used PowerShell to delete this element from the XmlDocuments collection of the content type, the Save as Template started working again.

     


    David Dean
    • Edited by David Dean Tuesday, January 04, 2011 5:39 PM fix spelling
    Tuesday, January 04, 2011 5:38 PM
  • Hi Dean, Can you please provide us the shell script used to clean up ElementsContentType.xml. As we are also facing the same issue with saving site templates. Regards, Ashwin Sidharthan
    Tuesday, April 12, 2011 10:19 AM
  • Funny, I ran into the same problem again six months later and, lo and behold, I found my own post above. Sure enough, it fixed the problem.

    Here's the PowerShell script I used to remove the PolicyDirtyBag element from the XmlDocuments collection in the bad content type:

    $siteUrl = "http://sharepoint";
    $web = Get-SPWeb $siteUrl;
    $ct = $web.ContentTypes["My Bad Content Type"];
    $doc = $ct.XmlDocuments["microsoft.office.server.policy.changes"]
    if ($doc -ne $NULL) {
     $ct.XmlDocuments.Delete("microsoft.office.server.policy.changes")
    }
    $ct.Update($TRUE);
    $web.Dispose()
    

    David Dean
    Tuesday, June 14, 2011 4:56 PM
  • Hey This worked, thanks a lot. I was getting Asset filed (site column) not found error ( Microsoft.SharePoint.SPException: Error exporting the site field named "Asset".) when trying to generate a template from a site, I was not using it anywhere and was not able to find it in the site columns gallery. Many Thanks!!

     

     

    Wednesday, August 10, 2011 9:05 PM
  • Hi SharePointGuy21,

     

    How did you fix the problem. I have the same error Assest field (site column) not found. I can't find this column and i checked the logs but they are not helpful. Can you please help me with this?

    Thanks

     

    Thursday, September 08, 2011 4:24 AM
  • Hi SharePointGuy21,

    can you please tell me how did you solve this. i have the same issue asset column not found.

     

    thanks

     

    Thursday, September 08, 2011 4:27 AM
  • how can know who is my bad content type?

     

     


    Nati Papirovitch SharePoint Department Manager P.Z Projects
    Thursday, November 17, 2011 2:45 PM
  • How can I find this bad content type.

    i have problem with workflow list and attachment column.

    how can i remove that column.

    Please help me in this.

    Monday, January 30, 2012 9:39 AM
  • I had the same problem after migrating from sharepoint 2007 to sharepoint 2010 with SP1, sites that was created using some templates from sharepoint 2007, when I tried to save a site as a template was showed the message:

    Error exporting the site field named "Asset"

    I solved the problem with the sequence commands:

    stsadm -o activatefeature -name TSATypes -url http://servername/sites/pmo -force

    stsadm -o deactivatefeature -name TSATypes -url http://servername/sites/pmo -force


    MCP, MCDST, MCTS(Forefront,Windows Vista, Windows7, Windows2008, 2008R2 Virtualization), MCSA, MCSE, MCT, ITIL, Vencedor do Winthe7.com.br 2009, Quarto lugar Copa de Talentos Microsoft 2010

    • Proposed as answer by Atul Shukla Tuesday, May 15, 2012 12:44 AM
    Tuesday, March 06, 2012 8:44 PM
  • Last week, I upgraded company's portal to SharePoint 2010. I did database attach process for upgrade.

    All worked well.

    However, today network engineer reported an issue when he was trying to Save a site as a template. I had TSATypes feature already installed and activated for the site collection. However, I did this activation before attaching the database which could be a reason that feature isn't actually activated for the site collection. So I did run following commands using SharePoint 2010 powershell:

    Enable-SPFeature TSATypes -url http://servername . This command raised an error saying the feature is already enabled for the site collection. So I used -force attribute.

    Enable-SPFeature TSATypes -url http://servername -force. With this there wouldnt be any error.

    Disable-SPFeature TSATypes -url http://servername -force. This command actually de-activates TSATypes feature from the site collection. Both Enable followed by Disable-SPFeature commands are required to be run to make it work correctly. Assumption: TSATypes feature is already installed. May or may not be activated though.


    Thanks & Regards, Atul Shukla

    Tuesday, May 15, 2012 12:50 AM