SOFTware is HARD

Step 1: You need to create a new Execute Queue (e.g. CriticalAppQueue) Click the name of the server instance where you will add the execute queue. Select the Monitoring —> General tab. Click the Monitor All Active Queues text link to display the execute queues that the selected server uses. Click the Configure Execute Queue text link to display the execute queues that you can modify. Click the Configure a New Execute Queue link. On the Execute Queue Configuration tab modify the following attributes or accept the system defaults: Queue Length : Always leave the Queue Length at the default value of 65536 entries. The Queue Length specifies the maximum number of simultaneous requests that the server can hold in the queue. The default of 65536 requests represents a very large number of requests; outstanding requests in the queue should rarely, if ever reach this maximum value. If the maximum Queue Length is reached, WebLogic Server automatically doubles the size of the queue to...

Debugging SharePoint is ridiculously difficult as the error in the title shows. To have any meaningful errors displayed, you need to enable the error display. To do so requires you to change the web.config of the site. Namely: Safe Mode Custom Errors Change Safe Mode to display call stack: <SafeMode MaxControls="200" CallStack="true" ... Change Custom Error to off: <customErrors mode="off"... After which, you will be able to see the standard ASP.NET error page that you're already accustomed to. More advanced troubleshooting tips can be found here: http://blog.thekid.me.uk/archive/2007/07/25/debugging-tips-for-sharepoint-and-wss-exceptions.aspx

Have you ever encountered a situation where after you've added a rogue WebPart into the SharePoint site's default.aspx page, the site perpetually complains "An unexpected error has occurred."? Such a rogue WebPart effectively blocks a user from entering the site to even correct the issue. The solution is rather simple: note the site URL (e.g. http://mymoss/sites/mysite/default.aspx) add "?content=1" to the end of the URL (e.g. http://mymoss/sites/mysite/default.aspx?content=1) at the Web Part Page Maintenance, remove the rogue WebPart and you're done!

Here are a number of useful links to help circumvent the campaign/ blast from being treated as SPAM: Check the SPAM score of the content: http://www.contactology.com/check_mqs.php Useful freeware: http://www.mailingcheck.com/ Nice blog entry that details someone's experience: http://blog.thecodingmachine.com/content/my-mails-are-being-treated-spam-what-should-i-do Comprehensive list of tests on email messages: http://spamassassin.apache.org/tests_3_3_x.html Best practices: http://wiki.apache.org/spamassassin/AvoidingFpsForSenders Some good guide and information regarding HTML mail (main culprit!) can be found here: http://mailformat.dan.info/ An online checker http://mailformat.dan.info/tools/check.html

Broad Categorisation of required skills Technical acumen and technology application Software Application platform & Operating Systems Middleware Database Domain knowledge Vertical – industry-specific, e.g. banking, insurance, telecommunication, legal, government Horizontal – cross-industry, e.g. workflow, document management, search, SOA Conceptualisation skills – able to conceptualise, describe and communicate the solution Leverage patterns – don’t reinvent the wheel! Manage relationships – need to manage stakeholders, vendors, providers, partners Leadership skills – able to garner support/ buy-in Communication and listening skills Strategic skills – able to zoom-in and zoom-out Experience in Processes Solution architecture Systems engineering Software engineering Programme/ Project management Role is to: Develop the overall vision Execute the vision into the desired solution Organise the development effort Implement strategic IT programmes Toolbox Requir...