Re: Frontpage custom web part error
From: Jeremy (jmaddreysp_at_cox.net)
Date: 06/29/04
- Next message: Hugo Frappier: "Re: Audiences and AD Groups"
- Previous message: Tommy: "Re: Archiving in SPS2003"
- In reply to: Edward Lee: "Re: Frontpage custom web part error"
- Next in thread: Jeremy: "Re: Frontpage custom web part error"
- Reply: Jeremy: "Re: Frontpage custom web part error"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 29 Jun 2004 09:18:19 -0400
Unfortunately this article hasn't helped me. I don't have an IP or host
header assigned to the virtual server. The error messages are identical to
the ones mentioned in the article, however the cause seems to be
different....
"Edward Lee" <elee@ulgm.org> wrote in message
news:%23W46cqVXEHA.3112@tk2msftngp13.phx.gbl...
> SharePoint definately supports basic authentication. Does this KB article
> help at all:
>
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;830342&Product=sppsvr2003
>
> --
> Edward Lee
> Microsoft MVP - Sharepoint Portal Server
>
>
> "Jeremy" <jmaddreysp@cox.net> wrote in message
> news:O9A44bTXEHA.3596@tk2msftngp13.phx.gbl...
> > I seem to be having a conversation with myself. But there's good
reason,
> I
> > found that my last post was inaccurate, the true cause was that the site
> was
> > set up with basic authentication. Using integrated windows
authentication
> > allows access through Frontpage 2003, however basic throws an error.
Does
> > anyone know of a good solution, or is the solution simply "Sharepoint
> > doesn't support basic authentication"?
> >
> > "Jeremy" <jmaddreysp@cox.net> wrote in message
> > news:u7rUvtSXEHA.3564@TK2MSFTNGP11.phx.gbl...
> > > I have tracked down the cause of this...still hoping for a solution
> > though.
> > > After installing my site as the default web site, rather than a newly
> > > created web site in iis, everything works fine. I am able to open a
> page
> > > with custom web parts through Frontpage. Seems to be a bug to me.
Does
> > > anybody have any recommendations for how to work around this. I'd
like
> to
> > > be able to have multiple portal sites running on the same box. Any
help
> > is
> > > appreciated!
> > >
> > > "Jeremy" <jmaddreysp@cox.net> wrote in message
> > > news:%23NTNkhuWEHA.3012@tk2msftngp13.phx.gbl...
> > > > I have recently moved a development site from sharepoint services to
> > > > portal server. When deploying web parts, I am able to add them via
> the
> > > > browser without any error. However, I can't add them through
> Frontpage,
> > > or
> > > > even open a file with one in it (in Frontpage). I receive a "server
> > could
> > > > not complete your request" error. The details display a soap
> exception
> > > > relating to an unsafe webpart. If I delete the web part through the
> > > > browser, no problem, the files open in Frontpage. I'm assuming this
> is
> > > some
> > > > sort of
> > > > configuration issue we've created with SPS, since it worked fine
with
> > WSS,
> > > > but I'm not sure what that issue is. An error shows up in the event
> log
> > > > when I try to open the page using Frontpage (Failure in loading
> > assembly,
> > > > event id 1000). I have seen posts on this, but none of the
suggested
> > > > solutions (i.e. all unassigned ip's) have worked. Any other
> > suggestions?
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Next message: Hugo Frappier: "Re: Audiences and AD Groups"
- Previous message: Tommy: "Re: Archiving in SPS2003"
- In reply to: Edward Lee: "Re: Frontpage custom web part error"
- Next in thread: Jeremy: "Re: Frontpage custom web part error"
- Reply: Jeremy: "Re: Frontpage custom web part error"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
