Sitecore Upgrade

#Sitecore Tip: Increase the timeout before installing .update file in UpdateInstallationWizard page.

Posted on Updated on

Lately, I’ve encountered a lot of timeouts while installing an .update package in the UpdateInstallationWizard page, and I hope this post might be helpful for those developers who might ran into this kind of problem as well.

Issue: When you reached the timeout, you would see a sitecore login in the center of the page. And when you logged-in, it would repeat the installation from the start.

Increase_the_timeout_before_installating_.update_file_in_UpdateInstallationWizard

Solution:

In web.config, increase the httpRuntime executionTimeout to 18000 (3 hours)

<httpRuntime maxRequestLength="512000" executionTimeout="18000" enableKernelOutputCache="false" 
 

In web.config, increase the .ASXAUTH timeout to 180 minutes (3 hours), just to give more time.

<forms name=".ASPXAUTH" cookieless="UseCookies" timeout="180" />

In web.config, adjust the sessionState timeout to 180 minutes (3 hours), please don’t forget to revert it back to its default value or from its original value.

<sessionState mode="InProc" cookieless="false" timeout="180" ...

In Sitecore.config

<setting name="Authentication.ClientSessionTimeout" value="180" />

Note: Please don’t forget to revert back the original value after the installation.

Reference:

How does a Sitecore session expire?

How to connect to two (2) sitecore instances from virtual machine / rdp simultaneously

Posted on Updated on

In this post, I would tackle the procedure on how to establish a connection from a virtual machine a.k.a RDP on your local machine.

Important note: This is for Development / System Integration (SIT) environment only.

The two (2) things:

  1. Configure to expose the two (2) SC instances to your network.
    1. Assumption: You’re connected on the same network.
  2. Connect from your local machine.
    1. Assumption: You’re connected to LAN. 🙂

The why? 

1. Easy to access

2. Less stress/processes on the virtual machine.

Let’s imagine you’re working with other 5 developers, and everyone are trying to connect to it. All of you may – for sure – experience the so-called ‘slowness’.

3. Easy to configure

The scenario:

Say you’re working on an upgrade, and you want to access both SC instances simultaneously . This time, not inside a virtual machine because your team should also connect to it and should be composed to the Project Manager, QA, FE and your boss. Amazing! 🙂

The variables:

Sitecore Instance 1: local.sitecore.com (eg. v. 7.2)

Sitecore Instance 2: upgraded.sitecore.net (eg. v.8.1 Update-3)

 

1.  Configure your two (2) SC instances from the virtual machine

In IIS, for local.sitecore.com, leave the Host Name empty, Port to 80 – default and IP Address to All Unassigned.

local.sitecore.com IIS bindings

In IIS, for upgrade.sitecore.com,

upgrade.sitecore.com:80 * : The binding when accessing the site inside RDP

upgrade.sitecore.com:80 203.130.253.230 : The binding when accessing the site outside RDP (This is what we want)

upgrade.sitecore.com:443 203.130.253.230 : The binding when accessing the site secured outside RDP (https)

More about creating self-assigned certificate here.

upgrade.sitecore.com IIS bindings

For hackers out there, FYI, the IP address is fake.

hacker everywhere

Leave as is. This is the default value of the SC instances upon installation.

File location : C:\Windows\System32\drivers\etc\host

host_file_entries

2.  Connect from your local machine

Update your host file.

File location : C:\Windows\System32\drivers\etc\host

local_host_file_entries.png

Note: For some cases, you need to put the website in your proxy settings, but for this case we don’t need to.

At this point, you would be able to access you site from your favorite browser in your local machine. What you only need to do is, just type the local.sitecore.com OR upgrade.sitecore.com in your browser.

Enjoy!