If you are like me, you do your portal development on Vista or Windows 2008 server. Up until the other day whenever I wanted to have the search (queryd.exe) running, I always had to run it from an administrative command line since the service always failed to start when running under the "Local System" account. So by chance I decided to try assigning a local administator account to the search service and would you believe that the service started? Now I'm not saying that you have to run it under an administrator account, I would probably suggest testing out to see if any lower level permissions...

So I recently encountered an error message I hadn't previously seen while developing with the IDK: The server committed a protocol violation. Section=ResponseStatusLine Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Net.WebException: The server committed a protocol violation. Section=ResponseStatusLine...

So I read a few interesting posts from people who were talking about how easy Windows Live Writer ( link to site ) to publish not only to their blogs, but how it could also be used to publish content to Graffiti CMS ( link to site ) since Graffiti supports the MetaBlog API ( info ). So I go to the site and download the installer and wasn't too happy with what I saw when I tried to install the program....

This site is officially online with the posting of the first article titled " ALUI v6.5 UICI with VS 2005 How-To ". For anyone looking to get the new ALUI v6.5 UICI environment setup to for custom builds using Visual Studio 2005, this is your how-to article.

With the release of ALUI 6.5 there are some of us who need to do core customizations that cannot be done using class overriding. For those moments (and I suggest you keep them as limited as possible) you need to have the v6.5 UICI in a state that not only compiles properly, but will allow you to make non-breaking changes once deployed. Since BEA is currently not providing a completed solution (though I have been told that they should be "soon"), here are the steps I took to get my environment up and running....