Posts

Top 7 Technical Support Best practices to ensure the positive customer experience

Some general best practices for any support functions that can help ensure a positive customer experience and effective resolution of issues. These practices include: Active listening:  It's important to actively listen to the customer and understand their issue fully before attempting to solve the problem. Listen to what the customer is saying and ask clarifying questions if necessary to ensure you have a complete understanding of the issue. Empathy:  Show empathy towards the customer and their issue. Try to understand their frustration or confusion and let them know that you understand and are there to help. Clear communication:  Communicate clearly and concisely, using language that the customer can understand. Avoid technical jargon and explain any technical terms or concepts as necessary. Timeliness:  Respond to the customer promptly and set clear expectations for resolution times. If a resolution will take longer than expected, communicate this to the customer and provide reg

दिल की चाहत

दिल की चाहत कल भी तुम थे आज भी तुम हो मेरी ज़रूरत कल भी तुम थे आज भी तुम हो तुमने तो मुझे कबका भुला दिया मेरी आदत कल भी तुम थे आज भी तुम हो तुमने न जाना कितना तुमको प्यार किया मेरी इबादत कल भी तुम थे आज भी तुम हो बेखबर बनते हो खबर हो के भी मेरी किस्मत कल भी तुम थे आज भी तुम हो

Setup is unable to proceed due to following error: This product requires Microsoft .net framework 4.5 SharePoint 2013

Hi Friends, Today i was doing SharePoint farm configuration for one of my client. Setup was as follow. Operating System : Windows Server 2012 R2 Database Server : SQL Server 2014 with SP2 The server was having . net framework 4.6.1 installed . SharePoint server requirement is to have .net framework 4.5 and above. But still i got an error: Setup is unable to proceed due to following error: This product requires Microsoft .net framework 4.5  SharePoint 2013. What was wrong? The update KB3102467 was causing the issue. During the installation the installer verifies if .NET framework 4.5 is available and fails to install SharePoint 2013 if .NET framework 4.6 is installed. The reason is that .NET framework 4.6 replaces .NET framework 4.5 and is not a side-by-side installation. As the installer is not able to match .NET framework 4.6 to .NET framework 4.5 it will prevent the installation. The solution is to uninstall  KB3102467 . After successful installation y

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