SQL SERVER SECURITY Update KB2977321 and KB2716436 Error Code 1642
I had gone through some of the related question that has been shared over here but since for me there was a definite Error Pop up stating
SQL SERVER SET UP FAILER "NT Service Unable to start MSSQLSERVER" but i noticed that after each of the update the version had changed and the database is running normally, just want to confirm if the updates are working fine or some
other measures has to be taken.
I Ran the discovery report and it shows the latest version
Can i take this as a successfull installation and no issues will occur?
Please suggest.
I have pulled this from the Setup Bootstrap log. IN the Administrative log in the event viewer there is nothing helpful.
2015-03-31 15:07:22 Slp: Sco: Attempting to open service handle for service MSSQLSERVER
2015-03-31 15:07:22 Slp: Invoking QueryServiceStatusEx Win32 API
2015-03-31 15:07:22 Slp: Sco: Attempting to close service handle for service MSSQLSERVER
2015-03-31 15:07:22 Slp: Sco: Attempting to close SC Manager
2015-03-31 15:07:22 Slp: Sco: Returning service process id 5644
2015-03-31 15:07:22 Slp: Waiting for nt event Global\sqlserverRecComplete to be created
2015-03-31 15:07:22 Slp: Waiting for nt event Global\sqlserverRecComplete or sql process handle to be signaled
2015-03-31 15:07:22 Slp: Error: Failed to start the following NT service after patch action: MSSQLSERVER
2015-03-31 15:07:22 Slp: Sleeping 10 seconds before retrying NT service start request
2015-03-31 15:07:32 Slp: Sco: Attempting to start service MSSQLSERVER
2015-03-31 15:07:32 Slp: Sco: Attempting to start service MSSQLSERVER, start parameters
2015-03-31 15:07:32 Slp: Sco: Attempting to start service MSSQLSERVER
2015-03-31 15:07:32 Slp: Sco: Attempting to open SC Manager
2015-03-31 15:07:32 Slp: Sco: Attempting to open service handle for service MSSQLSERVER
2015-03-31 15:07:32 Slp: Sco: Service MSSQLSERVER already running or pending start
2015-03-31 15:07:32 Slp: Sco: Attempting to close service handle for service MSSQLSERVER
2015-03-31 15:07:32 Slp: Sco: Attempting to close SC Manager
2015-03-31 15:07:32 Slp: Waiting for the following Sql NT service to indicate successful startup: MSSQLSERVER
2015-03-31 15:07:32 Slp: Sco: Attempting to get service process id for service MSSQLSERVER
2015-03-31 15:07:32 Slp: Sco: Attempting to open SC Manager
2015-03-31 15:07:32 Slp: Sco: Attempting to open service handle for service MSSQLSERVER
2015-03-31 15:07:32 Slp: Invoking QueryServiceStatusEx Win32 API
2015-03-31 15:07:32 Slp: Sco: Attempting to close service handle for service MSSQLSERVER
2015-03-31 15:07:32 Slp: Sco: Attempting to close SC Manager
2015-03-31 15:07:32 Slp: Sco: Returning service process id 5644
2015-03-31 15:07:32 Slp: Waiting for nt event Global\sqlserverRecComplete to be created
2015-03-31 15:07:32 Slp: Waiting for nt event Global\sqlserverRecComplete or sql process handle to be signaled
2015-03-31 15:07:32 Slp: Error: Failed to start the following NT service after patch action: MSSQLSERVER
2015-03-31 15:07:32 Slp: Error: Action "StartPatchedServices" threw an exception during execution.
2015-03-31 15:07:32 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: The NT service 'MSSQLSERVER' could not be started. ---> Microsoft.SqlServer.Chainer.Infrastructure.ChainerInvalidOperationException: The NT service 'MSSQLSERVER'
could not be started.
2015-03-31 15:07:32 Slp: at Microsoft.SqlServer.Configuration.SetupExtension.StartPatchedServicesAction.ExecuteAction(String actionId)
2015-03-31 15:07:32 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2015-03-31 15:07:32 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2015-03-31 15:07:32 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2015-03-31 15:07:32 Slp: --- End of inner exception stack trace ---
2015-03-31 15:07:32 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2015-03-31 15:07:36 Slp: Received request to add the following file to Watson reporting: C:\Users\imchenatadmin\AppData\Local\Temp\2\tmp4C5D.tmp
2015-03-31 15:07:36 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2015-03-31 15:07:36 Slp: Inner exceptions are being indented
2015-03-31 15:07:36 Slp:
2015-03-31 15:07:36 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInvalidOperationException
2015-03-31 15:07:36 Slp: Message:
2015-03-31 15:07:36 Slp: The NT service 'MSSQLSERVER' could not be started.
2015-03-31 15:07:36 Slp: Stack:
2015-03-31 15:07:36 Slp: at Microsoft.SqlServer.Configuration.SetupExtension.StartPatchedServicesAction.ExecuteAction(String actionId)
2015-03-31 15:07:36 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2015-03-31 15:07:36 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2015-03-31 15:07:36 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2015-03-31 15:07:36 Slp: Watson Bucket 1
Original Parameter Values
2015-03-31 15:07:36 Slp: Parameter 0 : SQL2008@RTM@KB2977321
2015-03-31 15:07:36 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.SetupExtension.StartPatchedServicesAction.ExecuteAction
2015-03-31 15:07:36 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.SetupExtension.StartPatchedServicesAction.ExecuteAction
2015-03-31 15:07:36 Slp: Parameter 3 : Microsoft.SqlServer.Chainer.Infrastructure.ChainerInvalidOperationException@1202@1
2015-03-31 15:07:36 Slp: Parameter 4 : Microsoft.SqlServer.Chainer.Infrastructure.ChainerInvalidOperationException@1202@1
2015-03-31 15:07:36 Slp: Parameter 5 : StartPatchedServices
2015-03-31 15:07:36 Slp:
Final Parameter Values
2015-03-31 15:07:36 Slp: Parameter 0 : SQL2008@RTM@KB2977321
2015-03-31 15:07:36 Slp: Parameter 1 : 0x0EE19F0D
2015-03-31 15:07:36 Slp: Parameter 2 : 0x0EE19F0D
2015-03-31 15:07:36 Slp: Parameter 3 : 0xF762992B@1202@1
2015-03-31 15:07:36 Slp: Parameter 4 : 0xF762992B@1202@1
2015-03-31 15:07:36 Slp: Parameter 5 : StartPatchedServices
2015-03-31 15:07:37 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150331_145638\MSSQLSERVER\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2015-03-31 15:07:37 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150331_145638\MSSQLSERVER\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2015-03-31 15:07:37 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150331_145638\MSSQLSERVER\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2015-03-31 15:07:37 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150331_145638\MSSQLSERVER\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft
SQL Server.reg_
2015-03-31 15:07:37 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150331_145638\MSSQLSERVER\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2015-03-31 15:07:37 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150331_145638\MSSQLSERVER\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2015-03-31 15:07:40 Slp: The NT service 'MSSQLSERVER' could not be started.
2015-03-31 15:07:40 Slp: Watson bucket for exception based failure has been created
2015-03-31 15:07:40 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2015-03-31 15:07:40 Slp: Sco: Attempting to open registry subkey
2015-03-31 15:07:40 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2015-03-31 15:07:40 Slp: Sco: Attempting to get registry value DW0201
2015-03-31 15:07:40 Slp: Submitted 1 of 1 failures to the Watson data repository
2015-03-31 15:07:43 Slp:
2015-03-31 15:07:43 Slp: ----------------------------------------------------------------------
2015-03-31 15:07:43 Slp:
2015-03-31 15:07:43 Slp: Error result: -2068709375
2015-03-31 15:07:43 Slp: Result facility code: 1202
2015-03-31 15:07:43 Slp: Result error code: 1
Similar Messages
-
SQL Server 2008 KB2977321 Failed with Error code 1642
As part of application of security patches via windows update, sql server KB2977321 was applied along with a number of OS security patches.
Prior to applying the patches, I stopped the agent, engine, reporting, analysis and full text services.
The Sql server build prior to windows update was (for both instances):
ProductVersion
ProductLevel
Edition
10.0.5500.0
SP3
Standard Edition (64-bit)
After the update process, my main instance is showing (the second instance is not in use yet and I have left it in its stopped state)
Microsoft SQL Server 2008 (SP3) - 10.0.5520.0 (X64)
Jul 11 2014 16:11:50
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM)
In the Administrative Logs after the OS patches were applied (and all were reported as successful by windows update), I found the following errors listed:
Log Name:
Application
Source:
MsiInstaller
Date:
11/18/2014 7:16:45 PM
Event ID:
1024
Task Category: None
Level:
Error
Keywords:
Classic
User:
SYSTEM
Computer:
SJCDB3.intranet.co.st-johns.fl.us
Description:
Product: Microsoft SQL Server 2008 Database Engine Services - Update '{9145CF54-462E-4A28-8FB5-A44C93AD3716}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot
issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">1024</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-11-19T00:16:45.000000000Z" />
<EventRecordID>1764186</EventRecordID>
<Channel>Application</Channel>
<Computer>SJCDB3.intranet.co.st-johns.fl.us</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data>Microsoft SQL Server 2008 Database Engine Services</Data>
<Data>{9145CF54-462E-4A28-8FB5-A44C93AD3716}</Data>
<Data>1642</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>
</Data>
<Binary>7B38373544383436332D313135422D343444322D414432352D3731454337453833423843437D207B39313435434635342D343632452D344132382D384642352D4134344339334144333731367D2031363432</Binary>
</EventData>
</Event>
In the C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_191448\Detail.txt file I found the following around the time the error was reported
2014-11-18 19:16:30 Slp: Baseline Package Id sql_engine_core_inst_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_engine_core_inst_Cpu64 - NotInstalled on the baseline msi package sql_engine_core_inst_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu32
BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_rs_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_rs_Cpu64 - NotInstalled on the baseline msi package sql_rs_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu32 BaselineVersion=10.3.5500.0;
PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_is_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_is_Cpu64 - NotInstalled on the baseline msi package sql_is_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_is_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_is_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_is.msp PatchCode={E870296C-24CC-4D82-BB59-CD136692E2BD}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_bids_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_bids_Cpu64 - NotInstalled on the baseline msi package sql_bids_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_bids_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_bids_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_bids.msp PatchCode={EA407FA6-C2D1-4D3D-9227-B9E06DDDEFD0}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_ssms_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_ssms_Cpu64 - NotInstalled on the baseline msi package sql_ssms_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_ssms_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_ssms_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_ssms.msp PatchCode={8A81B870-E8F0-415D-AC80-13BEAA3EC8C8}
2014-11-18 19:16:30 Slp: Baseline Package Id: sql_common_core_Cpu64 - No patches are found by SQL Discovery on the installed package whose ProductCode is {5340A3B5-3853-4745-BED2-DD9FF5371331}
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_common_core_Cpu64 - NotInstalled on the baseline msi package sql_common_core_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_common_core_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_common_core_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_common_core.msp PatchCode={CF023E0F-3A19-4DBF-BCA3-0F664B447EDB}
The instance came up successfully and seems to be operating normally. Was there an error or was the KB installed correctly as the result of the windows update process indicated?
Is there a way I can verify this?I did some research on this particular KB article and it seems to be related to Master Data Services which I am not using. The KB was pushed automatically and I am not sure that it was a required update in our situation. I'd like to understand exactly
what caused the error message before initiating a repair as this is a production and not a test environment. Everything appears to be functioning properly and I have received direction from Microsoft in the past that information in some logs identified
as level 'error' are in fact to be ignored. I checked the windows update and this KB shows 'Successful' rather than failed or cancelled.
I would also like more information on why sql server services should not be stopped prior to allowing the OS patches to be applied. I have received messages in the past that stopping the services before service packs are applied
prevent the necessity for a reboot of the machine. I've never heard before that it is a best practice not to stop Sql service prior to applying patches. Once the services are stopped, I have our infrastructure admin start a VM snapshot on
the machine then kick off the windows update process. When done, I reboot the machine, test out Sql Server processes and then if all goes well give the ok to release the VM snapshot. I've supported various databases for 12 years, Sql Server for 5
years and this is the first time I've heard stopping the service manually can cause problems. If that is the case, I will certainly change how I do things....
I did run the discovery report and the results follow:
Microsoft SQL Server 2008 Setup Discovery Report
Product
Instance
Instance ID
Feature
Language
Edition
Version
Clustered
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
SQL Server Replication
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Full-Text Search
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSAS10.MSSQLSERVER
Analysis Services
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSRS10.MSSQLSERVER
Reporting Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
EVAULT
MSSQL10.EVAULT
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Basic
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Complete
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Connectivity
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Backwards Compatibility
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools SDK
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Integration Services
1033
Standard Edition
10.3.5520.0
No -
Installing SQL Server 2012 on a new VM - Error Code 0x858C0017
TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
The SQL Server product key is not valid. To proceed, re-enter the product key values from the Certificate of Authenticity (COA) or SQL Server packaging.
Error code 0x858C0017.
For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&EvtType=0xFDC38F1F%25400x75B506EA%25401420%254023
BUTTONS:
OK
I am trying to create a new dev environment and I'm using VMware Player running Windows Server 2008R2 SP1. I am able to run through the setup checks but when I hit "Next" I receive the error above. Also, I am able to install this on my personal
computer - just not in my VM. Any way to solve this?
Thanks!
Edit: Just to clarify some things.
1) I am trying to install SQL Server 2012 Enterprise Edition.
2) I downloaded the .ISO file using my MSDN License and when I downloaded the file the text boxt next to it said that a product key was not required.
3) I went inside the setup directory and found the DefaultSetup.ini and there was a product key inside that has been confirmed by a rep to be a valid product key.Hello,
Try using WinRAR to unzip the ISO file to a local drive and install from there. Please do not use WinZIP.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
I was also facing the same issue
TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
The SQL Server product key is not valid. To proceed, re-enter the product key values from the Certificate of Authenticity (COA) or SQL Server packaging.
Error code 0x858C0017.
Earlier i used a different product to unzip the iso file.
Once i tried unzipping it using WINRAR, it worked. And installation went fine. Thanks Alberto -
SQL Server Service is stoping with an Error Code : 1814
Hi,
I have an SCCM Server in My organization. Where we have installed Microsoft SQL Server 2008 R2 for the database of SCCM Application.
Now I am not able to Start the SCCM console due to some dependent Services are not starting. 3 services has to be started for the perfect working of SCCM.
1)SQL Server
2) SQL Server Agent
3) SQL Server Reporting Services
Out of three the first two services are not starting at all. I am getting an error while trying to start SQL Server Services.
" Windows Could not start the SQL Server (MSSQLSERVER) on Local Computer. For more information, review the system event Log, If this is a non-Microsoft Service, contact the service vender , and refer to service-specific error code
1814."
Please help me to start the services and resolve the SCCM Server issue.
Thanks,
Henoy TM
+918888631370Hi Xing,
I have check the Error Log : Please find the logfile details:
2013-04-11 11:11:57.54 Server Microsoft SQL Server 2008 R2 (SP1) - 10.50.2811.0 (X64)
Apr 6 2012 01:59:29
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2013-04-11 11:11:57.54 Server (c) Microsoft Corporation.
2013-04-11 11:11:57.54 Server All rights reserved.
2013-04-11 11:11:57.54 Server Server process ID is 10348.
2013-04-11 11:11:57.54 Server System Manufacturer: 'HP', System Model: 'ProLiant DL380 G6'.
2013-04-11 11:11:57.54 Server Authentication mode is WINDOWS-ONLY.
2013-04-11 11:11:57.54 Server Logging SQL Server messages in file 'H:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2013-04-11 11:11:57.54 Server This instance of SQL Server last reported using a process ID of 4428 at 4/11/2013 10:41:54 AM (local) 4/11/2013 5:11:54 AM (UTC). This is an informational message only; no user action is required.
2013-04-11 11:11:57.54 Server Registry startup parameters:
-d H:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e H:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l H:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
-T 8295
-T 4199
2013-04-11 11:11:57.56 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-04-11 11:11:57.56 Server Detected 8 CPUs. This is an informational message; no user action is required.
2013-04-11 11:11:57.59 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.
2013-04-11 11:11:57.61 Server Node configuration: node 0: CPU mask: 0x00000000000000f0:0 Active CPU mask: 0x00000000000000f0:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2013-04-11 11:11:57.61 Server Node configuration: node 1: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2013-04-11 11:11:57.66 spid9s Starting up database 'master'.
2013-04-11 11:11:58.24 spid9s Resource governor reconfiguration succeeded.
2013-04-11 11:11:58.24 spid9s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2013-04-11 11:11:58.24 spid9s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2013-04-11 11:11:58.24 spid9s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-04-11 11:11:58.27 spid9s SQL Trace ID 1 was started by login "sa".
2013-04-11 11:11:58.27 spid9s Starting up database 'mssqlsystemresource'.
2013-04-11 11:11:58.29 spid9s The resource database build version is 10.50.2811. This is an informational message only. No user action is required.
2013-04-11 11:11:58.38 spid9s Server name is 'SGL-PANJ-SCCM'. This is an informational message only. No user action is required.
2013-04-11 11:11:58.39 spid12s Starting up database 'model'.
2013-04-11 11:11:58.39 Server The certificate [Cert Hash(sha1) "6E37DB5BAE65C704EF7C1BA0DE6587F34B5E8A53"] was successfully loaded for encryption.
2013-04-11 11:11:58.40 Server Server is listening on [ 'any' <ipv6> 1433].
2013-04-11 11:11:58.40 Server Server is listening on [ 'any' <ipv4> 1433].
2013-04-11 11:11:58.40 Server Server local connection provider is ready to accept connection on [
\\ . \pipe \SQLLocal \ MSSQLSERVER].
2013-04-11 11:11:58.40 Server Server named pipe provider is ready to accept connection on [ \\. \ pipe\ sql \ query].
2013-04-11 11:11:58.40 Server Server is listening on [ ::1 <ipv6> 1434].
2013-04-11 11:11:58.40 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2013-04-11 11:11:58.40 Server Dedicated admin connection support was established for listening locally on port 1434.
2013-04-11 11:11:58.41 Logon Error: 17187, Severity: 16, State: 1.
2013-04-11 11:11:58.41 Logon SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL
Server is ready before trying to connect again. [CLIENT: 172.17.5.20]
2013-04-11 11:11:58.42 spid12s The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2013-04-11 11:11:58.42 spid12s Error: 927, Severity: 14, State: 2.
2013-04-11 11:11:58.42 spid12s Database 'model' cannot be opened. It is in the middle of a restore.
2013-04-11 11:11:58.42 spid12s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in
the event log that may indicate why the tempdb files could not be initialized.
2013-04-11 11:11:58.42 spid12s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2013-04-11 11:11:58.43 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098, state: 15. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2013-04-11 11:11:58.43 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2013-04-11 11:11:58.52 Logon Error: 17188, Severity: 16, State: 1.
2013-04-11 11:11:58.52 Logon SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: ::1]
2013-04-11 11:11:58.54 Logon Error: 17188, Severity: 16, State: 1.
2013-04-11 11:11:58.54 Logon SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: 192.168.6.2]
2013-04-11 11:11:58.57 spid15s A new instance of the full-text filter daemon host process has been successfully started.
2013-04-11 11:11:58.60 spid16s Starting up database 'ReportServer'.
2013-04-11 11:11:58.60 spid17s Starting up database 'ReportServerTempDB'.
2013-04-11 11:11:58.60 spid18s Starting up database 'CM_P01'.
2013-04-11 11:11:58.60 spid15s Starting up database 'msdb'.
Cannot close event log because there are still event handle users active.
Regards,
Henoy -
update ios7 fail,reminder saying need to restore, but fail also, error code is 4005.
If you have a phone with no Facetime, it can't ever be added. As you note, it is outlawed in several mideast countries. If you bought it in one of those, it is not an option for you.
-
SQL Server 2012 Installed KB2793634 and it completed successfully but display error in the event log
Hi
Running SQL Server 2012 with SP1 on Windows 7 x64 SP1
One of the machines that this is installed displayed that the Windows Installer was starting repeatedly, like every 30 secs
I installed KB2793634 and everything completed successfully. No errors in any of the Summary, Detail, etc and all check marks at the end. I went throught the event viewer and in the application log and saw the following
Product: SQL Server 2012 Database Engine Services - Update '{4023B523-7241-4B6D-83A4-92105B0A3DC8}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the
following link for instructions on turning on logging support:
Is this something with the KB. How do I find what the issue is and what do I do to fix it? Or is this a real error?
I brought up SQL Server and the issue that the KB resolves seems to been resolved. I can connect to the instance just fine, the version of the KB has been applied to the instance so now it is at 11.0.3128
Any information will be greatly appreciated.Hi,
According to the description, I know the patch that was successfully installed after the msiinstaller error.
1. Per
KB304888 and mentioned the possibility that the hotfix was launched a second time after the initial successful update.
I suspect if you have installed any hotfixes or Cumulative updates after installing Service Pack 1 for SQL Server 2012.
Reference:
http://support.microsoft.com/kb/2793634
2. Check the application log. Is the error happening intermittently?
Thanks.
Tracy Cai
TechNet Community Support -
Hi All,
Here the linked server is created between sql server 2012 64 bit and sql server 2005 32 bit. I am getting the below error when i try to access linked server from third server. I have created linked from Instance 1 to Instance 2. When i access it from
instance 3 i am getting the below error. SPN setting has been done between these 2 servers. Also the option 'Trust the delegate' is enabled for the both the service account.
'Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
Appreciate your quick response.
Vikas.M.SHello,
Please read the following resources:
http://www.databasejournal.com/features/mssql/article.php/3696506/Setting-Up-Delegation-for-Linked-Servers.htm
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea26de43-4c6b-4991-86d7-e1578f107c92/linked-server-login-failed-for-user-nt-authorityanonymous-logon?forum=sqldataaccess
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Installation of update KB2977320 results in error code 29569 and 45671
When trying to manually install the update KB2977320 after the automatic installation failed I get the following entries in my log:
2014-11-20 17:10:47 Slp: Sco: Attempting to normalize directory path 'c:\Program Files\Microsoft SQL Server\100\Shared\SqlWtsn.exe.config'
2014-11-20 17:10:47 Slp: Sco: Attempting to check if file 'c:\Program Files\Microsoft SQL Server\100\Shared\SqlWtsn.exe.config' exists
2014-11-20 17:10:47 Slp: App config file c:\Program Files\Microsoft SQL Server\100\Shared\SqlWtsn.exe.config was not found
2014-11-20 17:10:47 Slp: Completed Action: NotifyProgressComplete, returned True
2014-11-20 17:10:47 Slp: ----------------------------------------------------------------------
2014-11-20 17:10:47 Slp: Running Action: FinalizeProgressStatus
2014-11-20 17:10:47 Slp: Completed Action: FinalizeProgressStatus, returned True
2014-11-20 17:10:47 Slp: ----------------------------------------------------------------------
2014-11-20 17:10:47 Slp: Running Action: CloseUI
2014-11-20 17:10:47 Slp: Stop action skipped in UI Mode Quiet
2014-11-20 17:10:47 Slp: Completed Action: CloseUI, returned True
2014-11-20 17:10:49 Slp:
2014-11-20 17:10:49 Slp:
2014-11-20 17:10:49 Slp: ----------------------------------------------------------------------
2014-11-20 17:10:49 Slp:
2014-11-20 17:10:49 Slp: Error result: -2068024447
2014-11-20 17:10:49 Slp: Result facility code: 1212
2014-11-20 17:10:49 Slp: Result error code: 29569
2014-11-20 17:10:49 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-11-20 17:10:49 Slp: Sco: Attempting to open registry subkey
2014-11-20 17:10:49 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2014-11-20 17:10:49 Slp: Sco: Attempting to get registry value DW0200
2014-11-20 17:10:51 Slp: Received request to add the following file to Watson reporting: C:\Users\schmieder\AppData\Local\Temp\tmp87E8.tmp
2014-11-20 17:10:51 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2014-11-20 17:10:51 Slp: Inner exceptions are being indented
2014-11-20 17:10:51 Slp:
2014-11-20 17:10:51 Slp: Exception type: System.IO.IOException
2014-11-20 17:10:51 Slp: Message:
2014-11-20 17:10:51 Slp: Das Verzeichnis ist nicht leer.
2014-11-20 17:10:51 Slp:
2014-11-20 17:10:51 Slp: Stack:
2014-11-20 17:10:51 Slp: bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
2014-11-20 17:10:51 Slp: bei System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive)
2014-11-20 17:10:51 Slp: bei System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive)
2014-11-20 17:10:51 Slp: bei Microsoft.SqlServer.Chainer.Infrastructure.WatsonService.CreateCab(WatsonBucket bucket)
2014-11-20 17:10:51 Slp: bei Microsoft.SqlServer.Chainer.Infrastructure.WatsonService.ReportFailures()
2014-11-20 17:10:51 Slp: bei Microsoft.SqlServer.Chainer.Setup.Setup.Start()
2014-11-20 17:10:51 Slp: bei Microsoft.SqlServer.Chainer.Setup.Setup.Main()
2014-11-20 17:10:51 Slp: Watson Bucket 2
Original Parameter Values
2014-11-20 17:10:51 Slp: Parameter 0 : SQL2008@RTM@KB2977320
2014-11-20 17:10:51 Slp: Parameter 3 : System.IO.IOException@-2147024751
2014-11-20 17:10:51 Slp: Parameter 4 : System.IO.IOException@-2147024751
2014-11-20 17:10:51 Slp:
Final Parameter Values
2014-11-20 17:10:51 Slp: Parameter 0 : SQL2008@RTM@KB2977320
2014-11-20 17:10:51 Slp: Parameter 3 : 0xAE9CC9E3
2014-11-20 17:10:51 Slp: Parameter 4 : 0xAE9CC9E3
2014-11-20 17:10:51 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20141120_170804\COMBIT\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2014-11-20 17:10:51 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20141120_170804\COMBIT\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-11-20 17:10:51 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20141120_170804\COMBIT\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2014-11-20 17:10:52 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20141120_170804\COMBIT\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2014-11-20 17:10:52 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20141120_170804\COMBIT\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-11-20 17:10:52 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20141120_170804\COMBIT\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2014-11-20 17:10:53 Slp: Das Verzeichnis ist nicht leer.
2014-11-20 17:10:53 Slp: Watson bucket for exception based failure has been created
2014-11-20 17:10:53 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-11-20 17:10:53 Slp: Sco: Attempting to open registry subkey
2014-11-20 17:10:53 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2014-11-20 17:10:53 Slp: Sco: Attempting to get registry value DW0200
2014-11-20 17:10:54 Slp: Submitted 2 of 2 failures to the Watson data repository
2014-11-20 17:10:54 Slp:
2014-11-20 17:10:54 Slp: ----------------------------------------------------------------------
2014-11-20 17:10:54 Slp:
2014-11-20 17:10:54 Slp: Error result: -1251036569
2014-11-20 17:10:54 Slp: Result facility code: 1390
2014-11-20 17:10:54 Slp: Result error code: 45671
Any help is very appreciated.
Thanks!Hi Technowizard15,
As your description, you come across an error when you manually install security update(KB2977320). Based on my research, security update(KB2977320) is used for SQL Server 2008 R2 Service Pack 2. So firstly, please check if your SQL Server version is SQL
Server 2008 R2 Service Pack 2 according to Shanky_621's post. If it is not SQL Server 2008 R2 Service Pack 2, you need to install related security update according to your SQL Server version.
However, if the error occurs when you use SQL Server 2008 R2 Service Pack 2, please help to post full error message in Detail.txt(%Program Files%\Microsoft SQL Server\100\Setup Bootstrap\Log\<YYYYMMDD_HHMM>\Detail.txt) for further analysis. For more
information about the process, please refer to the article:
http://support.microsoft.com/kb/955396. Additionally, based on my research, the issue could occur in the cases below.
1. Your account has no access to the following registry key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer. So please check if your account has access to the registry. If it has no access, you could follow the steps below to troubleshoot
your issue.
a. Located HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer in registry.
b. Right click and go to Permission, then you could see user accounts or groups. If your user account is not in the list, you could click Add to add your account there.
c. Select your account and check Full Control. Next, Click OK.
d. Install the update KB2977320 again. Please stop any Antivirus software in the installation process.
2. Installer Package (MSI) is missing. Please check if MSI exists in C:\Windows\Installer. If it doesn’t exist, you could solve this issue by one of the methods. Then install the update KB2977320 again and check if the error still occurs.
a. Use a script.
b. Manually restore the files.
For more information about the process, please refer to the article:
http://support.microsoft.com/kb/969052
Regards,
Michelle Li -
SQL Server 2005 Update mechanism problem
Hi Gurus,
We're faced with one SQL Server 2005 update mechanism problem. Here is my problem:
According to our requirement, an add_on interface program is designed to execute creation of production order by calling Bapi.
There are 3 steps in this add_on program:
Step 1: Create production order
Step 2: Change the information of production.
Step 3: Some other
After the step 1 has finished immediately step 2 is called, Howerver the information which should have inserted into database table couldn't be found from database. (Maybe because the time between two steps is too short to finish inserting)
In order to ensure the complete of the transaction, before the step 2 executed, the information in step 1 should have inserted into database.
Is there any solution to solve this problem?
I guess whether there is any parameter which control the time of writing buffer into database...
Any advice is appreciated.
Thanks & Best Regards,
Derek YangHi
I have the same problem, but that post didnt help me
This is the error I have:
My snapshot agent hangs.. waiting for a response from the server.. and timeouts.
This only hapens for a publication that has a filter based on HOSTNAME()
The other publications work fine
Error messages:
Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Command Text: sp_MSsetup_partition_groups
Parameters: @publication = XXXXXXX
Stack: at Microsoft.SqlServer.Replication.AgentCore.ReMapSqlException(SqlException e, SqlCommand command)
at Microsoft.SqlServer.Replication.AgentCore.AgentExecuteNonQuery(SqlCommand command, Int32 queryTimeout)
at Microsoft.SqlServer.Replication.AgentCore.ExecuteDiscardResults(CommandSetupDelegate commandSetupDelegate, Int32 queryTimeout)
at Microsoft.SqlServer.Replication.Snapshot.MergeSnapshotProvider.SetupPartitionGroups()
at Microsoft.SqlServer.Replication.Snapshot.MergeSnapshotProvider.DoRegularMergeSnapshotPreparations()
at Microsoft.SqlServer.Replication.Snapshot.MergeSnapshotProvider.DoPreArticleFilesGenerationProcessing()
at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot()
at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun()
at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: MSSQLServer, Error number: -2)
Get help: http://help/-2
Server XXXXXXXXX, Level 11, State 0, Procedure , Line 0
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Source: MSSQLServer, Error number: -2)
Get help: http://help/-2 -
Hi team,
what are the main difference in sql server patch and sql serve security patch ?
what is the sql server security patch and how to apply the security patch.Hello,
For SQL Server we have SP = Service Packs and CU = Cummulative Update; both are Kind of "patches" and there is no difference if a security issue or a bug is fixed with. Both are depolyed as an installation program to apply it to a SQL Server instance.
Olaf Helper
[ Blog] [ Xing] [ MVP] -
Dear Experts,
i am getting the below error when i was giving * (Star) to view all the items in DB
[Microsoft][SQL Server Native Client 11.0][SQL Server]The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator. 'Items' (OITM) (OITM)
As i was searching individually it is working fine
can any one help me how to find this..
Regards,
Meghanath.SDear Nithi Anandham,
i am not having any query while finding all the items in item master data i am giving find mode and in item code i was trying to type *(Star) and enter while typing enter the above issue i was facing..
Regards,
Meghanath -
SQL Server Express 2008 R2 and Windows 8.1 (Standard)
I recently re-engineered the backend of a legacy Access 2003 application because we knew that going forward we were going to loose the replication capability in Access. This is a small, departmental app, so the new SQL Server Express 2008 R2 backend is
hosted on a robust Windows 7 system. I tested the implementation with both Windows XP and Windows 7 clients running the updated Access 2003 frontend and everything worked great.
We are now in the midst of a company-wide upgrade to Windows 8.1 and I'm having issues. The legacy frontend works fine with Access 2013 (full version) when run locally on the Win7 machine, but I can't get any of the new Win 8.1 clients to connect to the
SQL database using the Access 2013 Runtime module. I CAN create ODBC connections to SQL Server from the clients and they test successfully, so I think I have a valid SQL connection to the Win 7 box.
To recap: old clients were WinXP Pro with Office 2003 Pro, new clients are Win 8.1 (non-Pro) with Access 2013 Runtime module.
Any ideas?Hi ,
Glad to hear that you have found the solution. Thank you for coming back and let us know the result:)
Best Regards,
Tracy
Tracy Cai
TechNet Community Support -
Hi Team,
Earlier i had SQL Server 2008 R2 on my Machine. For one work around i unistall SQL Server 2008 R2 and Trying to install SQL Server 2008 but i am not able to install with below error:
TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
Method not found: 'Boolean Microsoft.SqlServer.Configuration.MsiExtension.MsiExtensionMetadata.get_IsSlipstreamOrPatch()'..
ThanksHi Lydia,
i have followed the above step and i am able to proceed further but while installation i am getting the below error consistently.
TITLE: Microsoft SQL Server 2008 Setup
The following error has occurred:
Locating the SQL Server Browser service component failed with Windows Installer return code '2'. The component ID: '{2E86FD41-C179-456E-8E6A-5157ED427228}'.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1600.22&EvtType=0x8510C01B%25400x31BA4472%25401222%254052007
BUTTONS:
&Retry
Cancel
2:
TITLE: Microsoft SQL Server 2008 Setup
The following error has occurred:
SQL Server Browser configuration for feature 'SQL_Browser_Redist_SqlBrowser_Cpu32' was cancelled by user after a previous installation failure. The last attempted step: Retrieving full path to the SQL Server Browser service executable using Windows Installer
API for the SQL Server Browser component with ID '{2E86FD41-C179-456E-8E6A-5157ED427228}'..
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1600.22&EvtType=0x8510C01B%25400x31BA4472%25401222%254052007
BUTTONS:
OK
After ignoring these step..installation getting complete but ..at the end i am not able to connect to server.
Could you please help me on this.
Thanks,
Sumit -
MS SQL Server 2012 Updates via SCCM 2012 R2
I'm trying to determine if SCCM 2012 R2 can manage and deploy Hotfixes, Updates and Service packs for SQL Server 2012. Can someone please confirm that SCCM can manage this, how to download SQL Server Hotfixes, Updates and Service Packs into SCCM and where
I can find instructions on setting up my MS SQL Server computers to receive SQL updates from SCCM.
Thanks.ConfigMgr absolutely can deploy updates and service packs for SQL. You just need to choose the versions you want in Software Update Point Products and Classifications. It's no different than deploying any other Microsoft updates.
http://www.gerryhampsoncm.blogspot.ie/2013/04/sccm-2012-sp1-step-by-step-guide-part.html
Is it a good idea? I don't think so. I think SQL updates should be part of a carefully planned (and tested) manual upgrade.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson -
SQL Server 2005 64 bit and Oracle 9
Hi,
I have a situation which involves SQL Server 2005 64 bit and Oracle 9 32 bit,
I have a requirement that involves creating Stored Procedures from Oracle 9 which will call tables from SQL Server 2005 64 bit, with operations involving 'Select' 'Insert' 'Update' and 'Delete'.
it works fins, except when attempting to search for an SQL Server 'varchar' value, wher no mapping is done
though the Oracle sees the field as 'varchar2'
can anyone please advice on this
thanks
BaselI think you're somehow not getting a resuklt because you're query doesn't return any data.
Why the fiealdA=pat=parameterA construct? Wouldn't it just work if you changed it to fieldA=parameterA?
Also, can you not just define parameterA as a varchar to make them match?
What if you do "select * from (<your query without where>) a where a.fieldA = :parameterA"
While not efficient, it would make the filtering occur in Oracle and maybe that will let you see the problem in native Oracle land and then reuse the solution in your orginal query. If that doesn't work, drop the where clause and inspect the data closly and hardcode a simple where without using PL*SQL or bind variables.
Maybe you are looking for
-
How can I adjust fan speed?
Hi; I have an HP Comaq Presario CQ57. The fan has gotten pretty loud; even when I first turn on the laptop and it is well ventalated in a cool area it is obnoxiously loud. Is there any way I can turn the fan off or adjust the fan speed? (I know it's
-
I have downloaded a concert quite legally and can see it in downloads folder but how do I get to play the concert? Thanks John
-
Order By clause - View link consistency
Hi, I have created an EO ( EmpEO ) on EMP table. Created two VOs ( EmpVO and MaxEmpIdVO ) based on EmpEO. For MaxEmpIdVO, 1. Set the Updatable for EmpEO to false 2. Tuned it to return At Most One Row 3. Set the Order By to "EMPNO Desc" I want to use
-
Hi, I am getting the below error in BPEL console: Cannot fetch a datasource connection. The process domain was unable to establish a connection with the datasource with the connection URL "jdbc/BPELServerDataSourceWorkflow". The exception reported is
-
Please direct me to resources that describe how to insert images, set the transparent color for the image, and resize the image without losing quality. I have the full suite of tools in eLS 6 and I also have GIMP to edit images. I have a service mark