Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Run the Northern Region Print Script

Running the Northern Region Print Script DMW have recurring printing issues in the Northern Region. We have a powershell script to fix some of the most common ones, and occasionally they'll log a ticket to 'Run the script'. Edit How to check if you need to run it What's happening is that jobs are getting into an inconsistent state in the database, and it's preventing other jobs from being printed. The script will scan through all jobs currently being printed on the print node, then fix up any that are broken. You might need to run it a couple of times around 20 minutes apart to clear all the errors. You'll know if you are getting errors that can be fixed by this script by looking at the PrintNode log - C:\ProgramData\Winscribe\logs\Server.PrintNodeService.log. Scroll to the bottom, and if you see errors like this: 2024-05-15 22:25:29.5724 Error Could not update print node (Retries left: 1). System.ServiceModel.FaultException`1[Corridor.Client.CorridorDataService.CorridorFault]: There was an exception in the Data Corridor. Error code: NoPermissionToSite [NoPermissionToSite] (Fault Detail is equal to Corridor.Client.CorridorDataService.CorridorFault). Server stack trace: at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Corridor.Client.CorridorDataService.ICorridorDataService.UpdatePrintNode(UpdatePrintNodeContract contract) at Corridor.Client.CorridorDataService.CorridorDataServiceClient.UpdatePrintNode(UpdatePrintNodeContract contract) at Corridor.Client.CorridorProxy.UpdatePrintNode(PrintNodeContract printNode, Guid serviceUid, ServiceStatusContract status, List`1 logLines) at Server.PrintNode.Core.Services.CorridorCommunicationService.UpdatePrintNodes(PrintNodeContract printNode, Guid serviceUid, ServiceStatusContract status) at Server.PrintNode.Core.PeriodicWorkers.CorridorMessenger.OnCreateReport() Then running the script will help. Step 1 - run Powershell as service account First, you need to run Powershell as the service account. Use the appropriate service account for the environment from Keepass (svc_NuanceProd for production etc). Go to Start, then search for Powershell, then Shift-Right click on Windows Powershell and select 'Run as different user'. Once the powershell window has launched, you then need to launch an administrative window from within it. Step 2 - launch an admin Powershell window Run this command in the window that launches: start-process powershell –verb runAs That will launch a second powershell window, with admin priveleges. Step 3 - run the actual script Navigate to D:\Scripts and run .\ResetPrintNodeJobs.ps1 to run the script .\ResetPrintNodeJobs.ps1 You'll see a whole pile of output listing which jobs have been fixed and which have been left alone. Check the Print node logs again in about 15 minutes - you should see a whole bunch of jobs being printed, without the error occuring. If the error occurs, run the script again and then wait 15 more minutes. Repeat until the print happens without errors - usually you only need to run the script once or twice. 2024-05-16 10:15:54.4529 Info Preparing to print WS:C3203036:D3203036:Q565332 on RAD01P18. 2024-05-16 10:15:54.4529 Info Downloading document [WS:C3203036:D3203036:Q565332]... 2024-05-16 10:15:54.4842 Info Loading document... 2024-05-16 10:15:54.4842 Info Printing WS:C3203036:D3203036:Q565332 on RAD01P18. 2024-05-16 10:15:58.5038 Info Preparing to print WS:C3203036:D3203036:Q565333 on RAD01P18. 2024-05-16 10:15:58.5038 Info Downloading document [WS:C3203036:D3203036:Q565333]... 2024-05-16 10:15:58.5194 Info Loading document... 2024-05-16 10:15:58.5194 Info Printing WS:C3203036:D3203036:Q565333 on RAD01P18. 2024-05-16 10:16:47.3871 Warn Print Spool Reader completed successfully, however it consumed more than the allotted time (00:01:24.7757900 > 00:01:00) - please investigate. 2024-05-16 10:18:07.4477 Warn Print Spool Reader completed successfully, however it consumed more than the allotted time (00:01:20.0606271 > 00:01:00) - please investigate. 2024-05-16 10:19:25.9594 Warn Print Spool Reader completed successfully, however it consumed more than the allotted time (00:01:18.5116749 > 00:01:00) - please investigate. 2024-05-16 10:20:41.9521 Warn Print Spool Reader completed successfully, however it consumed more than the allotted time (00:01:15.9927063 > 00:01:00) - please investigate. 2024-05-16 10:21:58.2610 Warn Print Spool Reader completed successfully, however it consumed more than the allotted time (00:01:16.3089580 > 00:01:00) - please investigate. 2024-05-16 10:23:32.0427 Warn Print Spool Reader completed successfully, however it consumed more than the allotted time (00:01:33.7816404 > 00:01:00) - please investigate. 2024-05-16 10:25:03.4145 Warn Print Spool Reader completed successfully, however it consumed more than the allotted time (00:01:31.3718056 > 00:01:00) - please investigate. 2024-05-16 10:25:54.5784 Info Locating job to de-spool: PrinterName: RAD01P18, DocumentId: 0, PrintedPages: 0, TotalPages: 0, Status: None 2024-05-16 10:25:54.5784 Info De-spooling job [WS:C3203036:D3203036:Q565332] with Status: [Printed], resulting in JobStatus: [Deleted] 2024-05-16 10:25:54.7191 Info Locating job to de-spool: PrinterName: RAD01P18, DocumentId: 0, PrintedPages: 0, TotalPages: 0, Status: None 2024-05-16 10:25:54.7191 Info De-spooling job [WS:C3203036:D3203036:Q565333] with Status: [Printed], resulting in JobStatus: [Deleted] 2024-05-16 10:26:31.0465 Warn Print Spool Reader completed successfully, however it consumed more than the allotted time (00:01:27.6320153 > 00:01:00) - please investigate. Success!