OneDrive Files Accidental Deletion and Recovery within 93 Days!

 

If you have accidentally deleted your OneDrive files, then no need to worry. You can recover it from your OneDrive's recycle bin. You might also receive a warning email from SharePoint Online (no-reply@sharepointonline.com) Microsoft support team similar to the one listed below

Files are permanently removed from the online recycle bin 93 days after they're deleted

Hi Rinith KT, We noticed that you recently deleted a large number of files from your OneDrive. When files are deleted, they're stored in your recycle bin and can be restored within 93 days. After 93 days, deleted files are gone forever. If you want to restore these files, go to the recycle bin. Select what you want to restore, and click the Restore button. Ignore this mail if you meant to get rid of these files. Learn more about deleting and restoring files.

SharePoint Farm Configuration details

Make sure you have the SharePoint Farm Configuration details in your DR activity battle box

Go to codeplex website and download SPSFarmReport preferably on the SharePoint CA server (FE Server) or any one of the SP Farm

http://spsfarmreport.codeplex.com/

SPSFarmReport\SPSFarmReport\o15

Execute the PowerShell script file SPSFarmReport.ps1 via elevated PowerShell window using the account which has privilege to all farm including BE. This will generate an output XML file "2013SPSFarmReport11102016-40757.xml" in the same folder where the script file is located. Open the xml file using in IE. SP2013 Farm Configuration will be listed in detail.

Slipstreaming Patches into SharePoint 2013

Slipstreaming Patches into SharePoint 2013

Category: SharePoint 2013

Now that the latest CU is out we have a patch to play with. And this isn’t a normal patch. This patch is important. It will have to be installed in order to install any future patches. You should consider this the base version of SharePoint 2013, especially for new farms. One of the first things I wanted to test was slipstreaming the patch. The news was good, it’s the same process we used with SharePoint 2010. Just extract the update files into the Updates directory before you install SharePoint 2013. Nothing to it.

Let’s see how it looked when I did it. Here is what my directory structure looked like:

I copied the files from the SharePoint 2013 ISO into a folder in C:\Install. On a production system you would put this on a non C drive. After I copied the files over I peeked into the updates folder to see what’s in there. This is what I found:

That sounds delightful, let’s drop a patch in there and see what happens.

Extracting SharePoint 2013 patches follows the same process as SharePoint 2010, which you can find outlined in this brilliant blog post. Those are the instructions I used when writing this blog post. First I verified the March 2013 PU supported this.

Looks like it does. Let’s go ahead and extract it to our updates folder. After we accept the license terms our updates folder gets full of patch files.

Then install SharePoint 2013 the same way you normally would.

Please consider the environment before printing this email.

Disclaimer: This email and any attachment are confidential to the person to whom they are addressed.
If you are not the intended recipient, please inform the sender and delete the email and any attachment from your systems, without copying, forwarding or disclosing them.
WARNING: You should check this email and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by or with this email.

how to configure the “Replicating directory changes” for SharePoint 2013 via AD

How to configure the "Replicating directory changes" for SharePoint 2013 via AD

I can guide you in this matter by providing you with a reference and key points that may help you in your issue.

note that delegation to grant Directory Changes permission on a domain should be done on Root Domain level. The Replicate Directory Changes permission enables the synchronization account to read AD DS objects and to discover AD DS objects that have been changed in the domain. The Grant Replicate Directory Changes permission does not enable an account to create, modify or delete AD DS objects.

Reference:

https://technet.microsoft.com/en-us/library/hh296982.aspx?f=255&MSPPError=-2147217396#RDCdomain

Network Load Balancing and Virtual Machines: Tuneup

SharePoint 2010 Web-Front-End NLB Tuning (points to be noted before configuring Network Load Balancing and Virtual Machines on Windows Server 2008 R2):

When running NLB as a Virtual Machine (VM) guest using Windows Server 2008 R2 Hyper-V you need to be aware of some specific configurations settings in Hyper-V host prior to configuring NLB. If you do not enable spoofing of MAC address prior to configuring NLB on the VM you could potentially have problems with the NLB cluster. 

When configuring NLB in unicast mode on Hyper-V with enable spoofing of MAC Address disabled you may see some of the following symptoms:

• When initially configuring NLB you will lose network connectivity on the network adaptor NLB was configured on.
• Either of the nodes NLB status might show converging instead of converged and healthy status.
• There will be an NLB error event in the Windows Event Log stating that the network adaptor does not support dynamic MAC address updates.
• After rebooting the server, NLB will appear to be bound to the network adapter, but the cluster VIP will not have been added to the network adaptor.
• The cluster MAC address will still be the original MAC address associated with the network adaptor prior to configuring NLB.   Use CMD> ipconfig /all to view the MAC address.  It should start with "02-BF-***"
• If you ignore all previous symptoms and manually add the VIP you could get an IP conflict if there are other nodes in the cluster that have the same VIP.

With that said, to allow VM guests to run NLB you need to set the VM property for "Enable spoofing of MAC Address". 

To enable spoofing of MAC Addresses open the Hyper-V management console.  Make sure the VM is stopped open the properties of the VM.  Select the Network Adaptor for the NLB VM and check the "Enable spoofing of MAC Address" and click OK.  Then start the VM.

also refer articles from technet here http://technet.microsoft.com/en-us/library/cc917873.aspx

Real-Time Intranet (SharePoint) Replication: Production Site to Disaster Revovery Site

SharePoint 2010 real-time replication to the Disaster recovery site using third-party tool; DocAve from AvePoint is one among them

We have been using this software for SharePoint replication since last 4+ years. It's a wonderful software designed for MOSS 2007 & SharePoint 2010 environment. Lot of features are embedded to it. We just got replication module licensed as replication from production site to DR Site was our concern. All we have to do is to first restore the destination site using the latest SQL DB site level backups. We used an independent server for the DocAve Enterprise manager. DocAve 6 Client Plug-ins were installed on the below Web Front-End servers of both source and destination site. That's it. The configuration is pretty simple. It does real-time replication instantly in less than a minute.

We had slight issues when we activated real-time replication. However, the issue got stabilized after re-scheduling the replication method to trigger incremental replication after business hours. Accessing database from different process like backup plan and real-time replication plan could have been a conflict.

Check my other postings on:

SharePoint 2010 content level backup using Symantec Backup Exec

Three-Tier SharePoint 2010 Architecture

SharePoint 2010 content level backup using Symantec Backup Exec

..after our recent upgrade from MOSS 2007 to SharePoint 2010, we had to re-think about real scenario restoration; balancing compliance with the organizational SLAs.

Never we had a second thought that we should rely on with one kind of backup for our infrastructure. So we bridged 4 kinds of SharePoint backups including real-time replication functionality from third party vendors.

• Backup using SharePoint STSADM command which starts with a script and alerts the completion status.
• SQL Content DB level backups
• SharePoint 2010 content level backups from Symantec Backup Exec
• Real-Time replication to the disaster recovery site using AvePoint's DocAve replicator.

I'm also testing the SQL mirroring which would eventually eliminate the third party applications for replication. The only hurdle is huge database data transfer over MPLS line and fine tuning and enabling proper listner ports. I will shortly achieve that.. anyhow, I'm highlighting below the only issue what we encountered during 3rd party content backup.

Issues and remediation:

using Symantec Backup Exec 2010R3, server farm addition ended up with error: "none of the web servers for the specified server farm could be accessed"

adding backup exec system account (BESA) to the SP Farm Admin's group and addition of BESA to SharePoint's BE DB server with public and sysadmin privilege sorted the issue.

Sharepoint Farm visible from Backup Exec application

here you can restore a single file, site or anything which went erroneous before the previous backup.

note: make sure you have a valid SharePoint per server license from the vendor.

ref: http://www.symantec.com/business/support/index?page=content&id=TECH139224&actp=search&viewlocale=en_US&searchid=1338968135697

Three-Tier SharePoint 2010 Architecture

-  Uninterrupted SharePoint 2010 Farm

-  Scalable SharePoint Farm 

-  wfe cluster scalable upto 32 nodes

-  High availability SharePoint 2010 Farm

-  SharePoint 2010 Fail-over Farm

I had a great time during the migration process from MOSS 2007 (2-Tier) to SharePoint 2010 (3-Tier) architectural transition.
..migration was completed in April 2012.

Three-Tier SharePoint 2010 Architecture

network diagram showing 3-Tier SharePoint 2010 Farm: web front-end layer, application layer and database layer. The above architecture was successfully designed, tested and implemented by me.

The above scenario is scalable and highly available systems reliably provides an acceptable level of service with minimal downtime and finally easy to manage & maintain during patch management schedules.

Our aim was to:

* verify that each web request (http port 80) were distributed automatically to the available cluster WFE servers. .yes that’s how it works..!
* Shutdown WFE02 and make sure there is minimal downtime and automatic load distribution.. yes in case of abrupt failure of 1 web front end node, clients notices fraction of seconds delay in web response time however redundancy works magnificently as expected..! we will have sufficient time to plan and rebuild the failed server in such scenarios.

* Shutdown application layer and see if the intranet works uninterrupted... yes intranet works still uninterrupted..! coz.. 'Microsoft SharePoint Foundation Web Application' service runs only on WFE servers. Two other services which we enabled on wfe servers are: i) 'Search Query and Site Settings Service ' and ii) 'SharePoint Server Search' services.

* Shutdown Active SQL server and see if the Passive SQL server takes over or not.. yes it works..!

* Performance was superb..!

Three-Tier SharePoint 2010 Architecture 

showing uninterrupted farm in the event of multiple failures

network diagram showing 3-Tier SharePoint 2010 Farm with fail-over scenarios

microsoft reference

I have explained in my blog quick clustering steps for SQL 2008 R2 cluster and fail-over farm including best practices.

next steps:

our next step is to setup disaster recovery site and setup a test and development intranet environment.

so we have to scrap the existing disaster recovery intranet site and upgrade the architecture from 32bit to 64 bit OS.. from Server 2003 to Server 2008 R2 Enterprise and SQL 2005 32bit to SQL 2008 R2 64bit Enterprise edition environment and then upgrade Microsoft Office SharePoint Server (MOSS 2007) to SharePoint 2010. And finally start real-time replication from production farm to the disaster recovery farm.

currently we are using DocAve from AvePoint for real-time replication of SharePoint portal.

we can also achieve this directly from SQL DB replication technology, either via log-shipping or mirroring. however we will test this as the current databases are huge. ..I will shortly scribble the procedure while accomplishing this task

Best Practice: SharePoint 2010 - Take advantage of using Network Load Balancing (NLB)

Enhance performance of the application tier (WFE) servers by fine tuning NLB

You can specify that a filtering mode apply to a numerical range of ports. You do this by defining a port rule with a set of configuration parameters that define the filtering mode. Each rule consists of the following configuration parameters:

The virtual IP address that the rule should be applied.

The TCP or UDP port range for which this rule should be applied.

The protocols for which this rule should apply, including TCP, UDP, or both.

The filtering mode that specifies how the cluster handles traffic described by the port range and protocols. In addition, you can select one of three options for client affinity: None, Single, and Class C. Single and Class C are used to ensure that all network traffic from a particular client be directed to the same cluster host. In order to allow Network Load Balancing to properly handle IP fragments, you should avoid using None when selecting UDP or Both for your protocol setting. Also the rules entered on each host in the cluster must have matching cluster IP addresses, port ranges, protocol types, and filtering modes.

Reference: http://technet.microsoft.com/en-us/library/cc778263(v=ws.10).aspx

Network Load Balancing references the dedicated IP address only when a single network adapter is used to handle both client-to-cluster traffic and other network traffic that must go specifically to the dedicated IP address. Network Load Balancing ensures that all traffic to the dedicated IP address is unaffected by the Network Load Balancing current configuration, including:

When this host is running as part of the cluster

When Network Load Balancing is disabled due to parameter errors in the registry

Typically, both the dedicated IP address and the cluster IP address, entered during setup in the Network Load Balancing Properties dialog box, must also be entered in the Internet Protocol (TCP/IP) Properties dialog box. Make sure that the addresses are the same in both places (in fact cluster ip address is automatically added to all cluster servers at the time of NLB convergence)

Reference:  http://technet.microsoft.com/en-us/library/cc778263(v=ws.10).aspx

Multicast support is not enabled by default. To enable it, see Enable multicast support. However, if you do not enable multicast support, you are advised to consider using at least two network adapters (with one network adapter dedicated to handling client-to-cluster traffic) in order to achieve optimum performance and the full range of networking functionality. For more information, see Multiple network adapters and Optimizing network performance

Reference: http://technet.microsoft.com/en-us/library/cc778263(v=ws.10).aspx

following article specifies the IIS response to Load-Balanced Application Pool Behaviours

http://technet.microsoft.com/en-us/library/cc757659(v=WS.10).aspx

following article specifies the Best Practices used for configuring NLB.

http://technet.microsoft.com/en-us/library/cc740265(v=ws.10).aspx

Network Load Balancing at its best for SharePoint 2010

Configuring NLB for SharePoint 2010 

The concept behind Network Load Balancing is pretty simple: Each server in a Load Balancing Cluster is configured with a 'virtual' IP address. This IP address is configured on all the servers that are participating in the load balancing 'cluster' (a loose term that's unrelated to the Microsoft Cluster Service). Whenever a request is made on this virtual IP a network driver on each of these machines intercepts the request for the IP address and re-routes the request to one of the machines in the Load Balancing Cluster based on rules that you can configure for each of the servers in the cluster. Microsoft this process Network Load Balancing (NLB). Figure 1 shows how the process works graphically.

A network load balancing cluster routes requests to a single virtual IP to available servers in the load balancing cluster. Note that each machine is self-sufficient and runs independent of the others duplicating all of the resources on each server. The database sits on a separate box(es) accessible by all servers.

actually no need to configure a heart-beat adapter address for NLB. Single adapter is enough with an IP address on each server which can be part of your server LAN address. Importantly make sure that if your network switch is multicast enabled then the NLB Cluster mode needs to be in multicast mode or else the communication will be interrupted. If multicast is not enabled on switch, opt for unicast cluster mode in NLB.

out of umpteen blogs I referred, let me share few of the helpful blogs which I felt had acted upon and suited our infrastructure without much hassles.. 

reference 1

video ref 2
reference 3
reference 4
reference 5

- make sure you configure port rules on NLB for better performance.

- configure perfmon to verify the load on each cluster web front end servers.

Best Practice: SharePoint 2010
Three-Tier-SharePoint-2010-Architecture 

Configuring User Profile Service Application in SharePoint Server 2010

we referred the below blog for sorting issues related to user profile sync and configuring directory service connections to import AD users. 

http://blogs.msdn.com/b/alimaz/archive/2009/11/09/configuring-user-profile-service-application-in-sharepoint-server-2010.aspx


I successfully implemented Three-Tier SharePoint 2010 Architecture
..no hassles.. we could swiftly achieve the upgrade from MOSS2007 to SharePoint 2010 in April 2012.

Quick Fix: user profile service application error in SharePoint 2010

SharePoint 2010: User Profiles - You receive an error - "An unexpected error has occurred." when you try to browse to the page to Manage a newly created User Profile Service Application

You create a new User Profile Service Application and try browsing to the Manage link for the User Profile Service Application, this page might fail with the following error,

Sharepoint 2010 User profile service application error could be resolved by updating the below hotfix.

we could fix the above nature of error by applying the below hot fix of SharePoint 2010.

----------------------------------------------------------

KB Article Number(s): 2597150

Language: All (Global)

Platform: x64

Location: (http://hotfixv4.microsoft.com/Microsoft%20SharePoint%20Server%202010/sp2/office2010kb2597150fullfilex64glb/14.0000.6117.5002/free/445300_intl_x64_zip.exe)

Database attach method to upgrade to a new farm

ADDCONTENTDB

stsadm -o addcontentdb -url  http://intranet  -databasename wss_content_hr -databaseserver yoursqlservername\instancename

if you have multiple subsites then you can very well include all of those stsadm database attach command in a batch file and execute it at one stretch.

ex:

save the below in a execute.bat file:

'----
stsadm -o addcontentdb -url http://intranet -databasename wss_content_hr -databaseserver yoursqlservername\instancename >> result.txt

stsadm -o addcontentdb -url  http://intranet/sites/hr -databasename wss_content_hr -databaseserver yoursqlservername\instancename >> result.txt

stsadm -o addcontentdb -url  http://intranet/sites/it -databasename wss_content_hr -databaseserver yoursqlservername\instancename >> result.txt

'----

the above file execute.bat once executed will append result.txt with the upgrade status.

more reference

exciting office web apps for SharePoint 2010

No need of office installation on client machines, instead integrate web app bunch with Sharepoint 2010.

saves client licensing (CALs) cost or for those who needs to extend the office feature on the web browser. Clients can open office documents from anywhere outside office network like from Airport or from public internet zone using authorized connection. For better performance install Silverlight on client computers.

installation reference:

installing office web-apps for sharepoint 2010

high availability moss 2007 development and production environment

I attained the below infrastructure from scratch (a mix of windows 2003 R2 Ent 32bit and 64bit) for our team during mid of 2010

2 Tier MOSS2007 Architecture for both development and production environment

recent: refer also 3Tier Architecture for SP2010

Best practice to change SharePoint service account passwords

How to change service accounts and service account passwords in SharePoint Server 2007 (MOSS2007) and in Windows SharePoint Services 3.0

microsoft site reference: http://support.microsoft.com/kb/934838

Just changing domain account password from sharepoint services and from Application Pool identity will not do.
you have to follow the above article.
in short execute the following in batch (.bat) file will also do:
----------------------------------------------------------------------------------------------------------------------------------------------------
cd %commonprogramfiles%\Microsoft Shared\Web server extensions\12\Bin

stsadm -o updatefarmcredentials -userlogin domain\enterusernamehere -password enternewpasswordhere
iisreset /noforce

stsadm -o updatefarmcredentials -userlogin domain\enterusernamehere -password enternewpasswordhere -local
iisreset /noforce
           
stsadm -o updateaccountpassword -userlogin domain\enterusernamehere -password enternewpasswordhere -noadmin
iisreset /noforce
       
stsadm -o spsearch -farmserviceaccount domain\enterusernamehere -farmservicepassword enternewpasswordhere
iisreset /noforce

stsadm.exe -o spsearch -farmcontentaccessaccount domain\enterusernamehere -farmcontentaccesspassword enternewpasswordhere
iisreset /noforce
       
stsadm -o editssp -title (SharedServices1 change accordingly) -ssplogin domain\enterusernamehere -ssppassword enternewpasswordhere
iisreset /noforce
----------------------------------------------------------------------------------------------------------------------------------------------------

InfoPath published Forms error using DNS Record: Event ID 5566, in MOSS 2007 64Bit

InfoPath Form Services Error accessing data source eventid 5566 in SharePoint 2007 

SYMPTOM:

Forms when accessed through the browser using DNS Record (A Record created in DNS: intranet) was showing error. There are no issues when accessing the same forms using hostname(http://intra-app1)

ENVIRONMENT:

SharePoint 2007 SP2 (CU August 2011: 12.0.0.6565), OS: Windows 2008 R2 Enterprise Edn.

SCOPE:

Published Forms opens properly from client access using WFE server hostname (http://intra-app1 ) (Hostname of WFE: intra-app1)

However, the forms could not be accessed using the DNS entry (http://intranet). shoots errors ID 5566 as seen below:  

ACTION:

Inorder to solve this we configured the following setting in the registry for disabling the loopback check in the registry using the following method.

In Registry Editor, locate and then click the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

Right-click Lsa, point to New, and then click DWORD Value.

Type DisableLoopbackCheck, and then press ENTER.

Right-click DisableLoopbackCheck, and then click Modify.

In the Value data box, type 1, (hexadecimal) and then click OK.

No need to either restart the server or carryout IISreset /noforce

This is enough, just try accessing portal using the DNS and the published forms using DNS record (http://intranet). This should solve the problem.

 

Also, make sure AAM (Alternet Access Maping: http://intranet) to Intranet Zone is configured at the CA level .

Roll Out Plan for Adding iFilters in SharePoint 2007 64Bit Environment

Configure PDF iFilter 9 for 64-bit platform

The steps mentioned below are as per suggested by Microsoft. Please refer to links below for appropriate Microsoft KB articles.

>> http://www.adobe.com/special/acrobat/configuring_pdf_ifilter_for_ms_sharepoint_2007.pdf?PID=4172469
>> http://support.microsoft.com/?id=555209
>> http://blogs.msdn.com/ifilter/archive/2007/03/29/indexing-pdf-documents-with-adobe-reader-v-8-and-moss-2007.aspx

Download Adobe PDF iFilter 9 for 64-bit platforms http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025

1. Install Adobe PDF iFilter 9 for 64-bit platforms.
2. Verify that PDF has been added to the registry.

a. Run Regedit by browsing to c:\Windows\system32\regedt32.exe and double-clicking it.

b. Within left-side tree, browse to: \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\{site GUID}\Gather\Portal_Content\Extensions\ExtensionList

c. If PDF extension is present, skip to Step 3 . If PDF extension is not present, continue with Step d.

d. Right click on right-side Extension List pane and choose New > String Value

e. Add a name to the new Registry Key (e.g. "38")

f. Double click the new Registry Key. For "Value data", enter "pdf"

Note: This can also be achieved via SharePoint Server Search Administration page by adding 'pdf' to list of File Types in Search Administration->File Types. This would automatically add an entry for 'pdf' filetype as mentioned above in step 1

3. Verify that PDF has the correct settings in a second registry location.

a. While still in Regedit, within the left-side tree, browse to: \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\Filters\.pdf

b. Verify the following values. If values are not as shown, edit them.

i. <REG_SZ> Default = <value not set>
ii. <REG_SZ> Extension = pdf
iii. <REG_DWORD> FileTypeBucket = 1

iv. <REG_SZ> MimeTypes = application/pdf

4. Verify that PDF has the correct settings in a third registry location.

a. While still in RegEdit, within the left-side tree, browse to: \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf

b. Verify the following values. If values are not as shown, edit them.

i. <REG_MULTI_SZ> Default = {E8978DA6-047F-4E3D-9C78-CDBE46041603}

 

5. Verify that pdf.gif is present at the following location:

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

6. Add an entry in docicon.xml for the pdf icon:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\XML

<Mapping Key="pdf" Value="pdf.gif">

Note: Step 4 & 5 are done in order to have the pdf icon in SharePoint while it displays the search results.

7. Restart all SharePoint services as well as IIS.

a. Launch the DOS Shell (Start > All Programs > Accessories > Command Prompt).

b. Type the following at the prompt: "net stop osearch". Wait for success message.

c. Type the following at the prompt: "net start osearch". Wait for success message.

d. Type the following at the prompt: "iisreset". Wait for success message.

 Close the Command Prompt window
8. Microsoft Office SharePoint Server can now index PDF files. Also, PDF icon should show in File Types list

Roll Out Plan for PDF Configuration in SharePoint 2007 64Bit Environment

 How to add an icon to Windows SharePoint Services to represent Adobe PDF documents that are stored in document libraries

firstly, download adobe icons (small & large) http://www.adobe.com/misc/linking.html

1. Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Images
2. Copy in the PDF icon. Rename it to "pdficon.gif".
3. Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\xml
4. Locate the Docicon.xml file open with an xml editor.
5. Within the ByExtension tag add a new Mapping tag in alphabetical order with the following properties.

6. <Mapping Key="pdf" Value="pdficon.gif" />

7. Save the file. The Value needs to be the same as the icon you saved in images. Your file should look something like this.
   
   
   

SharePoint Site Error 503

SharePoint Site Error: Service Unavailable HTTP Error 503. The service is unavailable

** when we traced back the recent changes we could identify that from the CA Search Administration 'reset all crawled content' option was recently triggered which ended up with SSP page error 'Service Unavailable HTTP Error 503. The service is unavailable'. 

** other possible reason could be if you change the identity or account password either directly from IIS settings or if at all from web config file.

** another reason could be if you install another web based program or add feature.. unexpectedly causing IIS to stop the SharePoint services. for. eg: if you install AD on the same machine, OR added a new web site with a duplicate port.

make sure  that Web site protocols starts properly and the user account used to start Applicaion pool is correct and starts as well.

steps:

i.  Open up IIS Manager and click on Application Pools.

ii.  Locate your App Pool account and right-click on it and select 'Advanced Settings'.

iii. Click on the right of the Identity box to change it (A window will pop up).

iv. Click on Set and simply retype your App Pool Identity in there with the new password.