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
7  2939 
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" <ol**********@hotmail.com> wrote in message
news:Ok**************@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
how about "Big things are made up of useful things........"
or better still
"Big things are made up from useful help from lots of people........"
"Kevin Spencer" <ks******@takempis.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... 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" <ol**********@hotmail.com> wrote in message
news:Ok**************@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
Infact I will tell you why i crossed posted:
1. It's an asp.net app so it seems reason to post here and I don't whether
this is an asp.net issue.....
2. It's an asp.net that contains COM+ components and I don't whether this is
a com+ issue.....
3. It's all written in C# .net and I don't whether this is a C# issue.....
4. And..... what the hell I will ask in the COM+ newsgroup because may be
this is not a .Net managed environment issue but a general rights issue with
windows 2003
Ollie.
PS - why do you have an MVP is it to help other people who are trying to
solve problems when they can't see the wood for the tree's or is it because
you just want geek fame and big yourself up?
Because if you are an example of the current MVP's then god help us......
Have A Nice Day....
"Kevin Spencer" <ks******@takempis.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... 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" <ol**********@hotmail.com> wrote in message
news:Ok**************@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
In 2003, there are special permissions for who can write to the eventlog.
This may be part of your problem. Also, the ASP.Net worker process by
default does not have the registry permissions to create a new eventlog
source.
This page may help you, It helped me. http://support.microsoft.com/default...b;en-us;323076
GL
"Ollie" <ol**********@hotmail.com> wrote in message
news:Ok**************@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
cheers GL.....
I already have the settings to allow the local asp.net app to create and
write to the event log, the remote process can't currently write to a remote
event log
Ollie
"GL" <GL@noSpam.ReplyToNewsgroup.com> wrote in message
news:uL**************@TK2MSFTNGP09.phx.gbl... In 2003, there are special permissions for who can write to the eventlog.
This may be part of your problem. Also, the ASP.Net worker process by
default does not have the registry permissions to create a new eventlog
source.
This page may help you, It helped me.
http://support.microsoft.com/default...b;en-us;323076
GL
"Ollie" <ol**********@hotmail.com> wrote in message
news:Ok**************@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
If you think that p***ing people off is going to be useful to you, go ahead
and call my advice useless. Netiquette exists for a reason, and my advice is
there to help you continue to get answers when you need them. I believe that
teaching a man to fish is much more valuable than giving a man a fish. Go
figure.
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Ollie" <why do they need this!!!!> wrote in message
news:#8**************@TK2MSFTNGP10.phx.gbl... how about "Big things are made up of useful things........"
or better still
"Big things are made up from useful help from lots of people........"
"Kevin Spencer" <ks******@takempis.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... 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" <ol**********@hotmail.com> wrote in message
news:Ok**************@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
I wonder if I can report MVP's for the 'wrong' attitude and generally being
useless and therefore not being a 'VALUED PROFESSIONAL'......
because I am now off to search the MVP site for such a link.....
Have A Nice Day...
FYI - Willy Denoyette [MVP] provide a very useful short and precise answer
that helped the problem greatly. I suggest you have a lot to learn about
'HELPING' people, having a pro-active answer is what is required not a
negative unhelpful answer, I guess you get more MVP 'points' by the number
of replies you post not the quality.....
"Kevin Spencer" <ks******@takempis.com> wrote in message
news:e7**************@TK2MSFTNGP12.phx.gbl... If you think that p***ing people off is going to be useful to you, go
ahead and call my advice useless. Netiquette exists for a reason, and my advice
is there to help you continue to get answers when you need them. I believe
that teaching a man to fish is much more valuable than giving a man a fish. Go
figure.
--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Ollie" <why do they need this!!!!> wrote in message
news:#8**************@TK2MSFTNGP10.phx.gbl... how about "Big things are made up of useful things........"
or better still
"Big things are made up from useful help from lots of people........"
"Kevin Spencer" <ks******@takempis.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... 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" <ol**********@hotmail.com> wrote in message
news:Ok**************@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
>
>
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: Peter A. Schott |
last post by:
If I want to verify that a file has finished writing before deleting the remote
file, what would be the best method?
Current code on Python 2.4:
#filename - remote FTP server File Name...
|
by: Jacob |
last post by:
Hello All,
I am trying to serve out some content via IIS that is hosted on a
remote fileserver, and am unable to get the delegation working
correctly. Our setup is as follows:
Local LAN...
|
by: John White |
last post by:
Hi,
I am having trouble getting back the entry messages from a
remote event log using the System.Diagnostics.EventLog
class. When the code is run against the local event log,
the event message...
|
by: GEL |
last post by:
Hi, I want to open a new browser window, let the user use that window
for several minutes, and when they close, I'd like to change the page
displayed in the original window.
According to...
|
by: Ollie |
last post by:
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...
| | |
by: Jeff |
last post by:
I have an ASP.NET web page accessing a SQL database. I've used VS to build
the app and stored it in the eNPTest02 directory of my localhost on my
development machine. The database is on the web. ...
|
by: Patrick A. |
last post by:
Dll written in VB.NET 2003 to start a command remotely.
You can :
- launch the command and wait until it's finished. (Ex. 1)
- launch the command providing a timeout in seconds, it will wait...
|
by: Thom Little |
last post by:
I have a simple web service that requires no input and returns a character
string.
I created the service and FTPd it to a remote server. The .dll to the .bin
directory and the single .asmx file...
|
by: =?Utf-8?B?cGVsZWdrMQ==?= |
last post by:
how when i write to the event viewer to have a clean test withought :
thnaks i nadvance
peleg
|
by: schaf |
last post by:
Hi NG!
I have a problem in my remote application.
After calling a remote function the calculation will be done by the
service. The calculation result will be sent to the caller (client)
via...
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
| | |
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and...
| | |
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The...
|
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| |
