Custom Feature Deployment fails to create feature receiver object from assembly

Hello,

We're attempting to deploy a custom feature using STSADM on a SharePoint 2007 SP2 environment. When run from Visual Studio, and deployed using the WSP builder, the feature deploys as expected. However, when attempted using STSADM on another development machine, we get the error below.

It seems there is something missing from the code that STSADM doesn't know, that's inherent in VS. Would anyone know what that is?

The installation of features failed during deployment of the solution.
Last Operation Details: SPSERV : Failed to create feature receiver object from assembly "TEST_siteMasterPage, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b4f0af5467e0d3fb", type "TEST_siteMasterPage.TESTMasterPageFeatureReceiver" for feature bad759f6-0735-418f-a68a-134655d06639: System.ArgumentNullException: Value cannot be null.
Parameter name: type
   at System.Activator.CreateInstance(Type type, Boolean nonPublic)
   at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()
SPSERV : Failed to create feature receiver object from assembly "TEST_siteMasterPage, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b4f0af5467e0d3fb", type "TEST_siteMasterPage.TESTMasterPageFeatureReceiver" for feature bad759f6-0735-418f-a68a-134655d06639: System.ArgumentNullException: Value cannot be null.
Parameter name: type
   at System.Activator.CreateInstance(Type type, Boolean nonPublic)
   at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()

Thank you!
LVL 1
jcroexbdAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jcroexbdAuthor Commented:
We needed to clear the asp.net cache, as the solution had been deployed before and the cache needed clearing before we deployed it again.

Thanks to  Peter Brinch Larsen
http://blog.brinch-web.dk/CommentView,guid,2027eeb6-48ed-4938-b96f-d93c3bfad02d.aspx

To clear the cache:


On the CA/Index server:
net stop SPSearch
net stop SPAdmin
net stop SPTimerV3
net stop SPTrace
net stop OSearch
IISReset /stop
 
Rem *** Delete apropriate folders ***
rd /S /Q  "C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET  Files\root"
rd /S /Q  "C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\ssp  common"
 
net start SPSearch
net start SPAdmin
net start SPTimerV3
net start SPTrace
net start OSearch
IISReset
Pause
 
On the frontend servers:
 
net stop SPAdmin
net stop SPTimerV3
net stop SPTrace
net stop OSearch
IISReset /stop
 
Rem *** Delete apropriate folders ***
rd /S /Q  "C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET  Files\root"
rd /S /Q  "C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\ssp  common"
 
net start SPAdmin
net start SPTimerV3
net start SPTrace
net start OSearch
IISReset
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.