Properly Install SharePoint 2013 Prerequisites Offline

This goes for SharePointers who get stuck at the point of Installing SharePoint Servers mostly in production environments which are not usually granted for internet access. And also sometimes when you try to install SharePoint prerequisites through SharePoint Installer on Windows Server 2012/R2, it doesn’t run and gives error Occurred massage. This is because some of the features that readily bundled on windows Server 2012 (IIS and .NET related) and therefore the SharePoint Prerequisites Installer skipping them and rests aren’t performed too.

This is my scenario (With Windows Server 2012 + SQL Server 2012) and here are the steps I taken to get it done manually instead of trying prerequisites.exe.



Not a big deal. Just few steps to complete in the proper order.

Download All the prerequisites including Windows Server Feature Installer Script is here In my Share – https://onedrive.live.com/redir?resid=B998091330BF06C9!6177&authkey=!AFMPJmHtSAVbylA&ithint=file%2c.zip

Steps.

1. Install the Windows Server Features and Roles Required is the first thing. I used a cool script from ‘Craig Lussier’ to get this done. Even through the script there are two ways that you can Install the Prerequisites, either Online (By Switching ‘O’) or offline (By Switching ‘F’) for the prompted parameter in the script when you execute it. Continue this Offline you should have your Windows Server 2012 media inserted your server.

Run the Windows Feature Installer Script which is from "Craig Lussier" – This will install all the Windows Server features and roles required for SharePoint. – Don’t Forget to "Set-RemotePolicy RemoteSigned" before you excecute the Script.

You need to restart the server after the this. just say yes to the script.



2. Now Let’s Install rest of the things manually in below order:

• Install "microsoftidentityextensions-64"
• Install "synchronization"
• Install "setup_msipc_x64"
• Install "WcfDataServices"
• Install Sqlncli (SQL Native Client)
• FilterPack 3.0 – Install Manually from the "prereqsuiteinstallerfiles" folder inside your SharePoint Setup. the relevant version of FilterPack in always comes with the SharePoint Setup under PrerequisitesInstallerFiles Folder.
• Copy the App Fabric RTM Setup to C:drive and run – $file = “C:\WindowsServerAppFabricSetup_x64.exe” & $file /i CacheClient”,”CachingService”,”CacheAdmin /gac

• Now Install the App Fabric Update 1 Manually (AppFabric1.1-RTM-KB2671763-x64-ENU)



3. Open up SharePoint Installer exe and see whether it asks for any missing prerequisites. If everything went well, you will only see the "Restart Required" Massage.



4. and Finally Restart the Server

You Should be able to Install SharePoint without any issues now !

Surely I will be posting another one for rest of the Windows and SQL Versions..

Advertisement

The Ultimate SharePoint Business Intelligence – Setting up SharePoint 2013 Demo with SQL 2012 PowerPivot and Visio Services Step by Step

– Elaborate Real Strength of SharePoint in Business Intelligence Perspective –

Earlier We supposed to download Information worker (IW SharePoint) SharePoint Demos in SharePoint 2010 and 2007 Days as Virtual Disks which takes lot of time to download due to the size of the HDDs and VM Machine Configuration flies. IW 2010 Came out as a single box along with AD | SQL | SharePoint all in one and Exchange Server Separately as another Box.

The one I’m stepping today is an great Demo Setup for those who were waiting to elaborate and Demonstrate Real SharePoint 2013 BI which is the ultimate goal of Having SharePoint in place at Enterprise Organizational level. Microsoft has not released IW Setup for SharePoint 2013 yet but instead CodePlex has done a great job on sharing such a setup together with Microsoft Tools and Content Packs of their Demos. Really Appreciate the developers who did this outstanding job for the global SharePoint Community.

This setup demonstrate real awesomeness of SharePoint BI together with SQL PowerPivot for SharePoint and Visio Services. Once you set it up you will get various types of Reports | Dashboards | Workflows etc.. So before we begin have a look at below captures of the real output I got through this !

1. The Giant SharePoint BI with PowerPivot            2. The Ultimate Visio BI

                 

3. People Sites (My Sites) and the great New SharePoint Profile Look in Social Perspectives



This is only a PowerShell based script which can be easily downloaded from CodePlex and run on a Prepared VM. It also contains documentation for each package you download but since it doesn’t have screenshot and steps on preparing AD I thought of writing this article with step by step screen shots and little bit of experienced issues and troubleshooting.

Below are the steps (Installation Order) that we will take to prepare this lab. Following this order to install is Important

1. Download Scripts from Codeplex
2. Create a Virtual Machine with Recommended configurations
3. Install Prerequisites on top of Created VM
4. Configure Active Directory and DNS
5. Execute AD Builder Script
6. Execute SQL Script
7. Execute SharePoint Script
8. Execute People Pack Demo Script
9. Run PowerBI Deme Script
10. Configure PowerPivot For SharePoint 2013
11. Execute Visio Services Demo Script

Download Below Scripts

1. Active Directory Content Pack Demo 2.0
2. SQL 2012 SP1 Content Pack Demo 2.0
3. SharePoint 2013 Configuration Demo 2.0
4. PeoplePack – UserProfile Provisioning Demo 2.0
5. Self-Service BI Demo 2.0 Content Pack
6. Visio Services Demo 2.0 Content Pack

For More Refer – http://sharepointdemobuilds.codeplex.com/

Media Requirements

• Windows Server 2012 / R2 Standard
• SharePoint Server 2013 – This Setup seeking for SharePoint 2013 RTM Version (15.0.4420.1017). Later versions with Service packs and Cumulative packages will not be able to restore the backups during the script execution. – Download Here: http://technet.microsoft.com/en-us/evalcenter/hh973397.aspx http://technet.microsoft.com/en-us/evalcenter/hh973397.aspx
• SQL Server 2012 Enterprise with Service Pack 1 – Download Here: http://technet.microsoft.com/en-us/evalcenter/hh225126.aspx

So Let’s get this done. So excited isn’t it ? I was too !!

First Create a VM (Hyper V or VMware) with Minimum of 16 GB Ram together with 4 Virtual Processor Cores. You can run with less resources but it won’t perform really well since it runs three major roles (All in one – SQL, SharePoint and AD) together with all SharePoint Services and three SQL Instances.

Map the Windows Server 2012 Media in to Virtual Machine, Start it and boot it using Windows Server. Once Windows Is installed give the Administrator’s Password as – pass@word1. across the whole setup all the user and Service accounts will be using this password to make it easier of using.

Then after Windows Installation, modify the Local Machine name as – DEMO2013A from the Server manager. All the scripts will be referring to this name so it’s compulsory to use the same name.

Log-in to the VM as ‘Contoso\Administrator’

Give a Static Class C address to your Virtual Network Adaptor (e.g. 192.168.150.101).

Step 1 – Installing Windows Server and Configure Active Directory with DNS

Assuming you have followed above steps to install and configure Windows Server.

Next is to Add AD Role from the server manager: Prerequisites – Static IP for Primary Adaptor (for DNS Role)

Simply Click ‘Next’ here

Leave with the Default option here and ‘Next’

Here too it’s default and click ‘Next’

Choose the Server role here – Just ‘Active Directory Domain Services’ and ‘DNS Server’ we need. Click Add to include the chosen one and ‘Next’

Nothing to do here so simply hit ‘Next’

Summary will be displayed here. Review it and hit ‘Install’ to proceed.

Give it a moment. Probably it will take 6-8 Minutes. Depends on your HW resources

Once you are done with the Role installation. The completion pop up will be prompted, Click on the Link ‘Promote this server as a domain’ to configure AD DNS.

Below Wizard will Appear. Nothing to think much just Put the domain name and hit next (Its compulsory to put it as – ‘Contoso.com’ here )

Choose Windows Server 2012 in both Functional Levels and Leave the password with something you remember if in case of recovery (this isn’t the common password we use often in this setup)

Leave these defaults as well

Review it and go ahead

It will check all the prerequisites and validate. Click ‘Install’ to proceed.

Finally you will get this banner across so let it restart the server automatically.

Once restarted launch it will launch the Server manager. You should be able to see the new roles added.

Go to DNS Tab and right click and Launch the DNS Manager from there.

It will Launch the DNS Manager UI. Right Click and Create a new Reverse Look up zone via ‘New Zone’

Hit ‘Next’

Leave with the Defaults here and ‘Next’

Here you have to bring the tick up. Choose the ‘first option’.

Leave the Defaults Here too

Give the network address of your Adaptor here.

Go with the Defaults again

Click finish to Complete the wizard.

Now Expand the Reverse Lookup zones and right click on New Zone we just Created and ‘New Pointer PTR’

Give the IP of your Server Adaptor here and browse to get the Host Name from Forward Lookup Zone.

It will look like below once added.

Now Configure the Local Server adaptor as below

Right click on Server Name under ‘DNS Manager’ and click ‘Launch NS Lookup’. It Should Resolve the Name as below

Now we got few Setting to be configured which are important for moving with further steps.

Launch Windows Powershell as Administrator and type ‘Set-ExcecutionPolicy RemoteSigned’ and hit ‘Enter’

Launch the Server Manager and turn off Windows Firewall for Domain Networks, Remains ‘On’ for Private and Public. Remote Management and Remote Desktop must be Enabled too.

And then Turn off the ‘IE Enhanced Security Configuration’ as well.

Step 2 – Building AD for SharePoint and SQL (This will Create all the Active Directory Objects for SharePoint and SQL Such as user Accounts and Service Accounts)

Log-in to Server as contoso\administrator and Copy the Downloaded AD Script (ActiveDirectoryDemo15.2.3) to Server (make a folder in C: Drive and copy there). Unzip it and you will see the ‘ContentPackInstaller.exe’ utility there. Right Click on it and Run as Administrator.

Note: There are two ways that you can run these packages hereafter. You don’t need to run ContentPackInstaller every time, instead you can simply run them through Windows PowerShell. Simply run below line customized with each Package Name and Path.

Prerequisites:

1. AD, DNS Configured

2. Security Settings Configured (Firewall, IE Enhanced Security, Remote Management etc..)

3. Excecution Policy Modified (Set-ExecutionPolicy RemoteSigned)

4. ActiveDirectoryDemo15.2.3 Package Downloaded and Copied to VM

Locate to the Extracted Folder from PowerShell and run below Line (When use PowerShell it has to be Extracted)

.\Install http://intranet.contoso.com (This URL Depends on the Package you Deploy. e.g. for People Pack you have to use http://mysite.contoso.com)

e.g. :-

If you use ContentPackInstaller, When you run it first time you get the below choices. Go with Defaults here. (No Need to Extract When use Tool) and click ‘Next’

Browse the AD Content Pack (Zip File) and Click ‘Add’

Hit ‘Install’ to proceed

Leave the Default URL Here and Click ‘Ok’

Give It a Moment… This will Probably Take 3-4 minutes

Once done you will see it under installed packs. It will also generate the result in a Report and open up automatically right after the completion. So this completes our first package Installation which creates all the Demo AD Objects for SharePoint and SQL.

Step 3 – Install SQL Content Pack

Prerequisites:

1. AD, DNS Configured

2. Security Settings Configured (Firewall, IE Enhanced Security, Remote Management etc..)

3. Execution Policy Modified (Set-ExecutionPolicy RemoteSigned)

4. SQL Server 2012 With SP 1 ISO has to be mapped to VM as ‘D:’ Drive

5. SQL2012SP1Demo15.2.5 Content Pack File Copied to VM

6. Logged in to the VM as ‘Contoso\spadmin’ (Password is same for all the Accounts in this setup which is – pass@word1)

Here also You can Simply User PowerShell to Execute this. I’ll be showing the way through the tool. (as always PowerShell if Preferred and Reliable)

Same as the Previous Step, Browse and Locate the ‘SQL2012SP1Demo15.2.5’ Zip File and hit ‘Install’

URL is Default here (http://Intranet.contoso.com) so simply click ‘OK’

This will probably take 15-30 Minutes Depends on your resources. It installs 3 SQL Instances specifically for SharePoint Databases, PowerPivot requirements.

Once Completed It will also Generate and automatically open up the Result.

Step 4 – Install SharePoint Content Pack

Prerequisites:

1. AD, DNS Configured
2. Security Settings Configured (Firewall, IE Enhanced Security, Remote Management etc..)
3. Execution Policy Modified (Set-ExecutionPolicy RemoteSigned)
4. SQL2012SP1Demo15.2.5 Content Pack Installed
5. SharePoint Server 2013 RTM Media Copied to VM as ‘D:’ Drive (Required SP Version : 15.0.4420.1017 RTM – Do not use the latest releases which may not be able to restore the backup files through the script in the next steps)
6. All SharePoint Prerequisites are Installed
7. Logged in to the VM as ‘Contoso\spadmin’ (Password is same for all the Accounts in this setup which is – pass@word1)

First thing to get the SharePoint Server 2013 Binaries Installed (Do Not Run the Configuration Wizard. Entire Configuration handled through the SharePoint Content Pack which comes next)

Go ahead and Run the SharePoint Installer.



Leave the File Locations Default here.



Give it a moment. It will take about 5-8 Minutes Depends on your Resources.



Now to Install the SharePoint Configuration Content Pack. Here also I’ll be using tool but you may use PowerShell which is more reliable.

As Usual browse and point to the ‘SP2013ConfigDemo15.2.6.zip’ file and click ‘Install’ to start



URL Must be Default here as well.



It will automatically Launch the PowerShell and run below script. If everything is green you are cool.



Give it a Moment. This will take about 15-25 minutes Depends on your Resources.



Keep Monitoring !. You will notice the success through below lines on the Shell. User Access Control will prompt for PowerShell sometimes during this process so keep monitoring to click yes each time.



When Everything Completed it will open up the log file through WordPad.



Go Ahead and explore IIS. You will see the Web Applications has been created for each Purposes.



And Yes all three sites (Central Admin, MySite, Intranet) will be opened up automatically as well.





Step 5 – Install PeoplePack Content Package

Not yet Impressive this guy. So Next is People Pack to deploy which will upload all the nice profile images to Active Directory and Syncing Automatically to SharePoint through User profile Service App.

Prerequisites:

1. AD, DNS Configured
2. Security Settings Configured (Firewall, IE Enhanced Security, Remote Management etc..)
3. Execution Policy Modified (Set-ExecutionPolicy RemoteSigned)
4. SQL2012SP1Demo15.2.5 Content Pack Installed
5. SharePoint Content Pack Installed
6. ‘PeoplePack’ (PeoplePackDemo15.2.8) Content pack Copied to VM
7. Logged in to the VM as ‘Contoso\spadmin’ (Password is same for all the Accounts in this setup which is – pass@word1)

As Usual browse and point to the ‘PeoplePackDemo15.2.8.zip’ file and click ‘Install’ to start

Reminding Again that You don’t have to use Tool each time, just execute PowerShell lines instead if you are comfortable with it.



Leave the Path Default (It will refer to MySite URL Automatically here so do not change). Simply click ‘OK’ to start



Before You Start Make Sure the Forefront Identity Manager Service is up (coz this happens all the time when you setup a new SharePoint Environment). If it’s Not Go ahead and set it to Automatic and Start it Manually. (But the Identity manager Synchronization must be already Running else you may got a different issue with Service Account Permissions etc..)



Give it a Moment here. It will take probably 15-25 Minutes to Complete the Profile Updates and Synchronization. And keep monitoring as it’s really cool to see how each profile Being Updated through Shell during the Process !!.







Once Completed it will generate the report as usual.

If you browse the MySite through a general user you will see the updates. Or else just type a user Name like ‘Paul’ in Search Box, if everything went well you may see all the picture has been updated.



Step 6 – Install Self Service BI Pack

Next is to run the BI Pack. This Script configures the SharePoint BI Site with Samples which is the main module of this Demo. During this process it restores few Databases from backups located inside the package Folder.

Prerequisites:

1. AD, DNS Configured
2. Security Settings Configured (Firewall, IE Enhanced Security, Remote Management etc..)
3. Execution Policy Modified (Set-ExecutionPolicy RemoteSigned)
4. SQL2012SP1Demo15.2.5 Content Pack Installed
5. SharePoint Content Pack Installed
6. ‘PeoplePack’ (PeoplePackDemo15.2.8) Installed
7. ‘Self-ServiceBIDemo15.2.7’ Package Copied to VM
8. Logged in to the VM as ‘Contoso\spadmin’ (Password is same for all the Accounts in this setup which is – pass@word1)

Launch the tool and Locate the Self-ServiceBIDemo15.2.7.zip then add it as usual. Then Install



Leave the Path Default here. This will take about 6-10 Minutes depends on your resources. Once completed you will be able to see the Result opened automatically on WordPad.



Step 7 – Configure PowerPivot for SharePoint 2013

Prerequisites:

1. AD, DNS Configured
2. Security Settings Configured (Firewall, IE Enhanced Security, Remote Management etc..)
3. Execution Policy Modified (Set-ExecutionPolicy RemoteSigned)
4. SQL2012SP1Demo15.2.5 Content Pack Installed
5. SharePoint Content Pack Installed
6. ‘PeoplePack’ (PeoplePackDemo15.2.8) Installed
7. ‘Self-ServiceBIDemo15.2.7’ Installed
8. Logged in to the VM as ‘Contoso\spadmin’ (Password is same for all the Accounts in this setup which is – pass@word1)

To do this, Launch the PowerPivot for SharePoint 2013 Tool from the Start menu of the VM.



No option here except the First one so click ‘ok’ and go ahead



Give it a Moment



Once the validation Complete you will get below Interface. Fill the Parameters by Providing the account Details as below and hit ‘Validate’

– Default Account UserName – contoso\spservice

– Default Account Password – pass@word1

– Default Server – DEMO2013A

– PowerPivot Server – DEMO2013A\POWERPIVOT



If the validation Succeeded, you are getting this pop up. So click ‘ok’ to proceed.



Once Validation Successful, just Run It by saying YES here.



Give it a while. Probably 5-8 Minutes.



It’ll update the status like below In the Middle of the Process so keep monitoring.



Finally the Success massage is here.



This step completes the Self Service BI Model so now go ahead and Install the Silverlight on VM then try to Explore the Self Service BI Site, It will display the Site like a charm. Have a look below.



Step 8 – Install Visio Service Content Pack

So the final Step is to get the Visio Service Demo Installed. This step Completes the whole setup of our Demo.

Prerequisites:

1. AD, DNS Configured
2. Security Settings Configured (Firewall, IE Enhanced Security, Remote Management etc..)
3. Execution Policy Modified (Set-ExecutionPolicy RemoteSigned)
4. SQL2012SP1Demo15.2.5 Content Pack Installed
5. SharePoint Content Pack Installed
6. ‘PeoplePack’ (PeoplePackDemo15.2.8) Installed
7. ‘Self-ServiceBIDemo15.2.7’ Installed
8. VisioServiceDemo Package Copied to VM
9. Logged in to the VM as ‘Contoso\spadmin’ (Password is same for all the Accounts in this setup which is – pass@word1)

Browse and Point to the ‘Visio Service Demo Zip’ File. And Install



Install path should be the Default as below.



It will launch the Result on WordPad Once it completed as usual so This completes the entire Configuration of the Demo.

Go ahead and Open up http://Intranet.contoso.com/Sites/Visio

Known Issues:

1. You will get below Error on PowerShell if you haven’t run the – Set-ExecutionPolicy RemoteSigned

.\Install.ps1 : File C:\SharePointBIDemoBuilderWithSQL2012\PeoplePack\PeoplePackDemo15.2.8\Install.ps1 cannot be

loaded. The file C:\SharePointBIDemoBuilderWithSQL2012\PeoplePack\PeoplePackDemo15.2.8\Install.ps1 is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting

execution policy, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.

At line:1 char:1

1. The-term ‘Get-SPServiceApplication’ is not recognized as the name of a cmdlet, function, script file, or operatable program.



For this issue you have to Put below highlighted line in the Install.ps1 script in each Package



Also Make Sure the Relevant Files are Unblocked through their Properties



1. Sorry This Site Hasn’t been Shared With you. http://Intranet.contoso.com/Sites/Visio Site Isn’t accessible.

This is simply because Spadmin doesn’t have rights on Particular Site Collection. To resolve this open up Central Administration and Add SPADMIN as the Site Collection Admin for Visio Site Collection under Intranet.Contoso.com Web Application.

 

Obtain Service Pack 1 for SQL Server 2012

Microsoft Announced Service Pack 1 for SQL Server 2012 on November 2013 and here is the full list of Fixes/Improvements included with it – http://support.microsoft.com/kb/2674319/en-us

Improvements of SQL 2012 SP1 in SharePoint Perspective 

One of the major reason to Obtain SQL 2012 Service Pack 1 in SharePoint Environments is that you cannot enable SQL Server Reporting Instance without having SP1 which was the reason for me to obtain this. when you trying to enable SQL Server Reporting for SharePoint, You may get the issue in SharePoint Management Shell saying "The term ‘Install-SPRSService’ is not recognized as the name of the cmdlet".

Installing SP 1 for SQL 2012 resolved the above issue for me.

Take below steps to Obtain the SQL Service pack 1.

Note:

1. Make sure that you test this in a Staging environment before update your production SQL.
2. Also there is an mandatory KB (Non Security Update for SQL Server 2012 SP1 [KB2793634]) which needs to be Installed after SP1 Installation. This KB will fix "windows Installer Starts repeatedly" issue. Get in here to know more about known issues on SP 1 – http://blogs.msdn.com/b/psssql/archive/2013/07/31/after-applying-service-pack-1-for-sql-server-2012-you-may-encounter-a-known-issue-details-inside.aspx

1. Download SP 1 for SQL 2012 here – http://www.microsoft.com/en-us/download/details.aspx?id=35575. And run it on your Server

2. Accept the license Terms

3. Select the Features that you need to Update and hit next

4. Give it a moment

5. Hit "Update" to Install

6. It will take a while and make sure that your users are not using any services related to SQL.

7. If everything went well, you will get the below green lights on each feature.

8. Go ahead and now install the KB mentioned above

9. Restart the Server and you are done with the update !

Failed to create a database. An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: Could not find stored procedure ‘sp_dboption’. – Error Occurred when Installing SharePoint 2010 in SQL 2012.

got a new server for my Test environment and started creating a lab of SharePoint 2010 in it with SQL Server 2012 R2. everything went smoothly until I start Configuration Wizard. It came to the 3rd Level and Error Occurred suddenly saying – Failed to create a database. An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: Could not find stored procedure ‘sp_dboption’.

After thinking a while realized that my setup was just SharePoint 2010 RTM which is None SP. since my lab is brand new thought of trying on installing SP1. just downloaded and installed the SP1 for SharePoint 2010 and started the wizard again.

Everything Gone perfect after SP1. further when reading understood that it’s must to have SP1/above for SharePoint to install in SQL 2012.

Download SharePoint SP1 here – http://support.microsoft.com/kb/2460045

All SharePoint Updates are here – http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx

Error When Creating new Database on Clustered SQL Environment

Recently I got an Clustered SQL 2012 environment created with two nodes as I needed to deploy SharePoint 2013 on it. SharePoint Installation gone well but I got below error when I’m tying to create a new web application.

“Cannot use file ‘D:\MSSQL11.MSSQLSERVER\MSSQL\DATA\WSS_Content_7777.mdf’ for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the SQL Server does not have a dependency on it. CREATE DATABASE failed. Some file names listed could not be created. Check related errors.”

tried though SQL Management Studio to create a new DB in order to verify and it gives the same error. so it should be from SQL cluster side for sure.

 

 

 

 

anyway, we love these kind of little damns because always we learns something though them. let’s find out what it is.

when I look at the error it was clearly mentioning something about Dependency. so yes obviously my cluster is brand new. didn’t fine tune well because was bit hurry on deployment of SharePoint.

So it’s all about Configuring Dependency from Windows cluster.

1. SQL Server depends on the Network Name and a Disk Resource.
2. SQL Network Name depends on the IP Address.
3. SQL Agent depends on SQL Server.
4. The IP Address and the Disk Resource do not depend on anything.

generally SQL prevents the creation of Databases on volumes which are not Dependency of SQL Server resources. So The point of having dependencies is to prevent situations where SQL Server comes online before the disk containing the data goes on line. Therefore the term “DEPENDANCY.”

Let’s see how we can add the dependencies to get this fixed. by the way you don’t have to do this once you got a new clustered environment created as The dependencies are automatically established when you create the SQL cluster. but if you substitute any disk resources don’t wait till the error remind you for it, you have to add the dependencies.here in my case it was the point, I added some disk resources and I forgot to re-add the dependencies .

Open Failover Cluster Manager –> Select your clustered application (SQL) –> Right-click on your SQL Server resource then click Properties –> Click on the Dependencies tab –> Click the Insert button to add an additional row, then select the shared disk that contains your SQL databases –> Ensure that all resources are required (there is an AND next to subsequent resources) then click OK.

The Following Illustrate the Resource Settings of SPLAB which is my testing environment.

• The Name Depends on the IP Address

• IP Address does not depends on anything

• If Analyses services are Installed, it depends on the Network Name

• Cluster Disks has no Dependencies

• SQL Server has Dependencies of Disks and Network Name

• And Finally Agent depends on SQL Server

once all these added. you done !