WebPartPages:DataViewWebPart

[Derek Martin]

Hi, I am running SPPS2K3 on my dev box and FP2K3 on my
workstation and am trying to insert a
WebPartPagesataViewWebPart from some examples at MSDN
using the NorthWind database which is on my SQL Server. I
have everything installed properly (I think) but when I go
to add the data view from the Data Source Catalog, instead
of the data view, I get this error message:
WebPartPagesataViewWebPart - A Web Part or Web Form
Control on this Web Part Page cannot be displayed or
imported because it is not registered on this site as safe.
I have web.config turned up to FULL in the web part
security settings and it is still giving me these fits.
Can someone assist?

Thanks,
Derek

 

[John Jansen \(MSFT\)]

Hi Derek,

Did you run SPS or FP in their beta forms and upgrade to RTM?

What happens if you open your site in FrontPage and drag the Announcements
list directory from the Folder list onto a new page in Design view?

 

[Derek Martin]

Thank you for the assistance John. These are all clean installs on new
machines of the released versions of Sharepoint Portal Server 2K3 and
FrontPage 2K3. I didn't have an announcements list in my default setup,
only Contacts, Events, General Discussion, Links and Tasks. Dragging any of
these lists onto a page in design mode results in the same appearance of the
WebPartPagesataViewWebPart.

Any ideas?

 

[John Jansen \(MSFT\)]

Hi Derek,

This is a little puzzling. If you can answer each question one by one I
might get this figured out:

1. were there any errors during installation of SharePoint?
2. Can you open default.aspx without error in FrontPage?
3. Can you click on Data..Insert Web Part and drag a List View Web Part onto
a page (like the Events list from the Web Part Catalog instead of from the
Folder list)?
4. Can you revert the web.config file back to the default state and check as
well?

 

[Derek Martin]

Thanks again John. Here are the answers to your questions.

1. No errors during Sharepoint install.
2. I cannot open default.aspx. I recieve this error:
soap:Server Exception of type
Microsoft.SharePoint.SoapServer.SoapServerException was thrown. A Web Part
or Web Form Control on this Web Part Page cannot be displayed or imported
because it is not registered as safe on this site. You may not be able to
open this page in an HTML editor that is compatible with Microsoft Windows
SharePoint Services, such as Microsoft Office FrontPage. To fix this page,
contact the site administrator to have the Web Part or Web Form Control
configured as safe. You can also remove the Web Part or Web Form Control
from the page by using the Web Parts Maintenance Page. If you have the
necessary permissions, you can use this page to disable Web Parts
temporarily or remove personal settings. For more information, contact your
site administrator.

3. I get an error in teh Web Part Catalog when draggin the events on the
design screen of the new page: A Web Part or Web Form Control on this Web
Part Page cannot be displayed or imported because it is not registered on
this site as safe.
4. Reverting back to the standard 'installed' version of web.config does
not correct (only change was modding trust level to Full instead of
WSS_Minimal)

I guess at least it is consistant and everything is failing...but that isn't
too happy still

Any ideas?

Thanks!

Derek

 

[John Jansen \(MSFT\)]

Thanks for going through each step, it helps a lot.

I am going to forward your post internally to someone else who is an expert
in the sharepoint.dll to see if he knows about what could cause this.

When he replies to me I'll reply to you again.

My thoughts: the sharepoint.dll did not install on your server properly --
somehow.

 

[Derek Martin]

Wonderful, thank you very much and I like forward to hearing from you soon!

Derek

 

[John Jansen \(MSFT\)]

OK Derek, I think I found it. I forgot to ask if you are mapping your IP
address, but I am going to assume you are since this is the only known cause
of this profound an issue:

http://support.microsoft.com/?id=830342

I hope that helps!

 

[Derek Martin]

Hi John, yep that did it...thanks so much! Question is...why the heck does
that cause the strangeness?

Thanks,
Derek

 

[John Jansen \(MSFT\)]

Yeah, that is the question.

I'm definitely not the one to answer that...I just come up with workarounds.

 

[Fred Chateau]

...

I have a thread going on a similar problem in

microsoft.public.frontpage.client with Subject =
WebPartPagesataViewWebPart

Did your solution seem to fix errors of this type as well? I have been

fortunate to get a MS tech to help me out on it...feel free to reply to
group or me for more details.

Derek,

Yes, everything is working well. I read your thread in frontpage.client and
I think I have an explanation for you.

After reading the KB article it occurred to me that all of my virtual
servers are assigned an IP address with the exception of the default server,
which is set to *all unassigned addresses*. Even though the default server
is not extended, it would seem that .NET thinks it's the root for any
SharePoint extended site, most likely because it's the only one not tied to
a particular address.

This is an ideal situation for me because I also have many FrontPage 2002
extended virtual servers running .NET applications, and I was concerned
about interactions between the two. I want to be able to install and
register WebParts for all SharePoint sites simultaneously, and from what
I've read here, it appears that I can set up my individual .NET applications
as usual, with assemblies located in the bin folder and configuration files
in the root, while at the same time I can add my SharePoint WebParts and
configuration files to the default sever for all the SharePoint sites.

I'm assumming that the Microsoft.SharePoint assembly is installed in the
GAC, but if .NET searches the default Web site root folder for a web.config
file for *any* SharePoint site, I'm hoping it will also look in the default
server's \bin folder for WebPart assemblies. That means single folder
configuration and assembly deployment without screwing around with strong
names and the GAC.

As soon as I finish developing my first WebPart control and deploying it,
I'll report in here with the results. I suppose we can leave it to Microsoft
or the MVP's to discover whether there's a downside to doing it this way,
and specifically with regard to security issues.

I copied my original post below for the benefit of any frontpage.client
subscribers interested in this subject.

--
Regards,

Fred Chateau
e-mail: fchateauAtHotelMotelNowDotCom

--
After installing WSS and extending several virtual servers, I discovered
that all Web Part controls were returning the error message "Not registered
as safe", although each extended virtual server root contained a web.config
file. After several hours of working on this problem, I decided to place a
copy of one of the web.config files which SharePoint had installed, into the
default Web server's root folder. Since I hadn't extended the default
server, there was no web.config file located there. To my surprise, the Web
Part controls started working in all the extended virtual servers.

So my question is what's going on here? In retrospect, it makes some sense
to me. Although the ASP.NET script maps appear separately in IIS Manager, I
believe they are also inherited from the default server, but if the
web.config file is being inherited, why does SharePoint install one in each
virtual server?

Also, should I assume the other unmanaged folders and files that SharePoint
installs are similarly inherited?