I hope you all have a good one!

Today we were getting this error while trying to start one of those out-of-box Approval workflows: Failed on Start .

After much pain and trial-erroring, we finally got it working thanks to this post we found online:

«...
Changing the identity of the application pool to a user with administrative rights can cause the workflow to “fail to start“. If this sounds like something you've done, try changing it back to network service and try running the workflow again. (worked for me)
...»

Thanks to Raghu Iyer for posting a solution

If you ever want to check if a document library item's author is the current user, here's the code snippet on how to do it:

SPFieldUserValue authorUserValue = new SPFieldUserValue(myWeb, myItem["Author"].ToString());
if (myWeb.CurrentUser.LoginName == authorUserValue.User.LoginName)
{

// your code will go here

}

Hope this takes away pain from anyone trying to use GetByID

P.S.: sorry all of you I haven't yet replied to your emails - I've been on the road and jumping airports a lot, so life is kinda hectic which is making it hard to keep up with my mailbox.

Hi everybody!

Please vote for our solution - CaveDigital Board Meeting 2007, Town Hall Edition - for Council Meetings on the Clean Technology vertical for the Ingenuity Point contest.

Our solution renders Council Meetings paperless, thus saving a LOT of trees per year

Plenty of SharePoint, Windows Workflow Foundation and Office 2007

Thanks for your support!!

You're getting «HRESULT: 0x80070005 (E_ACCESSDENIED)» when you try to create subwebs using a custom site definition programmatically?

For a quick work-around, just add this to your Assembly.info.cs file, re-compile and re-deploy:

using System.Security;

...

[assembly:AllowPartiallyTrustedCallers]

Signing and making your code trusted should also work, but if you're on a tight spot, this code will probably get you some air to breath

Hope this helps someone out there

Florin just emailed me requesting to help on letting the word out on with the solution for this problem he was facing, so here it is, on his own words:

«If you upgrade from WSS 2.0 to Wss 3.0 and configure WSS 3.0 with anonymous access, you might get the following error while trying to create websites:

Error: File not found.

 

Looking at the Verbose Logfiles, you might get the following Error message:

Application error when access /_layouts/newsbweb.aspx, Error=A aplicação Web não foi encontrada em http://www.myportal.com/blogs/2a.

Verifique se escreveu o URL correctamente.

Se o URL tiver de fornecer conteúdo existente, o administrador do sistema poderá ter de adicionar um novo mapeamento do URL do pedido à aplicação de destino.

em Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite, SPUserToken userToken)

em Microsoft.SharePoint.Administration.SPNativeConfigurationProvider.LookupSite(String requestUrl, Int32 iisInstanceId, String& siteUrl, Int32& zone, Guid& appId, Guid& siteId, Guid& databaseId, String& databaseServer, String& databaseName, String& databaseUsername, String& databasePassword, Boolean& useHostHeaderForSiteName) ........

 

Resolution:

 

1. ISA 2004 Web Publishing Rule (additional configurations over  the default rule):

    A. Forward the original host header instead of the actual one

    B. Requests appear to come from the original client

 

2. WSS 3.0 Configuration:

    In SharePoint 3.0 Administration page -> Operations -> Go to Managed Paths (Mapeamentos de Acesso Alternativos)

    Set the Internet Url equal to the public FQDN of the website used by ISA 2004 to publish the your portal, e.g. www.myportal.com.

 

3. IIS Configuration:

    Add the public FQDN as Host Headers in IIS for the website extended with WSS 3.0, e.g. www.myportal.com.

 

I hope that this can help someone.

 

Greetings!
Florin Zamfir»

Cool, eh?

Both me and Daniel Pereira just did 70-630. Instead of bragging about it, let's just say it's done, with style