2012 SQL server log shipping problem

Scenario:
Site 1: 2012 Enterprise version 64-bit (11.0.3128.0) - Log shipping is enabled for four databases. Shipping logs over a WAN every 15 minutes to a DR site.
Site 2: 2012 Enterprise version 64-bit (11.0.3128.0) - Secondary server for log shipping.
Site two functions for a period of time with the databases in Standby/Read-Only mode, then the databases will mysteriously switch to "restoring..." mode and error 14420 Severity 16 State 1 will appear in the logs. I have located kb2987585
and this did apply to the situtation as the sector sizes were different, so as a work around I moved the log shipping shared folder on the secondary server to a drive with the same sector settings as the primary server but this did not resolve the issue.
Has anyone had this issue and can you offer potential solutions?
Thank you -

Hi,
I still consider the bug raised in
https://support.microsoft.com/kb/2987585?wa=wsignin1.0
is not fixed. I have seen lot of other users complaining. But at this point I need to have look at SQL Server errorlog
sp_readerrorlog
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Similar Messages

Sql server log shipping space consumption

I have implemented sql server logs shipping from hq to dr server
The secondary databases are in standby mode .
The issue is that after configuring it , my dr server is running out of space very rapidly
I have checked the log shipping folders where the trn files resides and they are of very decent size , and the retention is configured for twenty four hours
I checked the secondary databases and their size is exactly same as that of the corresponding primary databases
Could you guys please help me out in identifying the reason behind this odd space increase
I would be grateful if you could point me to some online resources that explains this matter with depth

The retention is happening . I have checked the folders they do not have records older then 24 hours .
I dont know may be its because in the secondary server (Dr) there is no full backup job working , is it because of this the ldf file is getting bigger and bigger but again I far as my understanding goes we cannot take a database full backup in the stand
by mode .
The TLog files of log shipped DBs on the secondary will be same size as that of primary. The only way to shrink the TLog files on secondary (I am not advising you to do this) is to shrink them on the primary, force-start the TLog backup job, then the copy
job, then the restore job on the secondary, which will sync the size of the TLog file on the secondary.
If you have allocated the same sized disk on both primary and secondary for TLog files, then check if the Volume Shadow Copy is consuming the space on the secondary
Satish Kartan www.sqlfood.com

I see most recent file is called sql server log shipping work file

What is "SQL server log shipping work file"?

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/62a6556e-6655-4d19-9112-1788cf7bbcfc/wrk-file-in-logshipping-2005
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Sql Server Log shipping

Hi,
We have configured log shipping in our production setup. Now we are planning to change the service account from local system on which SQL Server is running to to other domain account.
Pls let me know changing the service account would have any impact on Log Shipping.
Regards,
Varun

Hi n.varun,
According to your description, about startup account for SQL Server and SQL Server Agent Services on Log Shipping Servers, if you have placed SQL Servers in a domain, Microsoft recommends that you use a domain account to start SQL Server services. As other
post, the domain account has full control permissions on the shared location and is sysadmin role in SQL Server security. Even if
you change the account form Local System to the domain account in SQL Server Configuration Manager (SSCM), it would have no impact on Log Shipping.
In addition, if you configure SQL Server Log shipping in a different domain or workgroup, we need to verify that the SQL Server Agent service account running on the secondary server must have read access to the folder that the log backups are located in,
and has permissions to the local folder that it will copy the logs to, then in secondary server, we can change the SQL Server Agent from using Local System to the domain account you are configuring. For more information, see:
http://www.mssqltips.com/sqlservertip/2562/sql-server-log-shipping-to-a-different-domain-or-workgroup/
There is an detail about how to configure security for SQL Server log shipping, you can review the following link.
http://support.microsoft.com/kb/321247
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

"HadrLogCapture" messages in SQL Server Log

HI
After activating AlwaysOn High Availibility Groups in SQL Server 2012 R2 and adding databases at the availibilitygroup, SQL Server started genereting lots of messages in the SQL Server Logs.
Some example Messages are: "DbId (1466) log capture is rescheduled with partner generation: 45, log consumer id: 9828",
"HadrLogCapture::BuildMsgBodyForSend - DbId [2535]->[1807D374-DA55-4CAC-A831-AA3C3A8B8EC4] Send From
saved msg - LogBlockId (0x000221e800000010)"
Is there is a possibility to stop generating these messages?

I guess supressing them would be a wrong approach. there is some underlying problem with the data movement which you have between primary and secondary replicas.
Here are my questions:
What is the sync setting and how many replicas you have?
What is the SQL Version? Output of Select @@version query
Do you see any latency on Dashboard? Check if redo queue or log send queue is high
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Crystal Report 2008 results "Password did not match error" in SQL Server Log

Hi,
I am trying to develop some crystal reports using Crystal Report 2008 SP4 to connect to SQL server 2008 through RDO (ODBC). My problem is that anytime Crystal Report is trying to establish a connection with SQL Server, first it tries to connect with the wrong password and results the following error message in SQL Server log:
Login failed for user 'peyman'. Reason: Password did not match that for the login provided. [CLIENT: 192.168.2.198]
The login name 'peyman' is the right one as I have quoted the same in setting up ODBC System DSN using "SQL Server Native Client 10". But somehow Crystal Report is taking its chance and trying to connect before prompting me for the password. After this error logged to SQL server side, I can see Crystal Report pops up the prompt to enter DSN password. After supplying password to this prompt, Crystal Report works fine and pulls the data and renders the report without having any more incorrect password error logged to SQL Server.
The attached file shows the step I am taking to regenerate the issue. I need this to be fixed as anytime uses any of these reports and tries to render it with crystal runtime engine the same error message raises in SQL Server side and logged in the log file.
Thanks,

Hi Peyman,
This is the way it should work, In CR designer when you open the report it does nothing. As soon as you hit the Refresh button then CR tries to use the connection saved with the report. It assumes what is saved with the report is a valid server and connection info. CR simply tries to verify the server is still active.
If you don't want it to fail in CRD then before opening any report Click the File, Log on Database option and connect. Now when refreshing reports it won't log the failed.
In the SDK it does the same thing, it assumes the Server info is the same and does try to connect to verify the Server does exist. It only takes a few milli-seconds to do this
To stop this from happening set the log on info first then it won't log the attempt to connect, it's checking to see if Trusted is allowed.
TIMESTAMP    THREAD_ID    FILENAME    LINE_NUMBER    LOGGED_DATA    LEVEL
2014-6-2 8:30:11.439    57320    .\QESession.cpp    444    Set Product View Locale: 4105    20
2014-6-2 8:30:11.439    57320    .\QESession.cpp    478    Set Preferred View Locale: 4105    20
2014-6-2 8:30:11.439    57320    .\QESession.cpp    500    Set Process Locale: 4105    20
2014-6-2 8:30:11.440    57320    .\qecommon.cpp    117    This property is currently in a read-only state and cannot be modified. File Name: ".\QEProperty.cpp". Line: 217    1
2014-6-2 8:30:11.967    57208    .\QESession.cpp    444    Set Product View Locale: 4105    20
2014-6-2 8:30:11.967    57208    .\QESession.cpp    478    Set Preferred View Locale: 4105    20
2014-6-2 8:30:11.967    57208    .\QESession.cpp    500    Set Process Locale: 4105    20
2014-6-2 8:30:11.968    57208    .\qecommon.cpp    117    This property is currently in a read-only state and cannot be modified. File Name: ".\QEProperty.cpp". Line: 217    1
2014-6-2 8:30:11.999    57208    .\QESession.cpp    444    Set Product View Locale: 1033    20
2014-6-2 8:30:12.4    57320    .\qecommon.cpp    117    This value is write-only. File Name: ".\QEProperty.cpp". Line: 145    1
2014-6-2 8:30:56.278    57208    .\odbcapi.cpp    301    Beginning COdbcapi::DriverConnect    20
2014-6-2 8:30:56.342    57208    .\odbcapi.cpp    335    Ending COdbcapi::DriverConnect    20
2014-6-2 8:30:56.342    57208    .\connect.cpp    2170    SQLDriverConnect succeeded: DSN = 192.168.13.172, User ID = sa, Password = ********    10
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 854    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 854    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 854    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 916    1
2014-6-2 8:30:56.348    57208    .\QERowset.cpp    1184    Beginning CQERowset::readFirstRecord    20
2014-6-2 8:30:56.348    57208    .\QERowset.cpp    2149    Beginning CQERowset::restart    20
2014-6-2 8:30:56.348    57208    .\QERowset.cpp    2370    Beginning CQERowset::execute    20
2014-6-2 8:30:56.353    57208    .\DbQueryBuilder.cpp    514    Query Targets: sqlncli10, ODBC3SQLServer    10
2014-6-2 8:30:56.353    57208    .\DbQueryBuilder.cpp    525    Successfully built query:    SELECT "Orders"."Customer ID", "Orders"."Employee ID"   FROM   "xtreme"."dbo"."Orders" "Orders"    10
2014-6-2 8:30:56.353    57208    .\odbcapi.cpp    875    Beginning COdbcapi::ExecDirect    20
2014-6-2 8:30:56.354    57208    .\odbcapi.cpp    884    Finishing COdbcapi::ExecDirect    20
2014-6-2 8:30:56.354    57208    .\rowset.cpp    220    SQLExecDirect succeeded: SELECT "Orders"."Customer ID", "Orders"."Employee ID" FROM   "xtreme"."dbo"."Orders" "Orders"    10
2014-6-2 8:30:56.354    57208    .\QERowset.cpp    2814    bindToField succeeded: Orders.Customer ID is using client buffer    10
2014-6-2 8:30:56.354    57208    .\QERowset.cpp    2814    bindToField succeeded: Orders.Employee ID is using client buffer    10
Notice it doesn't try to connect first if I set the log on info first using code.
So nothing we can do to stop SQL server from logging this info. Check with the DBA, possibly they can "filter" out the application attempts to connect or change your work flow in the app.
If you have a Preview Button to view the report then simply add your Database log on info prompt there if Connectioninfo.Trusted is not true:
mainSecureDB = rpt.Database.Tables[tableIndex].LogOnInfo.ConnectionInfo.IntegratedSecurity;
if mainSecureDB = false then prompt the user for log on info and set accordingly, if it is true the it should not fail when it connects.
This is simply a matter of changing your App work flow...
Thanks
Don

Merge Replication from 2012 SQL Server publisher/distributor to 2014 SQL Express subscriber

Hi, I'm having a question about which version to use when running SQL Merge Replication.
In my test enviroment I have a SQL 2012 server running as Publisher and Distributor for my Merge Replication. I have now set up a test client running Win7 with SQL 2014 Express as a subscriber. The subscription initializes and runs perfectly.
But according to the SQL documentation this should not be possible as it states that the subscriber should have a version number equal or lower than the publisher. My subscription client was set ut using SQL-scripting, if I try using the wizard it will just
cause an error message telling that this is not possible since the client has a newer version number. I still not encountered any problems after I set it up using the script with the sp_addmergepullsubscription and sp_addmergepullsubscription_agent procedures.
The roll-out of my solution will start in a few weeks and I now have to decide whether to use 2014 Express or 2012 Express on the clients. Using 2014 Express will save me for a lot of upgades in a year or two. The 2012 SQL Server running as publisher/distributor
will be upgraded to/replaced with a 2014 Server in some few months.
I'm looking for good advices and recommendations for what to choose on the clients, 2012 Express or 2014 Express. Are the any known problems with using 2014 Express as a subscriber to a publisher/distributor running 2012 SQL Server?
All responses are welcome!
Regards, Anders

Hi,
As you understand that a Subscriber to a merge publication can be any version less than or equal to the Publisher version. When you set up a subscription from a publisher to a subscriber using SQL Server Management Studio, you will get error
“The selected Subscriber does not satisfy the minimum version compatibility level of the selected publication.” And you can use T-SQL script to get around this error message.
I would install SQL Server 2012 Express on the clients. Here is the reasons:
1. If you upgrade the publisher to SQL Server 2014, it is still working with SQL Server 2012 on the subscriber.
2. I cannot tell whether there are other potential problems if I choose the later one besides the error message.
Reference:
http://msdn.microsoft.com/en-us/library/ms143699(v=sql.120).aspx
Thanks.
Tracy Cai
TechNet Community Support

SQL Server Express 2014 problem new trigger

Hello
I had use MS SQL Express 2012 Sql Server Management Studio.
After I installed MS SQL Express 2014 SSManagement Studio for 64-bit with ms sql server 2014.
But when use database in SSMS Express 2014 I can not use New Trigger button(it is gray) for sql server 2014( and also for 2008R2, 2012). But I can create with query, and with SSMS 2008 R2 Express or SSMS 2012 Express.
I don't understood this problem. But when install SSMS Express 2014, I test install SQLManagementStudio_x64_ENU, and SQLEXPRADV_x64_ENU - The SSMS can created, but New Trigger button is gray and not enable
Thanks helps
Steve

maybe you can check below url.
https://connect.microsoft.com/SQLServer/feedback/details/873249/ssms-2014-new-trigger-is-disabled-for-older-2012-2008r2-versions-of-sql-server
以上說明若有錯誤請指教，謝謝。
| 台灣 SQL PASS 社群 |
SQL PASS Taiwan
|
歡迎參觀我的BLOG - 積沙成塔

Creation of System Stored Procedure in SQL Server 2012 & SQL Server 2012 R2.

Hi all,
I am stuck at a point I am looking for a system stored procedure named 'sp_dboption' in SQL Server 2012 & R2 but could not find.
Searched for it on the net and found that, this stored procedure 'sp_dboption' is now obsolete. So I tried to copy the content of 'sp_dboption' stored procedure from SQL Server 2008 R2 and create new system stored procedure with this name 'sp_dboption' in
SQL Server 2012 but was unable to create the system stored procedure.
Can you guys please tell me how to create system stored procedure in SQL Server 2012 & SQL Server 2012 R2. The reason of why I want to achieve this is because I have used 'sp_dboption' system stored procedure in my application to create a database.
As 'sp_dbotion' stored procedure is present in SQL Server 2008 R2 I am able to create the database in SQL server 2008 R2 but not in SQL server 2012.
Can you please guide me how to create system stored procedure. I am out of luck.
Please assist me, thanks & looking for help at the earliest. Hope someone will come to the fore and help me.

Hi Vishwajeet,
If you tried to create any object in the sys schema, you will get the error below.
The specified schema name "sys" either does not exist or you do not have permission to use it.
So I am afraid creating any object in sys schema is not supported by SQL Server. Here is a similar link for your reference.
How to create table in SYS schema in SQL Server?
Though sp_dboption is not in SQL Server 2012, does creating a user-defined one with the same content in 2008 make any difference in your business? You just need to specify the fully qualified name dbname.dbo.sp_dboption.
If you are still interested in creating a system sp_dboption, you can register it with the
sp_ms_marksystemobject.
See
Creating Your Own SQL Server System Stored Procedures.
Eric Zhang
TechNet Community Support

Difference between SQL SERVER 2008 & SQL SERVER 2012 & SQL SERVER 2014

Difference between SQL SERVER 2008 & SQL SERVER 2012 & SQL SERVER 2014 ?

What sort of databases do you have OLTP? Data warehouse? What requirements do you have for High Availability?
The main features for SQL 2012/2014, as I see it:
o Support for window functions, which makes it possible to write fast queries for running totals, sliding windows etc.
o Columnstore indexes, which can speed up your data warehouse enormously. But of no interest for OLTP. Only writable in SQL 2014.
o AlwaysOn and Availability Groups, a vastly improve story for high availability and disaster recovery.
o try_convert/try_cast, you can now easily filter out values from a column which does not convert to a number. A small but essential feature.
o In memory-OLTP, a new in-memory engine in SQL 2014. This far with very limited feature set, and quite specialised.
Of the points above, the second and third require Enterprise Edition, the first and fourth are in all editions. For the last, I don't think Microsoft has announced anything yet.
There are also new stuff in the BI area, but that's out of my league.
And, oh, there is a new licensing model - which I think is holding more than one customer back.
Erland Sommarskog, SQL Server MVP, [email protected]

Can 2008 reporting services read data from 2012 sql server

Will 2008 SSRS be able to retrieve data / speak
to 2012 SQL Server database?

I will try and see if it throws error. Check below similar thread.
https://social.technet.microsoft.com/Forums/en-US/067406f5-bd65-40eb-b333-3449adeefade/connect-to-sql-server-2012-databases-from-ssrs-2008-r2?forum=sqlreportingservices
Regards,
Vishal Patel
Blog: http://vspatel.co.uk
Site: http://lehrity.com

Possible to view MS SQL Server Log in SAP GUI?

Hi,
I am wondering if I can view the SQL Server log in SAP GUI using a transaction code.
I don't readily see how to do this with the TEs. It would be helpful to see things like: who has tried to log into the SQL Server via a Database Management tool : agnostic to SAP.: is SQL Server Management Studio or DBArtisan or other services.
thanks
Chris

Hi chris
Yes,you can view the Sql server log in transaction code ST04 & DBA Cockpit in SAPGUI.
Kindly refer the SAP notes.
139945 - SAP Database Monitor for MS SQL Server
1027512 - MSSQL: DBA cockpit for basis release 7.00 and later
Regards
Ram

SQL Server Logs

Hi,
I am getting an errors in SQL Server Logs.
Its eating up all my space from C: Drive.
now it says 0 bytes left.
What could be an issue???
Please help. its urgent.
Regards, Kunjay Shah

Hello,
Meanwhile you can limit the error log size with the following instruction:
USE
[master];
GO
EXEC
xp_instance_regwrite
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\MSSQLServer\MSSQLServer',
N'ErrorLogSizeInKb',
REG_DWORD, 5120;
GO
For more information, please read the following article:
http://support.microsoft.com/kb/2199578/en-us
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

How to Open Or read SQL Server log file .ldf

Hi all,
How to Open Or read SQL Server log file .ldf
When ever we create database from sql server, it's create two file. (1) .mdf (2) .ldf.
I want to see what's available inside the .ldf file.
Thanks,
Ashok

I am not too sure but may be the below two undocumented commands might yield the desired result.
DBCC Log
Fn_dblog function
Refer these links for more info,
http://www.mssqlcity.com/Articles/Undoc/SQL2000UndocDBCC.htm
http://blogs.sqlserver.org.au/blogs/greg_linwood/archive/2004/11/27/37.aspx
http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1173464,00.html
Some 3rd party tools like Log Explorer can do the job for you.
http://www.lumigent.com/products/le_sql.html
- Deepak

SQL Server Log: Login failed for user ''

We've found in SQL Server Log many records:
Date
3/22/2013 11:13:03 AM
Log
Windows NT (Application)
Source
MSSQLSERVER
Category
Logon
Event
3221243928
Computer
SBO05
Message
Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: <local machine>]
The server autentification is set to "SQL Server and Windows Autentification mode". But when we open SAP, before entering login/password, we see this message in log. But we still could work in SAP.
How could we solve this?
Kind regards,
Anna Shevchenko

Hi Joseph,
It doesn't help. The same things i've already done.
But when I change Mixed Autentification to Windows, i see another error:
Date
3/22/2013 11:04:26 AM
Log
SQL Server (Current - 3/22/2013 12:33:00 PM)
Source
Logon
Message
Login failed for user 'sa'. Reason: Failed to open the explicitly specified database. [CLIENT: 192.168.0.145]
Do you know why?
Kind regards,
Anna Shevchenko

2012 SQL server log shipping problem

Similar Messages

Maybe you are looking for