My IT Experiences - Microsoft 365, SharePoint & Azure

We had an issue with our Index server running out of disk space. The server was old and didn't have slots available to add more storage. The approach I took had a disadvantage that I had to do a Full Crawl again. Here are the steps I followed: 1. Setup MOSS server with all pre-requisites; do not add server to farm Note: It is important not to install .NET Framework 3.5 SP1 on this server, please read my previous blog post for more details. It can be installed after setting up search. 2. Reset all crawled content from Central Admin. We may choose to remove the existing Index server from farm if required 3. Run PS Config wizard on new Index server and add the server to farm. If you have done a complete installation of MOSS the Web Application service and Incoming Email service would have started. Before configuring search we may choose to stop these services. 3. Start search service from Services on Server page of Central Admin - Operations and do the configuration. 4. Navigate to S...

While trying to configure Search Settings in my new Index Server, I received this error when I clicked "Search Settings" from SSP: In my farm I was planning to run both Index and Query services on same server. I did some research and found that this could be because of corrupted SSL for the Office Web service. The reason it seems to be .NET Framework 3.5 SP1 !! Yes it seems if we enable search service or configure Index server on a box which has .NET Framework 3.5 SP1 the SSL of the Office web service in IIS would go corrupted. I had a similar situation; I was replacing the Index server in my MOSS farm version 12.0.0.6219 I brought up this new server with same OS and framework patch level as the existing index server. That was a mistake because my existing Index server was setup in 2008 and that time there was no .NET Framework 3.5 that time. It got installed later during a patching window. But in my case when I made the patch level same on my new server I installed all frame...

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.

We were receiving this error on the home page of root site collection of our SharePoint test farm and also on some inner site collections. Server Error in '/' Application. -------------------------------------------------------------------------------- Exception from HRESULT: 0x80041050 Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80041050 I had no clues as to why this happens because googling returned many results and confused me more. It turned out that the issue was related to Forefront for SharePoint. I had installed ForeFront for SharePoint evaluation and that had scanned and marked some pages as virus. I couldn't get Forefront to work properly and uninstalled it. May be this caused some jobs to get stuck or something; I'm not...

I got this error in my Manage forms template page in Central Admin: Object reference not set to an instance of an object. at Microsoft.Office.InfoPath.Server.Administration.FormTemplate.SolutionDeploymentFailed() at Microsoft.Office.InfoPath.Server.Administration.FormTemplate.get_FormTemplateStatus() at Microsoft.Office.InfoPath.Server.ApplicationPages.FormTemplatePropertiesPage.GetStatusString(FormTemplate template) at Microsoft.Office.InfoPath.Server.ApplicationPages.ManageFormTemplatesPage.AddTemplateToTable(FormTemplate template, DataTable table, SPWeb web) at Microsoft.Office.InfoPath.Server.ApplicationPages.ManageFormTemplatesPage.FillDataTable(DataTable table) at Microsoft.Office.InfoPath.Server.ApplicationPages.GridViewPageBase.GridViewDataSourceView.FillDataTable(DataTable table, DataSourceSelectArguments selectArguments) at Microsoft.Office.InfoPath.Server.ApplicationPages.GridViewPageBase.GridViewDataSourceView.Select(DataSourceSelectArguments selectArgum...

I was trying to start the Office SharePoint Search Service from Central Admin on our new MOSS farm and I received this error the moment I clicked on Start: An unhandled exception occurred in the user interface.Exception Information: The server committed a protocol violation. Section=ResponseStatusLine I had no clue what was going wrong because there were not much information in the Event log or ULS logs. After doing some research with the logs, I found these errors in the SharePoint logs: Exception caught in Search Admin web-service proxy (client). System.Net.WebException: The server committed a protocol violation. Section=ResponseStatusLine at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.Office.Server.Search.Administration.Search...

While checking the Surface Area settings in our SQL Server 2005 cluster environment, I received this error: You cannot configure surface area of clusted services by connecting to a computer name. connect to the virtual server to configure clustered services The reason was I had logged in remotely using the cluster name and tried to open the SQL Surface Area Configuration window; therefore it was assuming local settings. This is how I fixed the issue: In SQL Surface Area Configuration Windows, click Change Computer and select the cluster instance under the option Remote Computer