Hi, we have migrated a site from wss2.0 to MOSS 2007 another server. the site works as expected. but for the lists and libraries when we click New->NewItem to add a new item to the list the following error occurs Web Part 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 it works fine for editItem from the dropdown of the listitem. Any workarounds? your help is appreciated Christian

Do you register on the Web.config "C:\inetpub\wwwroot\wss\VirtualDirectories\..." on the safecontrol tag the reference to your webpart, do they have any custom webpart? example:<SafeControl Assembly="*" Namespace="*" TypeName="*" Safe="True" AllowRemoteDesigner="True" /> André Lage Microsoft SharePoint, CRM and Sybase Consultant Blog:http://aaclage.blogspot.com Codeplex:http://spupload.codeplex.com/http://simplecamlsearch.codeplex.com/

hi andre, thanks for your response. i can say that its not a custom webpart. thisi is OOB webpart for adding newitems to the lists(i realised that its also a webpart only when it threw the error). i have checked the safecontrol for both in the virtual directories and as well as in the web.config of the site, but the thing is i cant figure out the name of this webpart. do you know which one would that be for adding a new item to a list? thanks

Hi Christian, Do you see this error in NewForm.aspx? If not then open your list in sharepoint designer and verify if this list has Newform.aspx present. This is the first step to troubleshoot your problem. Reply to my question. Regards, Manvir

To add to that , just check for this entry in Microsoft.SharePoint,Version=12.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c the Safe Control entry in web.configManvir

Also as you have migrated from WSS2.0 also add the previous version of Microsoft.Sharepoint dll as safe control entry in web.config.Manvir

hey, thank you all. i have solved this issue and its so weird tha i still dont know what was the cause for this error. i just restored the content database again and everything works as expected.