Jobs not compiling in production, but they do in test
Posted: Thu Feb 19, 2009 7:29 am
I've got a strange situation.
I've got code that's been running in production without any issues for a long time. Then all of a sudden, various parts started erroring. I can't Compile them from Manager. If I open the jobs in Designer, some of the "nodes" get that little yellow warning symbol.
All the parts that are failing are "nodes" that call multi instance reusable jobs that require you to fill in the Invocation Id. Some of the invocation ids had quotes and periods which if I remove, the problem goes away. Some of them were trying to use variables that didn't seem to exist so I fixed them appropriately. So I was able to fix all these pieces and things seem to be running fine.
But I'm worried now that these jobs had no problems yesterday, nor does the issue show up in dev/test. So I may develop/test something with no issues and then move to production and it doesn't work.
Another strange part:
We have two servers: a dev/test server and a production server. We have three projects: dev, test, prod. I can technically log onto the production server and open the test project, and vice versa. Here's the strange part: If I log onto the dev/test server and open the production project (the one throwing errors when on the production server), I don't see any problems. Similarly, if I log onto the production server and open the test project (which doesn't show any issues when on the dev/test server), the errors/warnings show up. So it doesn't seem like this is a project specific issue, but more of a server/environmental issue.
For the sake of full disclosure:
None of the jobs were modified in production as far as I know. We did have a few routines that weren't set to read-only and were accidentally changed. When I discovered that problem, I changed them back, initialized them back into Version Control and then promoted them right back as read only so that that doesn't happen again. I wouldn't think this has anything to do with it, but it was a change that happened right around the time the issue popped up.
So, does anybody have any ideas on what could cause this? It's like the Invocation Ids weren't taken seriously/literally before and then all of a sudden they were.
I've got code that's been running in production without any issues for a long time. Then all of a sudden, various parts started erroring. I can't Compile them from Manager. If I open the jobs in Designer, some of the "nodes" get that little yellow warning symbol.
All the parts that are failing are "nodes" that call multi instance reusable jobs that require you to fill in the Invocation Id. Some of the invocation ids had quotes and periods which if I remove, the problem goes away. Some of them were trying to use variables that didn't seem to exist so I fixed them appropriately. So I was able to fix all these pieces and things seem to be running fine.
But I'm worried now that these jobs had no problems yesterday, nor does the issue show up in dev/test. So I may develop/test something with no issues and then move to production and it doesn't work.
Another strange part:
We have two servers: a dev/test server and a production server. We have three projects: dev, test, prod. I can technically log onto the production server and open the test project, and vice versa. Here's the strange part: If I log onto the dev/test server and open the production project (the one throwing errors when on the production server), I don't see any problems. Similarly, if I log onto the production server and open the test project (which doesn't show any issues when on the dev/test server), the errors/warnings show up. So it doesn't seem like this is a project specific issue, but more of a server/environmental issue.
For the sake of full disclosure:
None of the jobs were modified in production as far as I know. We did have a few routines that weren't set to read-only and were accidentally changed. When I discovered that problem, I changed them back, initialized them back into Version Control and then promoted them right back as read only so that that doesn't happen again. I wouldn't think this has anything to do with it, but it was a change that happened right around the time the issue popped up.
So, does anybody have any ideas on what could cause this? It's like the Invocation Ids weren't taken seriously/literally before and then all of a sudden they were.