Sunday, February 24, 2008

I can't post to my blog from external applications - Something Is Broken | Google Groups

After I transferred my blog to blogger, my posts stopped working. I did some investigation using wireshark (an excellent application) and could see that blogger was returning a posting id that when Windows Live Writer (WLW) tried to access returned a 401 not found error.

Turns out that there is a bug or feature with blogger that if you make more than 50 posts or changes in 24 hours, it starts returning bogus ids...! (glad I wasted all of those hours trying to work out why it wasn't working :|)

I can't post to my blog from external applications - Something Is Broken | Google Groups

Saturday, February 23, 2008

I've moved my blog

After a number of issues with my WSS site on webhost4life (instability, reliability etc) I have decided to move my blog to blogger. I am using Windows Live Writer again to write my posts. It seems that the released version doesn't post images properly to WSS, which is rather unfortunate. After a number of exchanges with the support team for WLW, I have come to the conclusion that it must not work because they have stopped answering my emails. I thought things would be better with blogger, BUT, images seemed to be a problem there too. I understand this is not a WLW issue, but rather something to do with the way blogger uses Picasa to store the images and how it copes with custom domains. So I am publishing my pictures to an ftp site now, and that seems to be working okay....

Update: After I did this post, now I can't get WLW to publish anything to blogger! WLW is throwing an exception...

Tuesday, February 19, 2008

SharePoint 2007 workflow 'Failed on Start'

I have been trying to work out for some time why I have been getting a 'Failed on Start' error when I try to run the OOB workflows in my MOSS VM.

When I look in the SharePoint log I see the following exception;

02/19/2008 20:04:53.82     w3wp.exe (0x14A0)                           0x1524    Windows SharePoint Services       Workflow Infrastructure           72fs    Unexpected    RunWorkflow: System.ArgumentException: Value does not fall within the expected range.     at Microsoft.SharePoint.Workflow.SPWorkflowActivationProperties..ctor(SPWorkflow workflow, Int32 runAsUserId, String associationData, String initiationData)     at Microsoft.SharePoint.Workflow.SPWinOEWSSService.MakeActivation(SPWorkflow workflow, SPWorkflowEvent e)     at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(Guid trackingId, SPWorkflowHostService host, SPWorkflow workflow, Collection`1 events, TimeSpan timeOut)     at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflowElev(SPWorkflow originalWorkflow, SPWorkflow workflow, Collection`1 events, SPRunWorkflowOptions runOptions)    
02/19/2008 20:04:53.82     w3wp.exe (0x14A0)                           0x1524    Windows SharePoint Services       Workflow Infrastructure           98d7    Unexpected    System.ArgumentException: Value does not fall within the expected range.     at Microsoft.SharePoint.Workflow.SPWorkflowActivationProperties..ctor(SPWorkflow workflow, Int32 runAsUserId, String associationData, String initiationData)     at Microsoft.SharePoint.Workflow.SPWinOEWSSService.MakeActivation(SPWorkflow workflow, SPWorkflowEvent e)     at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(Guid trackingId, SPWorkflowHostService host, SPWorkflow workflow, Collection`1 events, TimeSpan timeOut)     at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflowElev(SPWorkflow originalWorkflow, SPWorkflow workflow, Collection`1 events, SPRunWorkflowOptions runOptions)
    

I finally found a blog entry from Rodney Langley that steered me to the solution (see link below).

It turns out that at one stage I change the accounts for the application pools, but DIDN'T do it through the Central Admin interface. When I went into Central Admin - Service Accounts and changed them in there, the workflows miraculously started to work....

Thanks Rodney

Workflows, SSPs, and IIS Nightmares - SharePoint Squared - Rodney Langley's SharePoint Weblog

Sunday, February 17, 2008

Adventures of setting up MOSS on Windows 2008 – Part 3

It was not immediately clear to me how to disable the IE Enhanced Security in Windows 2008 (even though I blogged about it last year), so after a bit of looking around I found it here;

Server Manager

Adventures of setting up MOSS on Windows 2008 – Part 1

I have been installing MOSS on a Virtual Machine with Windows 2008 RTM. A colleague (David Marsh) is setting up the 64 bit version and I am trying the 32 bit version so we can compare if there is a noticeable difference in performance.

I have come up against a few issues while doing the installation which I thought I would share.

SQL 2005 Reporting Services

I had some difficulty configuring reporting services. I installed SQL 2005 Standard with SP2.

I went through the normal configuration and everything looked ok.

ReportServer

When I tried to access the ReportServer or Reports from the browser however, I received these errors;

(rsAccessDeniedToSecureData)

ReportsError

ReportServer Error

I checked the rsreportserverconfig to make sure the URLRool and WebServiceAccount were correctly configured.

rsreportserverconfig

After much effort trying to work out what was causing the problem, I decided to create a new database and remove the old one. This fixed the issue, so I can only imagine that there were some permission issues with database access.

CreateDatabase

Adventures of setting up MOSS on Windows 2008 – Part 2

Continuing my journey of trying to install MOSS on Windows 2008, I came across a couple of other issues.

Services on Server

When I tried to start Excel Services, I received the following error;

Failed to resolve the site ID for ‘Office Server Web Services’

Error

I found this post which has a work around Click Here

It shows a Powershell script

Start Powershell and run the following command;

Set-ExecutionPolicy RemoteSigned

Exit Powershell and Restart it.

The following is the script to start Excel Services
Set-Alias stsadm $env:CommonProgramFiles"\Microsoft Shared\Web Server
Extensions\12\BIN\STSADM.EXE"

stsadm -o provisionservice -action start -servicetype "Microsoft.Office.Excel.Server.ExcelServerSharedWebService,Microsoft.Office.Excel.Server, Version = 12.0.0.0, Culture = neutral,PublicKeyToken = 71e9bce111e9429c"

iisreset /noforce

It seems to work okay, but it is a concern that there doesn’t seem to be a reason why at this point.