Skip to main content

Hi,

We’ve been having problems recently with the IFS PrintAgent, which is perplexing and causing us operational issues as we need a reliable print service to run some of our Depot operations.

 

The behaviour we are seeing is that the PrintAgent will periodically crash. When we see the crash, we normally have this error in the PrintAgent log (sometimes there is no error logged):

  • [016] 30/05/2025 06:25:54: Error: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Any print jobs that were submitted at the time of the error get stuck in “Remote Working” state, and have to be restarted.

We see the following Windows Event log error at the same time as the crash events:

Faulting application name: IFSPrintAgent.exe, version: 1.0.3.0, time stamp: 0x609183ec
Faulting module name: ntdll.dll, version: 10.0.17763.7240, time stamp: 0xd2a47020
Exception code: 0xc0000374
Fault offset: 0x00000000000fb199
Faulting process id: 0x2a20
Faulting application start time: 0x01dbd1244e01fb82
Faulting application path: D:\IFS\PrintAgents\IFSPrintAgent_IFSL\IFSPrintAgent.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 60bfa663-5035-4b2b-b8cf-8f9ee50e9213
Faulting package full name: 
Faulting package-relative application ID: 

 

What’s perplexing us that we can go days without a problem, then suddenly have a period of time where the issue occurs several times in an hour. There is no correlation between the crash and the document being printed, whether it’s a Crystal or Report Designer report, which physical printer it’s being sent to etc. etc. The only pattern as such is that we tend to see it happen earlier in the morning (which is when ‘start’ work and have higher volumes of documents) and sometimes late in the evening (ironically when we have very low print volumes).

 

We are running IFS10, UPD25 and are are using the .NET version of the print agent. We have two print agents running on different servers servicing different physical printers - we see the same behaviour on both print agents.

We’re stuck on what could be causing this and what steps to look at to resolve.

Any help appreciated!

Ashley

Hi ​@AshT ,

Have you performed any recent windows system / certificate updates recently on the VM where the IFS Print agent is hosted?. Could you please share your windows version along with the .NET Framework Version which has been installed in the VM?

 

Regards,

Abises

Hi ​@Abises Weerasekera ,

Thanks for your thoughts.

 

We have two different agents running, on two Virtual Machines. We see the same issue on both servers:

  • Print Agent A
    • Windows Server 2019 Standard
    • .NET Framework version 4.7.03190
  • Print Agent B
    • Windows Server 2022 Standard
    • .NET Framework version  4.8.04161

(Note we created Print Agent B in the hope that a new print agent install would fix the problem - but we see the same)

 

The issue started a several months ago - so we’ve had a number of windows updates on IFS MWS, Oracle and Print Servers since the issue started to show up.

 Not sure if that gives you any clues?

Thanks,

Ashley

 

Hi ​@AshT,

I think better to create a support ticket for this issue with the Print Agent and other logs if the issue has not been resolved yet.

Hi ​@AshT ,

 

 did you get a solution from IFS R&D?

/Chandana

Terms & ConditionsCookie settingsAccessibility statement