Skip to main content
Known Participant
March 12, 2024
Question

How to get acrobat process count in the server machine

  • March 12, 2024
  • 1 reply
  • 1143 views

           We are the third party plug-in developers of Adobe Acrobat, and we have a product of plug-in applications,

and many of our customers using this product for many years.

            In order to evalutate the license of the product in Server machines(from where many client machines accessing this product), we use the logic of counting the number of acrobat processes running on the machine,  using the below code snippet

string MainFileName = System.Diagnostics.Process.GetCurrentProcess().MainModule.FileName;

System.Diagnostics.Process.GetProcessesByName(System.IO.Path.GetFileNameWithoutExtension(MainFileName)).Length;

From this we were getting number of Acrobat processes running the server and evaluting the same with license purchased, and

when all the licenses are in use, we display the message and opening the acrobat without loading our product.

this was working fine for many years.  But recently one of our customer (where they are on  Windows server 2019 datacenter), which purchased 6 liceneses, but when only 3-4 users open the acrobat,

it is saying all the 6 liceneses are in use and open the acrobat without our product.    Why our product failing to get the correct count of acrobat processes?  what causing to behave incorrectly,  can anyone help me on this?

 

This topic has been closed for replies.

1 reply

Participating Frequently
May 21, 2024

Here are a few potential reasons and steps to troubleshoot the problem:

Potential Causes and Solutions

  1. User Session Isolation: Windows Server environments, especially versions like Windows Server 2019, can run multiple user sessions. Each user session might have its own instance of Acrobat, but these might be isolated in a way that your current method isn't accounting for correctly.

  2. Permission Issues: The process of enumerating all instances of Acrobat might be failing due to insufficient permissions. Ensure that the process running your code has the necessary permissions to access all user sessions and enumerate all processes.

  3. Process Isolation by Service Packs/Updates: Recent updates or service packs to Windows Server 2019 might have introduced changes to how processes are handled or isolated. Make sure the server is fully updated, and consider any recent changes that might have affected this.

Elisabet

try67
Community Expert
Community Expert
May 21, 2024

Are you just copying and pasting responses from ChatGPT?

Participating Frequently
May 21, 2024

No... why?