Blocking on SQL server

From last few days we are seeing blocking on SQL SERVER where select is taking exclusive lock and blocking the Update statement. Even Read committed snapshot Isolation is enabled.
SQL SERVER 2012 SP2
Windows server 2012.
Lock pages in Memory has been enabled
Please let me know any one can help us :)

1) There's not really any such thing as a "blocking SQL Statement". A query is blocked by a session because that other session holds incompatible locks. Those incompatible locks may have been acquired by a previous query in the blocking
session's transaction. So the SELECT you see in the report may not be responsible for the blocking the UPDATE.
2) In RCSI only READ COMMITTED and SNAPSHOT isolation levels use the row versioning, lock-free reading. If you start a transaction an select a different isolation level you will acquire S locks to read data. For instance .NET apps using
TransactionScope, or COM+ apps using transactions can unintentionally start a SERIALIZABLE transaction. Effectively opting-out of RCSI. see eg
using new TransactionScope() Considered Harmful
David
David http://blogs.msdn.com/b/dbrowne/

Similar Messages

Sql server 2014 set password for backup file

We are using sql server 2014, all our databases will be automatically backed up as per schedule. Now need to protect our
backed up databases with password. We have tried below queries:
BACKUP DATABASE teknomectest TO DISK='C:\test.BAK' WITH MEDIAPASSWORD='sqlpas'
Executing it shows below error
One or more of the options (mediapassword) are not supported for this statement.
Analyzing which we came to know this feature is blocked in sql server 2012 itself. Is there any other way to protect bak file.
Bala
Bala

MayurPaghal, Bala said he is using SQL server 2014
Beginning with SQL Server 2012, the PASSWORD and MEDIAPASSWORD options
are discontinued for creating backups. It is still possible to restore backups created with passwords.
https://msdn.microsoft.com/en-us/library/ms186865.aspx

Named Pipes Provider: Could not open a connection to SQL Server [2]

Hi
I'm a complete sql/asp.net newbie and want to try this tutorial:
http://beta.asp.net/GuidedTour/
First I installed:
Visual Web Developer 2005 Express Edition Beta 2
systemsettings\software shows the "sql server 2005 express edition ctp (sqlexpress)" installed
mmc\service shows me the SQL Server (SQLExpress) is running
Following the guided tour I use the commandline, type cmd, and type in the commandbox:
"C:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLCMD90" -S "localhost\SqlExpress"
Instead of localhost I also tried computername.smallbusiness.local (thats my fully domain name).
However I always receive the error:
Named Pipes Provider: Could not open a connection to SQL Server [2]
Thank you very much for all your help

Typically I have found problems with connection strings as one of a few things:
1. Your instance is named different than the default. I labeled mine BrettSQLServer instead of the regular instance.
2. Your default storage of the your database has a user the system does not like and won't give it access.
3. You have ports blocked that SQL Server is trying to access.
1. Your instance should show up under 'SQL Server Configuration Manager'. Start>MS SQL Server 2008 > Configuration Tools> SQL Server Configuration Manager. You should see a left view panel where you can click 'SQL Server Services'. This
will show on the right all of your SQL services that are running. The most important one is SQL Server({Your SQL Server Name}). You will see column headers's displaying: "Name, State, Start Mode, Log on as, ProcessID" by default. If
you don't see a version of this you may have no installed SQL server properly and gotten SQL management studio but not the server. If you have the server and it's off or not running that is another problem. If your "LOG On AS" is a service account
is "NT ...." or something besides "Local System" that may be a problem. Without getting into the symantecs of protection suffice to say you log in with less than system, yes you are more secure but some built in functions for connections may not work.
2. Going off of rights of your 'Log On As' I WOULD USE 'System' NOT "NT Authority....". The reason is that you can access less things with 'NT Authority....' but yes you are more secure for that reason. If you are just trying to connect at home
to test non secure things I don't see the harm. If you are setting up a database for a multinational corporation than, Yes I would use a more secure account. If you need to change it while still in SQL Server Confi Manager: Right Click> SQL
Server(Your Version) > On 'Log On' tab > Choose drop down for 'Built-in Account' select 'Local System'. As extra steps make sure by some strange reason your database locales have this user by default(They should). MS likes to install database
as default to: C:\Program Files\Microsoft SQL Server\MSSQL10.{instanceName}\MSSQL. If you go to this location by going: right click>Properties>Security Tab .. and you fail to see your user that SQL server is defined as you may have lots of
issues.
3. Turn off Windows Firewall during SQL installation. If you are scared of being attacked during this down window, disconnect your NIC and reconnect later. I have not added a port manually in a while but it is simply easier to just
turn off your firewall during install. Having your TCP/IP connection from SQL Server blocked is kind of bad if you need to connect to it that way later.
Problems most commonly encountered with SQL Server by users I have seen and I myself encountered a lot with full blown SQL Server Enterprise as well as Express versions of SQL:
Connection string DO not work for BIDS, ADO.net, Linq, etc...
Once you follow steps above just go {ComputerName}\{SQL Server Instance} as your connection name. That mostly always works. As a preliminary test you should install SQL Management Studio first before doing connection strings for a basic test
that it can access your server. When you first boot it up and click 'New Database Engine Query' it will display Server Type: "Database Engine" and a blank field or autopopulated field for 'Servername'. The {ComputerName}\{SQL Server Instance} almost
always works. If it works and you can connect, you know that you have access, if you don't start there first before getting into connection strings through .NET languages. I suggest just adding an easy alias, my local SQL box is simply called
'Brett'. Go again back to SQL Server Configuration Manager. On the left side click 'SQL Native Client ...' > 'Aliases' > New > type in whatever you want. Go back to the left pane click on 'SQL Server Services' ensure the service
'SQL Server Browser' is running and set to run automatic. Have fun accessing SQL Server with your alias.
Help I can't get FileStream to work and I ran 'spconfigure' in SQL and it still doesn't work.
Kind of annoying that more sites don't list that it is entirely in the Configuration manager and has zilch to do with setting the option if the config has it off. I am not a master of the sp_configure TSQL access method but I know during installs turning
it on fails to REALLY turn it on. Once again go to SQL Config Manger > SQL Server Services > Right click your instance > Select FILESTREAM tab > enable both check boxes. Restart SQL Server. Install Adventureworks 2008 and whatever
else failed due to filestream access levels.
Medium to Advanced on some things, but always wanting to know more

Troubles connecting SQL Server

I do following:
1. Create new web application.
2. Create package and add servlet.
3. Write following code into servlet method
protected void processRequest(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
response.setContentType("text/html;charset=UTF-8");
PrintWriter out = response.getWriter();
String url = "jdbc:sun:sqlserver://WSSMN3839:1433";
String user = "????";
String pass = "????";
String res = "";
try {
Connection conn = DriverManager.getConnection(url, user, pass);
} catch (SQLException ex) {
res = "fail";
/* TODO output your page here */
Program goes to catch block although SQL Server driver installed and I can access DB through Runtime panel.
System.getProperty("jdbc.drivers") returns null too.

Check the permissions and server authentication from the below link,
http://technet.microsoft.com/en-us/library/ms179354(v=sql.90).aspx
Regards, RSingh

SQL Server not releasing memory

Hello,
I have created one stored procedure, which inserts data into 1 table.
It inserts around 1 million records at a time using XML input.
Problem is with SQL server memory I think. When I run this stored procedure and check the performance in the morning when server is not so busy, it finishes with less than 10 seconds.\
However, if I continuously test this stored procedure multiple times, it gives huge variation in performance.
Also, I call this stored procedure from C# front and there I have made sure that I am disposing Connection object every time.
After few runs, I have to restart my server computer as it doesn't allow me to run any of the query on that server.
So my question is :
What is that which occupies whole server memory?
Is there any thing which I can write in stored procedure to release memory once it is done?
Please assist me on this.
Thank you,
Mittal.

Hello,
I have created one stored procedure, which inserts data into 1 table.
It inserts around 1 million records at a time using XML input.
Problem is with SQL server memory I think. When I run this stored procedure and check the performance in the morning when server is not so busy, it finishes with less than 10 seconds.\
However, if I continuously test this stored procedure multiple times, it gives huge variation in performance.
Also, I call this stored procedure from C# front and there I have made sure that I am disposing Connection object every time.
After few runs, I have to restart my server computer as it doesn't allow me to run any of the query on that server.
So my question is :
What is that which occupies whole server memory?
Is there any thing which I can write in stored procedure to release memory once it is done?
Please assist me on this.
Thank you,
Mittal.
>> 1. What is that which occupies whole server memory?
Probably your application or the other application, but this need to be checked and not guess! Your machine execute hundreds if not hundreds of thousands applications on the same time! most of them are services that you do not see any
GUI. The SQL Server itself might execute hundreds if not hundreds of thousands transactions and these might interfere one another (lock tables or rows, use the same resources and so on).
* as a first test you should try to execute the query using a more reliable application like the SSMS. I recommend to try execute the query throw the SSMS several times and check the behavior.
>> 2. Is there any thing which I can write in stored procedure to release memory once it is done?
There are several option to free memory that used by SQL Server, but do you really need it?!? This is probably not the solution for your case. in the best option it will only give you a workaround.
* SQL Server do not use more resources that you let it (configure it). If you are using SQL EXPRESS than you have some limitations regarding the resources (for example memory and CPU and database size...).
Make sure that you configure the SQL Server not to use to much resources, so that other applications like the operating system will have what they need! There is no logic in restart the machine if the only
problem is with specific application (unless you have problems like memory leak which in rare cases can not be treat otherwise)
http://mrbool.com/how-to-clean-up-memory-sql-server/29242
https://msdn.microsoft.com/en-us/library/ms178067.aspx?f=255&MSPPError=-2147217396
** start monitor the SQL Server resources, locks and waits
https://technet.microsoft.com/en-us/library/aa213039(v=sql.80).aspx
http://www.brentozar.com/sql/locking-and-blocking-in-sql-server/
*** Give us more information instead of stories :-)
Post codes that you use, post DDL+DML and so on.
Ronen Ariely
[Personal Site] [Blog] [Facebook]

MS SQL Server 2008 server is experiencing blocking

All,
The DBA & I are at a loss as to what could be causing an intermittent alert to be produced against the MS SQL Server 2008 server. The following email is what I've been provided:
SQL Services Alert: COMPANY.com - COMPSQL01 is experiencing blocking
spid BSPID DatabaseName    Login                          LastBatch        Runtime (Alert@:1) Command
394 0     ORAEPM_HP_HPBUD 102.16.4.126\ORAEPM_HP_HPBUD 2015-04-06 10:52                  5 (@P1 int)SELECT * FROM HSP_ACTIVITY_LEASE WHERE ACTIVITY_ID = @P1
404 0     ORAEPM_HP_VISIO 102.16.4.126\ORAEPM_HP_VISION 2015-04-06 10:50                  7 (@P1 int)SELECT * FROM HSP_ACTIVITY_LEASE WHERE ACTIVITY_ID = @P1
403 404   ORAEPM_HP_VISIO 102.16.4.126\ORAEPM_HP_VISION 2015-04-06 10:49                  8 (@P1 int)UPDATE HSP_ACTIVE_SERVERS SET LAST_ACTIVE_TIME = GETDATE() WHERE SERVER_ID = @P1
395 394   ORAEPM_HP_HPBUD 102.16.4.126\ORAEPM_HP_HPBUD 2015-04-06 10:49                  8 (@P1 int)UPDATE HSP_ACTIVE_SERVERS SET LAST_ACTIVE_TIME = GETDATE() WHERE SERVER_ID = @P1
From what I've been told, it appears that SPID 394 is the offending one but it appears to be clashing with SPID 404 and causing the blocking to occur. Both appear to be automatic processes executed by Planning to monitor\track the status of the various Planning applications in operation.
As background info, the following applies:
- All servers are MS Windows 2008 R2 Enterprise SP1 (64-bit);
- Hyperion Planning is v11.1.2.3.502;
- The RDBMS platform is a MS SQL Server 2008 (64-bit) instance;
- ORAEPM_HP_HPBUD is the RDBMS database accessed by a custom-developed Planning application while ORAEPM_HP_VISION is the RDBMS database for Oracle's Vision Planning application;
Has anyone ever encountered - and resolved - such an issue? If yes, how?
Many thanks in advance,
JBM

Can you pin point a particular TopLink query tied to the " FETCH_APICURSOR* " call in the app and post how it is being created?
My guess is that the application is specifying the TopLink query object to return a cursor or stream and not closing it in all cases, or keeping them open for a long period - did you say they were leaking, or is it just that a large number are open at a time leading to performance problems?
This streams+cursors are described in the TopLink docs here
http://docs.oracle.com/cd/E21764_01/web.1111/b32441/qryadv.htm#CJGJBHGJ
or the 10g docs here:
http://sqltech.cl/doc/oas10gR3/web.1013/b13593/qryadv010.htm
If this is the case, you might want to use a different strategy such as pagination instead of cursors, described here:
http://docs.oracle.com/cd/E17904_01/web.1111/b32441/optimiz.htm#CHDIBGFE
Best Regards,
Chris

SQL Server - How to make SELECT block with TRANSACTION_SERIALIZABLE

I'm in the process of switching an application to use SQL Server. Is there anyway of making a SELECT in SQL Server implement a lock (and therefore also get blocked) similar to an INSERT or UPDATE?
Essentially, I have code that tracks a transaction ID for a particular customer; given there can be concurrent access from the same customer, I am using TRANSACTION_SERIALIZABLE:
long id = 0L; // Customer ID stmt = Conn.prepareStatement("SELECT TxID FROM TxIDTable WHERE (ID = ?)"); stmt.setLong(1, id); result = stmt.executeQuery(); result.next(); int tx_id = result.getInt("TxID"); result.close(); stmt.close(); stmt = Conn.prepareStatement("UPDATE TxID SET TxID = ? WHERE (ID = ?)"); stmt.setInt(1, tx_id + 1); stmt.setLong(2, id); stmt.executeUpdate(); stmt.close(); Conn.commit();
This code is working, however on SQL Server I have to wrap a loop around it, and if I catch a deadlock exception, rerun the transaction. This is costly and I would much rather have the SELECT create a lock and therefore block any concurrent SELECTs. One workaround is to force a dummy UPDATE up front:
long id = 0L; // Customer ID stmt = Conn.prepareStatement("UPDATE TxIDTable SET ID = ? WHERE (ID = ?)"); stmt.setLong(1, id); // THIS UPDATE DOES NOT REALLY UPDATE ANYTHING stmt.setLong(2, id); // (NOTE SET AND WHERE CLAUSE ARE IDENTICAL) stmt.executeUpdate(); // HOWEVER, IT DOES EFFECTLY PREVENT DEADLOCK // BY CREATING A TABLE LOCK BEFORE THE SELECT stmt.close(); // stmt = Conn.prepareStatement("SELECT TxID FROM TxIDTable WHERE (ID = ?)"); stmt.setLong(1, id); result = stmt.executeQuery(); result.next(); int tx_id = result.getInt("TxID"); result.close(); stmt.close(); stmt = Conn.prepareStatement("UPDATE TxIDTable SET TxID = ? WHERE (ID = ?)"); stmt.setInt(1, tx_id + 1); stmt.setLong(2, id); stmt.executeUpdate(); stmt.close(); Conn.commit();
This seems really like a waste -- anyway to make the SELECT lock on SQL Server??
Thanks,
Kevin

You want a table hint (the equivalent of SELECT ... FOR UPDATE in other dialects):
[http://msdn2.microsoft.com/en-us/library/ms187373.aspx|http://msdn2.microsoft.com/en-us/library/ms187373.aspx]

"block change tracking" equivalent in sql server

Hi All,
If someone has expertise in both oracle and sql server, pls let me know if there is " block change tracking" equivalent in sql server. I know sql server has incremental/differential backup, curious to know whether it got this equivalent feature.
Regards,
Satheesh Shanmugam
http://borndba.com

May be the below link will help you:
http://www.databasejournal.com/features/mssql/article.php/3824196/Introducing-Change-Tracking-in-SQL-Server-2008.htm

Effective GUI for monitoring blocks, memory, cpu,io in SQL server

Hi,
Is there any GUI/ tool to monitor SQL server 2008 R2 memory, CPU, IO, blocks?

Hi,
Is there any GUI/ tool to monitor SQL server 2008 R2 memory, CPU, IO, blocks?
Simply run below query to see SQL Server memory utilization.
select
(physical_memory_in_use_kb/1024)Memory_usedby_Sqlserver_MB,
(locked_page_allocations_kb/1024 )Locked_pages_used_Sqlserver_MB,
(total_virtual_address_space_kb/1024 )Total_VAS_in_MB,
process_physical_memory_low,
process_virtual_memory_low
from sys. dm_os_process_memory
Schedule it through agent job and add database mail to send mail to you.
I use Quest spotlight it does no gives memory utilization but shows Buffer cache hit ratio.Which is important parameter to mark.SQL utilizes memory heavily so any tool can flash message like memory utilization high which actually is not correct.I have seen
it with many tools.
For others you can go for Quest tool.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

WRV200 Blocking Port 1433 (SQL Server)

Hello,
I am working on a client's network and am having a frustrating time trying to connect to a SQL server within the internal network.
I have SQL Server Express running on one machine and a second machine on the LAN that connects to that server for management functions.
I previously had a D-Link Router on this network and switched to the WRV200 VPN Router. With the D-Link, the connection was no problem. Once I put the WRV200 in, I can no longer connect.
I can ping all the machines on the network from all the others. All machines are running Vista business with the Windows Firewall enabled, with an exception set up to allow port 1433 through.
When I put the D-Link back into place, the connection is allowed, so I have eliminated everything but the WRV200.
After reading the knowledge base and several messages here, I set up Port Forwarding on the WRV200 to allow the connection, and route it to the machine running the SQL Server instance. That did not work.
I am assuming there is some little, tiny setting that is specific to this router that has to be just so, but I have not been able to figure it out.
I appreciate any and all help.
Stephanie Hapke
GeekGirl Consulting

Hi,
I am experiencing the same issue. I have set up a PPTP VPN on windows 2008 R2. It works perfectly well and once connected my my client machine can access to the remote network.
However, the SQL server is not detected. I suspect a firewall issue.
both public and domain profiles are active. Incoming requests firewall policies are active and allow dbclient.exe connection for all profiles both TCP and UDP (all ports). However, dbclient cannot connect via VPN (it can when executed on the LAN).
I would like to test your solution but I do not understand how you changed your RAS connection profile.
I tried gpedit.msc
command to do it as described in the "Server 2012: File Sharing with VPN / RAS" but I cannot even see my PPTP VPN connection in the list of connections.
Could you indicate a way to do make i have the proper profile set up of the VPN connection.
Many thanks

Having issues with getting SQL Server Express to start services and run.

Good afternoon everyone,
I have been working on a 2012 R2 server getting ready to move databases to new hardware. I had SQL Server Express 2008 R2 running on this server with no issues. I was handed another software package that ran SQL Express 2012 and had to for compatibility
reasons. I have had multiple versions run on Server 2012 before with no issues. This time, not so lucky. When the installer from the updated package put on SQL Express 2012 it completed with errors ( error log posted at the end of post) and
would not allow me to run software. I then tried the db that I had installed on 2008 R2 and it also gave the same error as the 2012 version. IN basic terms the required services attempted to start and shut back down again. I have received
Error 1068 about database handles and error %%945. I know this db has plenty of space and the permissions were added for the Admin account to access both db's. I then uninstalled both versions and tried again, with the same errors listed when
I tried to start the services. I am thinking that a clean install would fix the issue however I am not certain what files/folders/reg entries need to be deleted or modified. I have researched all the errors I can find, however I am very
new with SQL anything so I know I am missing something. I also do not have an "E:" drive on this server (not sure why it is going there). Input would be very welcome as I am not certain where to go from here.
Thanks,
Matt
Error Log follows, server and domain names have been blacked out with ****.
2015-04-15 11:57:55.16 Server Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64)
Dec 28 2012 20:23:12
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
2015-04-15 11:57:55.16 Server (c) Microsoft Corporation.
2015-04-15 11:57:55.16 Server All rights reserved.
2015-04-15 11:57:55.16 Server Server process ID is 4104.
2015-04-15 11:57:55.16 Server System Manufacturer: 'HP', System Model: 'ProLiant ML350p Gen8'.
2015-04-15 11:57:55.16 Server Authentication mode is WINDOWS-ONLY.
2015-04-15 11:57:55.16 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2015-04-15 11:57:55.17 Server The service account is 'NT AUTHORITY\LOCAL SERVICE'. This is an informational message; no user action is required.
2015-04-15 11:57:55.17 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2015-04-15 11:57:55.17 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2015-04-15 11:57:55.48 Server SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-04-15 11:57:55.48 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-04-15 11:57:55.48 Server Detected 8157 MB of RAM. This is an informational message; no user action is required.
2015-04-15 11:57:55.48 Server Using conventional memory in the memory manager.
2015-04-15 11:57:55.68 Server This instance of SQL Server last reported using a process ID of 7840 at 4/15/2015 11:57:47 AM (local) 4/15/2015 3:57:47 PM (UTC). This is an informational message only; no user action is required.
2015-04-15 11:57:55.68 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2015-04-15 11:57:55.69 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2015-04-15 11:57:55.72 Server Software Usage Metrics is disabled.
2015-04-15 11:57:55.73 spid5s Starting up database 'master'.
2015-04-15 11:57:55.79 spid5s 20 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-04-15 11:57:55.79 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-04-15 11:57:55.80 Server CLR version v4.0.30319 loaded.
2015-04-15 11:57:55.86 spid5s Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
2015-04-15 11:57:55.89 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-04-15 11:57:55.91 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-04-15 11:57:55.91 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-04-15 11:57:55.94 spid5s SQL Trace ID 1 was started by login "sa".
2015-04-15 11:57:55.94 spid5s Server name is '********\SQLEXPRESS'. This is an informational message only. No user action is required.
2015-04-15 11:57:55.96 spid5s Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Binn\ftimport.dll'.
2015-04-15 11:57:55.96 spid5s Starting up database 'msdb'.
2015-04-15 11:57:55.96 spid9s Starting up database 'mssqlsystemresource'.
2015-04-15 11:57:55.96 spid5s Error: 17204, Severity: 16, State: 1.
2015-04-15 11:57:55.96 spid5s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2015-04-15 11:57:55.96 spid5s Error: 5120, Severity: 16, State: 101.
2015-04-15 11:57:55.96 spid5s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2015-04-15 11:57:55.96 spid5s Error: 17207, Severity: 16, State: 1.
2015-04-15 11:57:55.96 spid5s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2015-04-15 11:57:55.96 spid5s File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.
2015-04-15 11:57:55.99 spid9s The resource database build version is 11.00.3000. This is an informational message only. No user action is required.
2015-04-15 11:57:56.02 spid12s A self-generated certificate was successfully loaded for encryption.
2015-04-15 11:57:56.03 spid12s Server is listening on [ 'any' <ipv6> 53345].
2015-04-15 11:57:56.03 spid12s Server is listening on [ 'any' <ipv4> 53345].
2015-04-15 11:57:56.03 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2015-04-15 11:57:56.03 spid12s Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2015-04-15 11:57:56.04 spid12s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806.
This is an informational message only. No user action is required.
2015-04-15 11:57:56.04 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational
message. No user action is required.
2015-04-15 11:57:56.04 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/********.****.local:SQLEXPRESS ] for the SQL Server service. Windows return code: 0xffffffff, state: 53.
Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been
manually registered.
2015-04-15 11:57:56.04 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/********.****.local:53345 ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. Failure
to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually
registered.
2015-04-15 11:57:56.09 spid9s Starting up database 'model'.
2015-04-15 11:57:56.10 spid9s Error: 17204, Severity: 16, State: 1.
2015-04-15 11:57:56.10 spid9s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2015-04-15 11:57:56.10 spid9s Error: 5120, Severity: 16, State: 101.
2015-04-15 11:57:56.10 spid9s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2015-04-15 11:57:56.10 spid9s Error: 17207, Severity: 16, State: 1.
2015-04-15 11:57:56.10 spid9s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2015-04-15 11:57:56.10 spid9s File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2015-04-15 11:57:56.10 spid9s Error: 945, Severity: 14, State: 2.
2015-04-15 11:57:56.10 spid9s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2015-04-15 11:57:56.10 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Hi HMLunger,
Did you install the SQL Server instance successfully? If not, please help to post the summary and detail logs for analysis. By default, the logs can be found in: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log.
However, if you fail to start SQL Server Express service after successfully installing SQL Server,
you might have to change the paths of the files by running the following scripts from the command prompt. For more details, please review this similar
thread.
NET START MSSQL$SQLEXPRESS /f /T3608
SQLCMD -S .\SQLEXPRESS
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
go
exit;
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
NET STOP MSSQL$SQLEXPRESS
In addition, you can follow the steps in this KB article to uninstall SQL Server.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Unable to Access SQL Server 2005 Remotedly

Not sure if this is the right forum to post this...
After going through lot of old posts in various forums and changing lot of settings, i'm still not able to access my Server remotely.
This is Windows 2003 Server machine with Sonicwall Firewall, i have allowed Port 1433 in both Firewall and ISA and call is getting through but i'm getting following error msg :-
{"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"}
This machine is also having Sql Server 2000, and the SQL Server 2005 is installed with named instance.
My connection string is :-
"Data Source=192.168.0.1\MYSERVER;Initial Catalog=MyDatabase;Integrated Security=True"
In example above, i'm showing dummy values but actual string is having the actual live IP address and correct named instance and database.
If i use a local address like 192.168.0.1 then i'm able to connect.
My TCP/IP Address in Sql configuration is having my Live IP Address and the port 1433.
Any help will be highly appreciable..

i'm still checking on this. i have changed the port now to 1434 and changed in all places.
my connection string is also changed now, so now i'm using :- MYIP\MYSERVER,1434
now i'm getting a different error msg
{"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)"}
this can also be due to firewall or something else is blocking it, i will rechk n post back final answer.

Unable to install SQL Server 2012 Standard: Error code 0x851A0019

Hi All,
I am trying to install sql server 2012 standard edition on windows server 2008R2 but at the end of the installation it is giving me the following error message:
"The following error has occurred:
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes."
And in the log file I got the following error message:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
(I have posted part of the log file)
Need your help to resolve this issue.
Thanks,
MKNayeem

Hi,
Thanks for your reply.
I have already followed that article. I have changed the user to local account user, but it did not work.
Like you said the sql server is installed, but it is not starting the services. Following is the error log file message:
2015-03-16 10:12:15.27 Server Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
2015-03-16 10:12:15.27 Server (c) Microsoft Corporation.
2015-03-16 10:12:15.27 Server All rights reserved.
2015-03-16 10:12:15.29 Server Server process ID is 5724.
2015-03-16 10:12:15.29 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2015-03-16 10:12:15.29 Server Authentication mode is MIXED.
2015-03-16 10:12:15.29 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\Log\ERRORLOG'.
2015-03-16 10:12:15.29 Server The service account is 'NT Service\MSSQL$BNG1SECISO'. This is an informational message; no user action is required.
2015-03-16 10:12:15.29 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\DATA\mastlog.ldf
2015-03-16 10:12:15.29 Server Command Line Startup Parameters:
-s "BNG1SECISO"
2015-03-16 10:12:15.57 Server SQL Server detected 2 sockets with 1 cores per socket and 1 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-03-16 10:12:15.57 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-03-16 10:12:15.57 Server Detected 16383 MB of RAM. This is an informational message; no user action is required.
2015-03-16 10:12:15.57 Server Using conventional memory in the memory manager.
2015-03-16 10:12:15.67 Server This instance of SQL Server last reported using a process ID of 2452 at 16-03-2015 07:03:13 (local) 16-03-2015 01:33:13 (UTC). This is an informational message only; no user action is required.
2015-03-16 10:12:15.67 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2015-03-16 10:12:15.69 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2015-03-16 10:12:15.69 Server Software Usage Metrics is disabled.
2015-03-16 10:12:15.70 spid6s Starting up database 'master'.
2015-03-16 10:12:15.78 Server CLR version v4.0.30319 loaded.
2015-03-16 10:12:15.82 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-03-16 10:12:17.36 spid6s Error: 824, Severity: 24, State: 2.
2015-03-16 10:12:17.36 spid6s SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:377; actual 261:2228225). It occurred during a read of page (1:377) in database ID 1 at offset 0x000000002f2000 in
file 'C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\DATA\master.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and
must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Thanks
MKNayeem

Inserting data to a . SDF database (SQL Server Compact Edition connection)

Hi, all.
I'm working on a project that worked fine while connecting to SQL Server 2008. I used a connection string like this:
Driver={SQL Server Native Client 10.0};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
Now, I've replaced all database connections in my project to work with SQL Server Compact Edition, and my connection string is something like this:
Provider=Microsoft.SQLSERVER.CE.OLEDB.3.5;Data Source=myDir\myDataBase.sdf;
After changing the type of connection, I'm getting an error on "DB Tools Insert Data.vi". This is what I get:
Error -2147217872 occurred at NI_Database_API.lvlib:Cmd Execute.vi->NI_Database_API.lvlib: DB Tools Insert Data.vi->Main.vi
Possible reason(s):ADO Error: 0x80040E30 Exception occured in Microsoft SQL Server Compact OLE DB Provider: The given type name was unrecognized. [,,,,,] in NI_Database_API.lvlib:Rec Create - Command.vi->NI_Database_API.lvlib:Cmd Execute.vi->NI_Database_API.lvlib: DB Tools Insert Data.vi->Main.vi
This is a simplified block diagram (as I said, it worked perfectly while using SQL Server 2008 connection):
Could you please help me?
Thanks in advance,
Francisco

Hi, Steve. Thanks for your answers.
I worked around this problem by using directly a SQL query instead of this function (you were right, using DBTools Execute Query VI). But now I'm getting problems with other functions, when inserting data into the DB including NULL values.
I make a SQL query like this using DBTools Execute Query VI:
INSERT INTO Table1 (Column1, Column2, Column3, Column4, Column5, Column6) VALUES ('Value1', 'Value2', 'Value3', 'NULL', 'Value5', 'Value6')
and get the following error:
ADO Error: 0x80040E07Exception occured in Microsoft SQL Server Compact OLE DB Provider: A literal value in the command could not be converted to the correct type due to a reason other than data overflow. [,,,,,] in NI_Database_API.lvlib:Conn Execute.vi->INSERT (new) restricción (DBCT).vi->Restricciones a Base de Datos (DBCT).vi->Definir - editar restricciones.vi->Main.vi
The same SQL query worked perfectly when using the SQL Server 2008 connection, so it's not a database structure issue.
Could somebody please help me?
Regards,
Francisco

Rule "SQL Server 2012 feature Upgrade" Failed

I am doing an in-place upgrade of SQL Server 2008 R2 SP2 > SQL Server 2012 SP1, both 64-bit, installed on Windows Server 2008 R2.
I ran the SQL Server Upgrade Advisor tool prior to upgrade which reported no issues.
The error I am getting is:
In the detailed.txt log I can see the following:
(11) 2013-12-29 12:28:10 Slp: Initializing rule      : SQL Server 2012 Feature Upgrade
(11) 2013-12-29 12:28:10 Slp: Rule is will be executed : True
(11) 2013-12-29 12:28:10 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.SkuUpgradeRule
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_as_Cpu64'.
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Found feature package 'sql_as_ctp6_Cpu64' with SkuValue=ENTERPRISE (Enterprise) ProductVersion=10.52.4000.0
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 10.0 and edition ENTERPRISE for feature package 'sql_as_Cpu64'.
(11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=10.0 sourceEdition=ENTERPRISE (Enterprise) sourceArchitecture=X64 targetEdition=STANDARD (Standard) targetArchitecture=X64
(11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
(11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix did not find a match in sku matrix .
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_as_Cpu64' is blocking upgrade.
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' detection result: IsValidFeatureUpgrade=False
(11) 2013-12-29 12:28:10 Slp: Evaluating rule        : FeatureUpgradeMatrixCheck
(11) 2013-12-29 12:28:10 Slp: Rule running on machine: TAUPE-SERVER
(11) 2013-12-29 12:28:10 Slp: Rule evaluation done   : Failed
(11) 2013-12-29 12:28:10 Slp: Rule evaluation message: The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2012 version and edition upgrade in Books Online.
(11) 2013-12-29 12:28:10 Slp: Send result to channel : RulesEngineNotificationChannel
Prior to upgrade:
From Summary.txt file:
Overall summary:
Final result:                  Passed
Exit code (Decimal):           0
Start time:                    2013-12-29 12:04:28
End time:                      2013-12-29 12:08:02
Requested action:              RunRules
Machine Properties:
Machine name:                  TAUPE-SERVER
Machine processor count:       1
OS version:                    Windows Server 2008 R2
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services
1033                 Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text and Semantic Extractions for Search 1033
Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2   MSSQLSERVER          MSAS10_50.MSSQLSERVER          Analysis Services
1033                 Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2   MSSQLSERVER          MSRS10_50.MSSQLSERVER          Reporting Services - Native
1033                 Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2
Management Tools - Basic                 1033                 Enterprise Edition   10.52.4000.0
No
SQL Server 2008 R2
Management Tools - Complete              1033                 Enterprise Edition   10.52.4000.0
No
SQL Server 2008 R2
Client Tools Connectivity                1033                 Enterprise Edition   10.52.4000.0
No
Package properties:
Description:                   Microsoft SQL Server 2012
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
Installation location:
\\dovekie\drop\TFS2013\SQLServer2012SP1\x64\setup\
Installation edition:          Standard
Slipstream:                    True
User Input Settings:
ACTION:                        RunRules
CONFIGURATIONFILE:
ENU:                           true
FEATURES:
HELP:                          false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS:              false
INSTANCENAME:                  <empty>
PID:                           *****
QUIET:                         false
QUIETSIMPLE:                   false
RULES:                         GlobalRules
UIMODE:                        Normal
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131229_120425\ConfigurationFile.ini
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131229_120425\SystemConfigurationCheck_Report.htm
As far as I'm aware, the upgrade path I am following is a supported one, any suggestions will be much appreciated!
Thank you.

Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services
1033                 Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text and Semantic Extractions for Search 1033
Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2   MSSQLSERVER          MSAS10_50.MSSQLSERVER          Analysis Services
1033                 Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2   MSSQLSERVER          MSRS10_50.MSSQLSERVER          Reporting Services - Native
1033                 Enterprise Edition   10.52.4000.0    No
SQL Server 2008 R2
Management Tools - Basic                 1033                 Enterprise Edition   10.52.4000.0
No
SQL Server 2008 R2
Management Tools - Complete              1033                 Enterprise Edition   10.52.4000.0
No
SQL Server 2008 R2
Client Tools Connectivity                1033                 Enterprise Edition   10.52.4000.0
No
Package properties:
Description:                   Microsoft SQL Server 2012
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
Installation location:
\\dovekie\drop\TFS2013\SQLServer2012SP1\x64\setup\
Installation edition:          Standard
Slipstream:                    True
User Input
Hello ,
You are trying to upgrade to SQL 2012 standard edition which is not supported .you can only upgrade from SQL server 2008 R2 Sp2 Enterprise edition to SQL 2012 Enterprise or business intellgience. see below link for supported upgrade paths
http://technet.microsoft.com/en-us/library/ms143393.aspx
If you want to move ahead you should try Side by side approach.Create new SQL server 2012 box and restore backup.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Blocking on SQL server

Similar Messages

Maybe you are looking for