SharePoint 2013 CU upgrade

Hi Guys!
I'm in the process of updating our CU to May 2014. I downloaded 3 files, 1 executable and 2 cab files. I was able to install the executable file however, i forgot to unzip the cab files. now i get 15.0.4605.1002 version instead of 15.0.4605.1004.
is there a way to correct to correct this?
Thanks!
JD

You don't unzip the cab files. You should have three files:
.exe
.cab (1)
.cab (2)
That version number is correct. Sometimes the number reported in Manager servers in farm doesn't exactly match with what is reported in the KB article.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Similar Messages

  • Issues with SharePoint 2013 after upgrading from windows 2012 to 2012 r2

    We have a Sharepoint with Sp1 environment on windows 2012. Recently we upgraded the windows 2012 to 2012 r2. After the upgrade sharepoint environment is completely unstable.
    At first all the sites returned 401 errors. After resolving by resetting the object cache accounts the sites are back.
    Then i see that none of the performance point dashboards work. I figured that claims to windows token service is defaulted to local system account. I previously configured with a domain account. I reconfigured to work with domain account. 
    All the dashboard pages throw error.
           Some Error logs:Failed to get document content data. System.ComponentModel.Win32Exception (0x80004005): Cannot complete this function     at Microsoft.SharePoint.SPSqlClient.GetDocumentContentRow 
    Application error when access /Dashboards/Performance Dashboard/Main.aspx, Error=The EnableScriptGlobalization property cannot be changed during async postbacks or after the Init event.   at System.Web.UI.ScriptManager.set_EnableScriptGlobalization(Boolean
    value)    
      4.  I tried to create a new dashboard and this time the performancepoint designer wont launch. After some troubleshooting i see that c2w host file didnot have the caller  C:\Program Files\Windows Identity Foundation\v3.5. 
           I added <add value="WSS_WPG" /> and now it launches
      5.  Now the Dashboard launches and peruser identity works without having kerberos enabled at IIS. I have all the spn and required delegations setup for this url . But i did not configure at the IIS level
    yet.
    It looks like lot of things got messed up and reset. Can we upgrade to windows 2012 r2 with a sharepoint application inplace. what is the recommended approach and Whats happening with Performancepoint dashboards. IS there a known issue with sharepoint 2013
    sp1.
    Raj-Shpt

    Thanks for the above article. Few issues are solved . One of the main issue is with Performancepoint Dashboard.
     I have all the spn and required delegations setup for this url . But i did not configure at
    the IIS level yet. Still per user identity works without having kerberos enabled at IIS.
    Raj-Shpt

  • Hide option for SharePoint 2013 UI upgrade

    Hello,
    I just want to know if there is a way to hide the banner which pops up for UI upgrade on SharePOint 2013? We are trying to leave few sites on 2010 UI only.
    Thanks,

    Hi,
    Per my understanding, you want to hide the banner which pops up for UI upgrade as below:
    You can add this custom CSS style into the master page, it will hide the banner for all the pages in the current site collection.
    <style type="text/css">
    #status_preview {
    display: none !important;
    </style>
    About how to add custom CSS style into master page:
    http://techtrainingnotes.blogspot.com/2012/05/adding-javascript-and-css-to-sharepoint.html
    Thanks                      
    Patrick Liang
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
    contact [email protected]
    Patrick Liang
    TechNet Community Support

  • SharePoint 2013 visual upgrade: Behind the Scene

    Hello,
    I recently migrated site collection from SharePoint 2010 to SharePoint 2013. But is not visually upgraded yet. I wanted to create evaluation site collection before actual upgrading. My questions are:
    1) Will it create a new Web application?
    2) Will it extend a the existing web application?
    3) will it create only a new site collection? If yes, will the size of content database become double?
    I am worried about the size of content database, as my DB is almost 50 GB and haven't much space left.
    any help would be really appreciated.

    Hi Rizwan,
    Evaluation Site Collections is a new feature in the SharePoint 2013 upgrade story. Evaluation Site Collections lend site collection administrators the ability to try out the 2013 version of their site collection before actually upgrading the production site
    collection’s UI and content.
    An upgrade evaluation site collection creates an upgraded version of the site in a new, separate copy of the site that is running on SharePoint 2013. Unlike visual upgrade in SharePoint Server 2010, the upgrade evaluation site collection is a complete copy
    of the site collection, separate from the original. Actions taken in the upgrade evaluation do not affect the original site.
    Evaluation site collections have a default expiration period of 30 days. And the evaluation site collection will also automatically be deleted when its parent production site collection is upgraded.
    More information, please refer to the links:
    http://sharepointengineer.com/2012/11/15/sharepoint-2010-to-2013-upgrade-step-by-step-2/#_Toc340767198
    http://blog.fpweb.net/sharepoint-2013-evaluation-site-collections/
    I hope this helps.
    Thanks,
    Wendy
    Wendy Li
    TechNet Community Support

  • SharePoint 2013 - blog upgrade

    Hi,
    I did an upgrade of SharePoint 2010 to 2013. Most things work fine, but I have some issues with upgrading a blog. I got these scenarios:
    I upgrade the blog in 2010 design, everything works fine, until I make a visual upgrade to 2013. After visual upgrade the blog still seems to be fine, but when I select a category to filter categories, all links are broken. So f.e. I klick a category linked
    to "Lists/Kategorien/Category.aspx?CategoryId=15&Name=Firewall" for category "Firewall", all results are linked to "Lists/Kategorien/". Even the categories in navigation are now linked to "Lists/Kategorien/".
    To solve this I tried various export/import settings, with features enabled/disabled, but no success. ULS Log didn't show usefull informations at this time. So the Question: Why do I experience this behavior? Any idea to solve this?
    I get a different error, when I try to import the blog, when the site collection has publishing feature enabled. Than I don't even can access any blog site, I get an error: sorry that didn't work. On export site is publishing feature enabled, dunno
    why I can't just import here.
    Hopefully I can get some help here. Best solution for me is to get error 1 fixed, I don't need publishing features. SharePoint 2010 was installation with SP1 and CU august 2012.
    Thanks for help
    iruhe

    I experienced this issue after removing the Blog Tools web part from the page.  Once I added it back, the issue was resolved.

  • Issues in SharePoint 2013 after Upgrade from SharePoint 2010

    I have recently migrated sharepoint 2010 web applicaiton to 2013 using database attach and detach methods. 
    I have few issues and just wondering they are issues or not. 
    I am running in compatible mode in 2013.
    1.I am not able to make a copy of any existing webs which are migrated from 2010.
    I browse to site content and structure from the site actions menu.
    click on a site then click on the copy or move, then a pop up box with the list of sites appears. i pick one of them and click ok.
    now it goes to copy or move operation then at the end it gives me following error
    The current operation could not be completed. Try again, or contact your system administrator.
    Object reference not set to an instance of an object.
    You may re-try the operation, and you may need to clean up the half-created data first before re-trying. If the problem persists, please contact your system administrator.
    User account used is the Farm account. 
    This is from the logs:
    LRO - An exception was thrown by the DoWork method of a LongRunningOperation System.NullReferenceException: Object reference not set to an instance of an object.    
     at Microsoft.SharePoint.Publishing.PublishingPage.get_Layout()    
     at Microsoft.SharePoint.Publishing.Internal.DeploymentWrapper.cachePageInfoForXmlFiltering(PublishingPage publishingPage)    
     at Microsoft.Office.Server.Utilities.ContentIterator.ProcessItem(SPListItem item, Boolean fIncludeFolderItems, MonitoredScopeWrapper monitoredScopeWrapper, ItemProcessor itemProcessor, ItemProcessorErrorCallout errorCallout)    
     at Microsoft.Office.Server.Utilities.ContentIterator.ProcessItems(SPListItemCollection items, Boolean fIncludeFolderItems, Boolean fIterateInReverseOrder, MonitoredScopeWrapper monitoredScopeWrapper, ItemProcessor itemProcessor, ItemProcessorErrorCallout
    errorCallout)    
     at Microsoft.Office.Server.Utilities.ContentIterator.ProcessItems(SPListItemCollection items, Boolean fIncludeFolderItems, Boolean fIterateInReverseOrder, ItemProcessor itemProcessor, ItemProcessorErrorCallout errorCallout)    
     at Microsoft.Office.Server.Utilities.ContentIterator.<>c__DisplayClassc.<ProcessListItems>b__9(SPListItemCollection items)    
     at Microsoft.Office.Server.Utilities.ContentIterator.ProcessListItems(SPList list, SPQuery query, ItemsProcessor itemsProcessor, ItemsProcessorErrorCallout errorCallout)    
     at Microsoft.Office.Server.Utilities.ContentIterator.ProcessListItems(SPList list, String strQuery, UInt32 rowLimit, Boolean fRecursive, SPFolder folder, ItemsProcessor itemsProcessor, ItemsProcessorErrorCallout errorCallout)    
     at Microsoft.Office.Server.Utilities.ContentIterator.ProcessListItems(SPList list, String strQuery, UInt32 rowLimit, Boolean fRecursive, ItemsProcessor itemsProcessor, ItemsProcessorErrorCallout errorCallout)    
     at Microsoft.Office.Server.Utilities.ContentIterator.ProcessListItems(SPList list, String strQuery, Boolean fRecursive, ItemsProcessor itemsProcessor, ItemsProcessorErrorCallout errorCallout)    
     at Microsoft.Office.Server.Utilities.ContentIterator.ProcessListItems(SPList list, Boolean fIterateInReverseOrder, ItemProcessor itemProcessor, ItemProcessorErrorCallout errorCallout)    
     at Microsoft.Office.Server.Utilities.ContentIterator.ProcessListItems(SPList list, ItemProcessor itemProcessor, ItemProcessorErrorCallout errorCallout)    
     at Microsoft.SharePoint.Publishing.Internal.DeploymentWrapper.configureExportCopyOrMove(String[] sourceSmtObjectIds, SPExportSettings& exportSettings, SPIncludeVersions versionsToInclude)    
     at Microsoft.SharePoint.Publishing.Internal.DeploymentWrapper.Copy(String[] sourceSmtObjectIds, String destSmtObjectId)    
     at Microsoft.SharePoint.Publishing.Internal.WebControls.CopyObjects.Copy()    
     at Microsoft.SharePoint.Publishing.Internal.WebControls.CopyObjects.DoWork()    
     at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock) StackTrace: 
     at Microsoft.Office.Server.Native.dll: (sig=c3cf111a-d6fc-4ec5-ba1c-c9b8ebb47e41|2|microsoft.office.server.native.pdb, offset=131CE)
     at Microsoft.Office.Server.Native.dll: (offset=21BFD)
    Copy Operation under site 'testb' failed in the Content and Structure tool. Details in ULS logs
    LongRunningOperationJob.UpdateStatus(): Running, this=62082684
    LRO - Starting status update: Running
    LRO - Completed status update
    LongRunningOperationJob.UpdateStatus(): Failed, this=62082684
    LRO - Starting status update: Failed
    CatalogConfig.ReadFromPropertyBag; Catalog configurations don't exist for site collection http://sitecollection.
    SiteServicesAddins.ReadFromPropertyBag: Site services addins don't exist for site collection http://sirecolletion.
    Any ideas what can be the cause....
    kukdai

    I think its related to page layouts URL it will reference to old URL because you are using database attach and detach methods.
    You will need to update the current page layout (Check below PS script)
    http://myspworld.wordpress.com/2012/08/16/powershell-script-to-change-the-page-layout/

  • SharePoint 2007 to SharePoint 2013 Upgrade - Need to Goto SharePoint 2010 First?

    All,
    I've seen some posts that say one can go from SharePoint 2007 to SharePoint 2013 - without upgrading to SharePoint 2010. Other posts say otherwise.
    Therefore, what is indeed the answer. Ideally I'm looking to stand-up a new SharePoint 2010 or SharePoint 2013 farm then likely do a detach then upgrade of the SharePoint 2007 content databases to SharePoint 2010 or 2013.
    Thanks

    If you want to do a standard SharePoint upgrade, yes you must go to SharePoint 2010 prior to 2013. If you want to use a 3rd part/in-house custom application content migration upgrade, then you can go straight from SharePoint 20xx to 2013.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Word Viewer will not open documents from Sharepoint 2013 in IE11

    I've run into an issue while trying to open documents from SharePoint 2013 after upgrading to IE11. My organization uses Word Viewer with the compatibility pack and all other Word documents (local files, intranet hosted) will open with no problems. When
    trying to open a Word document from SharePoint the Word Viewer will open, but the file does not. We have verified that all Windows Updates are installed. We have tried opening SharePoint in Compatibility View and Enterprise Mode. We have re-downloaded the
    latest version of Word Viewer and reinstalled it along with the compatibility pack. If we open the SharePoint site in Explorer view and then open a Word document it will open in Word Viewer with no problem. Excel and PowerPoint documents open from SharePoint
    with no problem. This is only affecting Word documents with Word Viewer. When using the full version of Word the documents open fine. Within SharePoint we have tried activating the site collection feature "Open Document In Client Applications by Default"
    but it made no difference. We're completely at a loss how to make this work as there doesn't seem to be much information specifically pertaining to issues with Word Viewer.

    Hi Victoria.
    1. The PCs do not have Microsoft Office installed, nor are we using the Office Web Apps. "Word Viewer" means the Microsoft Word Viewer application available here (http://www.microsoft.com/en-us/download/details.aspx?id=4) that is available
    free for read-only viewing of Word documents.
    2. There are no errors when I open Word docs in Word Viewer. The Word Viewer application launches after clicking a Word document link in Sharepoint, but there is no file open in it. When that happens the IE11 Sharepoint window on the taskbar is flashing
    yellow, but when I click back to it there are no messages or alerts to click on.
    3. This issue does occur with all Word documents (.doc, .docx) in SharePoint. However, it does not occur when opening Word documents in the Word Viewer when they are local files or through IE11 from a non-SharePoint website like our local intranet.
    Those files will open with no problem in Word Viewer.
    4. I will try to get a screenshot, but we are working on creating images for deployment and I don't currently have a machine configured the same way. I'll work on reconfiguring one and post a screenshot.
    Thank you for your help!

  • Can't change the master page after upgrading to SharePoint 2013.

    After upgrading our farm to SharePoint 2013 we are having trouble changing the master page for sites that don't have sub-sites. We are still using the v4 UI version, and that appears to be what is causing the problem. The error we get when going to /_layouts/ChangeSiteMasterPage.aspx
    is:
    System.NullReferenceException: Object reference not set to an instance of an object.    at Microsoft.SharePoint.Publishing.Internal.CodeBehind.AreaChromeSettingsPage.OnLoad(EventArgs e)     at System.Web.UI.Control.LoadRecursive()    
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    I took a peek at the source code for AreaChromeSettingsPage.OnLoad and found that it references a CheckBox control that does not exist in the v4 ChangeSiteMasterPage.aspx:
    protected override void OnLoad(EventArgs e)
    base.OnLoad(e);
    this.EnsureChildControls();
    if (!this.Page.IsPostBack)
    this.LoadValues();
    if (base.Web.Webs.Count == 0)
    this.resetSystemMasterPageSubSitesCheckBox.Visible = false;
    this.resetSubSitesCheckBox.Visible = false;
    this.resetAlternateCssSubSitesCheckBox.Visible = false;
    this.resetThemeSubSitesCheckBox.Visible = false;
    base.ConfigureCancelButton(this.BtnCancel);
    If I manually add a checkbox control with the ID "resetThemeSubSitesCheckBox" to a hidden panel in the v4 copy of ChangeSiteMasterPage.aspx the page works, but obviously this is not a best practice. How can we fix this without upgrading the UI version, which
    we are not yet ready to do?

    Thanks Mike - Could you please share what is your next step then? I also have custom master pages and layout but I am going to make new master page and layout in 2013 as we need to change the existing branding too. so, i upgrade the site collection. I understand
    the Look and Feel will not persist after the upgrade but I am concern that at least the page should show the content on the page after the upgrade. The page had Calendar webppart on it but after the upgrade it is coming blank.
    any suggestion?
    Regards,
    Khushi
    Khushi

  • Issue with list saving data after sites upgrade from sharepoint 2010 to sharepoint 2013

    Issue with list saving data after sites upgrade from sharepoint 2010 to sharepoint 2013 
    Newform.aspx of list:-
    Custom List is not saving data sometimes in the new form after 15 minutes and only blank entry record got created without saving data, even though some columns are mandatory fields?

    Hello dcakumar,
    Sounds like a strang issue. If you can reproduce this can you see some errors in the ULS logs?
    - Dennis | Netherlands | Blog |
    Twitter

  • SharePoint 2013 Upgrade Issue

    We are running a small farm with one app server and wfe server and sql server and in the process of upgrading SharePoint servers from RTM version 15.0.4420.1017 to SP1. However, app server shows the status of "upgrade required" in Servers in
    Farm in CA. When I run stsadm.exe -o localupgradestatus, the output results on app server are:
    38] content database(s) encountered.
    [0] content database(s) still need upgrade or cannot be upgraded.
    [56] site collection(s) are contained in the content databases.
    [0] site collection(s) still need upgrade.
    [49] other objects encountered, [1] of them still need upgrade or cannot be upgraded.
    Also, logs on app server after running psconfig are 
    PSCONFIG.EXE -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures 
    Timestamp              
    Process                                
    TID   Area                          
    Category                      
    EventID Level    
    Message Correlation
    01/14/2015 11:27:07.81 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    INFO SPWebApplication Name=SharePoint - name of the URL
    .... 10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.81 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    ERROR CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.85 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    INFO SPWebApplication Name=SharePoint - name of the URL....
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.85 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    ERROR Exception: Object reference not set to an instance of an object.
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.88 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    INFO SPWebApplication Name=SharePoint - name of the URL....
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.88 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    ERROR   at Microsoft.SharePoint.Administration.SPWebApplication.SetVersionOnIisWebSite(String binaryVersion, String buildVersion, DirectoryInfo di)     at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
        at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.90 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxnf
    INFO SPWebApplication Name=SharePoint - name of the URL....
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.90 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxnf
    ERROR Cannot upgrade [Microsoft.SharePoint.Administration.SPIisWebSite].
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.25 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    INFO No context object
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.25 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    ERROR CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.28 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    INFO No context object
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.28 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    ERROR Exception: Object reference not set to an instance of an object.
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.34 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    INFO No context object
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.34 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    ERROR   at Microsoft.SharePoint.Administration.SPWebApplication.SetVersionOnIisWebSite(String binaryVersion, String buildVersion, DirectoryInfo di)     at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
        at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.43 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession aj0ur
    INFO No context object
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.43 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession aj0ur
    ERROR Upgrade Timer job is exiting due to exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft
    Shared\Web Server Extensions\15\LOGS\Upgrade-20150114-112257-939.log.  The number of errors and warnings is listed at the end of the upgrade log file.     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()
        at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId)
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    I checked event logs and ULS logs but find nothing which can help fix this issue ?

    Hi Sharma,
    According to your description, my understanding is that the app server shows "upgrade required" when you upgrade your SharePoint 2013 from RTM to SP1.
    Whether you upgrade your SharePoint on app server from RTM to SP1.
    If not, please install SP1 for your SharePoint on the app server.
    After installing SP1, you need to run SharePoint Product Configuration Wizard.
    Best Regards,
    Wendy
    Wendy Li
    TechNet Community Support

  • Sharepoint 2013 search broken after upgrade from 2013 foundation to 2013 ent.

    Hello
    I have tried many of the suggestions that I have found in the forums for this issue but non have worked as of yet.
    I have sharepoint 2013  sp1 running on server 2012 R2 connected to SQL 2012 DB, which was upgrade from SharePoint foundation 2013. Everything is working with the exception of the search. the errors are below.
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (1d094485-eab9-458d-a363-4b5e8704048f).
    Reason: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
    Technical Support Details:
    System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
    For some reason this is using the farm account which is not the account used for the search service but has full access to the sites and databases. So I'm not sure what or where it is getting an access denied error. Is there any way to find what it is trying
    to access? BTW I have disabled the loopback check, verified it has correct access to %windir%\tasks and recreated the search service many times, changed application pool accounts
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (1d094485-eab9-458d-a363-4b5e8704048f).
    Reason: The object you are trying to create already exists. Try again using a different name. 
    Technical Support Details:
    System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name. 
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
    Any help you can provide would be greatly appreciated.

    Hi  ,
    According to your description, my understanding is that you encountered the error Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
    after you upgraded SharePoint 2013 Foundation to SharePoint Server 2013.
    For troubleshooting your issue, please try adding the farm account  on the Server local administrator group and see if it is related to permission issue. Then try stopping the Timer Service, clearing
    the Configuration Cache and restarting the Timer Service:
    http://www.social-point.com/sharepoint-2010-event-id-6482-application-server-administration-job-failed-for-service-instance-microsoft-office-server-search-administration-searchserviceinstance
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

  • Sharepoint 2013 Upgrade Job failed.

    Hello everybody,
    I would like some help with a litle problem that occured after I installed November CU on all of Sharepoint 2013 servers, 1 app, and 2 WFE. I'm unable to get Timer Job Service working on my app server, and that is a big problem. Everytime I restart Timer
    Job Service I get this error - Upgrade Job Appserver :00:00 Failed 12/16/2014 1:33 PM.. And in Event viewer - 
    System
    Provider
    [ Name]
    Microsoft-SharePoint Products-SharePoint Foundation
    [ Guid]
    {6FB7E0CD-52E7-47DD-997A-241563931FC2}
    EventID
    6398
    Version
    15
    Level
    1
    Task
    12
    Opcode
    0
    Keywords
    0x4000000000000000
    TimeCreated
    [ SystemTime]
    2014-12-16T11:33:37.846840300Z
    EventRecordID
    41822872
    Correlation
    [ ActivityID]
    {CD50D69C-AE16-00AA-3D5F-ECACB6C25BFE}
    Execution
    [ ProcessID]
    11368
    [ ThreadID]
    3216
    Channel
    Application
    Computer
    AppServername
    Security
    [ UserID]
    S-1-5-21-1708537768-1425521274-1417001333-40380
    EventData
    string0
    Microsoft.SharePoint.Administration.SPUpgradeJobDefinition
    string1
    13096a33-a91b-4c73-ae6c-e0ba750c5d4e
    string2
    Object reference not set to an instance of an object.
    And, also from Sharepoint Log file -
    Updating SPPersistedObject SPUpgradeJobDefinition Name=job-upgrade. Version: -1 Ensure: False, HashCode: 16745860, Id: 13096a33-a91b-4c73-ae6c-e0ba750c5d4e, Stack:    at Microsoft.SharePoint.Administration.SPJobDefinition.Update()    
    at Microsoft.SharePoint.Administration.SPTimerStore.CheckEnterUpgradeMode(SPFarm farm, Object& jobDefinitions, Int32& timerMode)     at Microsoft.SharePoint.Administration.SPTimerStore.InitializeTimer(Int64& cacheVersion, Object&
    jobDefinitions, Int32& timerMode, Guid& serverId, Boolean& isServerBusy)     at Microsoft.SharePoint.Administration.SPNativeConfigurationProvider.InitializeTimer(Int64& cacheVersion, Object& jobDefinitions, Int32& timerMode,
    Guid& serverId, Boolean& isServerBusy)
    Updating SPPersistedObject SPUpgradeJobDefinition Name=job-upgrade. Version: 2925660 Ensure: False, HashCode: 16745860, Id: 13096a33-a91b-4c73-ae6c-e0ba750c5d4e, Stack:    at Microsoft.SharePoint.Administration.SPJobDefinition.Update()    
    at Microsoft.SharePoint.Administration.SPTimerStore.CheckEnterUpgradeMode(SPFarm farm, Object& jobDefinitions, Int32& timerMode)     at Microsoft.SharePoint.Administration.SPTimerStore.InitializeTimer(Int64& cacheVersion, Object&
    jobDefinitions, Int32& timerMode, Guid& serverId, Boolean& isServerBusy)     at Microsoft.SharePoint.Administration.SPNativeConfigurationProvider.InitializeTimer(Int64& cacheVersion, Object& jobDefinitions, Int32& timerMode,
    Guid& serverId, Boolean& isServerBusy)
    Created upgrade job definition id 13096a33-a91b-4c73-ae6c-e0ba750c5d4e, mode InPlace, entering timer upgrade mode
    Queued timer job Upgrade Job, id {13096A33-A91B-4C73-AE6C-E0BA750C5D4E}
    Updating SPPersistedObject SPUpgradeJobDefinition Name=job-upgrade. Version: 2925663 Ensure: False, HashCode: 6922919, Id: 13096a33-a91b-4c73-ae6c-e0ba750c5d4e, Stack:    at Microsoft.SharePoint.Administration.SPJobDefinition.Update()    
    at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition.ExecuteAdminJob(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition
    jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)
    The Execute method of job definition Microsoft.SharePoint.Administration.SPUpgradeJobDefinition (ID 13096a33-a91b-4c73-ae6c-e0ba750c5d4e) threw an exception. More information is included below.  Object reference not set to an instance of an object.
    And after that it all fails and Timer Jobs ain't working on App server, on WFE servers eveyrthing is allright and working as it needs to be.
    I searched a lot of forums and different, but none of offered solutions ain't working, and that is not good.
    PS. On development server eveything worked fine, looked through log files and this job run without any errors - Dev server is one in all installation, though.
    If there is somebody who can help me with this, I would appreciate your help.
    TY!

    TY for your response,
    I used the script to update timer job config, but that isnt helping, and, also, this isnt a timer job that is already in timer job definitions. Its the one, that's created and after execution gets deleted, because its grayed out in timer job history page
    and I cant access it. if you look closer at log files I have pasted, you will see that the timer job that is created gets deleted almost immediatily and isnt executed and after that all timer jobs on my App server aint working and this happens every time after
    I restart Timer Service on App server, event ID is 6398, but timer job config cache isnt the problem.
    And, as much as I cant tell from logs - Object reference not set to an instance of an object. - I recieve this error because there is no timer job with ID, that is shown in error, because of this:
    Deleting the SPPersistedObject, SPUpgradeJobDefinition Name=job-upgrade.
    Maybe this information cansomehow help:
    The Execute method of job definition Microsoft.SharePoint.Administration.SPUpgradeJobDefinition (ID 910fbcdc-2691-490e-a9e9-563ae767612e) threw an exception. More information is included below.  Object reference not set to an instance of an object.
    After previous error:
    Exception stack trace:    at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition.ExecuteAdminJob(Guid targetInstanceId)
        at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)
    And after that Upgrade timer job gets deleted and thats it, App server aint working like it nedds to and no Timer job are executed.
    I hope this can help to narrow this problem down to a specific component or help resolve this error.
    Rihards

  • SharePoint Search Service upgrade to 2013 fails: "Inner Exception: An item with the same key has already been added."

    Here's the situation:
    Upgrading a SharePoint Server 2010 Search Service Application dB to our SharePoint 2013 SP 1 development environment, using the Management Shell
    Running the following commands: 
    $applicationPool= Get-SPServiceApplicationPool -Identity 'SearchService_AppPool'
    $searchInst = Get-SPEnterpriseSearchServiceInstance -local
    Restore-SPEnterpriseSearchServiceApplication -Name 'SearchServiceApplication' -applicationpool $applicationPool -databasename 'SearchServiceApplicationDB' -databaseserver SERVERNAME -AdminSearchServiceInstance $searchInst
    Creates the search dBs (crawl, links, analytics) successfully; however, in the end, I get....
    "Exception: Action 15.0.107.0 of Microsoft.Office.Server.Search.Upgrade.SearchAdminDatabaseSequence failed."
    Looking at the ULS logs, I find the following:
    Inner Exception: An item with the same key has already been added.
    at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)     at Microsoft.Office.Server.Search.Administration.OOTBSchemaDefinition.FindAndFixExistingManagedProperties()     at Microsoft.Office.Server.Search.Administration.OOTBSchemaDefinition.InstallManagedProperties(Boolean
    upgrade)     at Microsoft.Office.Server.Search.Administration.OOTBSchemaDefinition.Upgrade()     at Microsoft.Office.Server.Search.Upgrade.UpdateAllOOTBProperties.Upgrade()     at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
    Exception: Action 15.0.107.0 of Microsoft.Office.Server.Search.Upgrade.SearchAdminDatabaseSequence failed.
    at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()     at Microsoft.SharePoint.Upgrade.SPDatabaseSequence.Upgrade()     at Microsoft.Office.Server.Search.Upgrade.SearchDatabaseSequence.Upgrade()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object
    o, Boolean bRecurse)
    Anyone encounter anything like this during their search upgrade process? I'm not honestly even sure what duplicate value to look for at this point, if I were to run a SELECT Id, ClassId, ParentId, Name, Status, Version, Properties FROM Objects on
    "SharePoint_Config" in SSMS. Any insight or opinions on the matter are welcome; and thanks to those who choose to reply to this, in advance.

    Hi ,
    You can enable the ULS log on verbose level (note, remember to reset to default level after finished troubleshooting) for more information per the following article, then check there should be more useful message for helping solve the issue.
    http://www.brightworksupport.com/enabling-verbose-logging-to-compare-against-c/
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/12c99279-d3aa-46de-bc57-d5d250692ff0/upgrade-of-search-service-application-from-2010-to-2013-failure?forum=sharepointadmin
    https://www.simple-talk.com/blogs/2014/04/22/sharepoint-2010-to-2013-search-service-application-upgrade-issueaction-15-0-80-0-fails/http://blogs.msdn.com/b/biyengar/archive/2009/10/27/psconfig-failure-with-error-an-item-with-the-same-key-has-already-been-added.aspx
    Thanks,
    Daniel Yang
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] 
    Daniel Yang
    TechNet Community Support

  • SharePoint 2013 site collection 'upgrade completed with errors'

    Hi All, 
    I am in process to upgrade SharePoint 2010 to SharePoint 2013 with all steps as mentioned in TechNet. 
    I was able to get all the SP2010 UI in SP2013 environment. However, when I navigated to top level site and clicked on “Site
    Collection health checks”. In SP2010 environment I never used (as Farm Admin) any Video content type. It belongs
    to out-of-the-box "digital asset content types" and cannot be deleted.
    Therefore I changed the name of Video to our department name like "Video - Company" and ran the site collection health check again. This time there was no conflict for content types. 
    After ran the site collection upgrade I got following error. 
    -------------------------------------------START------------------------------------------
    05/05/2014 14:34:28.66 OWSTIMER (0x1474)
    0x123C SharePoint Foundation Upgrade
    SPFeatureDefinition aj2bj
    ERROR Feature upgrade action 'AddContentTypeField' threw an exception upgrading Feature 'CTypes' (Id: 15/'695b6570-a48b-4a8e-8ea5-26ea7fc1d162') in Site 'http://sp13fe01-dev': Field type
    Rating is not installed properly. Go to the list settings page to delete this field.
    32d48d9c-70d4-f09a-6073-526808f844be
    05/05/2014 14:34:53.04 OWSTIMER (0x1474)
    0x123C SharePoint Foundation Upgrade
    SPSiteWssSequence2 ajy6m
    ERROR Feature upgrade incomplete for Feature 'CTypes' (Id: 15/'695b6570-a48b-4a8e-8ea5-26ea7fc1d162') in Site 'http://sp13fe01-dev'. Exception: Field type Rating is not installed properly. Go to the list settings
    page to delete this field. 32d48d9c-70d4-f09a-6073-526808f844be
    05/05/2014 15:18:43.95 OWSTIMER (0x1474)
    0x123C SharePoint Foundation Upgrade
    SPManager ajxoe
    ERROR RunUpgradeSiteSession [SPSite Url=http://sp13fe01-dev] failed.
    32d48d9c-70d4-f09a-6073-526808f844be
    05/05/2014 15:18:44.16 OWSTIMER (0x1474)
    0x123C SharePoint Foundation Upgrade
    SPManager ajxoe
    ERROR Exception: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS\SiteUpgrade-20140505-143330-61.log.  The
    number of errors and warnings is listed at the end of the upgrade log file.
    32d48d9c-70d4-f09a-6073-526808f844be
    05/05/2014 15:18:44.16 OWSTIMER (0x1474)
    0x123C SharePoint Foundation Upgrade
    SPManager ajxoe
    ERROR   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()     at Microsoft.SharePoint.Upgrade.SPManager.RunUpgradeSiteSessionCore(Object
    lockObject, SPSite site, SPUpgradeOperationFlags upgradeOperationFlags, Boolean checkConcurrentSiteUpgradeSessi
    32d48d9c-70d4-f09a-6073-526808f844be
    -----------------------------------END-------------------------------------
    Feature ID 695b6570-a48b-4a8e-8ea5-26ea7fc1d162 is Standard Content Type Definitions  https://social.technet.microsoft.com/wiki/contents/articles/7695.sharepoint-2010-list-of-features-id-displayname-and-scopes.aspx. 
    Any expert to solve the issue?? 
    Thank you. 
    regards, 
    Aroh Shukla

    Hi All and Inderjeet,
    Thanks for your reply and pointers. 
    I did follow the steps as mentioned in the links above. I used some third party solutions but not for any Video solution. I was able to successfully migrated the SP2010 (WSS_Content) to SP2013 (WSS_Content) environment a few weeks back with exactly same
    third party solutions and no site collection error:
    I renamed the default and out-of-the box video site content type as shown:
    I ran the "Site Collection Health Check" and did not receive any error as in my second screenshot. 
    But, after upgrade the Site Collection Upgrade and got the same errors. 
    I don't know if there is any SharePoint Server 2013 patch gave this error as I keep run the Windows Server 2012 (not running R2) and SharePoint Server 2013 regularly.  
    Can suggest how to resolve this error?
    Many Thanks!!
    --Aaroh 
    Aroh Shukla
    The same here. Opening a support ticket with MS.

Maybe you are looking for