This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

What about Creating WebBrowser Objects ? The logon process is far too long

Please tell me about Creating WebBrowser Objects?

Every logon the WebBrowser Objects was created! It Need's over 10 seconds for every logon.

For what is this process required? The logon process is far too long for my feeling.

Is it possible to Switch it off, if not really needed?

 

09:37:51 Creating WebBrowser Objects...

09:38:04 'slBrowser' is ready for use!

 

Thanks

Parents
  • Hi Werner,
    The webbrowser COM object is being registered with the system at the time that you see the delay. It should not take 10 seconds to register this object. It is not possible to switch it off and I suspect that if it were possible, that the delay would then simply move to the next object. We have seen this delay only a couple of times in the past and it has been related to either anti-virus or a bad machine.config file. It is more likely that anti-virus is responsible for the delay since we have only had one previous report of a bad machine.config on one workstation. My advice is to view the SLAgent_logon.log and look at the same time in that log that corresponds to the time in the trace file where you see the delay. Then take note of what the process is that the agent is doing at that time. Of course, it might be quicker and easier to either disable or remove the anti-virus from the client machine in order to see if that resolves the issue.
Reply
  • Hi Werner,
    The webbrowser COM object is being registered with the system at the time that you see the delay. It should not take 10 seconds to register this object. It is not possible to switch it off and I suspect that if it were possible, that the delay would then simply move to the next object. We have seen this delay only a couple of times in the past and it has been related to either anti-virus or a bad machine.config file. It is more likely that anti-virus is responsible for the delay since we have only had one previous report of a bad machine.config on one workstation. My advice is to view the SLAgent_logon.log and look at the same time in that log that corresponds to the time in the trace file where you see the delay. Then take note of what the process is that the agent is doing at that time. Of course, it might be quicker and easier to either disable or remove the anti-virus from the client machine in order to see if that resolves the issue.
Children
No Data