You are viewing limited content. For full access, please sign in.

Question

Question

Snapshot Printing Blank Images

asked on June 1

Some users will get files with no images when using snapshot. The file name also defaults to Snapshot job instead of the %(PrintJobName) that I configured in my settings. It doesn't happen with every file we use snapshot on. So far it seems to happen only with PDFs. We are currently experiencing the issue with Crowdstrike and Microsoft with snapshot, however this issue only started happening a week or two ago. Anyone else having this issue?

0 0

Replies

replied on June 1

After some digging by our IT department, it seems like we are getting this error every time snapshot fails to properly print images. Anyone have this happen or know the fix? This issue only started happening after the crowdstrike/microsoft issue with snapshot. Not sure if it's directly related but the error timestamp matches.

 

Error Message:

The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server -----. The target name used was HTTP/----.domain.prv. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain (domain.PRV) is different from the client domain (domain.PRV), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
 

0 0
replied on June 2

Hi Mui,

This is a total shot in the dark, but if continue to encounter that Kerberos error after checking on SPNs and passwords, I just had a customer encounter a very similar error and we found that one domain controller was issuing Kerberos tickets using a method of encryption that other domain controllers didn't like, resulting in the Laserfiche server rejecting Kerberos tickets from clients. Could be worth looking into if IT determines it's not SPNs or passwords causing the issue.

1 0
replied on June 3 Show version history

Thank you, Jacob! IT says we only have 1 domain. We have checked the SPN's for duplicates and there was none. We have not changed the password and the user account is set to NOT expire the password. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.