So we have Crystal Reports running on a server in a multi user environment. Crystal is used to send documents directly to printers on the local network. Today we noticed the server running at full load and multiple instances of rundll32 hogging all the CPU cycles.
On further investigation it seems that the rundll32 instances are Crystal Print jobs which have hung or otherwise not finished.
I have not been able to reproduce the error yet but does anyone have any suggestions as to what could be causing the rundll32 process to hang like that, and how to avoid it?
Killing the processes manually is not ideal but it's the only way to get the users back going again.
Turns out this was a bug in the printer driver when the 'Printer Notifications' options was enabled. The printer was low on toner, and was issuing a message to the server, which was then using 100% of the cpu.
I disabled the option in the driver and haven't had that issue since.
Related
First time debugging from PC to Mobile Phone work fine, when try again get error.
Any solution how fix this when try more debugging.
Add -debugport=54321 to Run->Parameters Parameters. By the way, the "inconsistent certificates" message is because the apk on the device was compiled with a different version of Delphi than the one you are using right now. You will have to uninstall it from the phone first. You can also use -cleaninstall in the Run->Parameters Parameters field.
There is no easy and fast solution.
You may need to:
Restart IDE
Kill adb.exe
Restart Windows
Restart device
Sometimes you will be able to debug again after doing only some of the above steps, however often you will need to do all of them.
Since every try takes plenty of time, I found out that complete Windows restart + device restart is the fastest thing to do.
With Delphi 10.3.3, it is enough to restart the device. After restarting the device problem goes away. It seems after the cancelation of code execution of the project debugged, the debugging service on Android continues to run. At this point, when new debugging started, IDE tries to run a new service with the same id of previous running service.
I have an Atmel SAM4S Xplained Pro, which I program and debug via a USB cable and Atmel's on-board EDBG chip (in other words, the way God intended). At the moment, if I "Stop Debugging" through Atmel Studio (v7.0), the code seemingly continues running (because I continue to get output in the terminal, which is application specific output).
Does anyone know how to stop this from happening, i.e., how to make "Stop" mean "Stop"? It's doing my head in!
Having contacted Atmel, the answer is that the debugger does not hold the MCU reset after debugging is stopped, so the code will continue to run. This is a known issue and is on their backlog to resolve.
I have embarcadero radstudio xe8 on a windows 10 machine. Everything was working perfectly till about 2weeks ago. Everytime I try to start Delphi xe8 I get an error :"Exception EOSError in module rtl220.bpl at 00050A4D.System Error. Code 111. The file name is too long. " I tried reinstalling a couple of times and I even tried installing appmethod but I still get the same error.
What can be the problem?
I've had the same issue today. I've traced it to a GetAdaptersInfo() call, and it turned out that for some reason (VirtualBox is my main suspect) I've had over 50 network adapters registered on my system. Removing all of them fixed the issue.
There is not enough info in your question in order to tell what exactly is wrong. Try using Process Monitor in order to check what files Delphi is trying to access. It will also show the errors of these file operations.
as they uri2x tell you the problem is that RAD Studio having issue with many network adapters registered more than 20 will not work properly you will have problem with debbuging and run project and you may find many cmd.exe process running in your system
delete duplicate and non needed network adapters registered on "Control Panel\Network and Internet\Network Connections"
that will fix your problem
This may be of help. I had a similar problem, error code 5 Access is denied. This turned out to related to a thread started to test an internet connection on an embedded panel (using BeginThread). If the user exits the form (which is testing the internet connection) immediately after displaying the form, the AV occurs.
On my development PC, the internet connection test was successful...and so fast I never saw the problem! After struggling for several hours, I finally tracked it down to this thread and reproduced it by disconnecting my network cable.
The solution was straightforward: When exiting the form (eg. in the FormDestroy event) ensure the thread is definitely not running before continuing.
I was hoping someone can point me in the right direction regarding an issue I am having with the message "Error creating window handle". I know this usually points to a memory leak problem with the code, however this only happens on a single machine. If the code was the issue, I would be expecting it to happen on other machines as well.
I have other machines that this application runs on that do not run into this problem. I have tried reproducing in on my development machine and other machines in the office. Neither has been successful. I have tried watching the memory in Task Manager on the offending machine and it does not skyrocket up before it throws the error.
The offending machine is running Windows XP Professional SP3. Any ideas on how to proceed would be great.
Thanks
I have just had the same problem in two different applications. For us, the problem was triggered by setting the Windows theme to "Windows Classic" rather than "Windows XP Style". The control that fails is a System.Windows.Forms.ListBox inside a Developer Express XtraLayout container, and our fix is to replace it with a DevExpress.XtraEditors.ListBoxControl.
I develop with Delphi 2010 in a VM, the app runs well inside the VM in any ways within the ide, alone with or without Eurekalog using mainly DevExpress grids and AidAim SQLMemtables.
When the same App is ran on the host (ie directly on windows) the eurekalog finds memory leaks on the SQLMemtable dataset component and sometimes but often enough to make it impossible to release it crashes on a simple Dataset.refresh. It is very hard to debug because in the debug environemnt it works.
Anyone would have any idea what is going on, I am at loss of ideas here
Thank you for your help
Regards
Philippe Watel
Your external dependencies (dlls) differ on both machines? Also consider using Delphi's remote debugger and log more details to find out more details about your problem.