I've run into a problem recently where sometimes timers in Microsoft Access forms stop working, having been fine for ages. It seems to be related to some kind of disruption of the host PC where the Access programs are running. In order to get them working again I have to restart the PC.
The scenario affects all currently open instances of Access where there are form timers active (four instances in this case).
Has anyone any ideas of how I might investigate what might be happening on the host PC (running Windows 10) that could break Access form timers?
The problem does make me wonder how Access works with the OS to control its timers.
TIA
It turns out this was down to vendor loaded software causing disruption to the Windows and Office system.
Related
i am having a small problem which is quite critical actually, i run a Unity instance in a google cloud VM that work as a server for a small social experience in VR.
The thing is, if Unity is running without GPU, it starts clogging the processor and the game kindda fails with many users, that is why i hired a eGPU Tesla P4, also, to run Unity, i must log in with Remote Desktop and hit Play.
The thing is, Windows disables the GPU when you go Remote Desktop, Unity opens without a GPU and the GPU is "Unknown" (in dxdiag), thats why i need to solve the RDP issue, i need to log in without disabling GPU acceleration so unity can open and go full power running my game, the server is like a player that doesnt show for the other clients, since its made in Photon PUN, its a weird hybrid, but it works as expected.
Now i have to solve this performance issue, i hope i am clear.
what i need to do now: log in with hardware acceleration (paying a lot for that online gpu and not using it).
What i have now : i log in without using the GPU, the CPU dies, and im wasting cash on the server.
thanks community!
PS: in a future i will use a headless server.
It seems this is a 'Windows' feature that many people have been complaining about. Basically windows switches to a generic driver when you are connecting via remote desktop. Try using an alternative remote desktop solution such as VNC.
Sources:
https://boinc.berkeley.edu/dev/forum_thread.php?id=7026
https://setiathome.berkeley.edu/forum_thread.php?id=70853
I have ZAP installed on a build server (Windows 2008 R2) and on my Windows 7 desktop, and Zap only occasionally starts. I click on the program and my cursor shows it is waiting for a second or 2 and then nothing. Attempting to run from the command line will also not show any signs of running.
Then just out of the blue the program may launch.
Is it possible it just takes forever to start. I left my computer running and the next day when I came to work there was the UI.
I get the same results if I try to run the program in the headless state. with the -daemon flag. it never starts, it never shows up in the task manager, as an application or a process
thanks Noel
Turns out there were 2 issues. The first was that the tool was taking 4-5 minutes to start (I timed it several times at around 4m 30s). I did not have the patience to wait, so I would try to start it again. Attempting to start the application when one had started, but no UI was showing invariable caused the application to hang.
Secondly if you start it as a headless application there is no way to stop it. So if you have it headless and then try to start the application it will cause it to hang. THe easiest way to tell if it is running is to follow the log information being written out as suggested by Psiion above in his link.
To kill the process, look in the task manager for the java process and kill it.
Just in case anyone stumbles across this post, my problem was I didn't have Java installed. I had removed it a few months ago due to security considerations.
You can stop your browsesr using Java easily by using the Java control panel http://www.java.com/en/download/help/disable_browser.xml
I was facing a similar issue, the ZAP tool was working fine on my local machine but was displaying erratic behavior on the Virtual Machine. I tried all the previously mentioned suggestions but none of them could mitigate the issue. Upon checking the log files i found out that the HSQLDB files were being locked even after closing the tool or even if the tool did not start. I eventually figured out that the difference between the 2 environments was just the operating system. My local had Windows 10 pro while the VM had Windows 10 enterprise. So in case if any one else is facing similar, kindly check the operating system.
I would love to have an idea on how to automatically install a Windows XP virtual machine on Virtualbox/VmWare. Is this feasable via a programming language, for example ? Or maybe an automated script ? I need this to avoid manual installation each time one of my VMs crashes.
I am not asking for a full program that does this, but I just needs technical hints on how to do this, then I will perform your suggestions myself.
Yes it's possible.
Can't you just make a snapshot to when the VM is working, or at least a "Clean Install" snapshot that saves having to reinstall your OS and common applications every time?
Yes, it is possible to do this via script. Actually, all IaaS cloud companies now try to do the deployment of VMs (and also physical servers) via automation. First of all, it's cheap a quick. And there is little human factor in it.
Not sure about VirtualBox, but if it works with VMware, KVM etc., there is no reason it shouldn't with VB.
As for the script itself, there are big money in this, so finding something may prove difficult. Try to check openStack, AFAIK it should be open source.
We run our application in a kiosk environment of sorts, replacing Explorer with our application. Everything worked fine under Windows XP, but with Windows 7 we can't get it to work.
We set the registry key WinLogon to a custom user.bat batch script (no further registry tweaking) in which we wait for several services to start (SQLServer, for example), then launch our application.
This worked great in XP. However, in 7, all needed services are detected, but when our application starts, it fails when trying to load its .fx file. It's as if some service or component related to DirectX has not been yet initialized. Any hints on troubleshooting this?
We solved this by making our program which waits for services try to play an avi (without displaying it) using DirectX. We cover that code with a try-catch block inside a loop and insist on it until it succeeds, which means DirectX is available. A nasty hack, but since the user can't see it, it's good enough for us.
This issue has come up three times in our environment. After installing the ClickOnce application, I expected it to startup automatically (as I have it set to do after install completes), but it did not.
I try running the application from the shortcut, and it brings up the "Launching Application" dialog, but then immediately closes and the application is not started. It's acting as if another instance of the application is currently running (I have it set to only run one instance at a time).
This issue is profile-specific. Installing it on the same machine using a different profile runs just fine, but for whatever reason, no amount of uninstalling, reinstalling, and restarting the computer seems to fix a profile once it runs into this problem.
Our current fix for this is to completely delete the profile and "reload" it. I'd really like to know what the actually problem is though, being that we've run into it three times now.
Some other information that may be of use:
This application was originally deployed using Windows Installer (MSI). I uninstalled the application from the Add/Remove Programs prior to installing the newer ClickOnce version.
These users were previously part of local administrators group (while running the MSI version). Their privileges have since been lowered to "standard user".
Do you have any logging at startup that shows exactly what the application is doing, so you can tell where it's crashing?
The user doesn't have Kensington mouse software installed, do they? There is a known conflict there, the symptoms of which are exactly as you report -- the user clicks the shortcut to start the application, it updates, and then does nothing.
I was able to fix those installations by creating a new certificate for the app. It appears this issue had to do with the certificate reaching its expiration date.
Instead of deleting the profile try this:
Log onto the PC as an admin
Delete/rename C:/Documents and Settings/(UserCorpID)/Local Settings/Application Data/Microsoft/Windows/UsrClass.dat file