gCode Notes - SW Development Tips & Notes
Tuesday, April 5, 2011
The New Life plus .NET, Win7 and NetworkInterfaceTypes not recognized...
Saturday, April 2, 2011
A New Challenge
I'm tackling a new professional challenge!
After some time thinking about my "carreer next steps" I've decided to take a dive into the IT Architecture world. So, I'm now facing a new challenge at a new corporation which requires me to have a broad, deep and general knowledge of almost all the technologies in use today (raging from middleware, development, DBs, quality assurance, mainframe, etc).
I'm really excited about this new work and have just been assigned one of many tasks/projects to come: MOSS to Sharepoint 2010 migration (yey - back to Sharepoint! Feels good!!!).
So expect a post regarding this MOSS migration subject on the coming days/weeks...
For now, I'll begin analysing and studying the migration process, its HW and SW requirements... and above all, its cost ("cost" is something which more than ever will become an integral part of my work from now on!).
Well... really really really excited!!
See ya,
G.
Sunday, March 13, 2011
PHP - hide DEPRECATED warning messages
error_reporting(E_ALL & ~E_DEPRECATED);
Check: http://php.net/manual/en/function.error-reporting.php
G.
Wednesday, March 9, 2011
RegExp
http://gskinner.com/RegExr/
Surf there and check it ;)
Monday, February 28, 2011
CSV tip
Monday, June 29, 2009
MOSS – HTTP 500 Internal Server Error
Have you ever opened your MOSS site to found out an http 500 error with no apparent reason?
Well this happened to me for 2x already. So, to “archive” the problem I’ll post here the eventual workaround.
In fact, this problem can have multiple sources, so the first thing to be done is to make sure that we are not trying to access any unpublished item in MOSS libraries.
If this does nothing and the problem remains, then another approach is needed: first we need to disable the “show friendly error messages” in IE advanced options. Disabling that option, we can now get the detailed error: “No authority could be contacted for authentication.”? – well, if this is the error message that’s being displayed, it is the product of a conflict in the current development workstation and it’s domain controller. Why is that? See below:
Analysing the Event Viewer, various DCOM related errors were occurring (e.g. “The trust relationship between this workstation and the primary domain failed. (Exception from HRESULT: 0x800706FD“).
To finally solve the problem, we had to remove the machine from the Domain Controller (putting it in a workgroup) and putting it back again. 2 restarts later… everything worked fine!
There might be other possibilities for this error still. I’ll update this post as soon as I get by them (hope not!!)…
Hope this helps someone out there.
Cheers
Monday, June 8, 2009
The "Hello World"
Welcome to my new tech blog.
This is where I plan to reunite some of my developer tips, notes, problems, solutions, etc.
This blog serves as a compendium for myself and as a platform to share my experiences as a SW (mainly .NET and MOSS) developer.
Hope you find useful stuff in here.
Regards,
Gonçalo