Subject: Application has been waited around 360 seconds
Posted: 21 December 2015 at 1:15am
Hello pinscomputer-san,
I used the same machine as both server and client, testing its own bandwidth etc. (whether the machine could be a limiting factor for another test, and to which degree) The usage of the same PC for both server and client should not be a problem. Whilst doing the testing, I found what seems to be bugs in the psping, and so am looking for answers ...
I'm trying to resolve an issue w/ MS Excel 2010. Specifically, when I try to open a file using thje File -> Open Dialogue, or clicking on one of the in-program icons, the programs hangs; it doesn't necessarily crash. Instead, it seems to be waiting for a response from me / the user, but is not able to display the File -> Open dialogue window. (Some mouse-wheel-driven up and down scrolling functionality is retained.) When I click directly on the file I want to open (from within the MS File Explorer), the file opens as expected.
Also, I ran SFC /scannow, and it indicated "Resource protection found corrupt files but was unable to fix some of them ..." CBS.log pointed to the following ... "C:\WINDOWS\SysWOW64\opencl.dll" (I'm not sure what to do with that info)
No joy.
One of the best clues I have as to what might be happening appeared immediately after re-installation of MS Office. During reinstallation I provided my product key. Then, upon opening Excel, I used the File -> Open icons, and the File Open dialogue appeared .. as it should! But, I was again prompted for my MS Office key, (this time from within Excel) and the problem immediately reappeared after I entered the key. It's a strange one. The MSFT chat representative confirmed I was using a good key.
There are many people w/ the File -> Open problem. One of related the posts in the MSFT community has received over 45,000 views!
This problem is quickly turning into a major inconvenience for me, and I'd really appreciate a hand / guidance. Thanks.
GPU: GeForce GTX 770
Memory: 32GB
Current Resolution: 1920 x 1080, 60Hz
OS: Win 10 Pro
![]() This is a bug related to monitor size. BGINFO can not handle the 1920 resolution. Previously reported, but just tested with 4.21 version and it is still a problem. |
if you want to try and further debug to isolate the problem to the NSI service, you can try and temporarily move NSI service to its own servichost.