Data Committed instead of Rollback after Deadlock Error in SQL Server 2008 R2 (SP2)
We're having a strange issue which is occurring only with one Customer having SQL Server 2008 R2 (SP2).
Basically we have multiple threads uploading data and when an error occurs (like deadlock or any other error). The deadlock victim (process/transaction) is rolledback (from .NET). However the rollback command is not reaching SQL Server as it doesn't show
in the trace (through SQL Profiler).
To make things worse, not only the transaction is not being rolled back but the INSERTs executed before the error are being somehow committed, leaving the database in an inconsistent state.
This is only produced in one environment.
Any idea what the issue could be?
All statements are executed with in a Transaction. Under the same scenario this code works perfectly fine for 1000s of customers. Only one customer has this issue.
You need to capture profiler to check transaction scope.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle
Similar Messages
-
Sql server 2008 R2 SP2 -Error: 18056, Severity: 20, State: 29
HI ,
I am getting this error in sql server 2008 R2 SP2 version .
The client was unable to reuse a session with <SPID>, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed
operations immediately before this error message.
I am getting same error messages but only SPID are different as of my knowledge this error will resolve in SP@ version but seeing now so please let me know how to resolve the issue
Thanks!
Regards,
SureshHave you upgraded to cu1 for sp2 yet?
Check this bug - http://support.microsoft.com/kb/2543687
More information -
http://blogs.msdn.com/b/psssql/archive/2013/02/13/breaking-down-18065.aspx
How are you trying to connect? Could you take a look at the physical SQL Server Error log and see if you find any other error?
Check this part of the blog (http://blogs.msdn.com/b/psssql/archive/2010/05/05/error-18056-can-be-unwanted-noise-in-certain-scenarios.aspx)
"If the above error message (note that the state number should reflect 29) is the only message in the SQL Server Errorlog along with no other errors noticed in the environment
(connectivity failures to the SQL instance in question, degraded performance, high CPU usage, Out of Memory errors), then this message can be treated as benign and safely ignored."
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com -
SMS_SRS_REPORTING_POINT - Error retrieving folders with SCCM 2012 and SQL Server 2008 R2 SP2
Hi:
According to all the Reporting Services logs my Reporting Point was setup correctly. When I try and run any report I see the entries below in the srsrp.log on the SQL Server. The report names show up in the Console but when I right any of the
listed reports I get errors and no report runs.
I am running SQL Server 2008 R2 SP2 on a remote server. SQL is installed on its own server. There is no firewall between the Configuration Manager server and SQL Server.
Thanks.
Mark
(!) Error retrieving folders - [A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance
name is correct and that SQL Server is configured to 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.)]. SMS_SRS_REPORTING_POINT
1/25/2013 9:15:07 AM 4532 (0x11B4)
No folder configuration information found.
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
Next security configuration at [1/25/2013 9:22:42 AM]
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
Root Folder exists
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
Successfully checked that the SRS web service is healthy on server DBSCCM.LOCAL
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
Waiting for changes for 1 minutes
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
SRSRP registry key change notification triggered.
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:16 AM
4532 (0x11B4)
Waiting for changes for 1 minutes
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:16 AM
4532 (0x11B4)
Timed Out...
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Reporting Services URL from Registry [http://dbsccm/ReportServer/ReportService2005.asmx]
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Reporting Services is running
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Retrieved datasource definition from the server.
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Retrieved datasource definition from the server.
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ManagedDesktops_MD1
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
(!) Error retrieving folders - [A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance
name is correct and that SQL Server is configured to 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.)]. SMS_SRS_REPORTING_POINT
1/25/2013 9:17:40 AM 4532 (0x11B4)
No folder configuration information found.
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Next security configuration at [1/25/2013 9:22:42 AM]
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Root Folder exists
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Successfully checked that the SRS web service is healthy on server DBSCCM.LOCAL
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Waiting for changes for 1 minutes
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Timed Out...
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Reporting Services URL from Registry [http://dbsccm/ReportServer/ReportService2005.asmx]
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Reporting Services is running
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Retrieved datasource definition from the server.
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Retrieved datasource definition from the server.
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ManagedDesktops_MD1
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)Hi:
Windows Firewall is off on both systems.
I can ping the Configuration Manager server from the SQL Server by netbios name, ip address and fully qualified domain name. I can ping the SQL Server from the Configuration Manager server by netbios name, ip address and fully qualified domain
name.
I have uninstalled and installed the Reporting Point Service a couple of times and everything looks fine according to the logs after the install finishes but these errors only appear each time I try and Run a report.
Mark -
SQL SERVER 2008 R2 SP2 APPLYING AFTER GEETING ERROR
HI,
I had updated 2008 R2 (RTM) VERSION to sp2.After that I was unable to open the SQL server instance and getting error messege
Like "Error: 18401
Login failed for user '<abc><login name><abc>'. Reason: Server is in script upgrade mode. Only administrator can connect at this time."
note : here i am the Administrator.Hello,
The following post may be useful:
http://blogs.msdn.com/b/sqlserverfaq/archive/2010/03/31/unable-to-connect-to-sql-server-2008-instance-after-applying-sp1.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Check Stored Procedures after Migration from MS SQL Server 2008 to Oracle11
I successfully migrated my application database (azteca) from MS SQL Server 2008 to Oracle 11g R2. After migration, I found there are few stored procedures are not valid. How do I check these invalid stored procedures and find what is wrong with them by using SQL Developer? Thanks for your help.
KevinHi Kevin,
You posted quite a bit today, so perhaps you have already worked this out. If not...
1. View -> Reports -> Data Dictionary Reports -> All Objects -> Invalid Objects [for a specific schema name]
2. Next, for each invalid stored procedure listed in (1)...
a. Open in the code editor from the Connections navigator tree
b. Click on the Compile icon (two gears meshed together) in code editor tool bar.
c. Look in the Compiler log pane for errors.
d. Correct the errorsOf course, success in addressing any errors depends on your skill level dealing with Oracle PL/SQL.
Also, it may be helpful to read over section *3.2 Stored Procedures* in the supplementary migration guide:
http://docs.oracle.com/cd/E35137_01/doc.32/e18462/trig_stored_proc.htm#CHDEIGBC
Regards,
Gary
SQL Developer Team -
[Error] Microsoft SQL Server 2008 Setup. Error reading from file msdbdata.mdf
Hi all
I'm trying to install SQL 2008 Express on my Computer: Hp compact DX7300 Slim tower.
and get this error:
TITLE: Microsoft SQL Server 2008 Setup
The following error has occurred:Error reading from file d:\8268cd7b247d294de359c9\x86\setup\sql_engine_core_inst_msi\PFiles\SqlServr\MSSQL.X\MSSQL\Binn\Template\msdbdata.mdf. Verify that the file exists and that you can access it.
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.1823.0&EvtType=0xF45F6601%25401201%25401
Log file
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-12-09 23:22:03
End time: 2014-12-09 23:40:28
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\sql_engine_core_inst_Cpu32_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1823.0
Machine Properties:
Machine name: VISTA-PC
Machine processor count: 2
OS version: Windows Vista
OS service pack: Service Pack 1
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: d:\8268cd7b247d294de359c9\x86\setup\
Installation edition: EXPRESS
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\ConfigurationFile.ini
ENABLERANU: True
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
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: SQLExpress
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: d:\8268cd7b247d294de359c9\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: VISTA-PC\VISTA
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
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\20141209_232121\SystemConfigurationCheck_Report.htm
I will very appriciate if someone can help me solve it. I was trying to set Full control for my account in Properties/Security of root folder and try again but error is still.
Many thanksHi Foreverduy,
Before you run SQL Server 2008 express setup, make sure that you have installed Windows installer 4.5 and.NET Framework 3.5 SP1 manually. For more information about the process, please refer to the article:
http://msdn.microsoft.com/en-us/library/ms143506(v=sql.100).aspx. Moreover, please turn off all the third-party softwares which could prohibit the installation process.
According to your error message, the issue could be due to that your account has no rights to install SQL Server, or the corruption on the media.
Firstly, please ensure that your account has admin rights. Also make sure that you right-click the setup.exe and choose “Run as administrator” to complete the installation.
Secondly, please check if "msdbdata.mdf" file exists at d:\8268cd7b247d294de359c9\x86\setup\sql_engine_core_inst_msi\PFiles\SqlServr\MSSQL.X\MSSQL\Binn\Template. If it exists, please make sure that your account has read permission to the extracted
folder.
However, if the file doesn't exist in the extraction, the media could be corrupt. Please download the
media
again and check if the issue still occurs.
Regards,
Michelle Li -
Installation Error for SQL Server 2008 R2 on windows vista
2014-09-20 07:49:26 Slp: ----------------------------------------
2014-09-20 07:49:26 Slp: Setting: TIMESTAMP
2014-09-20 07:49:26 Slp: Value specified: 20140920_074907
2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
2014-09-20 07:49:26 Slp: ----------------------------------------
2014-09-20 07:49:26 Slp: Setting: LOGMARKER
2014-09-20 07:49:26 Slp: Value specified: _ComponentUpdate
2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
2014-09-20 07:49:26 Slp: ----------------------------------------
2014-09-20 07:49:26 Slp: Setting: INSTALLMEDIAPATH
2014-09-20 07:49:26 Slp: Value specified: C:\Downloaded\SQL Server 2008\x86\setup\
2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
2014-09-20 07:49:26 Slp: ----------------------------------------
2014-09-20 07:49:26 Slp: Setting: MEDIALAYOUT
2014-09-20 07:49:26 Slp: Value specified: Full
2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
2014-09-20 07:49:26 Slp: ----------------------------------------
2014-09-20 07:49:26 Slp: Completed Action: ProcessChainerCommandLineArguments, returned True
2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:26 Slp: Running Action: ProcessMediaChainerConfigFileArguments
2014-09-20 07:49:26 Slp: Completed Action: ProcessMediaChainerConfigFileArguments, returned True
2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:26 Slp: Running Action: ProcessChainerConfigFileArguments
2014-09-20 07:49:26 Slp: Completed Action: ProcessChainerConfigFileArguments, returned True
2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:26 Slp: Running Action: ProcessSlipstreamParameters
2014-09-20 07:49:26 Slp: Completed Action: ProcessSlipstreamParameters, returned True
2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:26 Slp: Skipping Action: SetRoleAndUIModeForExpressMedia
2014-09-20 07:49:26 Slp: Action is being skipped due to the following restrictions:
2014-09-20 07:49:26 Slp: Condition "IsMediaExpress" did not pass as it returned false and true was expected.
2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:26 Slp: Running Action: ValidateChainerSetting
2014-09-20 07:49:26 Slp: -- PidPublicConfigObject : ValidateSettings is normalizing input pid=[PID value hidden]
2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : NormalizePid found null or empty pid
2014-09-20 07:49:26 Slp: -- PidPublicConfigObject : ValidateSettings proceeding with normalized pid=[PID value hidden]
2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : Initialize is initializing using input pid=[PID value hidden]
2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : NormalizePid found null or empty pid
2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : Initialize proceeding with normalized pid=[PID value hidden]
2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : Initialize called ValidatePid, output is pid=[PID value hidden] validateSuccess=True output editionId=EVAL(0x2467BCA1)
2014-09-20 07:49:27 Slp: -- PidPublicConfigObject : ValidateSettings initialized private object, result is initializeResult=Success
2014-09-20 07:49:27 Slp: Completed Action: ValidateChainerSetting, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: ProcessFeatureCommandLineArguments
2014-09-20 07:49:27 Slp: ----------------------------------------
2014-09-20 07:49:27 Slp: Completed Action: ProcessFeatureCommandLineArguments, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: ProcessMediaFeatureConfigFileArguments
2014-09-20 07:49:27 Slp: Completed Action: ProcessMediaFeatureConfigFileArguments, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: ProcessFeatureConfigFileArguments
2014-09-20 07:49:27 Slp: Completed Action: ProcessFeatureConfigFileArguments, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: StartSqmSession
2014-09-20 07:49:27 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-09-20 07:49:27 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
2014-09-20 07:49:27 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
2014-09-20 07:49:27 Slp: Completed Action: StartSqmSession, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: ValidateSettingsAgainstScenario
2014-09-20 07:49:27 Slp: Scenario: ComponentUpdate
2014-09-20 07:49:27 Slp: Completed Action: ValidateSettingsAgainstScenario, returned True
2014-09-20 07:49:27 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: SetComponentUpdateScenarioFlags
2014-09-20 07:49:27 Slp: Completed Action: SetComponentUpdateScenarioFlags, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: ExecuteInitWorkflow
2014-09-20 07:49:27 Slp: Workflow to execute: 'INITIALIZATION'
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: InitializeMsiExtension
2014-09-20 07:49:29 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-09-20 07:49:29 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100\Bootstrap
2014-09-20 07:49:29 Slp: Completed Action: InitializeMsiExtension, returned True
2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:29 Slp: Skipping Action: InitializeConfigAction
2014-09-20 07:49:29 Slp: Action is being skipped due to the following restrictions:
2014-09-20 07:49:29 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableExternalMsiConfiguration set" did not pass as it returned false and true was expected.
2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:29 Slp: Skipping Action: RunDiscoveryAction
2014-09-20 07:49:29 Slp: Action is being skipped due to the following restrictions:
2014-09-20 07:49:29 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableDiscoverableProducts set" did not pass as it returned false and true was expected.
2014-09-20 07:49:29 Slp: Completed Action: ExecuteInitWorkflow, returned True
2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:29 Slp: Running Action: ExecuteStartUiWorkflow
2014-09-20 07:49:29 Slp: Workflow to execute: 'STARTUI'
2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:29 Slp: Running Action: InstallWizard
2014-09-20 07:49:29 Slp: Start Action: ComponentUpdate
2014-09-20 07:49:29 Slp: Configuration file: C:\Downloaded\SQL Server 2008\x86\configuration.uicfg
2014-09-20 07:49:30 Slp: Adding registration information 'ShowWizard' for type 'Microsoft.SqlServer.Management.ActionHandlerInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'InstallWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'InstallClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'AddNode' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'RemoveNode' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'PrepareClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'CompleteClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'UninstallWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'UpgradeWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'ComponentUpdate' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'RepairWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'RunRulesUI' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'EditionUpgradeWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'PatchWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'RemovePatchWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'PrepareImageWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'CompleteImageWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: -- SkuPublicConfigObject : Calling SkuPublicConfigObject.Calculate.
2014-09-20 07:49:31 Slp: Completed Action: InstallWizard, returned True
2014-09-20 07:49:31 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:31 Slp: Running Action: GatherUserSettings
2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings is normalizing input pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid is normalizing input pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid added dashes to pid, output pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings proceeding with normalized pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Initialize is initializing using input pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid is normalizing input pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Initialize proceeding with normalized pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Read lcid 1033 from CultureInfo
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Pid validation of input pid '[PID value hidden]' succeeded, resulting edition is 'DATA_CENTER' channel 'OEM'
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Initialize called ValidatePid, output is pid=[PID value hidden] validateSuccess=True output editionId=DATA_CENTER(0xC5AA9665)
2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings initialized private object, result is initializeResult=Success
2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings is normalizing input pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid is normalizing input pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid added dashes to pid, output pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings proceeding with normalized pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings found pid=[PID value hidden] is already validated and initialized.
2014-09-20 07:50:22 Slp: License file: C:\Downloaded\SQL Server 2008\1033_ENU_LP\x86\1033\License_DC_OEM.rtf
2014-09-20 07:50:25 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-09-20 07:50:25 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
2014-09-20 07:50:25 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
2014-09-20 07:50:25 Slp: License file: C:\Downloaded\SQL Server 2008\1033_ENU_LP\x86\1033\License_DC_OEM.rtf
2014-09-20 07:50:25 Slp: Completed Action: GatherUserSettings, returned True
2014-09-20 07:50:25 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:25 Slp: Running Action: RegisterRetryHandler
2014-09-20 07:50:25 Slp: Completed Action: RegisterRetryHandler, returned True
2014-09-20 07:50:25 Slp: Completed Action: ExecuteStartUiWorkflow, returned True
2014-09-20 07:50:25 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:25 Slp: Running Action: NotifyProgressCountDisplay
2014-09-20 07:50:26 Slp: Completed Action: NotifyProgressCountDisplay, returned True
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Running Action: ExecuteCalculateScenarioWorkflow
2014-09-20 07:50:26 Slp: Workflow to execute: 'CALCULATESCENARIO'
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Running Action: ClearCalculatedState
2014-09-20 07:50:26 Slp: Completed Action: ClearCalculatedState, returned True
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Skipping Action: SetUninstallEnableInstallMatchingByInstanceId
2014-09-20 07:50:26 Slp: Action is being skipped due to the following restrictions:
2014-09-20 07:50:26 Slp: Condition "Is the user's scenario set to Uninstall" did not pass as it returned false and true was expected.
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Skipping property ArgInstanceName of class: SetFeatureInstallStateAction
2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s):
2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableDiscoverableProducts set" did not pass as it returned false and true was expected.
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Skipping property ArgSqlInstanceId of class: SetFeatureInstallStateAction
2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s):
2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableInstallMatchingByInstanceId set" did not pass as it returned false and true was expected.
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Skipping property ArgASInstanceId of class: SetFeatureInstallStateAction
2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s):
2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableInstallMatchingByInstanceId set" did not pass as it returned false and true was expected.
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Skipping property ArgRSInstanceId of class: SetFeatureInstallStateAction
2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s):
2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableInstallMatchingByInstanceId set" did not pass as it returned false and true was expected.
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Running Action: SetFeatureInstallStateAction
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_Cpu32: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_fulltext_Cpu32: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_Cpu32: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_Cpu32: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_spi_Cpu32: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_rs_Cpu32: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_rs_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_rs_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_rs_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_Cpu32: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_Cpu32: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_bids_Cpu32: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_bids_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_bids_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_Cpu32: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_Cpu32: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:29 Slp: Error: Action "Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction" threw an exception during execution.
2014-09-20 07:50:29 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Value cannot be null.
2014-09-20 07:50:29 Slp: Parameter name: productVersion ---> System.ArgumentNullException: Value cannot be null.
2014-09-20 07:50:29 Slp: Parameter name: productVersion
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion(String value)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallPropertyByProductCode(PackageInstallProperty pkg, String prodCode)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallProperty(PackageInstallProperty pkg)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.ExecuteAction(String actionId)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2014-09-20 07:50:29 Slp: --- End of inner exception stack trace ---
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2014-09-20 07:50:29 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
2014-09-20 07:50:29 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Value cannot be null.
2014-09-20 07:50:29 Slp: Parameter name: productVersion ---> System.ArgumentNullException: Value cannot be null.
2014-09-20 07:50:29 Slp: Parameter name: productVersion
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion(String value)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallPropertyByProductCode(PackageInstallProperty pkg, String prodCode)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallProperty(PackageInstallProperty pkg)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.ExecuteAction(String actionId)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2014-09-20 07:50:29 Slp: --- End of inner exception stack trace ---
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-09-20 07:50:33 Slp: Received request to add the following file to Watson reporting: C:\Users\Kimi Raikkonen\AppData\Local\Temp\tmpB4ED.tmp
2014-09-20 07:50:33 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2014-09-20 07:50:33 Slp: Inner exceptions are being indented
2014-09-20 07:50:33 Slp:
2014-09-20 07:50:33 Slp: Exception type: System.ArgumentNullException
2014-09-20 07:50:33 Slp: Message:
2014-09-20 07:50:33 Slp: Value cannot be null.
2014-09-20 07:50:33 Slp: Parameter name: productVersion
2014-09-20 07:50:33 Slp: Stack:
2014-09-20 07:50:33 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion(String value)
2014-09-20 07:50:33 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallPropertyByProductCode(PackageInstallProperty pkg, String prodCode)
2014-09-20 07:50:33 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallProperty(PackageInstallProperty pkg)
2014-09-20 07:50:33 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.ExecuteAction(String actionId)
2014-09-20 07:50:33 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2014-09-20 07:50:33 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2014-09-20 07:50:43 Slp: Watson Bucket 1
Original Parameter Values
2014-09-20 07:50:43 Slp: Parameter 0 : SQL Server 2008 R2@RTM@
2014-09-20 07:50:43 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion
2014-09-20 07:50:43 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion
2014-09-20 07:50:43 Slp: Parameter 3 : System.ArgumentNullException@-2147467261
2014-09-20 07:50:43 Slp: Parameter 4 : System.ArgumentNullException@-2147467261
2014-09-20 07:50:43 Slp: Parameter 5 : SetFeatureInstallStateAction
2014-09-20 07:50:43 Slp:
Final Parameter Values
2014-09-20 07:50:43 Slp: Parameter 0 : SQL Server 2008 R2@RTM@
2014-09-20 07:50:43 Slp: Parameter 1 : 0x2AA348CC
2014-09-20 07:50:43 Slp: Parameter 2 : 0x2AA348CC
2014-09-20 07:50:43 Slp: Parameter 3 : 0xF15156D0
2014-09-20 07:50:43 Slp: Parameter 4 : 0xF15156D0
2014-09-20 07:50:43 Slp: Parameter 5 : SetFeatureInstallStateAction
2014-09-20 07:50:43 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\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_, Win32 error
2
2014-09-20 07:50:43 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\20140920_074907\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_, Win32 error 2
2014-09-20 07:50:44 Slp: Value cannot be null.
Parameter name: productVersion
2014-09-20 07:50:44 Slp: Watson bucket for exception based failure has been created
2014-09-20 07:50:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey
2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2014-09-20 07:50:44 Slp: Sco: Attempting to get registry value DW0200
2014-09-20 07:50:46 Slp: Submitted 1 of 1 failures to the Watson data repository
2014-09-20 07:50:46 Slp:
2014-09-20 07:50:46 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:46 Slp:
2014-09-20 07:50:46 Slp: Error result: 1269611253
2014-09-20 07:50:46 Slp: Result facility code: 940
2014-09-20 07:50:46 Slp: Result error code: 478612014-09-20 07:50:43 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\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_, Win32
error 2
2014-09-20 07:50:43 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\20140920_074907\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_, Win32 error 2
2014-09-20 07:50:44 Slp: Value cannot be null.
Parameter name: productVersion
2014-09-20 07:50:44 Slp: Watson bucket for exception based failure has been created
2014-09-20 07:50:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey
2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2014-09-20 07:50:44 Slp: Sco: Attempting to get registry value DW0200
2014-09-20 07:50:46 Slp: Submitted 1 of 1 failures to the Watson data repository
2014-09-20 07:50:46 Slp:
2014-09-20 07:50:46 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:46 Slp:
2014-09-20 07:50:46 Slp: Error result: 1269611253
2014-09-20 07:50:46 Slp: Result facility code: 940
2014-09-20 07:50:46 Slp: Result error code: 47861
Hi,
For above error the error code is 2 which means system cannot find the file specified. It is saying it is unable to write at location which means SQL server account does not have access to
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
You can manually go to the location and add required rights may be installable is corrupt
Now did you ran SQL server setup as administrator. Always right click on setup.exe file and select run as administrator.
Please make sure you disable antivirus running on machine. Also if you have any registry scanner software which scans registry remove it as well.
Below thread might be helpful
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/d425791a-9a7c-4c16-9e93-d348ecde3a3f/sql-server-2008-r2-install-fails-on-win-2008-r2-x64-std-server-with-workflowxmltext-msg-error-help?forum=sqlsetupandupgrade
Can you also post summary.txt file
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles -
SSPI handshake error in SQL Server 2008 with SharePoint 2010
Hi,
I am having some trouble with my SharePoint database server this time. SharePoint Server 2010 is running on Windows Server 2008 R2 and SQL Server 2008 is running on Windows Server 2008 R2 as SharePoint database also. SharePoint users are authenticated through
Active Directory. I am getting the following error almost everyday in SQL Server-
SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure.
[CLIENT: (Server IP Address)].
Could somebody help me to resolve this error?
Thanks in advance.Hi pointtoshare,
No, a Service Principal Name (SPN) must be registered with Active Directory to use Kerberos authentication with SQL Server and not need to use NTLM authentication.
Could you run the following query on your SharePoint Server and check the value of the auth_scheme column?
SELECT auth_scheme FROM sys.dm_exec_connections WHERE session_id = @@spid ;
Edit:The
query above should run on the SharePoint machine with using SQL Management Studio.
Best Regards,
Eric
Eric Tao
TechNet Community Support -
"a network related or instance specific error in sql server 2008..." error in sbs 2011 standard.
Hi All,
When we try to open "Sql Server 2008 R2" in SBS 2011.......... we are getting the error message" “A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify
that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified) ”
How can we resolve the issue?
Thanks in advance.
Ram.
RamakrishnaHi Ram, you can check the solutions in the following links and see if that helps:
A network-related or instance-specific error occurred while establishing a connection to SQL Server
http://social.technet.microsoft.com/wiki/contents/articles/a-network-related-or-instance-specific-error-occurred-while-establishing-a-connection-to-sql-server.aspx
A network-related or instance-specific error occurred while establishing a connection to SQL Server
http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/3a1c4d72-300c-4f9b-a0ac-23027ce04d1c/
Also, rather than a SBS specific issue, it seems only relate to SQL server, you can also post it to SQL server forum so that SQL server experts there can provide more accurate solutions:
http://social.technet.microsoft.com/Forums/en-US/category/sqlserver
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
Error installing sql server 2008 management studio express
Hello,
I need to install sql server 2008 management studio express on a sql server 2k8 R2 instance.
First of all, I've downloaded this one from this link: http://www.microsoft.com/en-us/download/details.aspx?id=7593 (for 32 bits).
Once I've the downloaded file I run this file and choose the first option (New sql server stand-alone...) in the installation part. Finally, in the installation type I choose the option 'Add features to an existing instance of SQL Server 2008' with the instance
selected. I push Next and then I get the following error: 'The instance ID is required but it is missing'.
Can anybody help me?
Thanks a lot.
Regards.Hello,
What’s the edition of the SQL Server 2008 R2? If you had installed SQL Server 2008 R2 Developer edition, you should install “SQL Server 2008 Express with Tools” edition or “SQL Server 2008 Express with Advanced Services” edition.
Please refer to the following article for more information:
http://www.benlittler.com/2009/06/how-to-install-sql-management-studio-express-2008/
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support -
I have seen this error posted on msdn before but this seems to be a bit different. Same story. When I exec a SSIS package in BIDS it succeeds. When I run it as an agent job it fails with the error "Option -Daily" is not
valid.
Here is the script that SQL Server "New Job" wizard created.
/FILE "C:\Development\SSIS\Daily Report\bin\Daily Report.dtsx" /CONNECTION FlatFile2; "C:\Development\SSIS\Daily Report\base_daiily.csv" /CONNECTION "localhost.database";"\"Data Source=localhost;Initial Catalog=database;Integrated
Security=True;Application Name=""SSIS-Daily Report-{5786B48C-481E-9951-B486486231AF}localhost.database"";\CHECKPOINTING OFF /REPORTING E
I had to clean the above up a little bit to block restricted information. The error suggests that SQL Server is having problems parsing the string the wizard created. Any thoughts regarding what is occuring here.
Just my thoughts tomhwhy would you use new job wizard?
Just create the new job and a new SSIS step in it.
The error message looks like too abridged, but the issue actually might be with the parts
Application Name=""SSIS ...tabase"";\CH
Quotes after quotes
Arthur
MyBlog
Twitter -
Bcp error with SQL Server 2008
In working through the 70-432 training material, I have entered the follwing:
bcp AdventureWorks
.HumanResources.Department out
c:
\test/department.txt -c -S HOME -T
I receive the error message -- Could not find stored procedure'bcp'.
and a syntax error after c: What am I missing?Where are you entering these commands?
BCP is a command line program. NOte that there is a typo in teh code you pasted and is your server name HOME?
bcp AdventureWorks.HumanResources.Department out c:\test\department.txt -c -S HOME -T
Refer below for more details.
http://msdn.microsoft.com/en-us/library/ms162802.aspx| Sankar Reddy | http://sankarreddy.spaces.live.com/ | -
HI,
I have installed Cumulative Update 12 for SQL Server 2008 R2 SP2 on my SharePoint instances. This was to resolve a known issue faced with the instance. CU12 helped resolve the issue. My company is rather strict regarding security hotfixes. But I am
not sure if this particular hotfix [Security Hotfix (KB2977319)] is required if the instance has CU12 applied.
Tested this on a Lab server, the installation did run fine, the summary log also stated that the KB is applied. But the Build Number did not change. Hence the doubt.
Overall summary:
Final result: Passed
Exit code (Decimal): 0
Exit message: Passed
Start time: 2014-09-06 10:31:21
End time: 2014-09-06 10:55:49
Requested action: Patch
Instance SPNTSQLTRN overall summary:
Final result: Passed
Exit code (Decimal): 0
Exit message: Passed
Start time: 2014-09-06 10:48:08
End time: 2014-09-06 10:55:45
Requested action: Patch
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 2
KBArticle: KB2977319
KBArticleHyperlink: http://support.microsoft.com/?kbid=2977319
PatchType: QFE
AssociatedHotfixBuild: 0
Platform: x64
PatchLevel: 10.52.4321.0
ProductVersion: 10.52.4000.0
GDRReservedRange: 10.50.4001.0:10.50.4199.0;10.50.4200.0:10.50.4250.0
PackageName: SQLServer2008-KB2977319-x64.exe
Installation location: e:\ac2af22d88ee645b5b32b5c178\x64\setup\
Please inform if I need to apply the hotfix on CU12. Thanks in advance.
John SYes you must install Security update mentioned in KB 2977319 it is important for SQL Server to be patches with this security update. Without this it could allow an attacker to compromise your system and gain control over it.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles -
Service-specific error code -2146885628- MS SQL Server 2008 r2 Express
I have had no end of problems starting my MS SQL Server 2008 r2 Express.
My database program (Sage ACT! Pro 2011) starts fine. However when it attempts to start my default database, I get the following error message:
When I start my database within my application software (ACT Pro 2011) , I get the following error:
I am not abler to open any database with in ACT 2011. This error tells me that I must manually start SQL Server. I am running Windows 7 Pro, SP1. So I go to Services, and right click on SQL Server (ACT7) and click start and get the following error:
I have contacted Swiftpage and spent 2 hours on the phone with their technical support. They manually (via remote desktop connection) deleted ACT Pro 2011 and manually deleted SQL Server 2008 r2 Express (in registry and all files and folders).
I decided to upgrade, so ACT Pro v16 was installed. SQL Server still would not start automatically or manually. The ACT technical support person, after two very long hours said: that it is not an ACT problem, that I would need to turn to Microsoft for
a resolution as to why SQL Server will not start, and how to remedy this issue.
I hope someone can offer help or point me in the direction to get this very bad problem resolved. I cannot work without my CRM! can someone help?
Thanks!This is the sum total of an error log in: C:\Program Files\Microsoft SQL Server\MSSQL10_50.act7\MSSQL\Log. There are no error logs for June 23 to July 14. This is the closest
date to the first time I experienced this SQL Server problem.
2014-07-15 09:32:43.31 Server Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)
Jun 28 2012 08:36:30
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2014-07-15 09:32:44.12 Server (c) Microsoft Corporation.
2014-07-15 09:32:44.12 Server All rights reserved.
2014-07-15 09:32:44.12 Server Server process ID is 2276.
2014-07-15 09:32:44.15 Server System Manufacturer: 'TOSHIBA', System Model: 'Satellite L775D'.
2014-07-15 09:32:44.27 Server Authentication mode is MIXED.
2014-07-15 09:32:44.27 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\Log\ERRORLOG'.
2014-07-15 09:32:44.63 Server This instance of SQL Server last reported using a process ID of 6980 at 7/15/2014 9:13:22 AM (local) 7/15/2014 1:13:22 PM (UTC). This is an informational message only; no user action is required.
2014-07-15 09:32:44.63 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\DATA\mastlog.ldf
2014-07-15 09:32:46.39 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-07-15 09:32:46.40 Server Detected 4 CPUs. This is an informational message; no user action is required.
2014-07-15 09:33:00.47 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.
2014-07-15 09:33:33.57 Server Node configuration: node 0: 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.
2014-07-15 09:33:37.59 spid7s Starting up database 'master'.
2014-07-15 09:33:40.89 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'ACT7'.
2014-07-15 09:33:42.39 spid7s SQL Trace ID 1 was started by login "sa".
2014-07-15 09:33:42.56 spid7s Starting up database 'mssqlsystemresource'.
2014-07-15 09:33:42.86 spid7s The resource database build version is 10.50.4000. This is an informational message only. No user action is required.
2014-07-15 09:33:46.59 spid10s Starting up database 'model'.
2014-07-15 09:33:46.58 spid7s Server name is 'Harold_Schultz\ACT7'. This is an informational message only. No user action is required.
2014-07-15 09:33:46.59 spid10s Error: 17204, Severity: 16, State: 1.
2014-07-15 09:33:46.59 spid10s FCB::Open failed: Could not open file e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2014-07-15 09:33:46.85 spid7s Informational: No full-text supported languages found.
2014-07-15 09:33:46.85 spid10s Error: 5120, Severity: 16, State: 101.
2014-07-15 09:33:46.85 spid10s Unable to open the physical file "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2014-07-15 09:33:46.85 spid7s Starting up database 'msdb'.
2014-07-15 09:33:46.85 spid7s Error: 17204, Severity: 16, State: 1.
2014-07-15 09:33:46.85 spid7s FCB::Open failed: Could not open file e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2014-07-15 09:33:46.85 spid7s Error: 5120, Severity: 16, State: 101.
2014-07-15 09:33:46.85 spid7s Unable to open the physical file "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2014-07-15 09:33:47.04 Server Warning: Support for the VIA protocol is deprecated and will be removed in a future version of Microsoft SQL Server. If possible, use a different network protocol and disable VIA.
2014-07-15 09:33:47.33 Server Virtual Interface Architecture protocol is not supported for this particular edition of SQL Server.
2014-07-15 09:33:48.03 spid7s Error: 17207, Severity: 16, State: 1.
2014-07-15 09:33:48.03 spid7s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2014-07-15 09:33:48.04 spid10s Error: 17207, Severity: 16, State: 1.
2014-07-15 09:33:48.04 spid10s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose
and correct the operating system error, and retry the operation.
2014-07-15 09:33:48.08 spid7s File activation failure. The physical file name "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.
2014-07-15 09:33:48.08 spid10s File activation failure. The physical file name "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2014-07-15 09:33:48.15 spid10s Error: 945, Severity: 14, State: 2.
2014-07-15 09:33:48.15 spid10s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2014-07-15 09:33:48.38 spid10s 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.
2014-07-15 09:33:48.39 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2014-07-15 09:33:48.38 Server Error: 17190, Severity: 16, State: 1.
2014-07-15 09:33:48.38 Server Initializing the FallBack certificate failed with error code: 1, state: 1, error number: -2146893802.
2014-07-15 09:33:48.42 Server Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-07-15 09:33:48.44 Server Error: 17182, Severity: 16, State: 1.
2014-07-15 09:33:48.44 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2014-07-15 09:33:48.44 Server Error: 17182, Severity: 16, State: 1.
2014-07-15 09:33:48.44 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2014-07-15 09:33:48.44 Server Error: 17826, Severity: 18, State: 3.
2014-07-15 09:33:48.44 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-07-15 09:33:48.44 Server Error: 17120, Severity: 16, State: 1.
2014-07-15 09:33:48.44 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems. -
I ran into erro 3241 when you run RESTORE FILELISTONLY statement in SQL Server 2008 R2.
Found the hotfix
Cumulative Update 13 for SQL Server 2008 R2 SP1.
I have installed this hotfix, now running 10.50.2876.0
But I still get the same error when trying to restore a backup.
What else do I need to do?second to what bodo said Instead of installing SQL server 2012 SP1 CU13 it would be better to install
SQL Server 2008 r2 Sp2 SP's are more throughly tested and would include all fixes for CU and Sp1
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles
Maybe you are looking for
-
I created multiple libraries and multiple locations for music of different genres; however, in the end I decided that I wanted to keep all of my music in one location and to have just one iTunes library. The problem is that when I go to delete a son
-
GR Qty more than Delivery Qty in Production Order
Hi there are a amazing Production order that GR Qty more than Delivery Qty of finished goods in this production order. there are some data in this production order as below: Order Qty = 2680 Delivery Qty = 2680 Tolerance = 0 However, to my surprise,
-
ABAP QUERY: Selection text name change : seq. of column sequence in output
hi friends, 1)I need to change the text of the selection field in ABAP QUERY REPORT please help me. t code: SQ03 : User Group(zabc) and report name (zabc). Environment -> infosets. in the field group, double click field name to be changed. I tried to
-
After updating to 8.1 from 8 i cannot return to my message list from inside a message without clicking on the "compose new message" icon and then canceling out of that. Also, where it used to say return, it now says "Edit" and the word "Message" on t
-
Hello I was wondering if someone can help me with the syntax error, or if someone can give an example how to implement dynamic query based on a select list item. Last night I was looking how to implement simple PL/SQL report using Oracle Apex source