Things to consider while creating Web Applications or Site Collection

Things to consider while creating Web Applications or Site Collection

Web Application

Authentication

Isolation

Content DB

Self Service Site creation

Recycle Bin

Blocked File Types

Resource Throttling

File Upload Size

Blob Storage

Site Collection

New Content DB

Site Quota’s

New Security Context

Web Part Gallery

Blob Storage and associated Content DB

Ref:

Ron Schoen power point slide

Advertisements

Infrastructure error while connecting to a SQL server

I faced this error few times on different scenarios. For ex: one user cannot connect to SQL server using SSMS or Application cannot connect to SQL server. This usually happened to me when there was a change in the system like user computer has been replaced or there were some network updates.

Resolution:

  1. Some times just by rebooting the user machine I was able to resolve the issue .
  2. For today , I had to move a DB from Dev server to QA and when application configuration file has been modified to use the new server info I could not connect to it. When I checked the SQL logs surely I saw ‘. Login failed for user ‘xxxx’. Reason: Login-based server access validation failed with an infrastructure error. Check for previous error.  When I launch the SSMS on the SQL server itself I could connect to it using the same user, which means there is no problem with the authentication. But when doing the same across the network it has issues meaning it needed specific permissions on TCP endpoint . I used the below query to do this and it resolved the issue
    GRANT CONNECT SQL TO "xxxxx"
    GRANT CONNECT ON ENDPOINT::"TSQL Default TCP" TO "xxxxx";

Below site has detailed explanation of all the infrastructure errors with severity and state

http://sqlblog.com/blogs/aaron_bertrand/archive/2011/01/14/sql-server-v-next-denali-additional-states-for-error-18456.aspx