Re: writing to a remote event log.....

From: Kevin Spencer (kspencer_at_takempis.com)
Date: 04/22/04 

Date: Thu, 22 Apr 2004 14:22:51 -0400

Everybody who cross-posts has a reason for doing so. However, nobody has a
RIGHT reason for doing so. 

-- 
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Ollie" <ollie_riches@hotmail.com> wrote in message
news:OkRITSJKEHA.2680@TK2MSFTNGP11.phx.gbl...
> okay sorry for cross posting but want to see if any one can explain the
> solution to this problem for me:
>
> I have a .Net ASP.Net app written in C# that use COM+ components to do
some
> business processing......
>
> When I have the ASP.Net website and the COM+ components installed on the
> same machine (i.e everything local) it all works fine, and it can write to
> the event log....
>
> But when I moved the COM+ component onto a remote application server I get
> the following error when  the COM+ service attempts to write to a remote
> event log.
>
> A first chance exception of type 'System.InvalidOperationException'
occurred
> in mscorlib.dll
>
> Additional information: Cannot open log for source {0}. You may not have
> write access.
>
> Can anyone tell me how to cofig the event log so that the remote COM+
> service can write to this event log.
>
> All servers in my architecture are running windows 2003 server. I  know
that
> the COM+ service is running correctly because several calls i have made to
> the component have completed correctly, but when a particular method fails
> and attempt to wirte to the remote Event log it fails and the exception is
> generated in the ASP.Net application saying the above,  this indicates
that
> it can not write to the event log does it?
>
> Cheers in advance
>
> Ollie
>
>

Relevant Pages

  • Re: Event ID: 4000
    ... Based on the text of your event log, it appears that DNS is working fine. ... The problem may happen when your server attempts to connect to the remote ...
    (microsoft.public.exchange2000.protocols)
  • Re: Urgent!!! Large amount of DCOM 10020 errors in event log afte
    ... And the the Event log not accessible remotely as due to remote registry ... MCSA Windows 2003 server ... the restore, the DHCP database is corrupted and I had restored the ...
    (microsoft.public.windows.server.general)
  • Re: writing to a remote event log.....
    ... and call my advice useless. ... >> Everybody who cross-posts has a reason for doing so. ... >>> But when I moved the COM+ component onto a remote application server I ... >>> Can anyone tell me how to cofig the event log so that the remote COM+ ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: writing to a remote event log.....
    ... and call my advice useless. ... >> Everybody who cross-posts has a reason for doing so. ... >>> But when I moved the COM+ component onto a remote application server I ... >>> Can anyone tell me how to cofig the event log so that the remote COM+ ...
    (microsoft.public.dotnet.framework.component_services)
  • Re: writing to a remote event log.....
    ... and call my advice useless. ... >> Everybody who cross-posts has a reason for doing so. ... >>> But when I moved the COM+ component onto a remote application server I ... >>> Can anyone tell me how to cofig the event log so that the remote COM+ ...
    (microsoft.public.dotnet.framework.aspnet)
Loading