15

Internal File Structure A big difference is the internal structure of the .update package file. If you open up an update package file you will see the following folder structure: A standard .zip package does not contain all the folders for added, changed or deleted data. So an update package can do more than a standard zip package. IIRC you can't delete ...


14

There is a package directory for the Update Wizard packages at the following path under the site root: \sitecore\admin\Packages


7

Make sure that your Azure SQL is running on the latest V12 version. Since you're using Sitecore 8.0 update-4 it would suggest you maybe set these servers up a while ago, so there is the possibility that you created the databses on the older V11 version of the SQL Azure platform. You can check by logging into the portal and checking the databases. You can ...


6

I have seen similar slow-downs in Azure talking to Azure SQL. It seems to be related to the number of database calls made by the installation wizard and general network latency. When you execute locally, you eliminate all of that chatter back and forth. We ran into extreme performance issues when the Azure SQL had georeplication and we discovered we were ...


5

To do this quickly using PowerShell, without any new tools, see snippet below. It will handle dated packages generated by TDS as well. # use name of package without .update extension $packageName = "MyPackage" get-childitem -recurse -filter "*.config.$($packageName)*" | ? {$_.FullName -notmatch "\\temp\?"} | % { Move-Item $_.FullName $_.FullName.Substring(0,...


4

@Dheeraj First Please ensure you have folder("\temp__UpgradeHistory\Upgrade_Sitecore 8.1 rev. 151003_20170318T05502164") present in your website path. Go to IIS and check application pool of your website. Also go to App pools advance settings and check for which account identity is set for the same. If You have installed using sitecore exe installer, it ...


4

Typically when I run a Sitecore upgrade I'll attach the databases to a clean install of the old version and run the update package on that clean install. That will get the new content into your databases, then you can copy the new files in whatever way is most convenient for you. This doesn't solve the problem directly but it's a decent workaround. Like I ...


4

I've found some different steps if you would like to try 1. Use a different browser Always install upgrade package in Firefox rather than IE Yes, we know you are an engineer and you need logical justification for the same Don’t worry we have a logical justification for you — posted on my another blog - Long-running processes and browser timeout ...


4

The problem is with IIS application pool setting “Ping Maximum Response Time” which is the time in seconds the worker process is given to respond to health monitoring ping. After 5 missed responses the work process is timed out and causes the exception Exception: System.Web.HttpException Message: Request timed out. There are 2 solutions: Set ping enabled ...


4

Have you tried the Sitecore Package Deployer? You basically upload the .update package to a specific folder, it installs it, and then does that whole config activation. I've been using this for my production deploys now for 9 months and it saves so much time and hassle.


4

I have migrated sitecore 8 to 9 by using the Option#2 and it worked well for me. Templates, Items, Layout , System, etc you will be able to migrate easily by using the sitecore package. But if you have a huge media library then you can not use sitecore package to transfer this, So, to migrate the media library you need to serialize the whole media library ...


4

Found the issue. When moving Sitecore items using .update packages you need to first delete them and then add them to the target path. The problem with my .update package is that it only contains items addition. That’s why the installation process is never moving those items. Here is a screenshot of how my.update package looks like: Here is a screenshot ...


3

Sitecore is "very chatty" when communicating with the database server and one of the main reasons I've seen for both slow Sitecore instances and package installation is network latency. There can be number of reasons for this, the 2 main ones I have seen: Physical location of web server and database servers being separated, e.g. in different datacenters. ...


3

There are likely additional places and methods for retrieving this data, but the following is typically what I resort to: Note: I have not tested SPECIFICALLY for UpdateInstallationWizard logs In Azure Portal, select the App Service resource that you used to run the installation. Scroll down the blade and find App Service logs in the Monitoring section ...


3

Normally, the .update package can be converted to a zip file. You just need to rename the .update to .zip. Once this is done, open the package and see if the items and dlls are present in the sub folders. If you have more .update package inside the package, you can try to unzip the main .update package and the install the sub .update package individually. ...


3

There is a strange thing that the Sitecore Update Installation Wizard does for Standard Values items when it installs them in a Sitecore Update Package. For __Renderings and __Final Renderings fields, if you have reset the value (made it null) of one of those fields in your Standard Values item in the package...the Installation Wizard still won't make your ...


3

I'm guessing, based on your edits and the other responses, that you're issue lies in indexing - and that you're probably using Solr (where maybe you had Lucene in your local test). There's several configuration setups that trigger synchronous indexing during package installs, and these manifest as slow throughput without obvious load on either the DB or ...


2

With the update installation wizard you can install update packages remotely without direct access to the sitecore server. As it is a standard ASP.NET web application. Besides that you're able to delete files and items with the update wizard.


2

I suspect that you have a field that holds certain XML twice (i.e the definition of a carousel slide actually exists in two fields on the server). And maybe one of the four fields that it calculates the entire layout from is difference between your local environment and the server environment. Renderings are calculated via deltas, and it's a combination of ...


2

Removing Telerik_Web_UI_WebResource_axd and other Telerik handlers should be done on any Sitecore servers except Content Management, which requires these controls. On Content Management server those handlers should stay as they are plus additionally: On CM server you should: Extract the contents of the patch from your to the Sitecore website folder. Add ...


2

Yes you can. The way I have it setup, I use a Project layer TDS project to bundle all the other TDS projects up. If you go into the properties of the TDS Project and load the Multi-Project Properties tab. You can then set the Package Bundling properties. So in your main TDS project that you want to create the update package, add in all the other projects: ...


2

The .update package is just a compressed file. You can rename the file by replacing .update with .zip to view and extract any files that would be installed during the installation process For items, your best bet is to install the .update package on a local instance of Sitecore and create a new Sitecore package using the Package Designer.


1

That temp folder location is incorrect. That location (d:\local\temp) is temporary and is not shared between the application and the Kudu tools. Relevant snippet from the above documentation: Another important note is that the Main site and the scm site do not share temp files. So if you write some files there from your site, you will not see them from ...


1

You can use package bundling to create a single package containing items from multiple other TDS projects, see screenshot below. I have never tried putting this in the TdsGlobal.config but this should probably work just like any other project setting.


1

You'll find several blog posts on how to upgrade, but I can provide here the initial steps. Open the documentation page of the Sitecore version you want to update to and download the upgrade guide. In your case, open https://dev.sitecore.net/Downloads/Sitecore_Experience_Platform/82/Sitecore_Experience_Platform_82_Update3.aspx. Check the prerequisites in ...


1

You will only be able to install the .update package on the CM environment. For a single server setup that's all you need to do, but if you have a scaled setup (which it sounds like you do) then you need to also manually apply the server role specific packages on those roles c.f. Walkthrough: Configuring EXM in a scaled environment Now, in your case, when ...


1

As the message suggests, the error there is because Invoke-WebRequest cannot parse the $url variable that's being passed to it as a parameter. The message is saying that $url includes System.Collections.Hashtable.Sitecore.InstanceName - which suggests to me that there's something wrong with the variable replacement when the $siteName variable is being set up....


1

Based on your numerous updates and provided information, I have concluded that that issue at hand is most definitely something to do with infrastructure as I alluded to in my comment above. Things to Check I would advise checking the firewall to ensure communication with the SQL server If the SQL server resides remotely, try installing it locally to ...


1

The root cause of the timeout was infrastructure related. At this moment the IT team within the client is working to pinpoint exactly what the problem was. SQL server was having difficulties to communicate well with the sitecore QA server(not yet sure why maybe firewall rules) but installing sql server within the QA server and running the upgrade package it ...


1

You could do what Sitecore support would do in these scenarios. Use a tool like dotMemory- https://www.jetbrains.com/dotmemory/features/ to get a memory dump. More tools here: https://kb.sitecore.net/articles/488758 Take a snapshot of the W3WP process while you are installing the package. Analyse the results - this will give you some area to focus in in ...


Only top voted, non community-wiki answers of a minimum length are eligible