Hi all,
after creating the replication job (works) other agent jobs hang up. after restart the agent, the jobs work one time. t
can it be a problem with dieffernt agent profiles/accounts
many thanks
oliver
ok, i find some more details...
if i restart the agent i can manually start a job - and it works...
if i wait till the agent a job is starting it fails for each step:
Executed as user: domain\Administrator. The package execution failed. The step failed.
after manually starting the job the following automatic hangs up with step one till stop agent
The job was stopped prior to completion by Shutdown Sequence 0. The Job was invoked by Schedule 26 (Di - Fr ddddd). The last step to run was step 1 (AHD).
Executed as user: domain\Administrator. The step was cancelled (stopped) as the result of a stop job request.
manually restart the job works... could it be an user problem? which user probs were used when i start the agent job manu.
thanks
hi, sorry for the late reply ....
and thanks for yours!
we have 5 replication databases - with up to 15 tables.
+ we have up to 20 jobs for e.g. some ssis packages.
Hi Greg -
Can you point me to more information about your comment that there are known OS problems if one tries to start too many jobs at one time?
Paul
Here are a couple articles that document the problem, some of the know workaround is to increase the desktop heap, which I woulnd't recommend, stagger the start job times, change the proxy account for some of the jobs, move to 64bit OS (which isn't very practical for many):
http://support.microsoft.com/kb/824422
http://msdn2.microsoft.com/en-us/library/ms152544.aspx
