March 22, 2010 at 12:01 pm
hello everyone,
I am doing a full backup of a database.
When i manural backup it , it works.
But when I setup a maintenance plan task to do it,it doesn't work.
this is a new installation of SQL Server.
Thanks!
March 22, 2010 at 12:08 pm
Could you be a bit more specific as to the backup via the maintenance plan? If there's an error, what error, etc...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 22, 2010 at 12:20 pm
I ask the person who installed this server.
it was not one time installation.
their steps on the installation is:
(1) install engine, not include management studio and agent service.
(2) install SP 2 .
(3) reinstall engine and management studio and agent service without uninstall previous components.
(4) install sp2 again.
I slao made a test of the maintenance plan.
I write a simple T-SQL script on management studio, it runs good,
then I create a maintenance plan task to run only this T-SQL script,
result is the same with the full back up task,doesn't work.
So I think the problem is conflict of the original installation.
Any Idea?
Thanks!
March 22, 2010 at 12:36 pm
Can you expand on 'doesn't work'?
Is there an error? If so, what error?
Does the maint plan never run?
Does it run successfully but the backup file is damaged?
etc?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 22, 2010 at 2:19 pm
Are you trying to backup across the network? Is SQL Server running under a domain user account that has the necessary rights to the folder being backed up to?
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
December 8, 2014 at 5:12 am
Can you help me?
I also have the same problem..
The error I get is this.
Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 10:18:59 Error: 2014-12-08 10:19:14.75 Code: 0xC00291EC Source: {.....} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2014-12-08 10:19:14.75 Code: 0x80019002 Source: OnPreExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2014-12-08 10:19:29.48 Code: 0xC0024104 Source: Back Up Database Task Description: The Execute method on the task returned error code 0x80131904 (A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2014-12-08 10:19:44.20 Code: 0xC0024104 .....
December 8, 2014 at 5:22 am
From that error message:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
Have you done so?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 8, 2014 at 5:53 am
I will have my colleagues on server team to check on that..
I know this server is on a clustered environment and its quite secure and secluded.
I've checked the Host Name on SQL Server Agent properties and its pointing to the clustered machine..
December 8, 2014 at 6:00 am
You need to check that the SQL instance is running and accessible, because the error is saying that it's not.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 8, 2014 at 10:55 am
The instance is definitely working.
Here is some more info..
If I create a job with the script to run a backup on all DBs and schedule this job, it works. The SQL Server Agent does call this job and it also works if I run manually (Start Job at Step).
Now, if I create a Maintenance Plan that will do the same thing, it doesn't work!.. even if I call this job manually.. Even if I point the location of the backup to the local machine.
So, I am trying to find out what the difference is when I create a job and when the maintenance plan creates it..
Hope I was able to shed some light now..
Thanks!!
December 9, 2014 at 11:31 am
When the process is ran by a job, is the job step using a credential to run? If so it could be an account different from the one the Agent service uses. According to Books Online, " In SQL Server 2005 Database Engine, maintenance plans create an Integration Services package, which is run by a SQL Server Agent job. " Could this explain why it works under one method and not the other?
----------------------------------------------------
January 7, 2015 at 2:50 am
Just thought I'd add some response on how this worked for me.
I've finally checked the file MsDtsSrvr.ini located on C:\Program Files\Microsoft SQL Server\100\DTS\Binn, this is part of the SSIS package configuration. First I made a copy of this file and edited the old one to point to server name and instance name.
<ServerName>ServerName\InstanceName</ServerName>
Out of almost 20 servers, who would think this exactly one wouldn't be completely configured..
The existing maintenance plan still didn't work, but all the new ones are working just perfect!
Hope this helps someone.
Thanks
January 7, 2015 at 11:56 am
For the plan that still does not work, did you try changing the "Local Server Connection" in the maintenance plan to a custom one with the account used being Windows NT Integrated security? What account starts the Integration Services service on that machine (View this in services.msc dialogue)?
----------------------------------------------------
March 30, 2015 at 1:10 pm
Can you follow the below steps....
1. Right click on the maintenance plans and click view history.
2. Open the backup Job which is failing and click on the step where it is failing.
3. At the bottom of the window, you would see a text box named as "Error message"..... Can you reply back with the error message that you see over there?
April 20, 2015 at 5:26 am
Unfortunately I don't have the maintenace plan anymore, it's already deleted.
But I've got the mesage you are asking for, which I had sent it previously:
Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 10:18:59 Error: 2014-12-08 10:19:14.75 Code: 0xC00291EC Source: {.....} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2014-12-08 10:19:14.75 Code: 0x80019002 Source: OnPreExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2014-12-08 10:19:29.48 Code: 0xC0024104 Source: Back Up Database Task Description: The Execute method on the task returned error code 0x80131904 (A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2014-12-08 10:19:44.20 Code: 0xC0024104 .....
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply