Viewing 6 posts - 16 through 21 (of 21 total)
I have to admit, that this is indeed a duplicate post and apologize, if any policies, unwritten or written, have been ignored.
But since the cause of the problem might be...
September 9, 2009 at 3:59 pm
Thank you very much for the detailed information
"I owe you guys"
September 9, 2009 at 3:55 pm
Thanks for the hint
Can you also please elaborate on how to use this environment variable
Thanks
September 9, 2009 at 1:48 pm
The value of the Max Concurrent Executables parameter was changed from -1 to 1
September 4, 2009 at 5:26 pm
I am not sure which component was throwing the error
But setting the Maximum Concurrent Executables value on the ExecutionOption tab under General of the Job Step Properties solved the problem
September 4, 2009 at 5:25 pm
Hi Old Hand,
Let me first thank you for the provided link.
Now the environment set up within I operate is as follows.
My machine is only loaded with sql server client tools...
September 3, 2009 at 11:18 am
Viewing 6 posts - 16 through 21 (of 21 total)