Tuesday, March 20, 2012

scheduled jobs are failing

I had about 30 schedule jobs that either import data or run sql queries.
They have worked wonderfully for months. All of a sudden they are failing.
I get the error message 203 ENVVAR_NOT_FOUND which translates to The system
could not find the environment option that was entered.
I don't understand what this means, nor how to fix it. I've spent almost 2
days searching for a solution. Even more complexing is why it all
changed...I haven't done anything different that I can think of.
Can someone please assist and point me in the right direction?
thanks in advance!!!Is it a specific type of step that is failing, or is your package not
starting at all? Have you enabled a package error log, to see if the log
file holds any further information?
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"tag" <tag@.discussions.microsoft.com> wrote in message
news:20709349-62D5-436C-A256-F15AEA8A4D1E@.microsoft.com...
I had about 30 schedule jobs that either import data or run sql queries.
They have worked wonderfully for months. All of a sudden they are failing.
I get the error message 203 ENVVAR_NOT_FOUND which translates to The system
could not find the environment option that was entered.
I don't understand what this means, nor how to fix it. I've spent almost 2
days searching for a solution. Even more complexing is why it all
changed...I haven't done anything different that I can think of.
Can someone please assist and point me in the right direction?
thanks in advance!!!|||is sql agent running
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"tag" wrote:

> I had about 30 schedule jobs that either import data or run sql queries.
> They have worked wonderfully for months. All of a sudden they are failing
.
> I get the error message 203 ENVVAR_NOT_FOUND which translates to The syste
m
> could not find the environment option that was entered.
> I don't understand what this means, nor how to fix it. I've spent almost
2
> days searching for a solution. Even more complexing is why it all
> changed...I haven't done anything different that I can think of.
> Can someone please assist and point me in the right direction?
> thanks in advance!!!|||Yes, SQL server agent is running
"Jose G. de Jesus Jr MCP, MCDBA" wrote:
> is sql agent running
>
>
> --
>
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "tag" wrote:
>|||are the jobs running when executed manually?
check for any virus activity
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"tag" wrote:
> Yes, SQL server agent is running
> "Jose G. de Jesus Jr MCP, MCDBA" wrote:
>|||No, it appears that they are trying to kick off.
When I review the jobs I see that the last run status is "Failed".
When I review the job history I get
"The job failed. The Job was invoked by User sa. The last step to run was
step 1 (Census1 Load Text). Executed as user: CLFDATA\SYSTEM. The process
could not be created for step 1 of job 0xC4F7C84FC07C4A439571C7C4BE326910
(reason: The system could not find the environment option that was entered)
.
The step failed."
I noticed that the package error logs were not enabled. I'm correcting that
oversight now.
"Narayana Vyas Kondreddi" wrote:

> Is it a specific type of step that is failing, or is your package not
> starting at all? Have you enabled a package error log, to see if the log
> file holds any further information?
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "tag" <tag@.discussions.microsoft.com> wrote in message
> news:20709349-62D5-436C-A256-F15AEA8A4D1E@.microsoft.com...
> I had about 30 schedule jobs that either import data or run sql queries.
> They have worked wonderfully for months. All of a sudden they are failing
.
> I get the error message 203 ENVVAR_NOT_FOUND which translates to The syste
m
> could not find the environment option that was entered.
> I don't understand what this means, nor how to fix it. I've spent almost
2
> days searching for a solution. Even more complexing is why it all
> changed...I haven't done anything different that I can think of.
> Can someone please assist and point me in the right direction?
> thanks in advance!!!
>
>|||No, when I right click on the job and click on
"start job", they fail. I'm running the virus scan now.
"Jose G. de Jesus Jr MCP, MCDBA" wrote:
> are the jobs running when executed manually?
> check for any virus activity
>
> --
>
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "tag" wrote:
>|||try creating a new simple job then
try to run it manually
if it fails to run then
the box is in trouble
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"tag" wrote:
> No, when I right click on the job and click on
> "start job", they fail. I'm running the virus scan now.
> "Jose G. de Jesus Jr MCP, MCDBA" wrote:
>|||I've done that multiple times...and it fails.
why is the box in trouble?
"Jose G. de Jesus Jr MCP, MCDBA" wrote:
> try creating a new simple job then
> try to run it manually
> if it fails to run then
> the box is in trouble
> --
>
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "tag" wrote:
>|||I found my solution. I was missing a ; in my path. Full details are locate
d
at Microsofts site: http://support.microsoft.com/?kbid=322746
Thanks to all who responded!

No comments:

Post a Comment