NPrinting Sept 2018 - unexplained metadata reload error

[kdmarkee]

I have several qvp connections set up in the NP web console that are set up the same way except for the qvw name.  We recently had our qvws that NP connects to on a server that was on a VM (lets call it "qlikA") but recently changed it so those qvws now exist on a stand alone machine (lets call it "qlikB").  All of my NP connection paths were updated to use qlikB and their metadata reloads were successful, except for one, so naturally this doesn't make any sense to me because my NP connections are all the same and nothing else has changed...all the publishing tasks to qlikB are the same (except again for the destination server name of qlikB) as are all the qvws themselves.  Also, the NP connection verification test is successful (screenshot below), so I really need some suggestions on where to even begin to figure out what is going on (assuming it is not some crazy bug). 

I've tried to look at the DEBUG logs but I'm not finding any solution or solid info.  A few of the errors from the log files are listed below but I haven't found much help in the Community.

• Failed to open a resolver for connection navigator
• ERROR: System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed.

The Task log in the NP web console gives this generic error: 

Any help or explanation would be appreciated, thanks.

[Ruggero_Piccoli]

Hi,

1. Try to restart the Qlik NPrinting Windows services
2. Try to open the same QlikView documents from QlikView Desktop with the same user that runs the Windows Services

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.