Re: Error: Failure in loading assembly message issued - but the web parts work
From: David McKenzie (DavidMcKenzie_at_bonbon.net)
Date: 11/02/04
- Next message: David McKenzie: "Re: Error: Failure in loading assembly message issued - but the web parts work"
- Previous message: Mats Larsson: "VBScript result returned to XSL"
- In reply to: Loke Kit Kai: "Re: Error: Failure in loading assembly message issued - but the web parts work"
- Next in thread: Wei-Dong XU [MSFT]: "Re: Error: Failure in loading assembly message issued - but the web parts work"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 2 Nov 2004 08:36:13 -0600
Absolutly!
The web part works, but there are errors in the Event Log for each time a
web part page is initially loaded after IIS (re)starts.
I suspect that this contributes to a performance hit at this initial page
load, but if nothing else, I dislike the practice of consistantly ignoring
error messages.
It makes it harder to troubleshoot real problems
"Loke Kit Kai" <kitkaiml@singnet.com.sg> wrote in message
news:OIy3l3HwEHA.3976@TK2MSFTNGP09.phx.gbl...
> I'm not sure if u can deploy dlls in the bin directory, and sharepoint can
> still reference it... Have you tried deploying to GAC and see if the error
> disappears?
>
> "David McKenzie" <DavidMcKenzie@bonbon.net> wrote in message
> news:ejd$qVDwEHA.2012@TK2MSFTNGP15.phx.gbl...
> > I made the modification below in the dwp in \inetpub\wwroot\wpcatalog\
> > no change - error still occurs on first page load fillowing an iisreset
> > do i need to rebuild the wp?
> >
> > "Wei-Dong XU [MSFT]" <v-wdxu@online.microsoft.com> wrote in message
> > news:iLedSpivEHA.768@cpmsftngxa10.phx.gbl...
> > > Hi David,
> > >
> > > Thank you for posting the further troubleshooting result! Now, I'd
> suggest
> > > you can change the xml line below of your dwp file from
> > > <Assembly>DDocByAnalyst, Version=1.0.0.0,
> > > Culture=neutral,PublicKeyToken=null</Assembly>
> > > to
> > > <Assembly>DDocByAnalyst</Assembly>
> > >
> > > This full name of one assembly is "DDocByAnalyst, Version=1.0.0.0,
> > > Culture=neutral,PublicKeyToken=null", which doesn't mean this assembly
> is
> > > located at GAC because the publickeytoken is null. The publickey
token,
> in
> > > fact, is one hash value for the assembly which is used to figure out
the
> > > unique of this assembly. So when there is no value for this assembly,
> .Net
> > > will try to locate it from the /bin folder of your application; which
> > > should be the cause for the error message in the event log.
> > >
> > > Look forward to your reply!
> > >
> > > Best Regards,
> > > Wei-Dong XU (WD)
> > > Microsoft Product Support Services
> > > Get Secure! - www.microsoft.com/security
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >
> >
>
>
- Next message: David McKenzie: "Re: Error: Failure in loading assembly message issued - but the web parts work"
- Previous message: Mats Larsson: "VBScript result returned to XSL"
- In reply to: Loke Kit Kai: "Re: Error: Failure in loading assembly message issued - but the web parts work"
- Next in thread: Wei-Dong XU [MSFT]: "Re: Error: Failure in loading assembly message issued - but the web parts work"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|