Re: Remote debugging outside of domain
I'm guessing windbg gives you the same problems? In some respects it's better than remotedebugger and VisualStudio On 9 August 2010 13:35, Michael Lyons wrote: > Yes I have tried that and unfortunately it’s only native which means I > lose the ability to set break points as it doesn’t recognise the PDB’s. > > > > - > Michael Lyons > > > > *From:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *On Behalf Of *mike smith > *Sent:* Monday, 9 August 2010 1:26 PM > *To:* ozDotNet > *Subject:* Re: Remote debugging outside of domain > > > > It's probably bad security, (but if you're inside a LAN or connecting via > VPN or SSH it likely doesn't matter) but have you tried going to the options > dialog (inside remote debugger stub) and tick allow any user to debug? > > On 8 August 2010 20:02, Michael Lyons wrote: > > I'm needing to debug a Windows service to see why it is crashing after a > few > minutes. > I've setup the remote debugger on the host machine, but I receive the error > message "Unable to connect to the Microsoft Visual Studio Remote Debugging > Monitor named 'x'. Logon Failure: unknown username or bad password". > The issue is that my workstation is within a AD domain whilst the machine I > wish to debug is not. How can I go about debugging the remote machine > without disconnecting from the domain or connecting the remote machine to > the domain? > > The service has also for some reason or another stopped outputting to via > System.Diagnostics.EventLogTraceListener, would anyone have any clue why > this would happen? > > - > Michael Lyons > > > > > -- > Meski > > "Going to Starbucks for coffee is like going to prison for sex. Sure, > you'll get it, but it's going to be rough" - Adam Hills > -- Meski "Going to Starbucks for coffee is like going to prison for sex. Sure, you'll get it, but it's going to be rough" - Adam Hills
RE: Remote debugging outside of domain
Coincidently I spoke to the PM on this feature last week about this very issue. It's a known limitation - which requires a re-architecture of the remote debugging engine. Unfortunately, you won't see this supported until a future version of VS. -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Michael Lyons Sent: Sunday, August 08, 2010 8:19 PM To: 'ozDotNet' Subject: RE: Remote debugging outside of domain I have to say it would be really nice if it just worked similar to what you were saying but popped up with an authentication dialog where you could actually logon remotely using the debugging account. - Michael Lyons -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Wallace Turner Sent: Monday, 9 August 2010 11:52 AM To: 'ozDotNet' Subject: RE: Remote debugging outside of domain Condolences++ Why do you make it so damn hard to debug a process on a remote machine (listen up Microsoft) As always, I'm sure there is a good reason for everything but this is what would be nice: a) you install remote debugging on remote machine b) you forward port on firewall (optionally) c) enter remote machine name a la SQL connections (myhost.com,5000) and start debugging Yes I know it doesn't work this way. Geez it would be nice tho. No messing around with users, one port only. Security could be controlled per process via the remote debugging frontend on the remote machine (yes that would require some work) -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Keogh Sent: Monday, 9 August 2010 11:47 AM To: 'ozDotNet' Subject: RE: Remote debugging outside of domain "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor names 'x'. The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. Authentication failed. Please see Help for assistance." Hi Michael, my condolences. I spent many solid hours of suffering one afternoon last year trying every trick I could think of to get around this exact problem ... I failed. I gave up with remote debugging and used windbg on the server machine to attach to the troublesome process and I eventually found the problem (missing resource files). Sorry I can't offer any more than sympathy. Greg
RE: Remote debugging outside of domain
Yes I have tried that and unfortunately it’s only native which means I lose the ability to set break points as it doesn’t recognise the PDB’s. - Michael Lyons From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of mike smith Sent: Monday, 9 August 2010 1:26 PM To: ozDotNet Subject: Re: Remote debugging outside of domain It's probably bad security, (but if you're inside a LAN or connecting via VPN or SSH it likely doesn't matter) but have you tried going to the options dialog (inside remote debugger stub) and tick allow any user to debug? On 8 August 2010 20:02, Michael Lyons wrote: I'm needing to debug a Windows service to see why it is crashing after a few minutes. I've setup the remote debugger on the host machine, but I receive the error message "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'x'. Logon Failure: unknown username or bad password". The issue is that my workstation is within a AD domain whilst the machine I wish to debug is not. How can I go about debugging the remote machine without disconnecting from the domain or connecting the remote machine to the domain? The service has also for some reason or another stopped outputting to via System.Diagnostics.EventLogTraceListener, would anyone have any clue why this would happen? - Michael Lyons -- Meski "Going to Starbucks for coffee is like going to prison for sex. Sure, you'll get it, but it's going to be rough" - Adam Hills
Re: Remote debugging outside of domain
It's probably bad security, (but if you're inside a LAN or connecting via VPN or SSH it likely doesn't matter) but have you tried going to the options dialog (inside remote debugger stub) and tick allow any user to debug? On 8 August 2010 20:02, Michael Lyons wrote: > I'm needing to debug a Windows service to see why it is crashing after a > few > minutes. > I've setup the remote debugger on the host machine, but I receive the error > message "Unable to connect to the Microsoft Visual Studio Remote Debugging > Monitor named 'x'. Logon Failure: unknown username or bad password". > The issue is that my workstation is within a AD domain whilst the machine I > wish to debug is not. How can I go about debugging the remote machine > without disconnecting from the domain or connecting the remote machine to > the domain? > > The service has also for some reason or another stopped outputting to via > System.Diagnostics.EventLogTraceListener, would anyone have any clue why > this would happen? > > - > Michael Lyons > > -- Meski "Going to Starbucks for coffee is like going to prison for sex. Sure, you'll get it, but it's going to be rough" - Adam Hills
RE: Remote debugging outside of domain
I have to say it would be really nice if it just worked similar to what you were saying but popped up with an authentication dialog where you could actually logon remotely using the debugging account. - Michael Lyons -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Wallace Turner Sent: Monday, 9 August 2010 11:52 AM To: 'ozDotNet' Subject: RE: Remote debugging outside of domain Condolences++ Why do you make it so damn hard to debug a process on a remote machine (listen up Microsoft) As always, I'm sure there is a good reason for everything but this is what would be nice: a) you install remote debugging on remote machine b) you forward port on firewall (optionally) c) enter remote machine name a la SQL connections (myhost.com,5000) and start debugging Yes I know it doesn't work this way. Geez it would be nice tho. No messing around with users, one port only. Security could be controlled per process via the remote debugging frontend on the remote machine (yes that would require some work) -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Keogh Sent: Monday, 9 August 2010 11:47 AM To: 'ozDotNet' Subject: RE: Remote debugging outside of domain "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor names 'x'. The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. Authentication failed. Please see Help for assistance." Hi Michael, my condolences. I spent many solid hours of suffering one afternoon last year trying every trick I could think of to get around this exact problem ... I failed. I gave up with remote debugging and used windbg on the server machine to attach to the troublesome process and I eventually found the problem (missing resource files). Sorry I can't offer any more than sympathy. Greg
RE: Remote debugging outside of domain
I previously had it working once before on another project, but that was before we put our workstations into a domain and it was a slight challenge for 30 minutes, but then all ran smoothly. The notebook idea isn't a bad idea, but it's not really an ideal long term solution. Would be nice if there was a way to just tell Windows to dump all method calls with arguments and exceptions to the hard disk without having to do too much overhead such as tracing. I'm sure it could be done as it's similar to what most profilers do. Maybe I could possibly run a profiler thought it and find the answer with some guess work. - Michael Lyons -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Maddin, Peter Sent: Monday, 9 August 2010 11:25 AM To: ozDotNet Subject: RE: Remote debugging outside of domain If I was in this position, I would install VS on a notebook (if you don't have one spare, they are pretty cheap these days) and place it in the same network environment as your server. I would then use remote debugging to discover the issue and if necessary nuke the notebook afterwards. >From all the pain you are going through, maybe a simple approach would be quicker. That being said I have only debugged services remotely within a domain (and I found that challenging enough). Regards Peter Maddin Applications Development Officer PathWest Laboratory Medicine WA Phone : +618 9473 3944 Fax : +618 9473 3982 E-Mail : peter.mad...@pathwest.wa.gov.au The contents of this e-mail transmission outside of the WAGHS network are intended solely for the named recipient's), may be confidential, and may be privileged or otherwise protected from disclosure in the public interest. The use, reproduction, disclosure or distribution of the contents of this e-mail transmission by any person other than the named recipient(s) is prohibited. If you are not a named recipient please notify the sender immediately.
RE: Remote debugging outside of domain
Condolences++ Why do you make it so damn hard to debug a process on a remote machine (listen up Microsoft) As always, I'm sure there is a good reason for everything but this is what would be nice: a) you install remote debugging on remote machine b) you forward port on firewall (optionally) c) enter remote machine name a la SQL connections (myhost.com,5000) and start debugging Yes I know it doesn't work this way. Geez it would be nice tho. No messing around with users, one port only. Security could be controlled per process via the remote debugging frontend on the remote machine (yes that would require some work) -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Keogh Sent: Monday, 9 August 2010 11:47 AM To: 'ozDotNet' Subject: RE: Remote debugging outside of domain "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor names 'x'. The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. Authentication failed. Please see Help for assistance." Hi Michael, my condolences. I spent many solid hours of suffering one afternoon last year trying every trick I could think of to get around this exact problem ... I failed. I gave up with remote debugging and used windbg on the server machine to attach to the troublesome process and I eventually found the problem (missing resource files). Sorry I can't offer any more than sympathy. Greg
RE: Remote debugging outside of domain
"Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor names 'x'. The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. Authentication failed. Please see Help for assistance." Hi Michael, my condolences. I spent many solid hours of suffering one afternoon last year trying every trick I could think of to get around this exact problem ... I failed. I gave up with remote debugging and used windbg on the server machine to attach to the troublesome process and I eventually found the problem (missing resource files). Sorry I can't offer any more than sympathy. Greg
RE: Remote debugging outside of domain
If I was in this position, I would install VS on a notebook (if you don't have one spare, they are pretty cheap these days) and place it in the same network environment as your server. I would then use remote debugging to discover the issue and if necessary nuke the notebook afterwards. >From all the pain you are going through, maybe a simple approach would be >quicker. That being said I have only debugged services remotely within a domain (and I found that challenging enough). Regards Peter Maddin Applications Development Officer PathWest Laboratory Medicine WA Phone : +618 9473 3944 Fax : +618 9473 3982 E-Mail : peter.mad...@pathwest.wa.gov.au The contents of this e-mail transmission outside of the WAGHS network are intended solely for the named recipient's), may be confidential, and may be privileged or otherwise protected from disclosure in the public interest. The use, reproduction, disclosure or distribution of the contents of this e-mail transmission by any person other than the named recipient(s) is prohibited. If you are not a named recipient please notify the sender immediately.
RE: Remote debugging outside of domain
I've turned both off with no firewalls in between. :( - Michael Lyons -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of David Richards Sent: Monday, 9 August 2010 10:53 AM To: ozDotNet Subject: Re: Remote debugging outside of domain Windows (or any other) firewall maybe? David "If we can hit that bullseye, the rest of the dominoes will fall like a house of cards... checkmate!" -Zapp Brannigan, Futurama On Mon, Aug 9, 2010 at 10:50, Michael Lyons wrote: > S close. I can see that it logged on the remote host with the same > username, but now it's spewing out another error. > > "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor > names 'x'. The Visual Studio Remote Debugger on the target computer cannot > connect back to this computer. Authentication failed. Please see Help for > assistance." > > I checked help and it only talks about making sure that the machines can > actually see each other which they can. I even have put the full > workstations domain address into the windows hosts file just in case it may > be getting confused by the domain but to no avail. > > - > Michael Lyons > >
RE: Remote debugging outside of domain
I've used windbg before with crash dumps and I can even use the 'Problem reports and solutions' section under control panel to kind of see where the error is happening. But under test conditions this seems to work fine. I'm sure it's something to do with specific machine and particular function parameter information which I really need a full blown debugger to figure this one out. I really would prefer to get remote debugger working as this is our staging machine for an external environment which is fine to always debug on - just would prefer not having to install VS on the machine itself and worry about licensing issues. - Michael Lyons -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Wallace Turner Sent: Monday, 9 August 2010 10:18 AM To: 'ozDotNet' Subject: RE: Remote debugging outside of domain If you are still stuck then I would give windbg a try (see earlier post ' Unable to diagnose a crash') as it may be able to give you enough info to fix the problem -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Michael Lyons Sent: Monday, 9 August 2010 9:12 AM To: ozdotnet@ozdotnet.com Subject: RE: Remote debugging outside of domain No luck. Same result. Liked the idea though. I also made sure that the user was in the VS remote debugger permissions and they had debugging permissions under the local security policies. - Michael Lyons -Original Message- From: Ken Schaefer [mailto:k...@adopenstatic.com] Sent: Sunday, 8 August 2010 9:50 PM To: Michael Lyons Subject: RE: Remote debugging outside of domain One option to try: Connect to shared folder on the remote machine first (e.g. c$ admin share) using Explorer Then VS. NET might use your established credentials to attempt to connect to the remote debugger service Cheers Ken -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Michael Lyons Sent: Sunday, 8 August 2010 8:03 PM To: 'ozDotNet' Subject: Remote debugging outside of domain I'm needing to debug a Windows service to see why it is crashing after a few minutes. I've setup the remote debugger on the host machine, but I receive the error message "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'x'. Logon Failure: unknown username or bad password". The issue is that my workstation is within a AD domain whilst the machine I wish to debug is not. How can I go about debugging the remote machine without disconnecting from the domain or connecting the remote machine to the domain? The service has also for some reason or another stopped outputting to via System.Diagnostics.EventLogTraceListener, would anyone have any clue why this would happen? - Michael Lyons
Re: Remote debugging outside of domain
Windows (or any other) firewall maybe? David "If we can hit that bullseye, the rest of the dominoes will fall like a house of cards... checkmate!" -Zapp Brannigan, Futurama On Mon, Aug 9, 2010 at 10:50, Michael Lyons wrote: > S close. I can see that it logged on the remote host with the same > username, but now it's spewing out another error. > > "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor > names 'x'. The Visual Studio Remote Debugger on the target computer cannot > connect back to this computer. Authentication failed. Please see Help for > assistance." > > I checked help and it only talks about making sure that the machines can > actually see each other which they can. I even have put the full > workstations domain address into the windows hosts file just in case it may > be getting confused by the domain but to no avail. > > - > Michael Lyons > >
RE: Remote debugging outside of domain
S close. I can see that it logged on the remote host with the same username, but now it's spewing out another error. "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor names 'x'. The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. Authentication failed. Please see Help for assistance." I checked help and it only talks about making sure that the machines can actually see each other which they can. I even have put the full workstations domain address into the windows hosts file just in case it may be getting confused by the domain but to no avail. - Michael Lyons -Original Message- From: Ken Schaefer [mailto:k...@adopenstatic.com] Sent: Monday, 9 August 2010 9:13 AM To: Michael Lyons Subject: RE: Remote debugging outside of domain Can you create a local user on the remote machine that has the same username/password that you have in the AD domain? Cheers Ken -Original Message- From: Michael Lyons [mailto:maill...@ittworx.com] Sent: Monday, 9 August 2010 9:09 AM To: Ken Schaefer Subject: RE: Remote debugging outside of domain No luck. Same result. Liked the idea though. I also made sure that the user was in the VS remote debugger permissions and they had debugging permissions under the local security policies. - Michael Lyons -Original Message- From: Ken Schaefer [mailto:k...@adopenstatic.com] Sent: Sunday, 8 August 2010 9:50 PM To: Michael Lyons Subject: RE: Remote debugging outside of domain One option to try: Connect to shared folder on the remote machine first (e.g. c$ admin share) using Explorer Then VS. NET might use your established credentials to attempt to connect to the remote debugger service Cheers Ken -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Michael Lyons Sent: Sunday, 8 August 2010 8:03 PM To: 'ozDotNet' Subject: Remote debugging outside of domain I'm needing to debug a Windows service to see why it is crashing after a few minutes. I've setup the remote debugger on the host machine, but I receive the error message "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'x'. Logon Failure: unknown username or bad password". The issue is that my workstation is within a AD domain whilst the machine I wish to debug is not. How can I go about debugging the remote machine without disconnecting from the domain or connecting the remote machine to the domain? The service has also for some reason or another stopped outputting to via System.Diagnostics.EventLogTraceListener, would anyone have any clue why this would happen? - Michael Lyons
RE: Remote debugging outside of domain
If you are still stuck then I would give windbg a try (see earlier post ' Unable to diagnose a crash') as it may be able to give you enough info to fix the problem -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Michael Lyons Sent: Monday, 9 August 2010 9:12 AM To: ozdotnet@ozdotnet.com Subject: RE: Remote debugging outside of domain No luck. Same result. Liked the idea though. I also made sure that the user was in the VS remote debugger permissions and they had debugging permissions under the local security policies. - Michael Lyons -Original Message- From: Ken Schaefer [mailto:k...@adopenstatic.com] Sent: Sunday, 8 August 2010 9:50 PM To: Michael Lyons Subject: RE: Remote debugging outside of domain One option to try: Connect to shared folder on the remote machine first (e.g. c$ admin share) using Explorer Then VS. NET might use your established credentials to attempt to connect to the remote debugger service Cheers Ken -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Michael Lyons Sent: Sunday, 8 August 2010 8:03 PM To: 'ozDotNet' Subject: Remote debugging outside of domain I'm needing to debug a Windows service to see why it is crashing after a few minutes. I've setup the remote debugger on the host machine, but I receive the error message "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'x'. Logon Failure: unknown username or bad password". The issue is that my workstation is within a AD domain whilst the machine I wish to debug is not. How can I go about debugging the remote machine without disconnecting from the domain or connecting the remote machine to the domain? The service has also for some reason or another stopped outputting to via System.Diagnostics.EventLogTraceListener, would anyone have any clue why this would happen? - Michael Lyons
RE: Remote debugging outside of domain
No luck. Same result. Liked the idea though. I also made sure that the user was in the VS remote debugger permissions and they had debugging permissions under the local security policies. - Michael Lyons -Original Message- From: Ken Schaefer [mailto:k...@adopenstatic.com] Sent: Sunday, 8 August 2010 9:50 PM To: Michael Lyons Subject: RE: Remote debugging outside of domain One option to try: Connect to shared folder on the remote machine first (e.g. c$ admin share) using Explorer Then VS. NET might use your established credentials to attempt to connect to the remote debugger service Cheers Ken -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Michael Lyons Sent: Sunday, 8 August 2010 8:03 PM To: 'ozDotNet' Subject: Remote debugging outside of domain I'm needing to debug a Windows service to see why it is crashing after a few minutes. I've setup the remote debugger on the host machine, but I receive the error message "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'x'. Logon Failure: unknown username or bad password". The issue is that my workstation is within a AD domain whilst the machine I wish to debug is not. How can I go about debugging the remote machine without disconnecting from the domain or connecting the remote machine to the domain? The service has also for some reason or another stopped outputting to via System.Diagnostics.EventLogTraceListener, would anyone have any clue why this would happen? - Michael Lyons
RE: Remote debugging outside of domain
> Is the trace option turned off in the app.config? Do you mean have I setup the system.diagnostics section; then yes I have as below. I haven't however used the trace options which are part of system.web as I'm sure you don't need these in a windows service, please correct me though if I am wrong. - Michael Lyons -Original Message- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of David Richards Sent: Monday, 9 August 2010 8:03 AM To: ozDotNet Subject: Re: Remote debugging outside of domain Have you tried logging on with credentials from the remote computer? ie, create a local "testuser" account on the remote server and log on with "remoteserver\testuser". Is the trace option turned off in the app.config? David "If we can hit that bullseye, the rest of the dominoes will fall like a house of cards... checkmate!" -Zapp Brannigan, Futurama On Sun, Aug 8, 2010 at 20:02, Michael Lyons wrote: > I'm needing to debug a Windows service to see why it is crashing after a few > minutes. > I've setup the remote debugger on the host machine, but I receive the error > message "Unable to connect to the Microsoft Visual Studio Remote Debugging > Monitor named 'x'. Logon Failure: unknown username or bad password". > The issue is that my workstation is within a AD domain whilst the machine I > wish to debug is not. How can I go about debugging the remote machine > without disconnecting from the domain or connecting the remote machine to > the domain? > > The service has also for some reason or another stopped outputting to via > System.Diagnostics.EventLogTraceListener, would anyone have any clue why > this would happen? > > - > Michael Lyons > >
Re: Remote debugging outside of domain
Have you tried logging on with credentials from the remote computer? ie, create a local "testuser" account on the remote server and log on with "remoteserver\testuser". Is the trace option turned off in the app.config? David "If we can hit that bullseye, the rest of the dominoes will fall like a house of cards... checkmate!" -Zapp Brannigan, Futurama On Sun, Aug 8, 2010 at 20:02, Michael Lyons wrote: > I'm needing to debug a Windows service to see why it is crashing after a few > minutes. > I've setup the remote debugger on the host machine, but I receive the error > message "Unable to connect to the Microsoft Visual Studio Remote Debugging > Monitor named 'x'. Logon Failure: unknown username or bad password". > The issue is that my workstation is within a AD domain whilst the machine I > wish to debug is not. How can I go about debugging the remote machine > without disconnecting from the domain or connecting the remote machine to > the domain? > > The service has also for some reason or another stopped outputting to via > System.Diagnostics.EventLogTraceListener, would anyone have any clue why > this would happen? > > - > Michael Lyons > >
