SQL Server runs update on one record, returns -1 records updated to java

I am trying to troubleshoot an issue in SQL Server. For all the databases in a specific server, the return value for java initiated update statements have completed the update (ie. I can go into SQL Server and verify the values have changed), but returned
a value of -1 records updated. I am not sure what went wrong to cause this to fail. It works on one server, but not on any databases on the other server and it suddenly changed on Friday, April 10. Here is the results of the java I am running.
Driver vendor: Microsoft JDBC Driver 4.0 for SQL Server
DriverVersion: 4.0.4621.201
dbproduct: Microsoft SQL Server
JavaPlus Connection Made: no warnings
Executing :update maxsequence set maxreserved = 401 where sequencename ='SERVERSESSIONSEQ' and maxreserved=400
Using TYPE_SCROLL_INSENSITIVE
Execute Returned -- (boolean) --- false
Execute getUpdateCount -- (num) -1
Execute took :0(15) secs.
Update/Deleted :-1 records.
Fetching/Updating took :0(0) secs.
I am runnning SQL Server 2012 and Windows 2012R2
Microsoft SQL Server Management Studio 11.0.2100.60
Microsoft Analysis Services Client Tools
11.0.2100.60
Microsoft Data Access Components (MDAC) 6.3.9600.16384
Microsoft MSXML 3.0 4.0 6.0
Microsoft Internet Explorer 9.11.9600.16518
Microsoft .NET Framework 4.0.30319.34011
Operating System 6.3.9600

Can you clarify why your Java output saying Execute Returned -- (boolean) --- false
I suspect this update never happened and it is possible to get updated row counts such as by using stored
procedure and returning @@ROWCOUNT value through return statement to the data set
Would you like to try this?
Good Luck! Please Mark This As Answer if it solved your issue. Please Vote This As Helpful if it helps to solve your issue

Similar Messages

The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.

One of my replication job failed with below error, which means job failed because of permission issue on the folder. To resolve that, I have granted the permission and it started working fine. Now the question is as my job was running fine since long time
without any issue then how suddenly the permission of the folder got omitted automatically? I am sure that no one deleted the permission from the folder and as the server is part of SQL cluster no failover occurs.
Error:-The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.
Rahul

Hi Rahul,
Error code 5 indicates that the error is "access is denied." Please make sure that the COM folder is excluded from any antivirus scan that occurs on the system.
If the issue still persists, I recommend you use
Process Monitor to find out a bit more about the accounts and access requests involved. Then grant write permission to the exact COM folder for the account that is running the SQL Server Agent service. For more details, please review the following similar
thread.
http://www.sqlservercentral.com/Forums/Topic1364832-1550-1.aspx
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.

EKM using the Azure Key Vault is now available for SQL Database and SQL Server running in Azure VM's

In preview today, you can create keys in the Azure Key Vault, and use them with Azure SQL Database, or SQL Server running in a Azure VM. Use the Extensible Key Management (EKM) for TDE, backup encryption, or cell level encryption. For more information, see
Extensible Key Management Using Azure Key Vault (SQL Server)
http://msdn.microsoft.com/en-us/library/dn198405.aspx.
The announcement:
Azure Key Vault in public preview
Key Vault offers an easy, cost-effective way to safeguard keys and other sensitive data used by cloud applications and services. Included are the following features:
Enhance data protection and compliance:
Protect cryptographic keys and sensitive data like passwords with keys stored in Hardware Security Modules (HSMs). For added assurance, import or generate your keys in HSMs certified to FIPS 140-2 level 2 and Common Criteria EAL4 standards,
so that keys stay within the HSM boundary. Key Vault is designed so that Microsoft doesn’t see or extract your keys.
All the control, none of the work:
Provision new vaults and keys in minutes and centrally manage keys, sensitive data, and policies. You maintain control over your encrypted data—simply grant permission for your own and third-party applications to use keys as needed. Enable
developers to easily manage keys used for dev/test and migrate seamlessly to production keys managed by security operations.
Boost performance and achieve global scale: Improve
performance and reduce latency of cloud applications by storing cryptographic keys in the cloud (versus on-premises). Key Vault rapidly scales to meet the cryptographic needs of your cloud applications and match peak demand.
Get started with Azure Key Vault by creating keys for applications you develop,
SQL Server encryption (TDE, CLE, and Backup), and partner solutions like
CloudLink SecureVM.
Key Vault is available now at no charge with discounted preview pricing starting on January 15, 2015.
For more information, please visit the
Key Vault webpage. For a comprehensive look at pricing, please visit the
Key Vault Pricing webpage.
Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

Thank you for sharing this Rick.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server 2008 R2 Replication - not applying snapshot and not updating all repliacted columns

We are using transactional replicating on SQL Server 2008 R2 (SP1) using a remote distributor. We are replicating from BaanLN, which is an ERP application to up to 5 subscribers, all using push publications.
Tables can range from a couple million rows to 12 million rows and 100's of GBs in size.
And it's due to the size of the tables that it was designed with a one publisher to one table architecture.
Until recently it has been working very smooth (last four years)) but we have come across two issues I have never encountered.
While this has happen a half dozen times before, it last occurred a couple weeks ago when I was adding three new publications, again a one table per publication architecture.
We use standard SS repl proc calls to create the publications, which have been successful for years.
On this occasion replication created the three publications, assigned the subscribers and even generated the new snapshot for all three new publications.
However, while it appeared that replication had created all the publications correctly from end to end, it actually only applied one of the three snapshot and created the new table on both of the new subscribers (two on each of the
publications). It only applied the snapshot to one of the two subscribers for the second publications, and did not apply to any on the third.
I let it run for three hours to see if it was a back log issue.
Replication was showing commands coming across when looking at the sync verification at the publisher and
it would even successfully pass a tracer token through each of the three new publications, despite there not being tables on either subscriber on one of the publishers and missing on one of the subscribers on another.
I ended up attempting to reinitialize roughly a dozen times, spanning a day, and one of the two remaining publications was correctly reinitialized and the snapshot applied, but the second of the two (failed) again had the same mysterious result, and
again looked like it was successful based on all the monitoring.
So I kept reinitializing the last and after multiple attempts spanning a day, it too finally was built correctly.
Now the story only get a little stranger. We just found out yesterday that on Friday the 17th
at 7:45, the approximate time started the aforementioned deployment of the three new publications,
we also had three transaction from a stable and vetted publication send over all changes except for a single status column.
This publication has 12 million rows and is very active, with thousands of changes daily.
, The three rows did not replicate a status change from a 5 to a 6.
We verified that the status was in fact 6 on the publisher, and
5 on both subscribers, yet no messages or errors. All the other rows successfully updated.
We fixed it by updating the publication from 6 back to 5 then back to 6 again on those specific rows and it worked.
The CPU is low and overall latency is minimal on the distributor.
From all accounts the replication is stable and smooth, but very busy.
The issues above have only recently started. I am not sure where to look for a problem, and to that end, a solution.

I suspect the problem with the new publication/subscriptions not initializing may have been a result of timeouts but it is hard to say for sure. The fact that it eventually succeeded after multiple attempts leads me to believe this. If this happens
again, enable verbose agent logging for the Distribution Agent to see if you are getting query timeouts. Add the parameters
-OutputVerboseLevel 2 -Output C:\TEMP\DistributionAgent.log to the Distribution Agent Run Agent job step, rerun the agent, and collect the log.
If you are getting query timeouts, try increasing the Distribution Agent -QueryTimeOut parameter. The default is 1800 seconds. Try bumping this up to 3600 seconds.
Regarding the three transactions not replicating, inspect MSrepl_errors in the distribution database for the time these transactions occurred and see if any errors occurred.
Brandon Williams (blog |
linkedin)

WSUS wants our SQL server (running 2008 R2 SP2) to install SP1. Why?

We just installed a bunch of Windows Updates on our servers (that were pushed out from WSUS). One of the updates -- SQL Server 2008 R2
SP1 -- failed to install on our SQL server. But that's because it already had
SP2 installed. I ran a Discovery Report, and all of our SQL Server 2008 R2 components are at SP2. And yet, WSUS wants this server to install SP1.
Any suggestions as to why? I'd rather not re-install SP2 if it's not necessary.
Thank you!
p.s. I do see the following in the Sumary.txt file produced by the Discovery Report:
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       1
Installation edition:          EVAL
What is this "EVAL" version? I don't think we ever installed an evaluation version of SQL, though I suppose that's possible

Hi,
A similar thread discussed below was caused that reporting service didn’t work properly. And the solution is to run
Sp2 setup again and just select reporting service for upgrade.
For more information please refer to:
SQL Server 2008 R2 SP2 wants to install SP1 again via WSUS
http://social.technet.microsoft.com/Forums/en-US/6e711903-7c2c-4bec-a9d8-c0b56ba0f9f8/sql-server-2008-r2-sp2-wants-to-install-sp1-again-via-wsus?forum=sqlsetupandupgrade

How to stop SQL Server Agent Job if Stored Procedure returns value 0

I have SQL Server 2012 SSIS.
I have 2 SSIS packages.
I have created SQL Server Agent Job for running packages.
I have created steps. If first step have run succesfully next step is run.
I have need to add new logic.
I have validation stored procedure, which validate DB table values and returns 1 or 0.
I would like to create logic where first of all this SP is runned. Return value of SP determines if steps are run or not.
I was thinking to use Execute SQL Task for running SP.
If value 1 is returned, then run rest of Tasks is run.
If value 0 is returned, what should I do so that Job is stopped? I need assistance!
I want current step to stop never moved to next step.
Is there any SSIS tasks, which can stop the Job?
Or should I make Step for running validation SP?
How to do so that if value 0 is returned stop Job.
Kenny_I

Please refer the below link:
http://technet.microsoft.com/en-us/library/aa260308(v=sql.80).aspx
Please read Remarks carefully!!!
Remarks
If a job is currently executing a step of type CmdExec, the process being run (for example, MyProgram.exe) is forced to end prematurely. Premature ending can result in unpredictable behavior such as files in use by the process being held open. Consequently,
sp_stop_job should be used only in extreme circumstances if the job contains steps of type CmdExec.
Permissions
Execute permissions default to the public role in the
msdb database. A user who can execute this procedure and is a member of the
sysadmin fixed role can stop any job. A user who is not a member of the
sysadmin role can use sp_stop_job to stop only the jobs he/she owns.
When sp_stop_job is invoked by a user who is a member of the
sysadmin fixed server role, sp_stop_job will be executed under the security context in which the SQL Server service is running. When the user is not a member of the
sysadmin group, sp_stop_job will impersonate the SQL Server Agent proxy account, which is specified using
xp_sqlagent_proxy_account. If the proxy account is not available,
sp_stop_job will fail. This is only true for Microsoft® Windows® NT 4.0 and Windows 2000. On Windows 9.x, there is no impersonation and
sp_stop_job is always executed under the security context of the Windows 9.x user who started SQL Server.

Copying more tables from a SQL Server db to another one - SSIS 2012

Hi,
in order to copy data of more tables (more an hundred) from a SQL Server db to a SQL Server destination db I'd like to use the Transfer SQL Server objects task, but the source tables belonged to the dbo schema and the destination schema is a different
one.
It seems that this task doesn't provide a such option.
Any suggests to me, please?
Thanks

http://www.experts-exchange.com/Database/MS-SQL-Server/Q_26533111.html
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

Connect SharePoint to SQL Server Database Then Build Rules Based Returns System

Hello Guys,
I work for an ecommerce business. We sell a wide range of products to customers all around the world which are ordered from our websites and then dispatched to our customers from our warehouses.
I have been tasked with developing a computerised return system from the company because at the moment everything is done using paper forms.
We have all our customer, order and product data within SQL Server databases.
What I would like to know is...
1. Can we connect sharepoint online to a local sql server database
2. Could we then build searches within sharepoint to display data contained within these databases e.g. customer information etc
3. How is the data presented in sharepoint - is there a way to design how the data is displayed within sharepoint etc?
4. Can we then build a rules based return system within sharepoint? The on screen workflow would need to vary according to data contained within the database e.g. the weight if the product being returned and also on fields input by the service agent such
as the reason for the return, what solution the customer would like etc.
5. is it possible to build these workflows in such a way that they can be saved part way through then gone back to later
6. Can reports be build based on the returns that are being generated e.g. list of products most commonly returned
Sorry for all the questions, I am a bit of sharepoint novice. I think it may possible be able to do what we need but I just wondered if the answer to any of the above questions is definately a no because if it is that could mean it is not suitable
Thanks

You could use a BCS connection
http://community.office365.com/en-us/b/office_365_community_blog/archive/2012/10/11/business-data-connectivity-services-in-office-365-sharepoint-online.aspx, this will allow you to edit data in your non SharePoint SQL DB, on premises, from Office 365 SharePoint.
Search will index the web applications you point it at, and the lists from the BCS will be part of those web apps, site collections, sites at some place and will get indexed.
You can create views on the data, that can sort of work like a search, but when you search on the site where the lists are the query will return results based on the BCS data.
These views can be based on criteria such as the weight of the product being returned and other fields.
The data is presented as a list.
You can make it read only or read-write based on SharePoint permissions on the list. The account used to create the connection can edit.
BCS is possible in on-premises SharePoint too
here is a good read on it,
http://www.dotnetcurry.com/showarticle.aspx?ID=632
Stacy Simpkins | MCSE SharePoint | www.sharepointpapa.com

Multiple instance of Sql server running for Analyzer 7.0 install

Hi,I do have a Sql server instance where the server name is: abc\xyz. Will analyzer accetp a '\' as the server name. This instance of Sql server is not running is not running on the std port 1433. Let me know if there will be any issues whrn installing Analyzer 7.0.Thanks,

There can only be a single default instance and multiple named instances.
BOL: http://technet.microsoft.com/en-us/library/ms143547.aspx
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Lookout SQL Server Running at 100%

Hi there,
We have a system that is logging alarms for several sewage pumpstations. We recently had a problem with the HMI machine where the Microsoft SQL Server was running at close to 100%. I was unsure what SQL server was doing, so I disabled it in the services manager.
However, after doing this I found that I could not search the database for alarms (which makes sense). I then restarted the SQL Server, but once again found that it pushed the computer CPU close to 100%.
Is there any reason for this? How could this be fixed?
-andrew

Check this previous post.
http://forums.ni.com/ni/board/message?board.id=190&message.id=3160

I Am Getting Failed Notifications When Installing SQL SERVER 2008 can any one suggest me Wt can i do

Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068643839
Exit facility code: 1203
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-03-07 08:24:10
End time: 2014-03-07 09:07:13
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xC71AA851%400x73BA6908
Machine Properties:
Machine name: HOME
Machine processor count: 1
OS version: Windows XP
OS service pack: Service Pack 3
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: E:\Projects\Sqlserver2008\x86\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: NT AUTHORITY\SYSTEM
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: HOME\Administrator
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\ConfigurationFile.ini
ENABLERANU: False
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: E:\Projects\Sqlserver2008\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: HOME\Administrator
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: Analysis Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_as_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_as_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: Integration Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Books Online
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\SystemConfigurationCheck_Report.htm

Hello,
Please check below link
http://support.microsoft.com/kb/955403/en-gb
SQL Server enterprise edition is not supported on Windows XP.You can install but its not supported by Microsoft.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1

I am unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1. Log message is as follows:
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\xplog70.dll'.
Error: 17750, Severity: 16, State: 0.
Could not load the DLL xplog70.dll, or one of the DLLs it references. Reason: (null).

Hi JFriedley,
According to your error message, there might three reasons for this issue.
xplog70.dll is corrupt, you need to check if you have any SQL Server running on same file version and same production
edition. If xplog70.dll is corrupt, you can copy it from the new server where agent is running fine to your problematic server.
Native client not installed properly. If you try applying any latest Service Pack or Cumulative Update then check if the SQL Server Agent can start, if that also doesn’t solve issue then try to reinstalling SQL Server Native client from SQL Server setup
files.
There is a similar issue about error 17750, you can review the following article.
http://blogs.lostincreativity.com/sqldba/sqlserver-error-17750-could-not-load-the-dll-xpstar90-dll/
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

SSIS running through SQL Server agent Job Fails --SQL Server 2012

Hi All,
I am getting the below error.
Executed as user: sak\thiru. ...ion 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 3:31:17 PM Error: 2014-03-07 15:32:22.46 Code: 0xC0202009 Source: CommonDataSource
Connection manager "TESTDB" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0"
Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "A network-related or instance-specific
error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ". End Error Error:
2014-03-07 15:32:43.58
The package execution fa... The step failed.
I checked namedpipes, ports,services, SqlBrowser all are running fine.
share your views.
Thanks
Thiru
Thiru

Hi Thiru,
The error messages are rather general and the issue may occur due to various causes. You can check the “Connect Time” setting of the Connection Manager "TESTDB", and increase its timeout value.
If the issue persists, maybe it occurs because the Windows Firewall or certain anti-virus software blocks the RPC dynamic range of TCP Ports between SQL Server and Domain Controllers. In this case, temporarily disable third party anti-virus software, or
configure RPC dynamic port allocation to work with firewalls referring to the following KB article
http://support.microsoft.com/kb/154596.
In addition, the issue may be related to the SQL Server that the OLE DB Source adapter connects to. You can check the SQL Server log to see if any error occurs at that time.
Hope this helps.
Regards,
Mike Yin
TechNet Community Support

Update data automatically in sql server 2005 based on condition proplem

Hi guys i have problem I have two table
First one is
Second One is Vacation
as relation one to many (vacation has foreign key of Contract No OF Table Contract)
what i need is to update Contract table with field status =Finish where start vacation date >end contract Date
How i do that in sql server 2005 to make update automatically
Ex
contract table
status nvarchar(20)
end contract date time
vacation table
start vacation date time
end vacation date time
start vacation date is 23/10/2014
and End
is 26/10/2014
Now not update status in contract table to finish because vacation date start is less from end contract
but when date today is 27/10/2014 update contract table field status to finish
automatically with sql server 2005
How i do that condition to make update to data automatically based on changing on date
Update statement i need is
update Contract set status = finish where start vacation>end contract
but problem how i write this statement to update data automatically based on date today

Please post DDL, so that people do not have to guess what the keys, constraints, Declarative Referential Integrity, data types, etc. in your schema are. Learn how to follow ISO-11179 data element naming conventions and formatting rules. Temporal data should
use ISO-8601 formats. You failed again. Code should be in Standard SQL as much as possible and not local dialect.
This is minimal polite behavior on SQL forums. Now we have to write the DDL that you did not bother with! What you did post was wrong! There is no key or constraints. There is no generic “status” in RDBMS; a "<something in particular>_status"
is a state of being, so it needs a temporal duration. The correct idiom for this data model is:
CREATE TABLE Vacations
(vacation_contract CHAR(15) NOT NULL PRIMARY KEY,
vacation_start_date DATE NOT NULL,
vacation_end_date DATE,
CHECK(vacation_start_date < vacation_end_date),
Oh, a field is nothing like a column. You need to read a basic SQL or RDBMS book; you do not know the basics.
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking
in Sets / Trees and Hierarchies in SQL

How to run a SQL Server Agent job step on certain days/frequency

I've a SQL Server Agent job. One of the requirement is that a particular step should only run on certain frequency i.e. Certain Date and time. Any suggestions how can that be done?
GBM

yes
1. Make first step as a Transact SQL step. Keep command as below
IF DAY(GETDATE()) = <Your date value>
AND DATEPART(hh,GETDATE()) = <your time hour)
AND DATEPART(minute,GETDATE()) = <your time minute)
SELECT 1
ELSE
RAISERROR 'Job cant be run at this time'
Then for job step properties set the following properties in advanced tab
This would make sure it will quit the job without executing other core steps untill it reaches the required day and time
You can add more conditions in IF based on requirement like if you want time to be on certain second or month to be particular value etc
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SQL Server runs update on one record, returns -1 records updated to java

Similar Messages

Maybe you are looking for