Microstation Connect Hang with Windows 10

Hi Harshad Darji and Ian Lapper,

My general (user, admin or developer) recommendations for identifying performance issues are:

1. Identify the most simplified, yet most painful operation(s) first.  Like in this thread: "file open is very slow".
2. Productively capture and analyze (or once product support team requests) a Microsoft Process Monitor (procmon) Log.

The Microsoft Procmon log provides extensive and powerful filtering that can provide insights into what otherwise may appear to be silent/unexplained failings or performance issues and help identify items  to make progress and resolve root cause of most issues.  For a performance issue, my first stop is typically: Tools > File Summary ("File Time" then "Total Events"). If; e.g. Top 3; items are listed located in a network location; and possibly don't belong there; work with your CADD adminstrator to test and move (or configure) essential items to run local and see if that helps meet expectations or to better work with the IT department for any network performance issues/data collected.

If you or your company have software developers who's custom applications may be involved the Procmon log can also be very helpful to them since many of the lines of logging provide application Call Stacks (from available PDB files they likely have) to identify exactly what lines of code were executed in their own applications.

HTH,
Bob

Hi Harshad Darji and Ian Lapper,

My general (user, admin or developer) recommendations for identifying performance issues are:

1. Identify the most simplified, yet most painful operation(s) first.  Like in this thread: "file open is very slow".
2. Productively capture and analyze (or once product support team requests) a Microsoft Process Monitor (procmon) Log.

The Microsoft Procmon log provides extensive and powerful filtering that can provide insights into what otherwise may appear to be silent/unexplained failings or performance issues and help identify items  to make progress and resolve root cause of most issues.  For a performance issue, my first stop is typically: Tools > File Summary ("File Time" then "Total Events"). If; e.g. Top 3; items are listed located in a network location; and possibly don't belong there; work with your CADD adminstrator to test and move (or configure) essential items to run local and see if that helps meet expectations or to better work with the IT department for any network performance issues/data collected.

If you or your company have software developers who's custom applications may be involved the Procmon log can also be very helpful to them since many of the lines of logging provide application Call Stacks (from available PDB files they likely have) to identify exactly what lines of code were executed in their own applications.

HTH,
Bob