STSADM - Object reference not set to an instance of an object

Its been nearly 2 days am struggling to deploy a wsp solution in my farm by not using system account credentials. Am running a small farm locally on my system comprising of DC, SQL, Indexer and WFE. It all started with a issue where I was not able to activate a feature on my site using System Account, as activating feature would trigger a functionality in the code where it will check the user and send out a mail after fetching the details from DC. Now you wont find "System Account" in your DC would ya....

NOTE : If you log on to MOSS as an account that is used anywhere else in MOSS say for example an application pool in IIS being used by MOSS then it instantly associates your logged on account as a System Account or in a case where your have gone to Central Administration > Application Management > Policy for Web Application (i.e. /_admin/policy.aspx) and checked the option
"Account operates as System"
by Editing user under seleted WebApp. "You should therefore create unique accounts for managing he Application pools and web applications and create accounts as MOSS administrators.

This meant I had to use a different account other than system account to achieve my objective. I created a new account (fadmin) in my DC and added it to Domain Admins. When I logged to Central Admin Box (i.e. Indexer) using fadmin credentials and tried to add wsp solution using STSADM it threw following error:

stsadm -o addsolution -filename testWSP.wsp
Object reference not set to an instance of an object.testWSP.wsp:
The Solution installation failed.

Now this just did not stop here,I began googling.... after reading some blogs it seemed that issue is related to access rights. I it drove me nutts when, even after giving Farm Admin rights to fadmin account it threw the same error.
I began comparing System Account (i.e. domain\srohilla) access privileges with fadmin access privledges.

Comes out System Account has access to SharePoint_AdminContent_<GUID> DB in SQL,where as fadmin did not. So went ahead and gave appropriate rights to fadmin. This did the trick. Yippeeee!!!!!!!!! Now am able to add solution files successfully via STSADM and activate features.

SharePoint: Version Table (Service Packs/Hot Fixes)

MOSS 20071 or WSS 3.0 SP2 + Cumulative update (June 09) 12.0.0. 6510

MOSS 20071 or WSS 3.0 SP2 + Cumulative update (April 09) 12.0.0. 6504
MOSS 20071 or WSS 3.0 SP2 12.0.0.6421
MOSS 20071 or WSS 3.0 Cumulative update (Feb 09) 12.0.0. 6341
MOSS 20071 or WSS 3.0 Cumulative update (Dec 08) 12.0.0. 6335

MOSS 2007¹ or WSS 3.0 Cumulative update (KB956056 & KB956057) 12.0.0.6327
MOSS 2007¹ or WSS 3.0 Infrastructure Update (KB951695 & KB951297) 12.0.0.6318
MOSS 2007¹ or WSS 3.0 post-SP1 hotfix (KB948945) 12.0.0.6303
MOSS 2007¹ or WSS 3.0 post-SP1 hotfix (KB941274) 12.0.0.6301
MOSS 2007¹ or WSS 3.0 post-SP1 hotfix (KB941422) 12.0.0.6300
MOSS 2007¹ or WSS 3.0 SP1 12.0.0.6219
MOSS 2007¹ or WSS 3.0 October public update 12.0.0.6039
MOSS 2007¹ or WSS 3.0 August 24, 2007 hotfix package 12.0.0.6036
MOSS 2007¹ or WSS 3.0 RTM 12.0.0.4518
MOSS 2007¹ or WSS 3.0 Beta 2 TR: 12.0.0.4407
MOSS 2007¹ or WSS 3.0 Beta 2: 12.0.0.4017
Office 12 (PDC image - pre-beta): 12.0.0.3111 (This version of Office does not have a support link in the Add/Remove programs dialog box).