I'd appreciate help determining why my Word VSTO Add-In is causing 45 second load times.
The Add-In is used by multiple customers, only one of which experience this issue. I can not reproduce the problem on any of my test environments. (all running Windows 10, Office 365)
Findings:
v35 of the Add-In works fine (built back in March).
After the customer installs v55 the problem starts (built in July).
I've incrementally removed all my code, nuget packages, reference (everything) from the Add-In and the problem persists.
I've removed my Add-In and create a new WordAddin1 project. The 45 second problem occurs when this Add-In is installed at the customer.
If I rebuild v35 today and run on the customer machine it works fine.
I have established that the 45 seconds happens BEFORE my Add-In code get's a chance to run.
I have run fuslogvw.exe to determine if any dependencies are causing timeouts (they aren't)
I have run performance monitoring to ensure that CPU, Memory, Disk, Network traffic are at acceptable levels (they are)
I have run Telerik Fiddler to monitor traffic and can see multiple calls (4) to Windows Update that time out (the customer pushes out updates via SCCM and does not get updates from Windows Update)
2 of those Windows Update calls and timeouts happen when I disable my Add-In and Word opens within 5 seconds.
How can I better understand what Word is doing during that 45 seconds? It's a black box that I can't seem to peer into.
Any help greatly appreciated
Related
I am a network admin with very little experience coding or using Powershell. About once a month I have to check for and install Windows updates on about 25 servers. I've played around with Powershell in hopes of handling this task in a more automated fashion but get hung up getting the servers to actually install the updates after checking. I apologize for posting such a noob question, but can anyone let me know if this is possible and if so, show me the ways of your dark arts?
WSUS will require you to install the components and setup the profiles etc. If you have a large number of servers on a single network, that is your best bet for delivering the content.
If you just want to be able to schedule and run the updates on specific remote hosts, there is a ton of stuff already available that will do this and you just need to come up with your implementation of scheduling the updates for what hosts. I did this exact thing for a prior employer for 10k plus servers world wide using a web app for the owners to schedule the updates and then back end workflow to perform the approval requests, installs, logging, etc..
PowerShell Gallery is a good start. Here is a post that walks you through using PSWindowsUpdate.
We have a SaaS application running with an AngularJS front end and Jasper Reports integrated using the Visualize.js framework. We are seeing an issue where after the Jasper server has been running for a while, the call to get the input controls will stall in the browser. The strange thing is that all the other calls proceeding it (auth, resourcessearch, etc.) return just fine. It seems to be only the inputcontrols that stalls. When this happens, we see no errors in the logs, memory & CPU on the Jasper server are fine, etc. To fix the problem, we are generally forced to bounce the Jasper server.
Has anyone experienced this problem? Any advice?
A little more info:
Jasper Professional version 6.1.1
Seeing the problem in all supported browsers (IE, Firefox, Chrome)
Problem happens both with a single user and with concurrent users
Input controls will sometimes return after 8-10 MINUTES if we wait
long enough (with Apache timeout cranked to 15 minutes)
Something on my computer is randomly calling a couple SharePoint sites. The last time the mystery process ran, it made 20K calls to a couple different SharePoint sites.
I tried closing Outlook, OneNote, Designer, and other apps that were running. No Task Schedules are set to run around the time this happened.
Using Fiddler, is there a way to identify what is making a call to a site?
Look at the Process column to find out what process is issuing the request. You will likely either see one of the Office applications (which periodically refresh a registry-based list of SharePoint sites you've used) or a svchost.exe instance. If it's a svchost.exe instance, you'll need to use a tool like Process Explorer (or the Win8+ Task Manager) to see which services are running within the svchost.exe with the specified process ID.
WE have enterprise 2010 on a set of servers 3 front ends, tons of RAM. We use IE-9 exclusively. The issue is that sometimes the same web based InfoPath form opens very fast and sometimes opens very slow. By slow I mean one time the form might take up to 1 or 2 minutes by fast I mean the same form opening in a couple of seconds. This has nothing to do with the design of the form other than larger more complex forms take more minutes to open than smaller less complex forms but all forms open so slow as to be unacceptable to the user. They can open both fast or slow within the same minute. On our 2007 server they open just fine. Originally we didn't have this issue. I don't know whether it was an update, IE 9 or what. Any suggestions on what it might be or how we might diagnose this issue are welcome. thanks -dave
I have seen "random" performance issues like this when the Internet Explorer's "Automatically detect settings" option is selected. See this article. If possible in your environment, you might try disabling this on a test machine to see if this helps.
Using Fiddler, I want to send multiple requests in one hit, to check the response time from the server, if too many requests are sent at one time. Basically, I want to perform a, kind of, load testing on my service. Is there any way to perform this action? I want to repeat the process of hitting the server, again and again.
In Fiddler, you can repeat a request as many times as you like by hitting SHIFT+R on the selected Web Session. You'll be prompted for a repeat count and then Fiddler will issue the specified number of requests.
Caveat: Having said that, generally speaking, you'd want to use a tool like Telerik Test Studio's Load Test tool for a task like this. Alternatively, you could use Fiddler's Export architecture to generate a script for VS WebTest or Microsoft's free WCAT tool and use those tools to generate the load. You can then run these scripts on multiple machines from multiple networks and generate a more-realistic set of load than you could by simply running on a single client.
I've been load testing with StresStimulus today. Overall, I'm quite impressed.
It's now a standalone application (it used to be a fiddler extension). There's a 7 day free trial which allows up to 50 virtual users. Also, the setup wizard is great for beginners.
For basic load testing the trial should be fine. Consider upgrading for extensive/professional use.