Just need a bit of help to understand how would i diagnose this sort of fault.
user says they press saves text into a web site and it should write it to a folder location held in a database string.
basically i have a NLB web site spread over 4 web servers. the web app where user enters some XML text, press save , the asp then calls a sql stored procedure to get the location of where to save it to.
problem is the server is not managed by me so i cannot install tools like fiddler or procMon to see if it is even hitting the folder. i only have access to SQL profiler and i can see it call the location of the remote storage
strange twist is if they save the edits line by line it works. so i thought it was due to the sheer size of data being passed through IIS but this is not the case because i can save it for the customer fine and they were only changing 5 lines of text. but im thinking the user is 'thinking' this is the work around to save line by line when in actual fact its probably they are hitting 1 of the 4 'faulty' web server when they do the POST
when i check the iis logs when the user press save, i can always see it calls the commit.asp page so im a bit stumped???
how else would you guys diagnose this scenario
user says they press saves text into a web site and it should write it to a folder location held in a database string.
basically i have a NLB web site spread over 4 web servers. the web app where user enters some XML text, press save , the asp then calls a sql stored procedure to get the location of where to save it to.
problem is the server is not managed by me so i cannot install tools like fiddler or procMon to see if it is even hitting the folder. i only have access to SQL profiler and i can see it call the location of the remote storage
strange twist is if they save the edits line by line it works. so i thought it was due to the sheer size of data being passed through IIS but this is not the case because i can save it for the customer fine and they were only changing 5 lines of text. but im thinking the user is 'thinking' this is the work around to save line by line when in actual fact its probably they are hitting 1 of the 4 'faulty' web server when they do the POST
when i check the iis logs when the user press save, i can always see it calls the commit.asp page so im a bit stumped???
how else would you guys diagnose this scenario
