August 4, 2010 at 12:00 pm
This morning I was greeted by a problem I've never encountered and the resolutions I'm getting from different sources are conflicting, so I figured I'd ask you folks.
I have a 2 node cluster running SQL 2005 32 bit standard edition ; this cluster was created by one of our vendors. The cluster failed over last evening, intentionally, so one of our Windows engineers could apply Windows updates. After failing over, the periodic transaction log and nightly full backup jobs began to fail. After much digging, what I found was that the new active cluster ( first time it's ever failed over ) had a different level of SQL 2005 and did not have SSIS running.
The vendor is telling me that SSIS shouldn't matter ; another source I read said that the versions being different ( original active nose is SP2 ; new active node is base product ) would cause the failure. My gut is telling me that the real problem is SSIS not running but I know that the SP levels should be identical for thing to work properly.
Your input would be appreciated.
August 4, 2010 at 1:22 pm
After much digging, what I found was that the new active cluster ( first time it's ever failed over ) had a different level of SQL 2005 and did not have SSIS running.
If the instance is running on different level of SQL 2005, you must bring to the correct version. Also what is the error message you get when the jobs fail?
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
August 4, 2010 at 2:00 pm
I know I have to get the versions so they're the same ; I'm trying to get the vendor to agree to SQL 2005 SP3 for both servers. The server with SP2 has been the "active" node until the problem this morning. We rebooted the other node ( base version ) so the cluster would failover back to the SP2 version.
Am I correct that SSIS has to be running on both servers ?
There is no error in the SQL log and no log file for the maint plan. The only message I have is from the Idera SQL DM product that we monitor our servers with ; I have included that below :
-------------------------------------------------------------------------------------------------
8/4/2010 3:04:08 AM, SQL Server Agent Job Failure on GEWEBSQL is Warning.
SQL Server instance GEWEBSQL - SQL Agent job 'IDX Web Framework Backup.Subplan_1' failed with a Sql Severity of 0.
This job has run 1 times and failed 1 times since 8/4/2010 3:00:00 AM. The most recent job to fail started at 8/4/2010 3:00:00 AM and was in step Subplan_1 which issued the command '/Server "$(ESCAPE_NONE(SRVR))" /SQL "Maintenance Plans\IDX Web Framework Backup" /set "\Package\Subplan_1.Disable;false"'.
Sql Message ID: 0
Message:
Unable to start execution of step 1 (reason: line(1): Syntax error). The step failed.
Job Description: No description available.
SQL Server Agent Job Failure: The scheduled SQL Server Agent job ended with a Failed status.
August 4, 2010 at 8:44 pm
Please add an output file to the Job step of the job which is failing. It would give more details of the job execution.
[Edit] Adding to this, SQL Server 2005 and above does not require SSIS to be installed for running Maintenance Plans.
So please check if the Service Pack 2 has been correctly installed
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
August 5, 2010 at 5:43 am
Thanks for the link, Adiga. I will get SPs in line first and then try maintenance plan without SSIS loaded.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply