My IT Experiences - Microsoft 365, SharePoint & Azure

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

I got Win 7 installed the other day and suddenly I had log in issues one fine day. When I log in it would take my profile, but log me in to a temp profile. After searching for sometime in Google I read in a blog that profile could be corrupt. I had to follow these steps to clear the profile: 1.Reboot your Windows 7 machine and log on as different user. Make sure the different user account is a administrator (added to the Administrators group). Or you could log on in to safe mode if you don't know how to. 2.Open Explorer and open C:\Users. Delete the directory of “problematic” user profile and “Temp” directory. 3.Run the Windows Vista registry editor by type regedit in the Start Search box, and then press ENTER. 4.Locate and then expand the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList 5.You need to find the correct SID and delete it. To make sure you are deleting the right one, check the key ProfileImagePath which has the pro...

While clicking on "Audit Log Reports" under Site Collection Administration, I MOSS threw this error: The specified web does not contain a reporting metadata list There was no other information on this error. I activated the Reporting feature using force parameter and it solved the problem. This is the command: stsadm -o activatefeature -name Reporting -url http://[server]/[sitecollection]/ -force I do not know what caused this error, this site was not migrated from previous version of SharePoint, this happened in our root site collection. Regards, Manoj

I was trying to install MOSS 2007 64 bit on a Windows Server 2008 R2 (Virtual Server) and I encountered this error while running Sharepoint Products and Technologies Wizard on my first server in the farm: Failed to connect to the database server or the database name does not exist. Ensure the database server exists, is a Sql server, and that you have the appropriate permissions to access the database server. It seems certain ports needs to be open in the Windows Server where SQL Server 2008 was installed, this batch file solved the problem: @echo ========= SQL Server Ports =================== @echo Enabling SQLServer default instance port 1433 netsh firewall set portopening TCP 1433 "SQLServer" @echo Enabling Dedicated Admin Connection port 1434 netsh firewall set portopening TCP 1434 "SQL Admin Connection" @echo Enabling conventional SQL Server Service Broker port 4022 netsh firewall set portopening TCP 4022 "SQL Service Broker" @echo Enabling Transact...

I was trying to move some content dbs in our MOSS farm to another drive in the same Server. I stopped all website from IIS and stopped all the related services, then ran stsadm deletecontentdb command with all the required parameters. Then I detached the db and it threw an error and I just closed it by clicking Ok. Now I went to the drive to copy and paste the .mdf and .ldf file to the new drive. I tried to copy the .mdf file and I got access denied error but the db was already detached, I was screwed! The downtime was only for a couple of hours and I had many dbs to move to this new drive. I googled for some time and did not get many solutions, some people had encountered this error but none of them posted an answer. I tried to attach the file again from the old location, atleast site will not go down. But when I tried to attach I got this wierd error from SQL Server 2005 Management Studio: TITLE: Microsoft SQL Server Management Studio ------------------------------ Failed to retrieve...

Everything was working fine until got this Service Unavailable error from my MOSS central administration. I checked the IIS and app pool, everything seemed fine. I double checked that the domain account that ran my Central Admin app pool had sufficient rights, this was a dev server farm and people could be playing around with it. But this account had sufficient rights. Then I checked to login remotely to another server in this farm using the same domain account and I got the error that the account was locked! Now that was the problem. I checked with IT and got this account unlocked and Central Admin came back online :)