Category Archives: IIS

Installing SQL SERVER 2012 (for SharePoint 2013)

SQL Server

To install SQL SERVER 2012 we are using the following Setup file:

#####_SQLServer2012EnterpriseEditionwithSP1_ServerCAL(With_#########)_x64

Right Click and Mount, Run “setup” Application file as Administrator:

Note: We are logged in as [SharePoint Admin] for all installations.

This Screen will Show up:

Microsoft SQL SERVER 2012 Installation 1

Click “Installation” on the left side, the following screen will come:

Microsoft SQL SERVER 2012 Installation 2

Click “New SQL Server stand-alone installation or add features to an existing installation”, the following screen will come:

Microsoft SQL SERVER 2012 Installation 3

Click “Show Details” to view details, Click “OK” after verifying the setup support rules. In case there is a problem resolve it and Re-run the Setup. Now the following screen appears:

Microsoft SQL SERVER 2012 Installation 4

Wait for some time, the following screen will come:

Microsoft SQL SERVER 2012 Installation 5

In the product key section, Select “Enter the Product Key” which should be 25 character key. Click next, the following screen will come:

Microsoft SQL SERVER 2012 Installation 6

In the license Terms section, Select “I accept the license terms” and Select Send feature usage data to Microsoft….. Click next, the following screen will come:

Microsoft SQL SERVER 2012 Installation 7

Click Next to “Include SQL Server product updates”:

Microsoft SQL SERVER 2012 Installation 8

After the above screen, a prompt as shown below will appear for restarting the system:

Microsoft SQL SERVER 2012 Installation 9

After restart run the setup again and reach to the below screen:

Microsoft SQL SERVER 2012 Installation 10

When the Setup Support Rules screen pops up review any errors or warnings you get. If nothing bad has happened the Next button will be available to click. Click Next to view the following screen:

Microsoft SQL SERVER 2012 Installation 11

For Setup Role select SQL Server Feature Installation and click next.

Microsoft SQL SERVER 2012 Installation 12

On the Feature Selection screen this is where you need to be smart. In order to make SharePoint run you only need to select one check box, Database Engine Services. I would highly recommend you also check Management Tools – Basic and Management Tools – Complete. Click Next to view the following screen:

Microsoft SQL SERVER 2012 Installation 13

Wait for some time, the following screen will come:

Microsoft SQL SERVER 2012 Installation 14

Now when you read all of these awesome features you might be thinking “I want to kick the tires of Reporting Services – SharePoint” or some other random feature. That is great, tire kicking is fun and important but if you are reading the blog post to get SQL Server installed correctly for SharePoint then you probably aren’t ready to start randomly installing features. Even if you were ready to install them you would still most likely come back and do them after SharePoint was up and running, not before. So let’s ignore them for now and click next.

On the Installation Rules screen SQL will make some checks. In this case my Server did not have the Microsoft .NET Features installed. You will need to manually add the feature now. While you do go ahead and leave this SQL window open.

To add the .NET Windows Server feature click on Start > All Programs > Administrative Tools > Server Manager.

From the right side of the screen click on Features.

Over on the left side of the screen click on Add Features.

Check the box for .NET Framework 3.5.1 Features.

When you check the box a window for Add Features Wizard will appear telling you the additional required roles. Click Add Required Role Services.

Click Next.

At the Web Server (IIS) screen click Next.

Accept all of the defaults and click Next.

At the Confirm Installation Selections click Install.

At the Installation Results screen make sure everything was successful and then click Close.

Jump back over to your SQL Installation Rules screen and click the Re-run button.

If the tests are Passed click Next to continue.

After Installation Rules the Following screen appears:

Microsoft SQL SERVER 2012 Installation 15

Assuming this is the only install of SQL Server on this server then you are going to want to take all of the default settings for the Instance Configuration screen, but in my Case I have updated the name to be my server, Click Next.

Microsoft SQL SERVER 2012 Installation 16

Wait for some time, the following screen will come:

Microsoft SQL SERVER 2012 Installation 17

At the Disk Space Requirements screen click next.

Microsoft SQL SERVER 2012 Installation 18

For the Server Configuration screen it is asking you what accounts you want to run SQL Server as. The only service you are worried about right now is the SQL Server Database Engine. This service should always be run as a domain account not a local account. Next to SQL Server Database engine click on MANAMA1\spadmin and a drop down arrow will appear.

Click <<Browse…>>.

Select your SQL account you want to use and click OK.

Enter the account password and keep the startup type as Automatic click next.

Microsoft SQL SERVER 2012 Installation 19

Wait for some time, the following screen will come:

Microsoft SQL SERVER 2012 Installation 20

On the Database Engine Configuration screen there are lots of changes you could make and over time you will learn about these options but for the purpose this guide you will except all of the defaults. You only need to click Add Current User and it is shown as.

Microsoft SQL SERVER 2012 Installation 21

If you were building a production capable SQL Server best practice 101 would be to store your data and log files on different volumes. By default SQL Server will store everything on the C: drive. If you want change that behavior take a gander at the Data Directories tab.

Once you are ready click next the following screen appears:

Microsoft SQL SERVER 2012 Installation 22For the Error Reporting screen select Send Windows and SQL Server Error Reports…Click next the following screen appears:

Microsoft SQL SERVER 2012 Installation 23

At the Installation Configuration Rules screen click next.

Microsoft SQL SERVER 2012 Installation 24

You are ready to Install, so click Install.

Microsoft SQL SERVER 2012 Installation 25

Wait for some time, the following screen will come:

Microsoft SQL SERVER 2012 Installation 27 After Restart

When the installation finishes you may be prompted to restart. This is not directly because of SQL Server but instead because of other recent installs you have done that you haven’t rebooted since. In my case because I added the .NET feature. When SQL is all done click close. If you have any other open windows at this point you can close them as well. You are all done.

If you got the pop up screen to do a reboot it will not automatically happen, you will need to reboot on your own.

Microsoft SQL SERVER 2012 Installation 27 After Restart

Note: The Above error is due to Installation of .Net Framework 3.5, after resolving this when you run the setup again you receive the following screen:

Microsoft SQL SERVER 2012 Installation After Installing NetFx3

Now the SQL SERVER 2012 is successfully installed.

Now do what is mention in this post: Max Degree of Parallelism for SQL SERVER 2012 (before installing Sharepoint 2013)

Now do what is mention in this post: Starting/Running SQL SERVER 2012 (SQL Permissions) for SharePoint 2013

Now you have your whole SQL Server ready, so you can install SharePoint 2013.

Advertisements

WINDOWS SERVER 2012 AND R2 (FEATURES)

Features includes

Installation options
Unlike its predecessor, Windows Server 2012 can switch between “Server Core” and “Server with a GUI” installation options without a full reinstallation. Server Core – an option with a command-line interface only – is now the recommended configuration. There is also a third installation option that allows some GUI elements such as MMC and Server Manager to run, but without the normal desktop, shell or default programs like File Explorer.

User interface
Server Manager has been redesigned with an emphasis on easing management of multiple servers. The operating system, like Windows 8, uses the Metro-based user interface unless installed in Server Core mode. Windows Store is available in this version of Windows but is not installed by default. Windows PowerShell in this version has over 2300 commandlets, compared to around 200 in Windows Server 2008 R2.

Task Manager
Windows Server 2012 includes a new version of Windows Task Manager together with the old version.In the new version the tabs are hidden by default showing applications only. In the new Processes tab, the processes are displayed in varying shades of yellow, with darker shades representing heavier resource use. It lists application names and status, as well as CPU, memory, hard disk and network utilization. The process information found in the older versions are now moved to the new Details tab. The Performance tab shows “CPU”, “Memory”, “Disk”, “Wi-Fi” and “Ethernet” graphs. The CPU tab no longer displays individual graphs for every logical processor on the system by default; instead, it can display data for each NUMA node. When displaying data for each logical processor for machines with more than 64 logical processors, the CPU tab now displays simple utilization percentages on heat-mapping tiles. The color used for these heat maps is blue, with darker shades again indicating heavier utilization. Hovering the cursor over any logical processor’s data now shows the NUMA node of that processor and its ID, if applicable. Additionally, a new Startup tab has been added that lists startup applications, however this tab does not exist in Windows Server 2012. The new task manager recognizes when a Windows Store app has the “Suspended” status.

IP address management (IPAM)
Windows Server 2012 has an IP address management role for discovering, monitoring, auditing, and managing the IP address space used on a corporate network. The IPAM is used for the management and monitoring of Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) servers. Both IPv4 and IPv6 are fully supported.

Active Directory
Windows Server 2012 has a number of changes to Active Directory from the version shipped with Windows Server 2008 R2. The Active Directory Domain Services installation wizard has been replaced by a new section in Server Manager, and a GUI has been added to the Active Directory Recycle Bin. Multiple password policies can be set in the same domain. Active Directory in Windows Server 2012 is now aware of any changes resulting from virtualization, and virtualized domain controllers can be safely cloned. Upgrades of the domain functional level to Windows Server 2012 are simplified; it can be performed entirely in Server Manager. Active Directory Federation Services is no longer required to be downloaded when installed as a role, and claims which can be used by the Active Directory Federation Services have been introduced into the Kerberos token. Windows Powershell commands used by Active Directory Administrative Center can be viewed in a “Powershell History Viewer”.

Hyper-V
Windows Server 2012, along with Windows 8, includes a new version of Hyper-V, as presented at the Microsoft BUILD event. Many new features have been added to Hyper-V, including network virtualization, multi-tenancy, storage resource pools, cross-premise connectivity, and cloud backup. Additionally, many of the former restrictions on resource consumption have been greatly lifted. Each virtual machine in this version of Hyper-V can access up to 64 virtual processors, up to 1 terabyte of memory, and up to 64 terabytes of virtual disk space per virtual hard disk (using a new .vhdx format). Up to 1024 virtual machines can be active per host, and up to 8000 can be active per failover cluster. SLAT is a required processor feature for Hyper-V on Windows 8, while for Windows Server 2012 it is only required for the supplementary RemoteFX role.

ReFS
Resilient File System (ReFS), codenamed “Protogon”, is a new file system in Windows Server 2012 initially intended for file servers that improves on NTFS in some respects. Major new features of ReFS include:

Improved reliability for on-disk structures
ReFS uses B+ trees for all on-disk structures including metadata and file data. Metadata and file data are organized into tables similar to a relational database. The file size, number of files in a folder, total volume size and number of folders in a volume are limited by 64-bit numbers; as a result ReFS supports a maximum file size of 16 Exabytes, a maximum of 18.4 × 1018 folders and a maximum volume size of 1 Yottabyte (with 64 KB clusters) which allows large scalability with no practical limits on file and folder size (hardware restrictions still apply). Free space is counted by a hierarchical allocator which includes three separate tables for large, medium, and small chunks. File names and file paths are each limited to a 32 KB Unicode text string.

Built-in resilience
ReFS employs an allocation-on-write update strategy for metadata, which allocates new chunks for every update transaction and uses large IO batches. All ReFS metadata has built-in 64-bit checksums which are stored independently. The file data can have an optional checksum in a separate “integrity stream”, in which case the file update strategy also implements allocation-on-write; this is controlled by a new “integrity” attribute applicable to both files and directories. If nevertheless file data or metadata becomes corrupt, the file can be deleted without taking down the whole volume offline for maintenance, then restored from the backup. As a result of built-in resiliency, administrators do not need to periodically run error-checking tools such as CHKDSK when using ReFS.

Compatibility with existing APIs and technologies
ReFS does not require new system APIs and most file system filters continue to work with ReFS volumes. ReFS supports many existing Windows and NTFS features such as BitLocker encryption, Access Control Lists, USN Journal, change notifications, symbolic links, junction points, mount points, reparse points, volume snapshots, file IDs, and oplock. ReFS seamlessly integrates with Storage Spaces, a storage virtualization layer that allows data mirroring and striping, as well as sharing storage pools between machines. ReFS resiliency features enhance the mirroring feature provided by Storage Spaces and can detect whether any mirrored copies of files become corrupt using background data scrubbing process, which periodically reads all mirror copies and verifies their checksums then replaces bad copies with good ones.
Some NTFS features are not supported in ReFS, including named streams, object IDs, short names, file compression, file level encryption (EFS), user data transactions, hard links, extended attributes, and disk quotas. Sparse files was not supported by Preview, but it is supported by RTM. ReFS does not itself offer data deduplication. Dynamic disks with mirrored or striped volumes are replaced with mirrored or striped storage pools provided by Storage Spaces. However, in Windows Server 2012, automated error-correction is only supported on mirrored spaces, and booting from ReFS is not supported either.

IIS 8.0
Windows Server 2012 includes version 8.0 of Internet Information Services (IIS). The new version contains new features such as SNI, CPU usage caps for particular websites, centralized management of SSL certificates, WebSocket support and improved support for NUMA, but few other substantial changes were made.

Also View :

Resolving VS 2010 solution deployment issues for SharePoint 2010 projects

In my new SharePoint 2010 book, I touch base on variety of deployment approaches; in this article I wanted to focus on Visual Studio 2010 feature allowing to deploy SharePoint 2010 solutions right to the portal. However, you haven’t configured your development environment properly – you will run into issues. Here I’m talking about the following error:

Error occurred in deployment step ‘Recycle IIS Application Pool’: The local SharePoint server is not available. Check that the server is running and connected to the SharePoint .

Or this:

Error occurred in deployment step ‘Recycle IIS Application Pool’: Cannot connect to the SharePoint site: http://localhost/. Make sure that this is a valid URL the SharePoint site is running on the local computer. If you moved this project to a new computer or if the URL of the SharePoint site has changed since you created the project, update the Site URL property of the project

Visual studio uses the following process to deploy your solution: vssphost4.exe
Open your task manager and find the process in the list; take a note of the User Nameunder which this process is running, let’s say it’s myadmin_account

Now, open your SQL Management Studio and ensure this Username is added as a DBOWNER to the following databases:

SharePoint_Config
SharePoint_AdminContent_[guid]
SharePoint Site Content DB

sql-permissions

Close and Open your Visual Studio again, this will ensure the service is recycled; this should fix above deployment error. If you’re still having same issue, End the process in taskmanager and then VS 2010.

Good luck!

Ref : Sharemuch

Excel Services: Unable to process the request

Error

This error message appeared in a SharePoint 2010 farm/environment when trying to use Excel Services to display a Excel spreadsheet in SharePoint 2010.

image_thumb

Excel. Unable to process the request. Wait a few minutes and try performing this operation again.

After reviewing the Events and log files and finding error messages such as these:

image_thumb2

 

Event Viewer: Event 5239, Excel Services Application. There was an error in communicating with Excel Calculation Service (server address on port 32843, standard port for web services address ending with /ExcelService*.asmx) exception: The underlying connection was closed: An unexpected error occurred on a receive.

Issue

The issue was that the web site used for the SharePoint Web Services had the ASP.NET Impersonation Authentication method enabled.

Solution

The solution is to disable the ASP.NET Impersonation again.

Go to IIS Manager (Start, Administrative Tools, Internet Information Services (IIS) Manager). Expand the Sites node on the server running the Excel Services Service Application. Choose the Authentication icon in the IIS area. Choose ASP.NET Impersonation in the list and disable it using the action link on the right hand side.

image_thumb3

IIS Manager, Authentication settings for the SharePoint Web Services.

Ref : Stefan Johansson

VS Debug Problem with IE8

I decide to write about a problem that has been opened frequently on ASP.NET official forum which is VS debugger crashes with IE8.

How VS debugger could be crashed with IE8?

If you opened multiple instances of IE8 and you attempt to debug your project, you mostly will have the issue where VS debugger just stops and ignores your break points!

Why was that?

Well, IE 8 has a feature called Loosely-Coupled Internet Explorer (LCIE) which results in IE running across multiple processes.
http://www.microsoft.com/windows/internet-explorer/beta/readiness/developers-existing.aspx#lcie

Older versions of the Visual Studio Debugger get confused by this and cannot figure out how to attach to the correct process.

To overcome this issue, you need to disable the process growth feature of LCIE by follow the below steps:

1) Open RegEdit
2) Browse to HKEY_LOCALMACHINE -> SOFTWARE -> Microsoft -> Internet Explorer -> Main
3) Add a dword under this key called TabProcGrowth
4) Set TabProcGrowth to 0

If you run into the same problem on Vista or newer, you will also need to turn off protected mode.

And then go a head and start debugging your code.

Ref : Weblogs Asp.Net

Session TimeOut manually in web.config

if you would like to set Session TimeOut manually in web.config as 24 hours.

Solution : 

Use timeout in web.config, can also use timespan–20 minutes is default, also The timeout attribute cannot be set to a value that is greater than 525,601 minutes (1 year) for the in-process and state-server modes.

<sessionState
mode=”[Off|InProc|StateServer|SQLServer|Custom]”
 timeout=”number of minutes”…………

……/>

If you are using ASP.NET 2.0, use have to check in the IIS.

Open the IIS, click on the Application Pools, Select the Application pool for your application.

Right Click on that, Select Properties.

In the Performance tab, Set the idle timeout as your desired minutes for “shutdown worker processes after being idle for ….. minutes”.

Hope this works.

How to disable the process termination by IIS when debugging

When you are writing code for your SharePoint solution, you’ll probably be testing and debugging that code as well. You deploy your solution, attach Visual Studio to the worker process and when the debugger hits the break-point, you examine what happens and read the values of your variables at that moment. And before you know it, you get the message that IIS has terminates the process that was being debugged.

The Windows Process Activation Service (WAS) pings an application pool’s worker process at set intervals for monitoring. If a worker process is non-responsive, WAS can shut it down. This WAS pinging is enabled by default and the interval is set to 90 seconds.

To avoid this you can either disable the Ping Enabled setting of the application pool of your web application or increase the Ping Maximum Response Time. From the Administrative Tools menu, start the Internet Information Services (IIS) Manager and expand your server. Select the Application Pools node. In the Application Pools list select your application of your web application and click on the Advanced Settings link.

Now set Ping Enabled to false (or increase Ping Maximum Response Time to 900) and save your settings by clicking the OK button.

Reference : Blog by Octavie