Monthly Archives: June 2014

SharePoint error “Cannot complete this operation” – Creating site from site tempalte

Published / by / Leave a Comment

The SharePoint application pages under the layouts folder uses the web.config file at the following location. Default timeout is 3600 and increase it will make the execution complete successfully. 

Location: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS

[wc_highlight color=”blue”]<httpRuntime executionTimeout=”18000″ />[/wc_highlight]


[wc_box color=”primary” text_align=”left”]

If you are using Physical Load Balancer like F5 then check for LANTIMEOUT, WANTIMEOUT and adjust them appropriately.




SharePoint 2013 prompts for login credentials while editing Publishing pages

Published / by / Leave a Comment

SharePoint 2013 uses a Distributed Cache Service to cache login tokens. In SharePoint 2010 Products, the login token is stored in the memory of each web front-end server. Each time a user accesses a specific web front-end server, it needs to authenticate. If you use network load balancers in front of your web front-ends, users need to authenticate for each web front-end server that is accessed behind the load balancer, causing possible multiple re-authentications.

The Distributed Cache depends on Windows Server AppFabric and old versions of it had lot of issues and is known to cause login prompts while editing SharePoint Pages. Follow the below steps to upgrade to latest version and login prompt issues will be resolved. You may have to restart the computer after you apply this cumulative update package.

  • Go to
  • Download the latest cumulative update
  • Copy it to the server and update app fabric





AWS – Amazon RDS adds Multi-AZ support for SQL Server in US East Region

Published / by / Leave a Comment

Amazon RDS now offers Multi-AZ support for Amazon RDS for SQL Server in the US East (Northern Virginia) AWS Region. This new high availability option leverages SQL Server Mirroring technology with additional improvements to meet the requirements of enterprise-grade production workloads running on SQL Server. The Multi-AZ deployment option provides enhanced availability and data durability by automatically replicating database updates between two AWS Availability Zones. Availability Zones are physically separate locations with independent infrastructure engineered to be insulated from failures in other Availability Zones.

When you create or modify your SQL Server database instance to run using Multi-AZ, Amazon RDS will automatically provision a primary database in one Availability Zone and maintain a synchronous “standby” replica in a different Availability Zone. In the event of planned database maintenance or unplanned service disruption, Amazon RDS will automatically fail over the SQL Server database to the up-to-date standby so that database operations can resume quickly without any manual intervention.

Multi-AZ is available with Microsoft SQL Server 2008 R2 and 2012 Standard and Enterprise Editions. The increased availability and fault tolerance offered by Amazon RDS for SQL Server Multi-AZ are well suited for critical production environments using SQL Server. Multi-AZ deployments for Amazon RDS for SQL Server are also available in the US West (Oregon) and EU (Ireland) AWS Regions.

To learn more, visit the RDS SQL Server details page.


Source: AWS