Sharepoint Versions

Sometimes we come across a Sharepoint farm with an unrecognized Build number.

Fortunatly some one has put in the effort  all ready and wrote all the versions down :

The list for Sharepoint 2007 can be found here.

And the list for Sharepoint 2010 can be found here.

Cause you don't want to get the Wrong Build Number....

GAC Folder View

There are allot of ways that can allow us to View the GAC folder as plain File System Folder. (usefull if we want to simply copy\paste files from that folder)

The easiest way i have found that dosen't require mapping drives or even changing the registry is this :

Go to Start > Run > c:\windows\assembly\GAC_MSIL

Just know that you cannot use this path as a shortcut Because the server will just close the window for security reasons. so what you can do is write this path on a txt file and copy paste it to the run folder anytime you need it (or you can just remember the path like i do)

Short And Sweet :-)

Disable Loop Back Check

On so many errors and event Viewer Logs i encountered a problem that needs this Registry change so i won't Write a specific problem rather then just post the solution, i use it on all my servers even before i get and error in the Event Viewer.


To set the DisableLoopbackCheck registry entry to 1, follow these steps on the client computer:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click Lsa, point to New, and then click DWORD Value.
4. Type DisableLoopbackCheck, and then press ENTER.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor.
8. Restart the computer (otherwise the solution won't work for you)

Consider this as a best practice.

New Username

Hi Everyone,

We all know that from time to time users will have their Username changed in the Active Directory.
What happens behind the scenes is that their GUID is changed in the Sharepoint DB, and that could cause those users to lose the Permissions granted to them for site, lists etc.

Well...Fear no more our friend the stsadm comes to the rescue. what you should do is run the following command :
stsadm -o migrateuser -oldlogin DOMAIN\OldUserName -newlogin DOMAIN\NewUsername -ignoresidhistory

This command will Migrate all the Permissions the old username had and transfer them to the new username you provided in the stsadm command.

I'm sure someone will find this helpful :-)

unrecognized HTTP status

Hello citizens of the Sharepoint World.

Today i found myself facing a problem from a new kind, the kind that involves Crawling in a Proxy environment.

I encountered the following error message : 

To make a long story short - here is the answer.

The solution in a nutshell :

If you are behind a Proxy and want to crawl content Outside of your LAN, you should Disable the Proxy settings inside  Internet Explorer:

And set the Proxy settings inside the SSP Search Settings :

 And that Should do it for you.

Change App Pool User

It's Me again :-)

Our story Begins when we try to Change the user that runs the application Pool in Sharepoint 2010

We are getting the following error : 

The problem is that the Admin user in sharepoint Doesn't have enough permissions in the AD (2010) to VIEW other users.


The solution is to Enhance the permissions in AD for that user so he will be able to see other users.


(This issue has nothing to do with Sharepoint 2010, it's all about AD 2010)

Open up "Active Directory Users and Computer"

·  Select "Advanced features" from the "View" menu

·  Right-click the relevant account and select "Properties"

·  Select the "Securities" Tab

·  Scroll down and select "Authenticated users" in the "Group or user names:" field

·  Allow "Read" permissions in the "Permissions for Account Operators" field just below

·  Hit Ok


And you are done :-)

Enable \ Disable Sharepoint alerts

Hello Everyone 

Today i found out a cool way to Disable or Enable alerts in sharepoint.

Why is this so cool you ask ? because instead of canceling all the email features (such as Workflows) i can disable just the alerts. 

this is the way to do it : 

Disable Alerts 
stsadm -o setproperty -propertyname alerts-enabled -propertyvalue false -url http://Web_App-URL

Enable Alerts 
stsadm -o setproperty -propertyname alerts-enabled -propertyvalue true -url http://Web_App-URL

And if you want this to happen right away you should Restart the timer services by going to RUN > Services.msc and restarting a service called  " Windows Sharepoint Services timer"

after which this command should follow :
stsadm -o execadmsvcjobs
that it :-)

Event ID 5783

Some day this week (i can't remember which day was it) i checked my Event viewer for no reason and i saw a bunch of 5783 Errors.

So i turned to Google and found out that the issue is that there are a couple of DB's that are not Synchronized For some reason. the following rows will tell you guys the rest :

Stsadm -o sync -listolddatabases 1 > this will give you a list of the DB's that aren't synced at a period days Represented by the Number you entered.

Stsadm -o sync -deleteolddatabases 1 > i know this command looks scary but it won't delete your DB, it will Only delete the record of it being synced.

In order for us to make sure the Sync occurs now we need to Restart the Windows SharePoint Timer Service By going to RUN > services.msc > and restarting the service 

After which this command should follow in order to start all the executive jobs : 

Stsadm -o execadmsvcjobs

And....that should do it.

Configuration Databse

A couple of days ago i encountered the following error message :

The reason for that is that one of the SQL servers has restarted during the night but although the server is on the Farm doesn't realizes it. so i restarted all the server in the farm and walla - now everything works just fine.

Event id 8214

Hi everyone,

Today i encountered a strange error and when i searched Google - nothing came up.

The error began when i created a n Web Application and tried browsing it VIA  browser.

What i got was "Site does not exist", so i turned to the IIS and clicked "Browse" from there and i got the same error. so i turned to the Event viewer and and i saw that Error 8214 was logged.

From earlier exprience i know IIS 6 has sometimes problems if the IP Address is set to "All Unassigned"

So what i did was change it from the default value to the server's IP address.

I know what you are thinking - what the hell does that got to do with the problem at hand...well try it and see for yourself. It solved my problem :-)