Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
chris_cs
Posting Yak Master
223 Posts |
 Posted - 2012-01-06 : 05:46:47
|
| Over the last couple of days we've had issues with all jobs on a server running, but then seemingly being unable to call SSIS paskages.These jobs have been running without issue for some time so it's a little bit of a mystery as to what is causing this issue.I can't see any errors in any logs, so apart from giving the server a reboot I'm not sure what else to do.Has anyone else experienced this?----------------------------Junior DBA learning the ropes |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-01-06 : 14:30:34
|
| can you give some info on error messages? unless you do that i dont think its easy to determine the reason for sudden job failures------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
biswajitdas
Starting Member
44 Posts |
Posted - 2012-01-08 : 19:26:40
|
| Please check the account or the services account which the jobs are running , I mean to say the job or the ssis package were excuted may be the account password expired or somebody change the password. |
|
|
|
chris_cs
Posting Yak Master
223 Posts |
Posted - 2012-01-09 : 04:34:30
|
| Looks like this was a memory issue on the box. There were no error messages we could see to indicate what the issue may have been. After restarting the box on the weekend the jobs are now running ok.The problem is this is a 32 bit server which runs SQL engine, SSIS, SSAS and SSRS. It's also one of our most heavily used servers.----------------------------Junior DBA learning the ropes |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-01-09 : 06:20:02
|
quote:
Originally posted by chris_cs
Looks like this was a memory issue on the box. There were no error messages we could see to indicate what the issue may have been. After restarting the box on the weekend the jobs are now running ok.The problem is this is a 32 bit server which runs SQL engine, SSIS, SSAS and SSRS. It's also one of our most heavily used servers.----------------------------Junior DBA learning the ropes
Ok then that might be one off issue with agent serviceWe usually use seperate boxes for DB,Integration and Reporting serversin prod env------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
chris_cs
Posting Yak Master
223 Posts |
Posted - 2012-01-09 : 06:43:46
|
| Yeah that's what we should also be doing.Not sure why they've left it so long!----------------------------Junior DBA learning the ropes |
|
|
|
|
|
|
Agent job not executing SSIS package