VB issue with Office 2010 “Can not load an object because it is not available on this machine”

Prerequisite:

1.      The user applying the below fix should be a local administrator of the system

2.      The user should have a basic knowledge of Windows 7 operating system and files

3.      Before starting make sure you below files in it;

a.     MSCAL.OCX

b.     MSCOMCT2.ocx

c.      MSCOMCTL.OCX

The solution is for below error and mainly found for below site

Solution:

Clear Cache Remove all cached control type libraries as follows: Close all running instances of Excel or Word Navigate to: C:\Users\USERNAME\appdata\Roaming\Microsoft\Forms Remove all *.exd files
Coping the missing file Navigate to below paths and copy all three .ocx file present in “VBLoadIssue” folder Path: C:\Windows\System32 Path: C:\Windows\SysWOW64
Open the Command prompt with run as administrator:
Type the below command for registering the file to regsvr32.exe; regsvr32 c:\windows\system32\mscal.ocx
You will get the success window as per screenshot

 

SharePoint Beta 1 2013 prerequisite

 SharePoint 2013 Beta 1

Minimum System Requirements 2013

H/W Requirements- 64-bit 4 core processor , 4 GB memory for development or evaluation and 8 GB for production ,80GB Free Disk Space

Operating System-64bit Edition of Window server 2008 R2 SP1(KB976932)

Database -64 bit Edition of SQL Server 2008 R2 SP1(KB2528583)

Pre-Requisite

Microsoft .NET Framework version 4.5 Release Candidate (RC)

Windows Management Framework 3.0 Release Candidate (RC)

Application Server Role, Web Server (IIS) Role

Microsoft SQL Server 2008 R2 SP1 Native Client

Windows Identity Foundation (KB974405)

Microsoft Sync Framework Runtime v1.0 SP1 (x64)

Windows Identity Extensions

Microsoft Information Protection and Control Client

Microsoft WCF Data Services 5.0

Windows Server AppFabric

Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB 2671763)

 Hotfix

KB 2554876 - The SharePoint parsing process crashes in Windows Server 2008 R2

KB 2708075 - FIX: IIS 7.5 configurations are not updated when you use the ServerManager class to commit configuration changes

KB 2472264 - You cannot customize some TCP configurations by using the netsh command in Windows   Server 2008 R2

  SharePoint Foundation 2013

  Sharepoint Designer 2013

Garbage Collection an sweeper in SharePoint 2010

Hi All,

Below is my finding on Garbage collection (GC). I hope it will help you all to understand in depth the SharePoint performance and memory leakage cleanup.

1. Enumerate all BLOB files in the EBS Provider namespace that corresponds to a given SPSite identifier. Add these BLOB files to a hash table.
   
   String dirName = Utility.DirFromSiteId(site.ID);
   FileInfo[] files = Directory.GetFiles(dirName);
   foreach (FileInfo file in files)
   {
       ht.Add(file.Name, file);
   }
   

2. Locate all documents in the content database that corresponds to the SPSite identifier. Remove these entries from the hash table.
   
   foreach (SPExternalBinaryId blobid in site.ExternalBinaryIds)
     {
       String fileName = Utility.FileFromBlobid(blobid);
           if (ht.Contains(fileName))
           {
               ht.Remove(fileName);
           }
     }
   

3. Entries that remain in the hash table are files in the external BLOB store that do not have corresponding files in the content database. These are orphan files, and you can delete them.
   
   foreach (FileInfo file in ht.Values)
     {
         file.Delete();
     }

People search not working

When they try to do people search from their site http://server1 they do not get any results.

Cause:

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

There was an user added to the UPA Administrators group which was deleted from AD. Later when we tried to add the default content access account to the UPA Administrators we used to get an error stating cannot find user. Additionally, the crawl rule was not taking in effect and was crawling using spssearch account.

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

Resolution:

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

Removed the problematic user from the UPA Administrators.

Added the default content access account user to the UPA Administrators with permission to retrieve and crawl people data.

Removed the crawl rule.

Tried crawl, it was successful. The issue is resolved.

SP Calendar List web part shown error Unable to display this Web Part

Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator.

Correlation ID:

Resolution: Fixed by adding NT AUTHORITY\Authenticated Users with Read permission on the site collection page as well as in the Style Resource Readers Group

Disaster Recovery (DR) Plan

Disaster Recovery

•       No single feature provides disaster recovery within a SharePoint Server 2010 environment

•       Few Approaches to make Application available when a data center goes offline, including the following:

•       Cold DR - Offsite storage of backups, both within and outside your region.

•       Warm DR - Shipping images of servers to offsite locations after certain Interval.

•       Hot DR - Running multiple data centers, but serving data only through one, keeping the others available on standby

System Center Data Protection Manager 2010 – Tool for Backup/Recovery

• Recovery of SharePoint sites, document libraries, lists and documents to either the original server location or an alternate SharePoint farm.
• Unified Protection for Disk, Tape, and Cloud
• Item level recovery for SharePoint 2010 without a SharePoint recovery farm
• Automatic detection of deleted content databases from a protected SharePoint farm
• Support for moving content databases between instances
• Auto-Heal and Retry for Failed Backups
• DPM 2010 seamlessly interacts with the SharePoint and SQL Server Volume Shadow Copy Services (VSS) writers so that DPM captures consistent versions of a SharePoint deployment without interrupting client access to SharePoint content
• Recovery of SharePoint content stored on SharePoint 2010 farms without requiring the use of a recovery farm

Recommendations – Backup Strategy

• Scheduling Backups

• For Ad hoc changes backup whenever modified

• Storage – SAN, SATA, Tape drive
• Backup of Virtual images of Servers - Monthly

Recovery Strategy – 1 (using SharePoint)

• Restore from a farm backup that was created by using built-in tools, or restore from the backup of a component taken by using the farm backup system.
• Restore from a site collection backup.
• Connect to a content database by using the unattached content database feature, back up or export data from it, and then restore or import the data
• Restore Customizations (http://technet.microsoft.com/hi-in/library/ee748613(en-us).aspx)

Recovery Strategy – 2 (using System Center DPM 2010)

System Requirements

In an ideal scenario, the failover components and systems match the primary components and systems in all ways:

• Platform, hardware, and number of servers.

At a minimum, the failover environment must be able to handle the traffic that you expect during a failover.

Keep in mind that only a subset of users may be served by the failover site.

The systems must match in at least the following:

•    Operating system version and all updates
•    SQL Server versions and all updates
•    SharePoint 2010 Products versions and all updates

The system uptime will also be affected by the other components in the system. In particular, make sure that you do the following:

• Ensure that infrastructure dependencies such as power, cooling, network, directory, and SMTP are fully redundant.
• Choose a switching mechanism, whether DNS or hardware load balancing, that meets your needs.

References: 

•http://eval.symantec.com/mktginfo/enterprise/fact_sheets/b-be2010_agent_sharepoint_solution_brief.en-us.pdf

•http://symcdata.info/vmworld/assets/BE-2010-R2.pdf

•http://www.edugeek.net/blogs/zag/455-microsoft-dpm-2010-vs-symantec-backup-exec-2010.html

Windows scheduling a PowerShell Script

Task Scheduling a powershell script

This section describes the steps to schedule the power shell script.

Note: Script should be stored locally on server

Step 1: Go to Startè Administrative tools è Task schedulerè Right click on Task Scheduler libraryè Create task

Step 2: Type the necessary fields as per below screenshot

Step 3: Click on next tab (Triggers) and click on New

Step 4: Under settings click on Monthly and select all

Step 5: Under days click on 15 and 30 and click ok

Step 6: Click on action tab and then on new action and browse to the PowerShell client app on below location

Program/script: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

Add argument (optional): -Command "& Path of the script -url URL of script -List List name"

Once the above entries are done click on ok