TRACE doesn't work on the remote box

  • Thread starter Thread starter Jay
  • Start date Start date
J

Jay

I have an ASP.NET app that works on my box.
When I deployed it to the server, it doesn't work
It calls a webmethod, and looks like that call doesn't work.There is no
exception thrown.
So, I wanted to look at the trace. But nothing gets logged there too.
Although, On my box, the logging works, the webmethod works.
 
The same code works on my box.
I haven't changed anything while deploying to the remote server.
Where do I check that anyways?
 
You were talking about Tracing though - whether it works or not - if you
want to do tracing, it needs to be turned on somewhere
You can do it inside the web.config file, or you on each web page where you
want tracing. For instance, you can turn it off everywhere (completely) in
the Web.config, but enable it in the page directive in your web page.

--
David Wier
MVP/ASPInsider
http://aspnet101.com
http://aspexpress.com
 
I have this in my web.config file:
<system.diagnostics>

<trace autoflush="false" indentsize="4">

<listeners>

<add name="myListener" type="System.Diagnostics.TextWriterTraceListener"
initializeData="C:\\temp\\guestpulls\\Guestpull.log" />

<remove name="Default" />

</listeners>

</trace>

</system.diagnostics>

--------------------------

In my Code, I have the line:

Trace.WriteLine("Initialize(): Hello!");



Nothing gets logged to my log file on the remote server.

(On my local box, it works)
 
Back
Top