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

Logshipping configuration error (Microsoft SQL Server, Error: 14262) Expand / Collapse
Author
Message
Posted Tuesday, September 2, 2014 6:31 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, September 22, 2014 12:35 PM
Points: 1, Visits: 17
Hi,

an error occurred while configuring logshipping in SQL Server 2008R2 Ent.Edition. can one of you please suggest me how to fix this error

=================================

TITLE: Microsoft SQL Server Management Studio
------------------------------

The current log shipping configuration is not functional because the required backup job cannot be found. You must drop the current configuration by clearing the 'Enable this as a primary database in a log shipping configuration' checkbox. To resume log shipping, recreate the configuration using the same settings.

If you resume log shipping and you specify the backup and restore paths that you used before, any backup files from the old configuration that are uncopied or unrestored will be copied and restored by the new configuration. Reinitializing the secondary database(s) is unnecessary.

------------------------------
ADDITIONAL INFORMATION:

The specified @job_id ('text') does not exist. (Microsoft SQL Server, Error: 14262)

Post #1609858
Posted Wednesday, September 3, 2014 2:00 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Wednesday, September 24, 2014 5:37 AM
Points: 498, Visits: 1,845
The error message tells you how to fix it, look. Do this.
jakeer.basha (9/2/2014)You must drop the current configuration by clearing the 'Enable this as a primary database in a log shipping configuration' checkbox. To resume log shipping, recreate the configuration using the same settings.

If you resume log shipping and you specify the backup and restore paths that you used before, any backup files from the old configuration that are uncopied or unrestored will be copied and restored by the new configuration. Reinitializing the secondary database(s) is unnecessary.
Post #1609899
Posted Thursday, September 4, 2014 8:42 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 6:42 PM
Points: 419, Visits: 2,594
Basically it's telling you to remove the existing log-shipping and configure new one.

Regards,
SQLisAwe5oMe.
Post #1610724
Posted Friday, September 5, 2014 5:03 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 3:53 AM
Points: 152, Visits: 470
Follow the below procedure.....

Step 1: Primary server i run below queries.

Note: here MyDB is your database name.

1)delete from msdb.dbo.log_shipping_primaries where primary_database_name = 'MyDB'
2)delete from msdb.dbo.log_shipping_monitor_primary where primary_database= 'MyDB'
3)delete from msdb.dbo.log_shipping_primary_databases where primary_database= 'MyDB'
4)delete from msdb.dbo.log_shipping_primary_secondaries where secondary_database= 'MyDB'


Step 2: Secondary server i run below queries.

1)delete from msdb.dbo.log_shipping_secondary where primary_database='MyDB';
2)delete from msdb.dbo.log_shipping_monitor_secondary where primary_database='MyDB';
3)delete from msdb.dbo.log_shipping_secondary_databases where secondary_database='MyDB';


Regards
Chowdary...
Post #1610838
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse