User profile for Sachin

1) Reboot your machine (the old classic ) SB: I tried on 3 different machine but of no avail. 2) Run "netstat -a" in a command prompt. Look for any lines that mention port 8013. SB: no where mentioning of 8013 3) Try connecting to port 8013 using telnet - in a command prompt, "telnet localhost 8013". If it connects, it will blank the terminal, if not, it should give some error like "could not open connection". I'd hope you'd get a "could not open connection", since that port shouldn't be in use. SB:- you are right i got a msg "Could not open connection". Apart from this tell me one thing: If our webservice is running on port 80, what number should we enter in Dialog box "Profile an ASPnet application in IIS" screen 3rd, while running profiler. I think it should be any port which is free. right! Secondly, I read some where that you should give previlage to some IISMetadata, is that the case / comments

1) Reboot your machine (the old classic ) SB: I tried on 3 different machine but of no avail. 2) Run "netstat -a" in a command prompt. Look for any lines that mention port 8013. SB: no where mentio...

0 votes

Sorry, forgot to mention that there are no error in eventvwr! / comments

Sorry, forgot to mention that there are no error in eventvwr!

0 votes

Nothing happened. I just pasted the command as-is given by you in cmd prompt (both at cmd as well on VS cmd) and pressed enter. It came out immediately, doing or showing nothing! What next [image] Sachin Bansal / comments

Nothing happened. I just pasted the command as-is given by you in cmd prompt (both at cmd as well on VS cmd) and pressed enter. It came out immediately, doing or showing nothing! What next Sachin ...

0 votes

Hi Rob, The event vrw log you were saw was very old. Actually i was trying plenty of things, so might have given 9120 port. The latest error msg in EventVwr for port 8013 is: Unable to start profiler - exception details RedGate.Profiler.Engine.IIS.PortTimeoutException: Timed out waiting for port 8013 on 127.0.0.1 to become available Server stack trace: at RedGate.Profiler.Engine.IISUtilities.WaitForPort(IPAddress address, Int32 port, Int32 timeout) at RedGate.Profiler.Engine.IISUtilities.WaitForPort(String hostname, Int32 port, Int32 timeout) at RedGate.Profiler.Engine.ProfileIISController.StartProfilingIIS(String currentUserName, String& url, WebApplicationDefinition appDef) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext) Exception rethrown at [0]: at RedGate.Profiler.Engine.ProfilingSession.StartProfiler() at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink) Exception rethrown at [1]: at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase) at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData) at System.Windows.Forms.MethodInvoker.EndInvoke(IAsyncResult result) at _5._4(IAsyncResult ) I hope it will help... Thanks, Sachin Bansal / comments

Hi Rob, The event vrw log you were saw was very old. Actually i was trying plenty of things, so might have given 9120 port. The latest error msg in EventVwr for port 8013 is: Unable to start profil...

0 votes

I dont know which log are you refering to. I am sending you the latest log when i ran the app with port 8013. My webservice is running on 80. Log file 1: ANTSProfilerLog16340.txt 3/27/2007 4:24:24 ...

0 votes

Hi Rob, I am now getting confused... I think I am making some small mistake somewhere... Let me explain you what I am doing... I did this w3wp -debug -d http://localhost:9120/ -s 1 -ap "DefaultAppPool" and control came out immediately. I dont know whether I should mention it as a crash/terminate. But it gave me cmd prompt immediately. There was no error msg. I am using WindowsNT SP1 I am running my web service on 80 port. but we need to mention a different port for profiler so i mentioned 8013(it can be anything, i believe). I dont have any idea regarding: "the logs below suggest a timeout on 9120." I think my log files which i posted at "http://www.red-gate.com/messageboard/viewtopic.php?t=4551" says: 3/27/2007 1:51:38 PM ENGINE - Caught Exception in ProfilingSession: Timed out waiting for port 8013 on 127.0.0.1 to become available Regards, / comments

Hi Rob, I am now getting confused... I think I am making some small mistake somewhere... Let me explain you what I am doing... I did this w3wp -debug -d http://localhost:9120/ -s 1 -ap "DefaultAppP...

0 votes

I am using IIS6.0 I entered the command in command prompt. it did nothing just came out to the next line. Then I tried accessing my Web service, i could access it well. / comments

I am using IIS6.0 I entered the command in command prompt. it did nothing just came out to the next line. Then I tried accessing my Web service, i could access it well.

0 votes

Hi Rob, Answers Inline: Firstly, let's look at the IIS side of things. After you try to start profiling (but before the timeout happens), could you check in task manager to see whether another w3wp.exe process gets started? (You might need to discount any previously running as part of IIS) SB: No i dont see a single w3wp.exe in task manager under process section. Could you also check the event log for any other errors from W3WP, ASP.NET, IIS or similar that occur at around the same time as you start profiling? SB: No there are none. Secondly, when you try and use WebDev, what error do you get there? They're probably unrelated, but might not be... SB: I ran it, and it is working fine now, y'day I was not taking snap shots... now I took and got the results. But we are really interested in doing it by IIS. Hope it help you to investigate... Regards / comments

Hi Rob, Answers Inline: Firstly, let's look at the IIS side of things. After you try to start profiling (but before the timeout happens), could you check in task manager to see whether another w3wp...

0 votes

hi Rob, Thanks for your quick reply. I am an administrator on my machine and I dont think there is any credential problem. I have mentioned each detail with the topic "Problem in profiling WebService! Exception thrownby Profiler at this group only. The url is: "http://www.red-gate.com/MessageBoard/viewtopic.php?p=16398#16398" May i request you to look into it, and please try to help me out. I am also pasting the log enteries. In my case log files says: /****************************************************/ File 1 ANTSProfilerLog17760.txt: 3/27/2007 1:50:20 PM ANTSProfilerLog initialized 3/27/2007 1:50:20 PM PID = 11788 3/27/2007 1:50:20 PM Log file name = ANTSProfilerLog11788.txt 3/27/2007 1:50:20 PM OS version = Microsoft Windows NT 5.2.3790 Service Pack 1 3/27/2007 1:50:20 PM Machine name = TCS031751 3/27/2007 1:50:20 PM User name = administrator 3/27/2007 1:50:20 PM PARAMHOST - Listening on port 8084 3/27/2007 1:50:20 PM PARAMHOST - Listening on port 8084, channel registered 3/27/2007 1:50:42 PM EditProjectClosingWizard start 3/27/2007 1:50:42 PM EditProjectClosingWizard start 3/27/2007 1:50:43 PM Using IIS Version 6 3/27/2007 1:50:43 PM About to get ASPNet username and password for IIS6 3/27/2007 1:50:43 PM About to get site for URL 3/27/2007 1:50:43 PM About to get IIS6 sites 3/27/2007 1:50:43 PM Got site 'Default Web Site' with identifier 1 3/27/2007 1:50:43 PM Got best VD match at path: [url=IIS://localhost/w3svc/1/root]IIS://localhost/w3svc/1/root[/url], URL /LM/W3SVC/1/ROOT 3/27/2007 1:50:43 PM AppPool for URL http://localhost/CheckProfiler is DefaultAppPool 3/27/2007 1:50:43 PM About to show wizard 3/27/2007 1:51:00 PM Wizard dialog returned 3/27/2007 1:51:02 PM UI Start profiling 3/27/2007 1:51:02 PM ENGINE - Core2.dll found in regisry 3/27/2007 1:51:02 PM ENGINE Start profiling performance of ASP.NET web application http://localhost/CheckProfiler/Service.asmx 3/27/2007 1:51:02 PM ENGINE The profiler is enabled 3/27/2007 1:51:02 PM TRANSFER - Waiting for pipe connection from core 3/27/2007 1:51:02 PM WaitForPort on address 127.0.0.1, port 8086 3/27/2007 1:51:03 PM ENGINE - Managed to hook into status updates from IIS Profile Host 3/27/2007 1:51:37 PM ENGINE - Closing IISProfileHost 3/27/2007 1:51:38 PM ENGINE - Caught Exception in ProfilingSession: Timed out waiting for port 8013 on 127.0.0.1 to become available ############################################## File 2: IISProfileHostLog12584.txt 3/27/2007 2:33:54 PM IISProfileHostLog initialized 3/27/2007 2:33:54 PM PID = 12584 3/27/2007 2:33:54 PM Log file name = IISProfileHostLog12584.txt 3/27/2007 2:33:54 PM OS version = Microsoft Windows NT 5.2.3790 Service Pack 1 3/27/2007 2:33:54 PM Machine name = TCS031751 3/27/2007 2:33:54 PM User name = administrator 3/27/2007 2:33:54 PM ANTS Profiler IISProfileHost Start up 3/27/2007 2:33:54 PM Listening on port 8086 3/27/2007 2:33:55 PM StartProfilingIIS currentUserName SOLOMON\administrator, url http://localhost/CheckProfiler/Service.asmx, .NET 2.0 Two, IIS6 3/27/2007 2:33:55 PM Parse IIS metabase 3/27/2007 2:33:56 PM InitServiceList 3/27/2007 2:33:56 PM StartIIS 3/27/2007 2:33:56 PM StartWebService for IIS 6 3/27/2007 2:33:56 PM WaitForPort on address 127.0.0.1, port 8013 3/27/2007 2:33:58 PM About to get site for URL 3/27/2007 2:33:58 PM About to get IIS6 sites 3/27/2007 2:33:59 PM Got site 'Default Web Site' with identifier 1 3/27/2007 2:33:59 PM About to get IIS6 x64 status 3/27/2007 2:33:59 PM WaitForPort start, url = http://localhost:8013/CheckProfiler/Service.asmx 3/27/2007 2:33:59 PM WaitForPort on address 127.0.0.1, port 8013 3/27/2007 2:34:30 PM StartProfilingIIS - threw exception 3/27/2007 2:34:30 PM ENGINE - Received request to close IISProfileHost 3/27/2007 2:34:30 PM IISPROFILEHOST - Exiting due to closing: True and UI Exit: False 3/27/2007 2:34:30 PM Main() exiting /****************************************************/ Please do let me know if you need any other information, thaanks, Sachin Bansal / comments

hi Rob, Thanks for your quick reply. I am an administrator on my machine and I dont think there is any credential problem. I have mentioned each detail with the topic "Problem in profiling WebServi...

0 votes

Hi, I am also undergoing the same problem. I did all the things suggested by you and other user group. But it is not working. Can we presume that red-gate profiler fails to profile Web Service! Regards, Sachin Bansal / comments

Hi, I am also undergoing the same problem. I did all the things suggested by you and other user group. But it is not working. Can we presume that red-gate profiler fails to profile Web Service! Reg...

0 votes

How can we help you today?

Sachin

Activity overview