What I've come to think as a result of your question is that the subprocedure in the service program is reading and updating some fields from a file that contains an encrypted value as well. It isn't touching the encrypted field but still. Could that cause behavior like this?
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.