TechOnTip Weblog

Run book for Technocrats

Archive for the ‘Sharepoint’ Category

Fix: Access CNAME based URL from same server (SharePoint, CRM etc)

Posted by Brajesh Panda on March 22, 2011

You may have observed you can’t access host header or cname FQDN URLs from same sharepoint & crm IIS Web Server. I grabbed these things from below MS KB Articles. For me the Method 1 always fix the issue which is recommended by MS.

Due to this URL access error, you may face issues with MS CRM Email Router. If you can’t access the CRM Applicatioin URL from same machine your email router will not able to crawl the users & may through an error.
http://support.microsoft.com/kb/896861/en-us

http://support.microsoft.com/kb/281308

Method 1: Specify host names (Preferred method if NTLM authentication is desired)

To specify the host names that are mapped to the loopback address and can connect to Web sites on your computer, follow these steps:

  1. Click Start, click Run, type regedit, and then click OK.
  2. In Registry Editor, locate and then click the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0

  3. Right-click MSV1_0, point to New, and then click Multi-String Value.
  4. Type BackConnectionHostNames, and then press ENTER.
  5. Right-click BackConnectionHostNames, and then click Modify.
  6. In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.
  7. Quit Registry Editor, and then restart the IISAdmin service.

Method 2: Disable the loopback check (less-recommended method)

The second method is to disable the loopback check by setting the DisableLoopbackCheck registry key.

To set the DisableLoopbackCheck registry key, follow these steps:

  1. Click Start, click Run, type regedit, and then click OK.
  2. In Registry Editor, locate and then click the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

  3. Right-click Lsa, point to New, and then click DWORD Value.
  4. Type DisableLoopbackCheck, and then press ENTER.
  5. Right-click DisableLoopbackCheck, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Quit Registry Editor, and then restart your computer.

You may need to do (Mostly applies when we use Alias, CNAME records to access the server over network using UPN)

Step -1

  1. Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
  2. Apply the following registry change to the file server. To do so, follow these steps:
    1. Start Registry Editor (Regedt32.exe).
    2. Locate and click the following key in the registry:

      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters

    3. On the Edit menu, click Add Value, and then add the following registry value:

      Value name: DisableStrictNameChecking
      Data type: REG_DWORD
      Radix: Decimal
      Value: 1

    4. Quit Registry Editor.
  3. Restart your computer.

Step-2

You may also have to set the SPN (Service Principal Name) for the Alias Name.

For example, you may have to enter a command that resembles the following commands:

setspn -a host/aliasname targetserver

setspn -a host/aliasname.contoso.com targetserver

Advertisements

Posted in Microsoft CRM, Sharepoint | Tagged: , , | 4 Comments »

SharePoint 2010 Small Farm Site Resilience Architecture

Posted by Brajesh Panda on June 14, 2010

Please Note:

SharePoint 2010 is just release 30days before. All promise features may not work correctly or if any product bug comes in-between team have to wait till next service pack to overcome the same.

SharePoint Architecture;

  • Backend SQL Infrastructure
    • Use Existing deployed SQL infrastructure (Deployed by
    • In Production Site-A use existing 2 Node Windows 2008 R2 Failover SQL Cluster for HA as 1st Level of HA to address Server Failure
    • In Production Site-B use exiting Mirror SQL Server for 2nd Level of HA for Production Site Failure
    • Every time one SharePoint database gets created in Site-A cluster, mirroring must configured manually to site B. SharePoint do not configure mirroring in application. It needs SQL Administration Skill & helps from DBA team.

       

  • SharePoint Front End
    • Two Front End Servers can be deployed
    • These servers will hold below set roles/features in both server giving redundancy
      • IIS 7 Role
      • Central SharePoint Administration Console (Port 10,000)
      • SharePoint Web Applications
      • SharePoint Virtual Directory
      • IIS Application Pools
    • These servers can hold Managed Services like Search etc. However at a time services can run on one server. If that server fails, SharePoint admin have to start services on other server. All services can run on a single front end server, can be divided among front end servers or dedicated extra application server can be used.
    • No need to start all Managed Services from the day one, it will create un necessary loads on farm. It should be on demand i.e. if YOU need that feature in future & if YOU developing applications using those features then should turned on. Else it will be management overhead

     

  • High Availability
    • Front End Servers should be load balanced using existing F5 Hardware Load Balancer hence seamless front end redundancy can be provided to end user
    • In general situation all Front end server from Site A & B will be doing transactions on Production Clustered SQL Databases
    • If one SQL server fails, databases will be transferred to other available SQL node providing complete redundancy.
    • For failover to Site B database in case of failure Managed Failover Database Partner must be configured for all Content & Service Application databases. This is a new feature in SharePoint 2010.
    • Before this SQL Admin must have configured Database Mirroring & production data must be stored in Site-B In Recovery SQL databases.
    • In case of Production Cluster SQL Database fails; SQL Administrator can initiate failover from Production Clustered SQL Server in Site A to Mirror SQL Server in Site B.
    • As soon as Databases get activated at Site B, Site A databases will move to in-recovery mode. SharePoint Front End & Managed Application Services will be do transactions in Site B database.
  • Backup/Restore
    • Backup Best Practices
      • Regular SQL Database Backup for Database Level Recovery in case logical database corruption
      • Use Disk to Disk to Tape backup solution
    • Web Application/Site Collection/Site level/Farm Level Backup/restore can be possible using Central Administration Tool & Powershell commands.

Posted in Sharepoint | Leave a Comment »

 
%d bloggers like this: