How to find issue on remote server that you don't have access to?

Question

Ok, so this is my dilemma... I have an ASP.NET MVC site that is running into some conditions that it is pegging the processor on the iss boxes it's running on. I don't have access to these servers (it's a farm of about 5 iis6 boxes behind a netscalar). I am doing some logging to a sql database, but the problem is that when the cpu pegs my database starts timing out. The iis servers are hosted in house, but I can't get access to them.

And to make things ever more complicated, I can't reproduce any of these issues in my qa environment (which I don't have access to either). QA is setup to similarly to our prod environment, but it runs on a single box that isn't behind a netscalar.

So, any thoughts on the best way to try to track down where my issues lie? Thanks!

Answer 1

Since you are already logging to a database, why you don't log to another database, install this DB on another computer, so that when your MVC application starts killing the CPU the database won't be affected (since it is working on another computer).

or you could log to an FTP folder that you can access.

Hope I helped. Regards.

Answer 2

ASP.NET Trace. Haven't used MVC, but I'm assuming it still works...

http://msdn.microsoft.com/en-us/library/y13fw6we%28VS.71%29.aspx

Answer 3

If you want to know what is going on with the system you could read from the event viewer programatically: http://support.microsoft.com/kb/815314 This should help you to learn what is going on with the system. This way you can build a web interface for it and capture any info you may want to look at for what is going.