MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Provisioning Web Applications - sandbox solution showing in new data

  Asked By: Ariel    Date: Aug 22    Category: MOSS    Views: 858

I had been doing a lot of banging around in the sandbox when I started getting a
COM error in my application. After much debugging I decided to try and redeploy
the solution to a fresh web application, but I was still getting the cryptic COM
error. I went digging and I noticed that each time I provision a new web
application, a row is getting created in the dbo.Solutions table in each new
content database with my sandbox solution in it, even though I have never
deployed anything to the site. I just verified that the solution is in the
database before I even create a root site collection for the web app.

I have created three web applications with the same behaviour, and the sandbox
solution row in the database exists in WSS_Content and all other
WSS_Content_<guid> databases. Any thoughts as to why this might be happening,
or what I can do to fix? I have been googling and looking into some sort of
Content Database "reset", as this is a development environment and I don't mind
blowing everything away, but I would like to be more knowledgeable about a good
way to handle something like this. My worst case scenario would be to reinstall
MOSS. Is there anything else I could consider?



3 Answers Found

Answer #1    Answered By: Cecil Mckenzie     Answered On: Aug 22

What's in the project? Are you writing a feature? Do you have an event receiver
that is deploying to the Farm instead of a Web Application, Site or Web?

I know there are times when an event receiver I have created is not actually
pulled from the system even though I go through all of the steps to uninstall
correctly. I can find instances of my features attached to lists, for example,
even when the solution that deploys it is no longer on the server.

Answer #2    Answered By: Jaclyn Gordon     Answered On: Aug 22

It was during the development of a List Item Event Receiver that this error
started to occur. It sounds like my issue is very close to yours in that the
solution is no longer there but the event receiver is there somehow, and maybe
that is the reason the solution refuses to leave the database. What did you do
in these cases? I reverted to an earlier snapshot of my VM to keep moving, but
I would really like to know if there is guidance out there on how to
troubleshoot something like this. Are you using PowerShell heavily, or is there
some guidance from Microsoft on how to troubleshoot these types of issues that
you're using?

Answer #3    Answered By: Bhupendra Bajpai     Answered On: Aug 22

Being that your issue is in SharePoint 2010 I would suspect that you would be
able to scrub the event receiver through PowerShell. In 2007 I am using "Event
Handler Explorer" by U2U. It is free and allows me to view all event handlers in
tree-form in all solutions on the server. I can remove anything I may find
through the tool. It is a simple WinForms application you run on the server.

However, I can't find it for 2010 anywhere. I imagine there must be a built-in
tool for that now...? Anybody on 2010 with an idea?