Skip to main content
Solved

IFS10 .Net Print Agent Cannot start


Forum|alt.badge.img+7

Just installed a new IFS10 .net PrintAgent on a window 2019 server, everything went through but the server cannot start, here is log:

[005] 3/23/2023 4:02:45 PM: Starting REST Service...
[005] 3/23/2023 4:02:45 PM: Registering...
[012] 3/23/2023 4:02:45 PM: REST Service started on http://OCI-IFS10UD-SJ:8200/
[005] 3/23/2023 4:02:47 PM: Registered as [#HOST]-IFS10DE_PA
[005] 3/23/2023 4:02:47 PM: Added printer mapping:  PRINTER1->DUMMY 
[005] 3/23/2023 4:02:47 PM: State changed: RUNNING
[007] 3/23/2023 4:02:47 PM: Looking for jobs...
[007] 3/23/2023 4:02:47 PM: Error while looking for jobs. Reason:Internal Server Error
[007] 3/23/2023 4:02:47 PM: An internal server error occurred. Contact administrator.
The key value 'NodeName' is invalid.]
[007] 3/23/2023 4:02:57 PM: Looking for jobs...
[007] 3/23/2023 4:02:57 PM: Error while looking for jobs. Reason:Internal Server Error
[007] 3/23/2023 4:02:57 PM: An internal server error occurred. Contact administrator.
The key value 'NodeName' is invalid.]
……

he config file is 

 

Not sure what is the  ‘NodeName’  and where to change it,  anyone has a clue ?   

Thanks in advance,

David Cheng

 

Best answer by DavidSmile

It turned out to be the <ID>, changing to “IFS10DE” worked.  Giving credit to Salman Siddiqui from IFS.

thanks  

View original
Did this topic help you find an answer to your question?

3 replies

Forum|alt.badge.img+7
  • Author
  • Sidekick (Customer)
  • 14 replies
  • March 24, 2023

Btw, since this is first test, to simplify the scenarios, I tried to installed the print agent in the same server as the MW server, and the service account is local administrator.   Thanks


Forum|alt.badge.img+7
  • Author
  • Sidekick (Customer)
  • 14 replies
  • Answer
  • March 27, 2023

It turned out to be the <ID>, changing to “IFS10DE” worked.  Giving credit to Salman Siddiqui from IFS.

thanks  


Forum|alt.badge.img+3
  • Do Gooder (Customer)
  • 6 replies
  • September 19, 2023

Hello, 

 

We are experiencing the same issue. We have tried removing #Host with no luck. Has anyone else experienced this issue? 

 

Thank you for taking time and reviewing. 

Ashlyn


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings