*.dannyg

After deciding that I wanted to query the much reveled OData services offered by Sharepoint 2010 I ran into multiple issues (now which I’ve resolved).

This is the service endpoint

http://<hostname>/_vti_bin/ListData.svc

1) OData services do not work over HTTPS.  I’m assuming this is related to configuration of WCF.  This is a key point to remember. 

2) Installing of the ADO.NET Data Services v1.5 CTP2 on the Sharepoint 2010 Server.  Do an IISRESET or reboot after this.

3) Ensure that there are no corrupt lists on a site.  If there are you’ll be able to hit a specific list but not hit the endpoint.  You’ll keep getting prompted with the NTLM/Keberos login from your web browser and never get logged in.  To remove a corrupted list (mine happened from upgrading from Sharepoint 2007 to Sharepoint 2010 without installing custom list types), run the following command from the Sharepoint Powershell Prompt (thanks to Harold van de Kamp’s blog entry on this one.)

stsadm.exe -o forcedeletelist -url <url>

A sharepoint service as defined by Sharepoint 2010 is not your typical “run-of-mill” service.  You can’t simply go to the Windows Service snap-in (commonly referred by sysops as services.msc), and hit Stop or Restart.

You’ll need to fire up the Sharepoint 2010 Management Shell.  You might need to logged into the box as a Farm Administrator.  Run the command:

Get-SPServiceInstance.   Locate the GUID, and then run.

Stop-SPServiceInstance <GUID>

Select ‘Y’ to stop it.  You should be able to refresh the Central Administration > Services on Server dashboard and see the respective service is stopped.

Ran into an issue today with Sharepoint 2010 and Datasheet View.  Microsoft has provided two workarounds.  I did method 2, which is much more simplistic.

http://support.microsoft.com/kb/2266203

I had inadventenly locked myself out of Sharepoint by removing myself as site administrator. But, because I have access to the SQL database I was able to restore my permissions. First run the following query to find out your tp_ID. (You will have to run this on the correct Content database).

select tp_id, tp_siteadmin, tp_login from userinfo

Find your user name in the query results (you can use a WHERE LIKE clause to simplify this step). Then run the following query to give yourself permissions.

UPDATE userinfo SET tp_siteadmin = 1 WHERE tp_Id = ?

That should give you everything you need.  Log into Sharepoint and you should be a Site Collection Administration

There was a slight issue with uploading documents larger than 28 MB on Windows Server 2008.  This Microsoft knowledgebase article helped me resolve it.

http://support.microsoft.com/kb/925083

I feel like I should explain this really cool idea that I had.  Basically to quickly check-in and check-out documents in Sharepoint.  I’ll show you with MSword.  First thing to do is fire up Word.  You’ll notice that in the upper left hand corner near the Office Menu, a quick menu bar.  See below.

Drop down the arrow to right of the bar and you’ll see an option to add “More Commands”.  From this new window that pops up, go to the drop down “Choose command from” and select “All Commands”.

From here find Check-In and Check-Out and add them.  (I’m adding version history too!).  You can even add keyboard shortcuts from here too.  Once you’ve completed, click OK.  You’ll see your quick access bar updated.

http://www.codeplex.com/sharepointinstaller

stsadm -o addsolution -filename helpdesk.wsp

stsadm -o deploysolution -name helpdesk.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs