> Killed Microsoft.SharePoint.exe
This is fascinating. I have seen this problem appear on PCs since Win7, likely pre Microsoft.SharePoint.exe. I am guessing that is not the only cause.
There are some other refences to OneDrive.
After you Killed Microsoft.SharePoint.exe…
…does it return?
…what happens after reboot?
--
You received this message because you are subscribed to the Google Groups "TheDBCommunity" group.
To unsubscribe from this group and stop receiving emails from it, send an email to thedbcommunit...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/thedbcommunity/418cc884-84d9-409b-a63a-cf38bd0cf92an%40googlegroups.com.
Windows 10, running complex system on standalone PC.
After 10plus years or more...
PrinterSetCurrent started hanging last few days. Reboot fixes it. For now.
Again, no real changes.
I cannot find anything new or odd running in services.
Microsoft.SharePoint.exe not running. Fusion 360 cam not running.
I reset paradox default printer and the PC default printer. No change.
I could roll back the latest Win update, it was over a week ago.
There is a system created restore point from a few days ago, might revert to that.
Ugh. It kills
me that these pops up seemingly randomly. In the past the only way to fix was to
reinstall windows.
>
Tahl Inc
Aug 30, 2024, 12:15:04 PM
I went down the
list killing processes until it stopped hanging. One computer it was Fusion 360
cam
<
Was it hanging (spinning) and as you killed the process it completed? Or did you have to kill a process, then restart Paradox and try again, etc?
I may switch to have the PDF printer as the default in Paradox and print to PDF then print the PDF if needed. Anyone done that?
something new must be added to the conflict list, but we must discover it first
--
You received this message because you are subscribed to the Google Groups "TheDBCommunity" group.
To unsubscribe from this group and stop receiving emails from it, send an email to thedbcommunit...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/thedbcommunity/a662fdfd-f404-4a50-a192-961ad37e2807n%40googlegroups.com.
On this PC I have 3-4 users.
Once this problem occurs, it affects other users doing a login or switch to another user. Until reboot.
BUT
I also have a hidden user that runs Paradox jobs from the scheduler. When I trigger a job for that user it does not hang. Basically, the hidden user logs in, opens Paradox and runs code, such as making PDFs. One difference is the hidden user (run as other user situation) does not show me the a “screen,” it runs in background, like a service account.
I also use AnyDesk and one of the crash logs (only one) listed waiting on AnyDesk. Maybe unrelated.
Bad to worse.
Since yesterday.
I have a few overnight processes that print PDFs (we use Adobe Pro).
These run under the hidden user.
A printing job, about 200 PDFs, failed mid run completing 85 PDFs.
Resetting and manually running the job (so I can watch it), it stops at 85 PDFs each time.
I login in as the hidden user (sometimes the login will be hung at Windows 11 upgrade, I turned that off, but now see a Windows backup reminder screen, bypassed that) and run directly from hidden user. Same issue, but stops at about 81.
The likely eliminates AnyDesk as these run unattended in AM hours and hang.
Then tried running a single job that switches to adobe, prints to file, switches back, fails for all users even after reboot. (Which are what others described, reboot no longer fixes it).
Later I will trace the code (and have base test code) to verify it hangs on printerswitching, BUT my code checks if Paradox printer is already set to Adobe and does not switch if it is already set to Adobe. After each print job I switch back to what the default printer was set to before job. If I change the default printer to Adobe before I start, the PDFs generate faster as it does not have to switch back and forth. (Even If running 100s of PDFs the switching time after each PDF is hardly noticeable). With the default printer set to Adobe, it still hangs.
This leads me to the printersetcurrent is not the problem? Will trace that later today.
When using Adobe, you preset the PDF name in the registry. This location has changed over the versions, but I have it documented. It seems OK. Since it works “sometimes” I do not think it can be an Adobe setup issue.
I will be checking Windows restore points and maybe updates. Did the basic table damage checks, etc. When this is happening, I watch processes and CPU, there is almost nothing else active.
This kills our PDF making process (even manually). These are synced to multiple PCs and emailed.
Considered changing default printer to Adobe and working it so it then prints hard copy, but as of now Paradox will not print to PDF even interactively if using the automated setup.
I will try manual open to screen printing and other variations later today.
Considering changing to HTML or text-based docs, but you know how customers like change.
the problem is printing, not creating, correct? go back to a batch file maybe?
copy my file.pdf \\myserver\myprinter
To view this discussion visit https://groups.google.com/d/msgid/thedbcommunity/84c5ae7f-2cda-4457-bcc1-23dc4daac524n%40googlegroups.com.
I tried many things remotely, found nothing.
Every time Paradox hung I rebooted, so almost a reboot after each test.
I found 100s of acrodist.exe tasks (we use acrobat) instances running. They very slowly cleared themselves. Normally during this process, I see them, but they clear quickly to the point of only seeing 2-3 as the press progresses. Odd but still not an explanation. Note I kill task some of the adobe tasks (including this one) after each PDF print having seen these pile up before. It seems they were not being killed. Since a reboot did not correct the problem (a reboot would have cleared all these), I thought it might be a memory capacity issue with acrobat, but again just randomly started a few days ago.
Turned of OneDrive,
but it seems to be present around after turn off, so rebooted.
No change to
the issue.
I removed the
OneNote printer (wish it would never come back removed it in the past.).
No change to
the issue, but remember other citing OneNote Printer issues.
Since this issue happened when I was not remoting using AnyDesk, likely not the cause, think I ruled out remote conflict issues.
Next, went in to location (day later).
Intended on using breakpoints / DEBUG() to see it stop hang PrinterSetCurrent().
Ran manual baseline
test, single PDF. Ran to success.
Ran unattended
baseline test, single PDF. Ran to success.
Ran large batch
tests. Ran to success.
Ran multiple
combination tests, all to success.
So, it is fixed?
Since it is “fixed itself,” I cannot verify it hung on PrinterSetCurrent() but it seems it did not. It somehow hung on not returning from acrobat, but also not killing that task.
Maybe OneNote printer / Acrobat conflict issues? Maybe one of the reboots?
Not sure when OneNote printer returned.
There seems to be no update to Windows recently. No update to Acrobat, the version we have is the last Pro version before they went to subscription server (ugh), so no updates ever.
Continuing to monitor, likely not a strict Paradox issue.
>>
My
"default" solution is:
I've created a ldl-library with my own Print-Method.
printerSetCurrent(ar[i])
<<
Right. I have many routines like this, dynamic printer checks, etc. THIS problem is that printerSetCurrent() hangs. It never returns or errors.
It has been a mystery for many years.
>>>
What I've not found, is a solution to read out the incoming e-mails (pop and
imap). Perhaps there's something to do it.
<<
The email object methodology in Paradox no longer functions as it used to function due to Microsoft and Windows changes. Most people found they cannot make it work.
I have moved to third party email programs, there are several (especially for plain text, that allow you to build a config or setup file dynamically and send and receive emails).
I have dedicated library for rolling dynamic batch files or command lines and executing them for many third party tools, email send, email receive, PDF editing, scanning, etc. In one case I built my own emailer in c# and hooked in the EXE.
>>>
And a small remark to smb problem:
There's a dBase SW - is the same situation like pdox (since about 2022 ist's
over, but still exists e.g. as FoxPro).
My idea: I
don't know, if it'll by possible to get the pdox code. If yes, then one can
ask, if it'll be possible, to stick both (pdox + dbase) together for a LAN
database. Later ask for MariaDB (= mySQL) as an enhancement for WAN, internet,
... databases.
<<<
Note, so far (anyone) has reported Paradox problems with SMB. I mostly have it on standalone PCs and have not yet seen an issue. Others have more experience, but a few reported no issue with is disabled. Depnds on your setup.
Paradox is still wholly owned and compiled to run in the latest WordPerfect suite, which is certified on the latest Windows OS. There have not been any functional updated in many years. I heard once they had 1-2 support people that only make sure it runs on latest Windows, as it is (only) part of the WordPerfect Suite. The source code has never been (and unlikely it will ever be) released to public domain or open source.
Here, we all recognize this and offer support where possible.
> Right. I have many routines like this, dynamic printer checks, etc. THIS problem is that printerSetCurrent() hangs. It never returns or errors.
> It has been a mystery for many years.
Looks like my long post reply with more details was deleted?
Summary:
The problem has returned after seemingly fixing itself.
Researching Randal’s change Windows default printer and open blank report solution, setting the Paradox printer to Adobe, this seems to work, testing.
But it only allows for setting the Paradox printer at first time printing is engaged. Meaning Paradox must “get” the Windows default printer on the first time (blank report) and then hold it as its default in memory? No one has ever found where this is stored.
I need to switch on the fly many multiple times without using printerSetCurrent()
Currently my unattended user only uses the PDF printer so it never uses printerSetCurrent().
Interactively I can CTRL-P and manually switch printers if I know a function will print to PDF.
Not the best and killing some canned hit a button processes.
Looking at:
1)
If I use the blank report to set Paradox default printer to Adobe and always print to PDF, then hard copy print PDFs as needed, that might work, I have all the pieces of code to do that. But a lot of work. Most f the printing sets and code are in a central library.
2)
My unattended user works as it only prints to PDF so never uses PrinterSetCurrent(). Its Windows default printer is Adobe. I might use that as a PDF print device. This unattended user invokes a Paradox library via windows scheduler using a batch file to pass in parameters then makes PDFs. I can call those maybe.
Using another users login to print PDFs.
Randy
interesting discussion.. only thing I'll add is AFAIK "all printers" to memory, not just the default.. that's how the "ghost printer" GP happens
To view this discussion visit https://groups.google.com/d/msgid/thedbcommunity/71c6cbce-ac93-418c-b469-4d5201a9581en%40googlegroups.com.
>
I don't use WMIC because it may go away at some point since it is deprecated by Microsoft: https://learn.microsoft.com/en-us/windows/win32/wmisdk/wmic
<
…
This utility is superseded by Windows PowerShell for WMI
….
Right, this was the fastest solution for me, but I wrapped it in a library method so I can just update that one method if needed. There are many ways to do this.
“superseded,” ha, Like Windows 10, Paradox, the version of MS-Office we have, probably 5-6 third party utilities, etc. but point taken.
The key was really the report open and close to lock it in.