I have SQL Server 2005 log shipping setup with primary/secondary configuration. I can confirm from the logs that log shipping is working without issue, however, reports generated from the monitor server show this message:
Violation of PRIMARY KEY constraint 'PK__#log_shipping_mo__3ABBDC91'. Cannot insert duplicate key in object 'dbo.#log_shipping_monitor'. The statement has been terminated.
There is nothing special about the configuration. Any ideas?
The above mentioned script by Ron Craig was put on the SWYNK site on 22 February 2002. When all the SQL Server scripts were moved from SWYNK to Jupiter, this article and scripts were lost. I have contacted Jupiter and they admit that it has been lost. If anyone has downloaded this article(prior to the move from SWYNK), please can you forward it to me. If Ron Craig should read this, please can you forward your article to me and ask Jupiter to put it back.
I have 4 sql 2000 servers. One is a the primary, one is a local stand-by, one a remote standby and one is a training server. WHen configuring which server should monitor log shipping I was torn between the local standby and the training. The training server which only has a few users if ever, might be used for some DTS tasks in the future for some B to B stuff. Based upon this I am leaning on the local standby to monitor. Anyone have an experience or input? Thanks! (No I can't buy any more servers)
I have set up log shipping between two servers with a third serving as a monitoring server. Recently the monitoring for the eight databases that I am log shipping began to indicate that everything was failing. Upon further inventigation of the log_shipping_monitor_history_detail tables on the prinary and secondary everthing appears to working properly but I have been unable to resyncronize the monitoring. I have attempted to use the stored procedure sp_refresh_log_shipping_monitor to no avail, it does not appear to do anything with respect to the data in the dbo.log_shipping_primary_databases and log_shipping_monitor_primary tables on the primary server or the log_shipping_monitor_secondary and dbo.log_shipping_secondary_databases tables on the secondary. I have also manually updated the records in these tables in an attempt to syncronize but after the next sucessful backup, copy and restore this monitoring data is not updating. Does anyone have any ideas as to what I am doing wrong or how I might rectify this situation.
At one of our client side a wired log shipping issues has come up.while monitoring those two server i noticed that although log-shipping report says both server are in sync, report displays information related to both backup and restore , it doesn't shows information related to copy that is when was last file copied and last file copy column is showed blank. Same is when i execute proc "sp_help_log_shipping_monitor" . I get same result ...
When i expand copy job history to analyse its what i found is although job has executed successfully , but in depth reading each steps says that no .trn file was copied .
My copy directory is at secondary server itself where .trn files are placed.And from this location itself files are begin restored.
SQL server and agent on both servers are run by same domain account ....
We have set-up log shipping in both our development and production environments. The difference between the two is that development is using SQL 2005 Developer Edition SP2 and production is using SQL 2005 Enterprise Edition SP2. As well, the production environment runs using 64-bit 3-node failover cluster set-up for the source, whereas the development source server environment is 32-bit and not clustered. Also, our development environment destination/monitor instance is located within the same geographic location mapped to the same domain controller. The production environment destination/monitor instance is located off-site, and although is part of the same domain, uses a different domain controller which is synched-up with the primary domain controller used for the source server and entire development environment. Other than that, both environments run using Windows 2003 Server Enterprise Edition SP1.
Originally, both environments were configured to use Monitor connections "By impersonating the proxy account of the job (usually the SQL Server Agent service account of the server instance where the job runs)". This presented no problems in the development environment, but in the production environment, this results in the following error whenever the source server tries to update the monitor instance with the backup alert status:
Error: 18456, Severity: 14, State: 11. Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. [CLIENT: XXX.XX.XX.XX]
This also results in the log-ship alert job falsely reporting that backup jobs are "out-of-synch", since the source server cannot write log information to the log ship tables on the destination/monitor instance.
Now, according to BOL, when choosing to impersonate the proxy account, this is supposed to default to the SQL Server Agent Service account, which in our systems (both development and production), is a Windows domain account with full administrator priviledges and a SQL system adminstrator on both source and destination/monitor instances.
Upon trying to open a case with Microsoft originally when we were running on SQL 2005 SP1, and spending several hours ensuring there were no duplicate SPNs and linked servers were properly configured, they had come to the conclusion that this was the result of a known SP1 issue (http://support.microsoft.com/kb/925843), and would be solved by applying SP2. We are now running SP2 + hotfix (9.0.3152), but are still receiving this error.
The only way I have currently of fixing this issue is by changing the Monitor connection from authenticating via proxy account to using a SQL Server login account which has system admin priviledges.
I have limited knowledge of how security is applied across different domain controllers within the same domain. Any help would be greatly appreciated.
If I'm on a remote machine, meaning a computer not in the WSFC cluster, and I open SSMS 2014, point it to a SQL Instance, and open activity monitor:
1. I get all the panes and charts except % Processor Time.
2. Then, if I authenticate to the cluster's domain by mapping a drive with valid domain credentials, I'm free to put performance counters in the Perfmon - - - but SQL Activity Monitor shuts down with“The Activity Monitor is unable to execute queries against server SQL-V01INSTANCE1..Activity monitor for this instance will be placed into a paused state.Use the context menu in the overview pane to resume the activity monitor.
Additional information: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))(Mscorlib)”
3. Of course, the Activity monitor can't be resumed via the context menu. Removing counters and closing the perfmon do not work. I dropped the mapped drive and rebooted the machine. That brought back 95% of the information in the Activity monitor.
4. Further experimentation showed that any mapping of drive shares present on the SQL Server to the computer running SSMS cut off functionality of the 'overview' pane in the remote machine's SQL Activity monitor -- the monitor that had been trying to watch the server offering the shares.
I have implemented log shipping on one my databases. Logs are being shipped just fine and are even being applied. Change something on primary and you will see it on the secondary.
However when I generate Transaction Log Shipping Status Report from the Primary Server, I see that Stauts is GOOD. I see primary and secondary servers names. I see when the Last backup occured. But there is no data on COPY and RESTORE. Those columns are grayed out or should I rather say colored gray with no values.
When I go onto secondary node and generate Transaction Log Shipping Status Report, columns under Restore header are popluated. But columns under BACKUP and RESTORE are grayed out.
On monitor node Transaction Log Shipping Status Report doesnt show when the last backup, or restore or copy occured. It only shows the threshold value for backup and restore.
So I have two questions: 1) why am I not seeing all the info in one place? how can I find out how far behind is secondary? 2) shouldnt Transaction Log Shipping Status Report from any node show me same information? 3) even though changes are making it to secondary once the threshold value is hit, status would not be GOOD anymore. so no matter what I do it would be out sync when it is not.
I have a log shipping configuration where Server A is primary, B is secondary and C is the monitoring Server. When I run a query on both A and B I get similar results. Which means log shipping is working fine.
However when I run 'Transaction Log Shipping Status' Report on the monitor server I am unable to tell which files were recently copy and which files were last applied. or even when the last backup occurred or a copy was made. The columns are empty. I would like to find out what would cause this to heppen?
Also is there a way to find out the lsn of the databases on both primary and secondary servers.
hi, i am facing a problem in creating labels usin Report Builder. i need to create a 4X6 label containing 4 rows. But in Report Builder , when i try to create a table format, it only allowing one row. How to insert another row and place data in it?
i was successfully developed labels using report server project in VS 2005.
but it's not possible in Report Builder.
please help me out.if not understand quesion well, please feel free to ask.
When Replication monitor shows an error icon, I removed all the publication jobs completedly. After I reconfigured publishing, subscriber,Distribution, why the replication monitor still shows an error icon even though there is no replication job scheduled?
We have recently set up two SQL Server 2005 Standard Edition serverswith database mirroring. The mirrors function and fail over without aproblem, but the Database Mirroring Monitor Job fails every time withthe following error message:Incorrect syntax near '.'. [SQLSTATE 42000] (Error 102) Incorrectsyntax near the keyword 'with'. If this statement is a common tableexpression or an xmlnamespaces clause, the previous statement must beterminated with a semicolon. [SQLSTATE 42000] (Error 319). The stepfailed.Both SQL Servers are running SP2 with the latest patches.Can anyone help with the resolutionto this this issue?Thank you!Bosko
Have two servers, one production server and one backup server. Both are Windows 2003 Server having SQL Server 2000 installed.
I have created replication on these servers using a wizard. I then generated SQL scripts to delete and create the replication. These scripts work well, but to test to remove the replication on both servers I used sp_removedbreplication 'DBNAME' on both servers. Not all were removed and on Replication Monitor and sub items plus Log Reader Agent there were added an icon, a red 'X' as in error. The replication seems to work.
Does anyone have any idea on why this happened and what I can do about it. It is not very nice to have errors in replication on a customers servers.
Trying to use WMI to monitor a SQLExpress DB and not getting anywhere. In fact, wmiprvse.exe croaks.
Here's the query I'm running from within CIM Studio: select * from Win32_PerfRawData_MSSQLSQLEXPRESS_MSSQLSQLEXPRESSDatabases
(Just did a search for SQL and found this class)
When trying to get an instance, WMIPRVSE throws this exception: The exception unknown software exception (0xc000000d) occurred int he application at location 0x7814454d.
Ok to that, then another msgBox shows up with a title of
"Multiview Message" and text as below: Win32: The remote procedure call failed. An error occurred while attempting to retrieve the list of objects.
Any suggestions on this would be appreciated. Or perhaps another WMI class to use?
(XP Pro SP2, current with the patches; SQLExpress and MSDE both running)
I have setup log shipping for one of my production server.The purpose of setting log shipping is having a standby server in case the primary fails. Now i am getting the error saying: The log shipping destination server is out of sync by 640 minutes. [SQLSTATE 42000] (Error 14421) Associated statement is not prepared [SQLSTATE HY007] (Error 0). The step failed.
SQL Server Management Studio could not save the configuration of 'B1' as a Secondary.
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
The specified @server_name (A1) does not exist.
The specified @server_name (A1) does not exist.
The specified @server_name (A1) does not exist. (Microsoft SQL Server, Error: 14262)
I have two sql 2005 servers A1 and B1 but the databases are setup with sql 2000 compatibility.
A1 service accounts use local system account. B1 service accounts use domain system account.
I can easily restore a database from a shared folder on A1. I followed this article to setup log shipping. http://deepakinsql.blogspot.com/2007/06/how-to-configure-log-shipping-in-sql.html
Log Shipping is not replication in the immediate sense, but it is as close as I could find in this set of forums. If there is a better place for this question, please direct me to it.
I keep encountering this error when I try to install another SQL Server after uninstalling Express: - Performance Monitor Counter Requirement (Error) Messages Performance Monitor Counter Requirement
The System Configuration Check for Performance Monitor counter registry value has failed. For details, see How to: Increment the Counter Registry Key for Setup in SQL Server 2005, in the readme file or in SQL Server Books Online. I've looked up the solution and it says to change the Perflib entry in the register...only I don't seem to have one! this is highly annoying as I can do nothing to remedy the situation. Any ideas?
I'm attempting to configure log shipping on 2 servers with SQL Server 2000 sp4 Enterprise Edition. I keep getting the following error when the job attemtps to execute.
Error 14261: The specified primary_server_name.primary_database_name('C') already exists.
I have tried this KB http://support.microsoft.com/kb/298743 and i got the same error again!
Scenario : MS Windows 2003 SP1 - MS SQL Server 2000 EE SP4
Log Shipping
My secondary server was restoring backup logs successfully, but suddenly i got the following error:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4323: [Microsoft][ODBC SQL Server Driver][SQL Server]The database is marked suspect. Transaction logs cannot be restored. Use RESTORE DATABASE to recover the database. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.
How can I fix this situation without re create the maintenance plan ??
I have a pretty complicated report (lots of subreports, tables, etc) that can be well over a few hundred pages long. I can generate the report just fine, but I cannot seem to export it to anything other than an html archive. I need to export to PDF. Every time I try to export it get an error that says:
An internal error occurred on the report server. See the error log for more details.
I don't get any more information than that. Is there a way that I can figure out what the actual error is, or any other way I can go about troubleshooting this? Thanks.
I am receiving errors from a job that no longer exists. The databases created for this no longer exist also.
DATE/TIME: 4/6/2007 3:32:00 PM
DESCRIPTION: The log shipping secondary database LOG1.log_ship_test has restore threshold of 45 minutes and is out of sync. No restore was performed for 6004 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
COMMENT: (None)
JOB RUN: (None)
I have gone into agent jobs and deleted those associated with it. I have also gone into the msdb database and deleted any lines associated with it in the log_shipping tables. But the errors keep coming. What do I need to do to clean this up?
I have log shipping set up between two servers (s1 and s2). Data is flowing from s1 to s2 and the log shipping monitor is on s1.
I get the following error sporadically "Transaction Log Backup Job for DB Maintenance Plan 'LogShip DatabaseName" failed.. Error: 60000, Severity: 10, State: 1
So i usually go and start the job manually and it runs fine. But why does this happen and what does the error mean? The above job is scheduled to run every 5mins daily.
Thanks in advance!
THE LADDERS (The Most $100k+ Jobs.) www.TheLadders.com
I am getting the following error " The specified servername does not exist" when I run the Log Shipping procedure. There is only a Primary server running Win Server 2003 withe Service pack 2 and SQL Server 2005 with service pack 2 and one secondary server runnung Win Server 2003 R2 with service pack 2 and SQL Server 2005 with service pack 2. All permission setting look ok . Can anyone help
I could not able to find Forums in regards to 'Log Shipping' thats why posting this question in here. Appriciate if someone can provide me answers depends on their experience.
Can we switch database recovery model when log shipping is turned on ?
We want to switch from Full Recovery to Bulk Logged Recovery to make sure Bulk Insert operations during the after hours load process will have some performance gain.
my database is already deleted and there is no job are running for that database .previously we configure a log shipping for that database and deleted.log shipping backup job also deleted.the log shipping alert job is throwing bellow error.
The log shipping primary database tes1 has backup threshold of 60 minutes and has not performed a backup log operation for 132722 minutes. Check agent log and logshipping monitor information.
I have setup transactional replication everything on one box. later(two or three weeks later), Replication monitor is show red X Under my publishers (publications is disconnected). this is SQL2005.
We tried to configure log shipping using script generated by GUI and when executed specific script which is meant for secondary server the database is not created and threw below error.
Msg 15010, Level 16, State 1, Procedure sp_add_log_shipping_secondary_database, Line 50
The database 'BUBALLO' does not exist. Supply a valid database name. To see available databases, use sys.databases.
Note: Only Copy, restore and alerts jobs have been created.
The account I'm trying to configure log shipping is the service account by which SQL and agent services are running and folder in where data and log files are intended and to be created is open to all (everybody has read/write permissioins) believe the issue is not with permissions.
I set up Log Shipping with just 2 servers primary and secondary. When I run from the Wizard for the very first time keeps failing at the stage of saving Secondary Server Configuration info. When i instead run the generated script this problem disappears but then restoring of transactions fails - the process can backup transactions from the Primary server , copy them accross to the secondary and fails on the restore. Any ideas why.
I 'm sure I am missing something obvious, hopefully someone could point it out. After a failover log shipping, I want to fail back to my inital Primary server database; however, my database is marked as loading. How can I mark it as normal?
I did the failover as follow:
I did a failover log shipping from the 2 server Sv1 (Primary) and Sv2 (Secondary) by doing the following
1) Stop the primary database by using sp_change_primary_role (Sv1)
2) Change the 2nd server to primary server by running sp_change_secondary_role (Sv2)
3) Change the monitor role by running sp-change_monitor_role (Sv2)
4) Resolve the log ins - (Sv2)
5) Now I want to fail back - I copy the TRN files to Sv1 - use SQL Ent to restore the database at point in time. The task is done; however, the database is still mark as loading. I could not use sp_dboption.
I received an alert from one of my two secondary servers (all servers are running 2012 SP1):
File 'E:SQLMS SQL ServerMSSQL11.MSSQLSERVERMSSQLDATAMyDatabaseName_DateTime.tuf' is not a valid undo file for database 'MyDatabaseName (database ID 8). Verify the file path, and specify the correct file.
The detail in the job step shows this additional information:
*** Error: Could not apply log backup file 'MyDatabaseName_DateTime.trn' to secondary database 'MyDatabaseName'.(Microsoft.SqlServer.Management.LogShipping) ***
*** Error: Table error: Page (0:0). Test (m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
Table error: Page (0:0). Test ((m_type >= DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE && level == BASIC_HEADER)) failed. Values are 0 and 0.
Table error: Page (0:0). Test (m_freeData >= PageHeaderOverhead () && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot)) failed. Values are 0 and 8192. Starting a few minutes later, the Agent Job named LSRestore_MyServerName_MyDatabaseName fails every time it runs. The generated log backup, copy, and restore jobs run every 15 minutes.
I fixed the immediate problem by running a copy-only full backup on the primary, deleting the database on the secondary and restoring the new backup on the secondary with NORECOVERY. The restore job now succeeds and all seems fine. The secondaries only exists for DR purposes - no one runs reports against them or uses them at all. I had a similar problem last weekend on a different database that is also replicated between the same servers. I've been here for over a year, and these are the first instances of this problem that I've seen. However, I've now seen it twice in a week on the same server.
