Monday, October 31, 2011

A network-related or instance-specific error occurred while establishing a connection to SQL Server.

Problem: A network-related or instance-specific error occurred while establishing a connection to SQL Server.
Server OS: windows 2008
Client OS: Windows 7

Solution: Open outbound port on client machine, and open inbound port on server
1.On Server - Open outbound port by adding a new rule for port 1433 in firewall at server machine
2.On Client - Open inbound port by adding a new rule for port 1433 in firewall at client machine

See the sample "How to add rule for inbound/outbound port"

Tuesday, October 25, 2011

Alternate of IssApp command in windows 2008

This is a shortcut alternate for IssApp command in windows 2008:
Go to C:\Windows\system32 and type inetsrv\appcmd.exe list wp
Here is the output you will get for this command:
WP "7056" (applicationPool:1c931ee15fb748979d16454c705d8d07)
WP "11392" (applicationPool:SecurityTokenServiceApplicationPool
WP "3956" (applicationPool:SharePoint - 80)

Tuesday, October 4, 2011

How to change owner of Sharepoint site from administrator to NetworkService

Steps to "How to change owner of Sharepoint site from administrator to NetworkService":



A. Look application pools in IIS



  1. Look the identity column in application pool List in IIS 6.0 and the select the application pool which is using administrator as Identity.

  2. Change identity from Administrator to NetworkService(right click on a pool, click Advance setting, click on Identity and type NetworkService)

B. Open Database server where Sharepoint database is created for central admin as well as content dbs for webApps(Login to db server with Administrative or DomAdminitrator’s userId)



  1. Go to security and select user NetworkService. Right click and select properties.

  2. Allow access for this user as dbo by selecting User Mapping. User mapping will show you all the database for this userid.

  3. Click on each database name and select db_owner under “database role membership”

  4. If your content database was offline or under suspect condition, make it online now.

C. Restart IIS
Open Central admin or any sharepoint site now for testing