Hi Support

Discovered an issue this morning which I can't really explain and can't really provide evidence for. I recently upgraded one of our servers from 6.1.5 to 6.1.7. I ran an SQL job which failed and when I looked in to it further, it seems as if it has picked up an old version of the SQL statement. I know this because I changed the SQL last week to include some additional fields which have now dissappeared.

There is only one SQL job defined so I'm not mixing up jobs, but I am now wondering if I am losing my mind! 😉

Could this be possible? I know that there were some changes made in 6.1.5 to encrypt SQL statements as I ended up needing to re-define them.

Cheers

Andy

There could be a natural explanation. In version 6.1.7. we have started to encrypt the query string. Upgrade normally go in the following order:

1. check if old unencrypted string is empty
2. if not empty, encrypt and save new Task in new encrypted property
3. set old unencrypted string to empty

Not sure how this happened, maybe because of new server and old client or similar.

---