Comments on Mikhail Dikov: Unable to add selected web part(s).

Good article, unfortunately it didn't help... ...

2011-12-05T02:09:44.155-08:00

Good article, unfortunately it didn't help... :( still get the same error...

Chris, the example is for SharePoint 2003, in Shar...

2011-10-21T10:42:17.739-07:00

Chris, the example is for SharePoint 2003, in SharePoint 2007 and later the best practice for most cases is to use the ASP.NET namespace. Here is a bit more info http://tinyurl.com/3uvlz44

The Namespace attribute of the web.config SafeCont...

2011-10-21T09:04:13.233-07:00

The Namespace attribute of the web.config SafeControl entry can be confusing.

My .cs file declares a namespace of TestWebPart, but the Namespace attribute should match the value of the type name in the .webpart file (which in my example was TestWebPart.TestWebPart).

Mikhail, why do you say the web part should not inherit from Microsoft.SharePoint.WebPartPages.WebPart?

This can happen for the following reason. This is...

2011-09-18T09:14:50.765-07:00

This can happen for the following reason.

This is security problem, So When you adding a web part it should be given CAS Permission.

So while adding a project in VS 2008, it will ask for BIN or GAC Deployment. So if you select GAC Deployment then , It will work without a problem.

Hari Gillala

Ok , this may be very late but will be useful for ...

2011-09-08T14:42:51.433-07:00

Ok , this may be very late but will be useful for the rest. I created a webpart and was getting the error "A Web Part or Web Form Control on this Page cannot be displayed or imported. The type could not be found or it is not registered as safe."

I figured that I was using a Chart inside this webpart and once I removed the reference of the chart, it worked. So, the Chart

I usually get that error. Is there a way for me to...

2011-08-03T01:58:49.563-07:00

I usually get that error. Is there a way for me to avoid it?

web design Perth

G, this statement is not true. YOU SHOULD NOT inhe...

2010-10-26T09:28:06.095-07:00

G, this statement is not true. YOU SHOULD NOT inherit from the SharePoint web part namespace as you suggest, but from the ASP.NET library System.Web.UI.WebControls.WebParts.

Also make sure your Webpart is inheriting from the...

2010-10-26T06:45:06.097-07:00

Also make sure your Webpart is inheriting from the SharePoint webparts

Microsoft.SharePoint.WebPartPages.WebPart

If you have renamed your namespace, verify that th...

2010-10-19T05:02:07.457-07:00

If you have renamed your namespace, verify that the namespace name changed on all places! (for example: SharePointProjectItem.spdata)

I have the exact same problem as Nebojsa. I have p...

2009-12-12T04:15:32.601-08:00

I have the exact same problem as Nebojsa. I have pulled my hair out already. Works fine internally but we have one custom webpart that wont work or be added from a public IP. Not registered as safe is all I get.

@AndersR: Ha. I was pulling my hair out, and I rea...

2009-12-03T07:20:50.893-08:00

@AndersR:
Ha. I was pulling my hair out, and I realized I forgot to declare it public... Thanks for the tip!

@hamidi:
Locate your "web.config" file for your site. Open the file and search for the tag "SafeControl", this is where you add the entry. Add your entry at the bottom of this list. It would be safe to follow the same format as the ones above if you

i'm too newbie in SharePoint. plz let me know ...

2009-10-17T23:48:23.462-07:00

i'm too newbie in SharePoint. plz let me know how can i add an entry in web.config to introduce my webpart as safe for it.
thx

Check the site collections webpart gallery!. I ha...

2009-10-02T08:58:59.807-07:00

Check the site collections webpart gallery!.

I have see an old copy of the .webpart file get stuck in there. if you've change the assembly reference it might be picking it up from this old copy.

My troubleshooting today ended at step 1 of 7. Tha...

2009-08-01T07:52:20.381-07:00

My troubleshooting today ended at step 1 of 7. Thanks, Mikhail!

Make sure when you change the signing file "*...

2009-07-13T05:44:19.966-07:00

Make sure when you change the signing file "*.snk" you build the solution and get the new PublicKeyToken of it with "sn.exe -T yourwepart.dll". Then change the PublicKeyToken in manifest.xml, solutionConfig.xml and yourwebpart.webpart.

Note: I use STSDEV for webpart development.

Hey, guy who said:

"Check that you acciden...

2009-02-03T13:05:00.000-08:00

Hey, guy who said:

"Check that you accidentially forgot to declare the web part as public"

Thanks man. Can't believe I missed that.

Ok, we did not manage to get those web parts on ou...

2008-10-28T08:17:00.000-07:00

Ok, we did not manage to get those web parts on our page, but when i extended web app to extranet zone, and set host header for that web app web parts are working, they can be inserted to a page. So that worked for us, not sure what i’m missing still…

One stupid mistake I made was to forget to make th...

2008-10-07T14:30:00.000-07:00

One stupid mistake I made was to forget to make the web part class public.

Thanks for the tips!

I was going nuts tryin...

2008-09-25T01:54:00.000-07:00

Thanks for the tips!

I was going nuts trying to get this working, just to find out I had a minor typo in the namespace in the .webpart file.

Make sure that the type listed in th .webpart file...

2008-08-21T17:17:00.000-07:00

Make sure that the type listed in th .webpart file is exactly the same as the class file. For instance, my webpart type was "Company.OrderCheckIn.OrderCheckInWebPart" and my .webpart file referenced "Company.OrderCheckIn.OrderCheckinWebPart". Notice the lowercase "I" in th e.webpart file. that was what was killing me.

nebojsa, why don't you try to post this to one of ...

2008-07-18T07:25:00.000-07:00

nebojsa, why don't you try to post this to one of the SharePoint usergroups. There are many people that track these and that can give good suggestions. From your description it could be an issue with the way you setup your service accounts, but it's hard to tell.

Well the problem is that neither custom nor build-...

2008-07-17T04:44:00.000-07:00

Well the problem is that neither custom nor build-in web parts are able to be added on page. It’s completely new installation at the moment, with no custom web parts deployed. Just those build-in by Microsoft as part of MOSS 2007. The strange thing is that everything was working fine until one day, then no more web parts couldn’t be added over internet. Now we have followed previous procedure of

Are you sure your web part does not require specif...

2008-07-15T20:15:00.000-07:00

Are you sure your web part does not require specific CAS configuration? One quick way to see if that's the issue is to change the trust level to Full and run your web parts. If that's the case analyze your assembly and create proper CAS policies or use WSPBuilder, which does that for you.

I have same problem with MOSS 2007 on my server ma...

2008-06-27T01:39:00.000-07:00

I have same problem with MOSS 2007 on my server machine. “Unable to add selected web part(s)”. Strange thing is that I cannot add web part when I access my page over my public IP, and from local that’s no problem. Another strange thing is that this is the case with Microsoft build in web parts and mine custom ones, but not with KWizCom web parts. If this is permission problem I’m not sure where

Where do you store your page. Do you provision it ...

2008-06-19T20:27:00.000-07:00

Where do you store your page. Do you provision it in the web site, do you create it in a document library, or you use an aspx page in the _layouts folder?