Posts

VCenter vs Hyper-V: Which is right for your company

Virtualization remains one of the hottest trends in business IT. Whether your organization has already invested heavily in the cloud or is considering a first-time migration, it can be critical to consider the role of a hypervisor in youroverall experience. A hypervisor is computer software, firmware, or hardware that creates and runs virtual machines. The hypervisor presents virtual, or guest operating systems to virtual machines and manages the execution of these virtual operating platforms, which can consist of a variety of operating systems. The right hypervisor can ensure ease of use, flexible resource allocation, and minimal disruption to each of the operating systems in use. Two of the most common choices for hypervisors include vSphere by VMware and Hyper-V, by Microsoft. Hyper-V is built into Windows Server, or can be installed as a standalone server, known as Hyper-V Server, both of which can ease the learning curve for virtualization administrators who already have kn

The Security Token Service is not available (SharePoint 2013)

Error:   The Security Token Service is not issuing tokens Today I have faced error in Security Token Service. I was consolidating SharePoint farm servers. When I created SQL Server Reporting service application, it showed an error on system settings and managed jobs page.  When I checked ULS logs error was An exception occurred when trying to issue security token: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+msbin1) The error logs does not helped me much. Still I was unclear what was happening. Then I enabled verbose logging and scanned GB’s of logs. The error I found was: SharePoint Installation Claims Error: Failed to create instance of cookie value handler type / handler object As the error says that it is a claims problem I first checked the SharePoint Security Token Service but the web service was fine. When I browse the web service, the page is rendered without errors. After tha

The tool was unable to install Application Server Role, Web Server (IIS) Role

Image
Hi Friends, As you know that SharePoint 2016 beta 2 has been released. I decided to make my hands dirty on this buggy version. My setup was as follow. SharePoint Box-  16 GB RAM - 120 GB HDD- Windows Server 2012 R2 SQL 2012 --- 8 GB RAM - 120 GB HDD -- Windows Server 2012 R2 I started installation with Prerequisite installer. You do not believe it gave error from first basic step. The tool was unable to install Application Server Role, Web Server (IIS) Role The issue was setup was not able to install .NET framework 3.5. Server manager also unable to install it. I ran the following command and issue was just ran away. Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs /LimitAccess Somehow tool was able to install IIS and its components. Later it gave error on following components  vc_redist.x64 for 2015 vc_redist.x64 for 2012 I manually downloaded it form Microsoft website and finally all prerequisites installed.

A Web Part or Web Form Control on this Page cannot be displayed or imported. The type YourNameSpace.YourPart, YourPart, Version=1.0.0.0, Culture=neutral, PublicKeyToken=SomeToken could not be found or it is not registered as safe.

Hi Friends, Its over a year since we met each other. I am back guys. Lets start the post. This time i am going to describe one stupid error in SharePoint web part deployment. The developer came to me today with a issue . A Web Part or Web Form Control on this Page cannot be displayed or imported. The type YourNameSpace.YourPart, YourPart, Version=1.0.0.0, Culture=neutral, PublicKeyToken=SomeToken could not be found or it is not registered as safe. When you closely see , error itself shows some assembly is not added in safe control list. This is an unusal behaviour. When you deploy any solution , SharePoint does take care about adding safe control values in web.config. But what goes wrong here?? Web Part namespace was diffrent than specified in solution. It mayy possible that code is taken from some one or copied from another location If you have a web part, you will have a .webpart file. Open it up. You will want to ensure that the type name references your namespace and ty

This project cannot be opened in read-write mode because a previous checkin for this project is not complete.

Image
Error: this project cannot be opened in read-write mode because a previous checkin for this project is not complete. Here is the solution: Close Microsoft Project 2013 if it is open Press windows key + R.  In the Run dialog, enter the following command:                 %appdata%\Microsoft\MS Project\15\Cache     4.  Delete the all folders in it.

Shadow Rebundancy and SMTP delay Acknowledgement

                     Exchange 2010 introduced the shadow redundancy feature to minimize the loss of any message during delivery after it enters the Exchange organization. Exchange Transport servers achieve this by using the shadow redundancy SMTP protocol extension.         However, in any organization Exchange Transport servers need to communicate with other third-party SMTP servers that may not support the shadow redundancy protocol. Transport servers delay sending acknowledgement to incoming messages until they verify final delivery within the organization. However, when a specific threshold was reached, the Transport server issued an acknowledgement even if final delivery wasn’t verified. This presented a scenario where messages received from hosts that don’t support shadow redundancy can be lost in transit.         To address this issue, a new feature called shadow redundancy promotion is introduced in Exchange 2010 SP1. When faced with the scenario described above, instea

Exchange Server Object version / Schema version

To install any exchange server you need to upgrade the Active directory Schema. The administrator should verify it before stepping further. Following is the schema version of Active Directory . you need to verify it from ADSIEDIT tool. Exchange Version   Forest rangeUpper attribute   Forest objectVersion   Domain objectVersion   Exchange 2000 SP3   4406 -   4406 Exchange 2003 RTM   6870 6903 6936 Exchange 2003 SP1   6870 6903 6936 Exchange 2003 SP2   6870 6903 6936 Exchange 2007 RTM   10637 10666 10628 Exchange 2007 SP1   11116 11221 11221 Exchange 2007 SP2   14622 11222 11221 Exchange 2007 SP3   14625 11222 11221 Exchange 2010 RTM   14622 12640 12639 Exchange 2010 SP1   14726 13214 13040 Exchange 2010 SP2   14732 14247 13040 Exchange 2010 SP3   14734