Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

backup on maintenance plan doesn't work. Expand / Collapse
Author
Message
Posted Monday, March 22, 2010 12:01 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, October 19, 2011 8:22 AM
Points: 11, Visits: 80
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!
Post #887559
Posted Monday, March 22, 2010 12:08 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:36 AM
Points: 40,615, Visits: 37,080
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #887569
Posted Monday, March 22, 2010 12:20 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, October 19, 2011 8:22 AM
Points: 11, Visits: 80
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!
Post #887589
Posted Monday, March 22, 2010 12:36 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:36 AM
Points: 40,615, Visits: 37,080
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #887608
Posted Monday, March 22, 2010 2:19 PM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Friday, December 12, 2014 12:03 PM
Points: 4,363, Visits: 9,547
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
Problems are opportunites brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs
Post #887677
Posted Monday, December 8, 2014 5:12 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, December 15, 2014 7:28 AM
Points: 3, Visits: 27
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 .....
Post #1642267
Posted Monday, December 8, 2014 5:22 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:36 AM
Points: 40,615, Visits: 37,080
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1642269
Posted Monday, December 8, 2014 5:53 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, December 15, 2014 7:28 AM
Points: 3, Visits: 27
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..
Post #1642278
Posted Monday, December 8, 2014 6:00 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:36 AM
Points: 40,615, Visits: 37,080
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1642279
Posted Monday, December 8, 2014 10:55 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, December 15, 2014 7:28 AM
Points: 3, Visits: 27
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!!
Post #1642377
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse