SQL Server 2008 R2 & 2008 R2 SP1 installation fails in Windows server 2012
Hi All,
I have a strange issue here. I have a Windows server 2012 VM where i want to deploy SQL 2008 R2 Enterprise edition.
When i Run the setup every thing goes fine and during the installation wizard i get this error " The Folder path Program files contains invalid characteristics. I get this error 3 - 4 times during the installation wizard and the installation fails.
Below is the screenshot for the same.
So i checked few articles regarding the compatibility issue and found the below article and upgraded my setup to SQL 2008 R2 SP1 using the below article.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
Again i still see the same above errors and with that a new error related to a MOF File.
Below are the contents of the error logs. Can some one assist on this issue.
======================================================
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): -2068052692
Exit facility code: 1212
Exit error code: 1324
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: 2015-01-15 13:53:03
End time: 2015-01-15 14:04:29
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0xA60E3551%400xD3BEBD98%401211%401
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
Installation location: D:\SQLServer2008R2_SP1\x64\setup\
Installation edition: ENTERPRISE
Slipstream: True
SP Level 1
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: E2KLAB\SCOMAC
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
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: Automatic
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE: D:\SQLServer2008R2_SP1\SP
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: E2KLAB\SCOMAC
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: E2KLAB\SCOMAC
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr,E2KLAB\SCOMAC,E2KLAB\SCOM Admins
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\sql_common_core_loc_Cpu64_1033_1.log
MSI error description: The folder path 'Program Files' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\SystemConfigurationCheck_Report.htm
Gautam.75801
Hi Alberto,
Still the same issue.
I installed the SQL 2008 R2 without SP1 and changed the service accounts to system account and repaired the .NET using the .NET Repair tool
Also changed the installation directory to D:\ Drive this time. Still same issue.
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): -2068052692
Exit facility code: 1212
Exit error code: 1324
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: 2015-01-15 22:55:37
End time: 2015-01-15 23:07:32
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SQLSysClrTypes_Cpu64_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 1
Installation location: D:\SQL Server 2008 R2 Datacenter edition for only Windows server 2008 R2\x64\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
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\20150115_225416\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: D:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: D:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: D:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SystemConfigurationCheck_Report.htm
Any other suggestion i can try ?
Gautam.75801
Similar Messages
-
SQL Server 2008 Express SP1 installation failed
Hello guys,
System Info:
Windows 7 64Bit.
Scenario: I have an application, while installation it installs SQLServer 2008 instance with some xyz database name.
Issue: The system already has the SQLServer 2008 R2, and now I am trying to install the application but the SQLServer instance of my application is not getting installed, its giving error saying that the installation failed.
The error code is :
0x84B40000
The below is the log file data.
07/07/2014 16:15:14.283 ======================================================================
07/07/2014 16:15:14.283 Setup launched
07/07/2014 16:15:14.298 Attempting to determine media source
07/07/2014 16:15:14.298 Media source value not specified on command line argument.
07/07/2014 16:15:14.298 Setup is launched from media directly so default the value to the current folder.
07/07/2014 16:15:14.298 Media source: c:\80424454fe36892978\
07/07/2014 16:15:14.298 Attempt to determine media layout based on file 'c:\80424454fe36892978\mediainfo.xml'.
07/07/2014 16:15:14.361 Media layout is detected as: Core
07/07/2014 16:15:14.361 Media LCID is detected as: 1033
07/07/2014 16:15:14.361 Media is a slipstream package
07/07/2014 16:15:14.361 Only patch related actions can run patch setup.exe, so continuing to run setup.exe from media.
07/07/2014 16:15:14.361 /? or /HELP or /ACTION=HELP specified: false
07/07/2014 16:15:14.361 Help display: false
07/07/2014 16:15:14.361 Checking to see if we need to install .Net version 2.0
07/07/2014 16:15:14.376 Determining the cluster status of the local machine.
07/07/2014 16:15:14.376 The local machine is not configured as a cluster node.
07/07/2014 16:15:14.376 Attempting to find media for .Net version 2.0
07/07/2014 16:15:14.376 .Net version 2.0 is installed
07/07/2014 16:15:14.376 RedistMSI::GetExpectedBuildRevision - Setup expects MSI 4.5.6001.22159 at the minimum
07/07/2014 16:15:14.376 Attempting to get Windows Installer version
07/07/2014 16:15:14.376 Windows Installer version detected: 5.0.7601.17807
07/07/2014 16:15:14.376 RedistMSI::IsVistaRTM - Not Vista RTM build
07/07/2014 16:15:14.392 Required version of Windows Installer is already installed
07/07/2014 16:15:14.392 Current running setup.exe full path: c:\80424454fe36892978\setup.exe
07/07/2014 16:15:14.392 Media setup.exe file version detected: 2007.100.2731.23
07/07/2014 16:15:14.392 Locally installed setup.exe full path: c:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Release\setup.exe
07/07/2014 16:15:14.408 Local setup.exe file version detected: 2007.100.2731.23
07/07/2014 16:15:14.408 Local setup.exe version 2007.100.2731.23 is equal or greater than media version 2007.100.2731.23, so re-launching setup.exe from local
07/07/2014 16:15:14.408 Media source: c:\80424454fe36892978\
07/07/2014 16:15:14.408 Install media path: c:\80424454fe36892978\x86\setup\
07/07/2014 16:15:14.423 Media layout: Core
07/07/2014 16:15:14.423 Attempting to get execution timestamp
07/07/2014 16:15:14.423 Timestamp: 20140707_161514
07/07/2014 16:15:14.439 Attempting to launch local setup.exe
07/07/2014 16:15:14.439 Attempting to launch process c:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Release\setup.exe
07/07/2014 16:15:38.962 Process returned exit code: 0x84B40000
07/07/2014 16:15:38.962 Local setup.exe returned exit code: 0x84B40000
07/07/2014 16:15:38.962 Setup closed with exit code: 0x84C40013
07/07/2014 16:15:38.962 ======================================================================
Please do reply if anyone knows how to fix this issue.
Thanks,
Shiv
0x84B40000Hi,
You can install SQL server express 2008 on machine having SQL Server 2008 r2 is supported. From what you posted I guess SQL server 2008 r2 is default instance so you need to install SQL server 2008 express SP1 as named instance. Your error matches problem
mentioned in below thread
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/1e8cfab3-4b99-4b4d-82bf-97799dabe34c/failure-when-installing-from-command-prompt-config-file?forum=sqlexpress
If issue is not solved please post complete log files from location
%programfiles%\Microsoft SQL Server\100\Setup Bootstrap\Log\.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles -
Windows 2008 r2 SP1 installation failed with unspecified error 0x80004005 - E_FAIL
Hi Team,
We have SQL data base server with Win 2008 r2 OS.When trying install Sp1 it fails after reboot with unspecified error -0x80004005 - E_FAIL.
Server having snap drive connected with 6 SQL data bases. Sp1 installation running 7 hrs and falling after couple of reboot.
Any help appreciated.CBS log attached.
================================ 2015-01-24 18:48:22, Info CBS Starting TrustedInstaller initialization. 2015-01-24 18:48:22, Info CBS Loaded Servicing Stack v6.1.7601.17514 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\cbscore.dll
2015-01-24 18:48:23, Info CSI 00000001@2015/1/24:18:48:23.137 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee8d4e94d @0x7fee9079839 @0x7fee90434d3 @0xff03e94c @0xff03d769 @0xff03daff) 2015-01-24 18:48:23, Info CBS Could not load SrClient DLL
from path: SrClient.dll. Continuing without system restore points. 2015-01-24 18:48:23, Info CSI 00000002@2015/1/24:18:48:23.139 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee8d4e94d @0x7fee90c6806 @0x7fee9092a9c @0x7fee90435a9 @0xff03e94c @0xff03d769)
2015-01-24 18:48:23, Info CSI 00000003@2015/1/24:18:48:23.139 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee8d4e94d @0x7fee9988728 @0x7fee9988856 @0xff03e444 @0xff03d7ae @0xff03daff) 2015-01-24 18:48:23, Info CBS Ending TrustedInstaller initialization.
2015-01-24 18:48:23, Info CBS Starting the TrustedInstaller main loop. 2015-01-24 18:48:23, Info CBS TrustedInstaller service starts successfully. 2015-01-24 18:48:23, Info CBS SQM: Initializing online with Windows opt-in: False 2015-01-24 18:48:23, Info CBS
SQM: Cleaning up report files older than 10 days. 2015-01-24 18:48:23, Info CBS SQM: Requesting upload of all unsent reports. 2015-01-24 18:48:23, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT
= 0x80004005 - E_FAIL] 2015-01-24 18:48:23, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL] 2015-01-24 18:48:23, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6 2015-01-24
18:48:23, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL] 2015-01-24 18:48:23, Info CBS No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending. 2015-01-24
18:48:23, Info CBS NonStart: Checking to ensure startup processing was not required. 2015-01-24 18:48:23, Info CSI 00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x136f6c0
2015-01-24 18:48:23, Info CSI 00000005 Creating NT transaction (seq 1), objectname [6]"(null)" 2015-01-24 18:48:23, Info CSI 00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x23c 2015-01-24 18:48:23, Info CSI 00000007@2015/1/24:18:48:23.144
CSI perf trace: CSIPERF:TXCOMMIT;1211 2015-01-24 18:48:23, Info CBS NonStart: Success, startup processing not required as expected. 2015-01-24 18:48:23, Info CBS Startup processing thread terminated normally 2015-01-24 18:48:23, Info CSI 00000008 CSI Store
3877440 (0x00000000003b2a40) initialized 2015-01-24 18:48:23, Info CBS Session: 30423046_1416810351 initialized by client RMT. 2015-01-24 18:48:24, Info CSI 00000009@2015/1/24:18:48:24.057 CSI Transaction @0x1761b90 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195}
with flags 00000002 and client id [26]"TI5.30423046_1416810351:1/" 2015-01-24 18:48:24, Info CSI 0000000a@2015/1/24:18:48:24.059 CSI Transaction @0x1761b90 destroyed 2015-01-24 18:48:24, Info CBS Appl: DetectUpdate, Package: Microsoft-Windows-SecureStartup-OC-Package~31bf3856ad364e35~amd64~~6.1.7600.16385,
Remote Parent: DirectoryServices-DomainController-Tools, Intended State: Staged 2015-01-24 18:48:24, Info CBS Appl: DetectUpdate, Package: Microsoft-Windows-SecureStartup-OC-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, Remote Parent: DirectoryServices-DomainController-Tools,
Intended State: Staged 2015-01-24 18:48:24, Info CBS Appl: Evaluating applicability block(detectUpdate part), disposition is: Staged, applicability: NotApplicable, result applicability state: Staged 2015-01-24 18:48:24, Info CBS Appl: Package: Microsoft-Windows-SecureStartup-OC-Package~31bf3856ad364e35~amd64~~6.1.7600.16385,
Update: BdeAducExtTool, Applicable: NeedsParent, Dis 2015-01-24 18:48:24, Info CBS Appl: DetectUpdate, Package: Microsoft-Windows-WMI-SNMP-Provider-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, Remote Parent: SNMP, Intended State: Installed 2015-01-24 18:48:24,
Info CBS Appl: Evaluating applicability block(detectUpdate part), disposition is: Staged, applicability: Applicable, result applicability state: Installed 2015-01-24 18:48:24, Info CBS Appl: Package: Microsoft-Windows-WMI-SNMP-Provider-Package~31bf3856ad364e35~amd64~~6.1.7600.16385,
Update: WMISnmpProvider, Applicable: Applicable, Dis 2015-01-24 18:48:24, Info CBS Appl: DetectUpdate, Package: Microsoft-Windows-IIS-WebServer-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, Local Parent: IIS-WebServerRole, Intended State: Staged 2015-01-24
18:48:24, Info CBS Appl: Evaluating applicability block(detectUpdate part), disposition is: Staged, applicability: NotApplicable, result applicability state: Staged 2015-01-24 18:48:24, Info CBS Appl: Package: Microsoft-Windows-IIS-WAppreciate your suggestion Dave,
Any idea what could be cause of this failure.?Do you see anything from the CBS logs.
This server attached with SNAP drive luns,is there something or SQL application preventing this installation ?
After reboot it revert the installation...it shows "Failure config service pack..reverting changes,do not not turn off your computer".
Surprisingly it happens both of our SQL data base server.
Do you think Increasing MaxNumFilters to
14 shall work ?
=====================
=================================CheckSUR.Log==========
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-02-01 09:37
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 555
No errors detected -
Unable to upgrade SQL Server 2008 R2 to SQL Server 2012 SP1
I'm encountering error after error, after successfully installing the upgrade advisor (which took some doing) and running it with essentially no warnings/errors (the one warning was on the connection strings, as I recall -- and all of the warnings had a
"fix after" status.
First failure involved SSRS and the inability to create the "managed account". Backed out the upgrade using http://sqldbanotes.blogspot.com/2013/10/how-to-fix-failed-in-place.html
Now the failure involves SSAS and unable to connect to analysis services with name MSSQLServerOLAPService. That is the logical name for the service, although it shows up as just MSSQLServer when looking at it in the services list. I tried
setting the service account to a local account as well as to Local System -- did not make a difference, the upgrade couldn't apparently find it regardless.
Has anybody successfully done an in place upgrade from SQL Server 2008 R2 to SQL Server 2012?Hi Bob,
Thanks for your post and I am glad to hear that the issue is resolved. Thanks for you posting a reply to share your solution and I had marked it as answer. That way, other community members could benefit from your sharing.
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support -
SQL Server 2012 DB Engine does not start (clean install with server 2012 and 2008 R2)
I'm trying to do clean installation of SQL server 2012 on Server 2012 (which is runnning as a VM on ESX server) and getting this "wait on the DB engine recovery failed" message. Initially, I though this issue was related to some permission issues
but changing the permission or service accounts didn't help. I'm not seeing any "denied" messages in the log files either. Even with Server 2008 R2 (clean built VM), the installation gives the exactly the same error messages.
My setup is purely for test purpose; so, the security is not a concern. Can someone help or give me a clue where to look?
(Summary)
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2014-05-28 17:12:12
End time: 2014-05-28 17:19:47
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: WIN-1V3VKPV5Q19
Machine processor count: 1
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: E:\x64\setup\
Installation edition: Evaluation
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x64
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x64
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$TESTDB
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: TESTDB
INSTANCENAME: TESTDB
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$TESTDB
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: WIN-1V3VKPV5Q19\Administrator
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\SystemConfigurationCheck_Report.htm
(Error Log)
2014-05-28 17:17:26.64 spid8s 0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2014-05-28 17:17:26.73 spid9s Starting up database 'model'.
2014-05-28 17:17:28.24 spid9s Error: 9004, Severity: 23, State: 6.
2014-05-28 17:17:28.24 spid9s An error occurred while processing the log for database 'model'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
2014-05-28 17:17:28.24 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
(Details)
(01) 2014-05-28 17:17:28 Slp: Exception type: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException
(01) 2014-05-28 17:17:28 Slp: Message:
(01) 2014-05-28 17:17:28 Slp: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
(01) 2014-05-28 17:17:28 Slp: HResult : 0x851a001a
(01) 2014-05-28 17:17:28 Slp: FacilityCode : 1306 (51a)
(01) 2014-05-28 17:17:28 Slp: ErrorCode : 26 (001a)
(01) 2014-05-28 17:17:28 Slp: Data:
(01) 2014-05-28 17:17:28 Slp: SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2014-05-28 17:17:28 Slp: WatsonConfigActionData = INSTALL@CONFIGRC@SQL_ENGINE_CORE_INST
(01) 2014-05-28 17:17:28 Slp: WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2014-05-28 17:17:28 Slp: Stack:
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.ConfigSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean useInstallInputs)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.DoCommonDBStartConfig(ConfigActionTiming timing)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2014-05-28 17:17:28 Slp: Watson Bucket 1
Original Parameter Values
(01) 2014-05-28 17:17:28 Slp: Parameter 0 : SQL Server 2012@RTM@
(01) 2014-05-28 17:17:28 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart
(01) 2014-05-28 17:17:28 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart
(01) 2014-05-28 17:17:28 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
(01) 2014-05-28 17:17:28 Slp: Parameter 6 : INSTALL@CONFIGRC@SQL_ENGINE_CORE_INST
(01) 2014-05-28 17:17:28 Slp:
Final Parameter Values
(01) 2014-05-28 17:17:28 Slp: Parameter 0 : SQL Server 2012@RTM@
(01) 2014-05-28 17:17:28 Slp: Parameter 1 : 0xD15B4EB2
(01) 2014-05-28 17:17:28 Slp: Parameter 2 : 0xD15B4EB2
(01) 2014-05-28 17:17:28 Slp: Parameter 3 : 0x4BDAF9BA@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 4 : 0x4BDAF9BA@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
(01) 2014-05-28 17:17:28 Slp: Parameter 6 : 0x9C5770A6Hi Nababoya:
As you are telling this is a test installation process...
In the logs i m seeing the error message "An error occurred while processing the log for database 'model'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.".
1) If the SQL Services was installed successfully and SQL Service was not able to start because of model database issue...
1.1) If you have model database SQL back file, start the SQL Server in single user mode with minimum configuration and try to restore MODEL database
http://blogs.msdn.com/b/sqlserverfaq/archive/2011/05/11/inf-hey-my-sql-server-service-is-not-starting-what-do-i-do.aspx
1.2) If you don't have backups., try to rebuild the system databases but make sure that you are not losing any data critical data on master and SQL Jobs on MSDB
http://msdn.microsoft.com/en-us/library/dd207003%28v=sql.110%29.aspx#RebuildProcedure
2) As if this is a new installation try to repair the instance with the help of setup media file
3) If the repair option fails., the last option wipe out the complete SQL Server components from Services.msc and Registries and start new installation.
4) Make sure when you are doing un-installation all the required SQL Server components on services.msc should be in stop state.
Hope this helps and let me know any questions...
Thanks,
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :) -
Hi there;
I have a windows server 2008 SP2 (32bits) in which I have an instance of SQL Server
2008 and another of 2012.
My Windows server 2008 installed the following updates; (see below).
(KB2898858),(KB2909921),(KB890830),(KB2898869),(KB2911502),(KB2901126),
(KB2916036),(KB2862973),(KB2901113)
After the machine was re-started, I was not abble to connect
to the instance of SQL Server 2012. I am able
to connect to the instance of SQL Server 2008.
The error message I get when I atemp to connect can be found
at the end of the list of updates below.
Do I need to uninstall an update? if so, which one and how do I do that?
Thanks Gabriel I. Ruiz
Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Vista SP2 and Windows Server 2008 SP2 x86 (KB2898858)
Installation date: 2/12/2014 11:42 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2898858
Cumulative Security Update for Internet Explorer 9 for Windows Server 2008 (KB2909921)
Installation date: 2/12/2014 11:42 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2909921
Windows Malicious Software Removal Tool - February 2014 (KB890830)
Installation date: 2/12/2014 11:41 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/890830
Security Update for Microsoft .NET Framework 4.5.1 on Windows 7, Windows Vista and Windows Server 2008 x86 (KB2898869)
Installation date: 2/12/2014 11:40 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2898869
Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Vista SP2 and Windows Server 2008 SP2 x86 (KB2911502)
Installation date: 2/12/2014 11:36 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2911502
Security Update for Microsoft .NET Framework 4.5.1 on Windows 7, Windows Vista, and Windows Server 2008 x86 (KB2901126)
Installation date: 2/12/2014 11:36 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2901126
Security Update for Windows Server 2008 (KB2916036)
Installation date: 2/12/2014 11:34 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2916036
Security Update for Windows Server 2008 (KB2862973)
Installation date: 2/12/2014 11:34 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2862973
Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Vista SP2 and Windows Server 2008 SP2 x86 (KB2901113)
Installation date: 2/12/2014 11:34 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2901113
===================================
Cannot connect to HAVANA\HAVANA_2012_1ST.
===================================
The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server; the server was too busy
to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
Server Name: HAVANA\HAVANA_2012_1ST
Error Number: 233
Severity: 20
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParserStateObject.SNIWritePacket(SNIHandle handle, SNIPacket packet, UInt32& sniError, Boolean canAccumulate, Boolean callerHasConnectionLock)
at System.Data.SqlClient.TdsParserStateObject.WriteSni(Boolean canAccumulate)
at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode, Boolean canAccumulate)
at System.Data.SqlClient.TdsParser.SendPreLoginHandshake(Byte[] instanceName, Boolean encrypt)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer
timeout)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
No process is on the other end of the pipeHi,
Check if SQL Server service is running fine. I doubt you may have changed the user account password used for SQL Server service. After restarting the machine, you also need to update the user account of SQL Server service in Configuration
Manager. Re-type the user account name and password under Log on tab and see how it helps.
Thanks.
Tracy Cai
TechNet Community Support -
Hi
I'm working on upgrading sharepoint 2010 to sharepoint 2013 with sql server 2008 r2. I've ran into some problems but have been able to get a test farm upgraded. However to run SSRS 2013 it seems Sql Server 2012 Reporting Services are required. Upgrading
to a full sql server 2012 database isn't an option. I know that sql server 2012 reporting services can use sql server 2008 r2 as a catalog and content database so I was wondering could this be a workaround? Importantly would I need a separate machine/virtual
machine to host sql server 2012 reporting services? or could it live on the sql server 2008 r2 machine? Any pointers appreciated. Thanks DanRemember that SSRS must be deployed on the SharePoint server. Having said that, yes you can install SSRS 2012 SP1 on a server running SQL 2008 R2. And yes, you can use 2008 R2 as your Database Engine server while SSRS 2012 SP1 runs on the SharePoint server.
Trevor Seward
Follow or contact me at...
  
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs. -
I have an Script mostly that is generated by SSMS which works with-out issue on SQL Server 2008, but when I attempt to run it on a new fresh install of SQL Server 2012 I get an Msg 8631. Internal error: Server stack limit has been reached. Please look for
potentially deep nesting in your query, and try to simplify it.
The script itself doesn't seem to be all that deep or nested. The script is large 2600 lines and when I remove the bulk of the 2600 lines, it does run on SQL Server 2012. I'm just really baffled why something that SQL Server generated with very
few additions/changes AND that WORKS without issue in SQL Server 2008 R2 would suddenly be invalid in SQL Server 2012
I need to know why my script which is working great on our current SQL Server 2008 R2 servers suddenly fails and won't run on an new SQL Server 2012 server. This script is used to create 'bulk' Replications on a large number of DBs saving a tremendous
amount of our time doing it the manual way.
Below is an 'condensed' version of the script which fails. I have removed around 2550 lines of specific sp_addarticle statements which are mostly just copy and pasted from what SQL Management Studio 'scripted' for me went I when through the Replication
Wizard and told it to save to script.
declare @dbname varchar(MAX), @SQL nvarchar(MAX)
declare c_dblist cursor for
select name from sys.databases WHERE name like 'dbone[_]%' order by name;
open c_dblist
fetch next from c_dblist into @dbname
while @@fetch_status = 0
begin
print @dbname
SET @SQL = 'DECLARE @dbname NVARCHAR(MAX); SET @dbname = ''' + @dbname + ''';
use ['+@dbname+']
exec sp_replicationdboption @dbname = N'''+@dbname+''', @optname = N''publish'', @value = N''true''
use ['+@dbname+']
exec ['+@dbname+'].sys.sp_addlogreader_agent @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1, @job_name = null
-- Adding the transactional publication
use ['+@dbname+']
exec sp_addpublication @publication = N'''+@dbname+' Replication'', @description = N''Transactional publication of database
'''''+@dbname+''''' from Publisher ''''MSSQLSRV\INSTANCE''''.'', @sync_method = N''concurrent'', @retention = 0, @allow_push = N''true'', @allow_pull = N''true'', @allow_anonymous = N''false'', @enabled_for_internet
= N''false'', @snapshot_in_defaultfolder = N''true'', @compress_snapshot = N''false'', @ftp_port = 21, @allow_subscription_copy = N''false'', @add_to_active_directory = N''false'', @repl_freq = N''continuous'', @status = N''active'', @independent_agent = N''true'',
@immediate_sync = N''true'', @allow_sync_tran = N''false'', @allow_queued_tran = N''false'', @allow_dts = N''false'', @replicate_ddl = 1, @allow_initialize_from_backup = N''true'', @enabled_for_p2p = N''false'', @enabled_for_het_sub = N''false''
exec sp_addpublication_snapshot @publication = N'''+@dbname+' Replication'', @frequency_type = 1, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 8,
@frequency_subday_interval = 1, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1
-- There are around 2400 lines roughly the same as this only difference is the tablename repeated below this one
use ['+@dbname+']
exec sp_addarticle @publication = N'''+@dbname+' Replication'', @article = N''TABLE_ONE'', @source_owner = N''dbo'', @source_object = N''TABLE_ONE'', @type = N''logbased'', @description = null, @creation_script =
null, @pre_creation_cmd = N''drop'', @schema_option = 0x000000000803509F, @identityrangemanagementoption = N''manual'', @destination_table = N''TABLE_ONE'', @destination_owner = N''dbo'', @vertical_partition = N''false'', @ins_cmd = N''CALL sp_MSins_dboTABLE_ONE'',
@del_cmd = N''CALL sp_MSdel_dboTABLE_ONE'', @upd_cmd = N''SCALL sp_MSupd_dboTABLE_ONE''
EXEC sp_executesql @SQL
SET @dbname = REPLACE(@dbname, 'dbone_', 'dbtwo_');
print @dbname
SET @SQL = 'DECLARE @dbname NVARCHAR(MAX); SET @dbname = ''' + @dbname + ''';
use ['+@dbname+']
exec sp_replicationdboption @dbname = N'''+@dbname+''', @optname = N''publish'', @value = N''true''
use ['+@dbname+']
exec ['+@dbname+'].sys.sp_addlogreader_agent @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1, @job_name = null
-- Adding the transactional publication
use ['+@dbname+']
exec sp_addpublication @publication = N'''+@dbname+' Replication'', @description = N''Transactional publication of database
'''''+@dbname+''''' from Publisher ''''MSSQLSRV\INSTANCE''''.'', @sync_method = N''concurrent'', @retention = 0, @allow_push = N''true'', @allow_pull = N''true'', @allow_anonymous = N''false'', @enabled_for_internet
= N''false'', @snapshot_in_defaultfolder = N''true'', @compress_snapshot = N''false'', @ftp_port = 21, @allow_subscription_copy = N''false'', @add_to_active_directory = N''false'', @repl_freq = N''continuous'', @status = N''active'', @independent_agent = N''true'',
@immediate_sync = N''true'', @allow_sync_tran = N''false'', @allow_queued_tran = N''false'', @allow_dts = N''false'', @replicate_ddl = 1, @allow_initialize_from_backup = N''true'', @enabled_for_p2p = N''false'', @enabled_for_het_sub = N''false''
exec sp_addpublication_snapshot @publication = N'''+@dbname+' Replication'', @frequency_type = 1, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 8,
@frequency_subday_interval = 1, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1
-- There are around 140 lines roughly the same as this only difference is the tablename repeated below this one
use ['+@dbname+']
exec sp_addarticle @publication = N'''+@dbname+' Replication'', @article = N''DB_TWO_TABLE_ONE'', @source_owner = N''dbo'', @source_object = N''DB_TWO_TABLE_ONE'', @type = N''logbased'', @description = null, @creation_script
= null, @pre_creation_cmd = N''drop'', @schema_option = 0x000000000803509D, @identityrangemanagementoption = N''manual'', @destination_table = N''DB_TWO_TABLE_ONE'', @destination_owner = N''dbo'', @vertical_partition = N''false''
EXEC sp_executesql @SQL
fetch next from c_dblist into @dbname
end
close c_dblist
deallocate c_dblist
George P Botuwell, ProgrammerHi George,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
If you have any feedback on our support, please click
here.
Allen Li
TechNet Community Support -
Problem installing SQL Server 2012 SP1: "managed sql server installer has stopped working"
Hello,
I have a big problem.
I just downloaded SQL Server 2012 SP1 and I only want to install SSMS. The installer always crashes with an error message "managed sql server installer has stopped working".
I already tried all solutions from Google for this problem but nothing works.
Can someone help me plase?
My System: Window 8 Pro with Visual Studio 2012.
Thanks
SvenWould you please uplaod/share SQL Server setup logs
C:\Program
Files\Microsoft
SQL Server\110\Setup
Bootstrap\Log\20130125_133342
to file sharing service like SkyDrive.com
FAQ
Regards,
Ahmed Ibrahim
SQL Server Setup Team
My Blog
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and "Vote as Helpful"
on posts that help you.
This can be beneficial to other community members reading the thread. -
I am investigating the impact of upgrading from SQL Server 2008 R2 to SQL Server 2012. To reduce the impact of the upgrade, I am planning to restore / create our application database onto SQL Server 2012 with compatibility level 100 (SQL Server 2008 and
SQL Server 2008 R2).
Are there any differences in feature support for database running in native mode on SQL Server 2008 R2 vs a database installed on SQL Server 2012 with compatibility level 100 set?Are there any differences in feature support for database running in native mode on SQL Server 2008 R2 vs a database installed on SQL Server 2012 with compatibility level 100 set?
Yes there can be difference and impact there are few features deprecated in SQL Server 2012 you must be aware about that. Please see
Deprecated Database Features in SQL Server 2012
Deprecated SQL Server features in SQL Server 2012
After you migrate database to 2012 please don't move ahead with production unless you have tested your application to new created database
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP -
How to change backend databases sql server 2008 R2 to Sql server 2012 datacenter
Hi
i have current sharepoint 2010 form has backend database is sql server 2008 R2 on windows server 2008 R2 Enterprise
and this form has
1 application server
1 Search server (index server)
1 wfe server ( all web applications are running)
1 databse server
here how i change this form back end to new windows server 2012 and sql server 2012 datacenter
adilInformation on SQL Aliases (using cliconfg.exe):
http://sqlandme.com/2011/05/05/create-sql-server-alias-cliconfg-exe/
You need to migrate content back into the database prior to migration:
http://technet.microsoft.com/en-us/library/ff628255(v=office.14).aspx
http://technet.microsoft.com/en-us/library/ff628257(v=office.14).aspx
Trevor Seward
Follow or contact me at...
  
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs. -
Will the reports developed in sql server 2008 r2 BIDS work when deployed on sql server 2012 reporting manager?
when I check on Microsoft site it says
Reports are not upgraded when you upload a report definition file directly to the report server
or SharePoint site. Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
When you open an .rdl file in Report Designer in SQL Server Data Tools (SSDT), if the report was
created for a previous namespace, Report Designer automatically creates a backup file and upgrades the report to the current namespace.
This is the only way you can upgrade a report definition file.
Now here is another confusing statement which says
You can upload an .rdl file created in an earlier version of Reporting Services to a SQL Server
2012 report server and it is automatically upgraded on first use. The report server stores the report definition file in the original format. The report is automatically upgraded the first time it is viewed, but the stored report definition file remains
unchanged.
All I want to know is if I deploy a rdl made in 2008 r2 to 2012 will it work on the report manager of
2012?
<o:p>
</o:p>
MudassarI have tested this fucntionality and can confirm that ssrs 2008 r2 reports work when you deploy them on new ssrs 2012 report manager .
No Migration is required .
I didnt even moved report server dbs .All I did is just deployed reports on the report manager and it worked .
"You
can upload an .rdl file created in an earlier version of Reporting Services to a SQL Server 2012 report server and it is automatically upgraded on first use. "
Microsoft needs to correct this the documentation is misleading
Mudassar -
Difference between SQL SERVER 2008 & SQL SERVER 2012 & SQL SERVER 2014
Difference between SQL SERVER 2008 & SQL SERVER 2012 & SQL SERVER 2014 ?
What sort of databases do you have OLTP? Data warehouse? What requirements do you have for High Availability?
The main features for SQL 2012/2014, as I see it:
o Support for window functions, which makes it possible to write fast queries for running totals, sliding windows etc.
o Columnstore indexes, which can speed up your data warehouse enormously. But of no interest for OLTP. Only writable in SQL 2014.
o AlwaysOn and Availability Groups, a vastly improve story for high availability and disaster recovery.
o try_convert/try_cast, you can now easily filter out values from a column which does not convert to a number. A small but essential feature.
o In memory-OLTP, a new in-memory engine in SQL 2014. This far with very limited feature set, and quite specialised.
Of the points above, the second and third require Enterprise Edition, the first and fourth are in all editions. For the last, I don't think Microsoft has announced anything yet.
There are also new stuff in the BI area, but that's out of my league.
And, oh, there is a new licensing model - which I think is holding more than one customer back.
Erland Sommarskog, SQL Server MVP, [email protected] -
Change Tracking internals behave differently, SQL Server 2012 vs SQL Server 2008
<original post by Glenn Estrada>
Reposting an issue from Stack Overflow that a coworker and I are dealing with.
In trouble shooting an issue with synchronizing disconnected devices with a central database server using Sync Framework 1.0, we are experiencing a problem after upgrading to SQL Server 2012 on the server. It appears that the CHANGE_TRACKING_MIN_VALID_VERSION
is returning a value 1 higher than it should (or at least than it did prior to the upgrade.)
I have been working thru Arshad
Ali's great walk thru example of how to set up a simple example.
I have run the scripts from #1 thru #5 to insert, delete, and update a row in the Employee table in both a SQL Server 2008 and a 2012 environment.
In 2008, the following statement returns a 0:
SELECT CHANGE_TRACKING_MIN_VALID_VERSION(OBJECT_ID('Employee'))
In 2012, it returns a 1.
In working thru a few more scripts (6-8) in the tests, I set the retention period to 1 minute to hopefully force a cleanup action. I left for the day and apparently it ran overnight.
In the 2008 instance, the CHANGE_TRACKING_CURRENT_VERSION and the CHANGE_TRACKING_MIN_VALID_VERSION are equal (11). In the 2012 instance, the CHANGE_TRACKING_MIN_VALID_VERSION is one higher (12) than the CHANGE_TRACKING_CURRENT_VERSION (11). This could have
an impact to the synchronization process when a database is idle for extended periods of time. And we have found that process could get caught in a loop, especially when the following test is performed to determine if a re-initialization, as opposed to synchronization,
is required:
IF CHANGE_TRACKING_MIN_VALID_VERSION(object_id(N'dbo.Employee')) > @sync_last_received_anchor
RAISERROR (N'SQL Server Change Tracking has cleaned up tracking information for table ''%s''...
Has anyone else experienced this change in behavior? Does anyone have an explanation?<original post by Glenn Estrada>
Reposting an issue from Stack Overflow that a coworker and I are dealing with.
In trouble shooting an issue with synchronizing disconnected devices with a central database server using Sync Framework 1.0, we are experiencing a problem after upgrading to SQL Server 2012 on the server. It appears that the CHANGE_TRACKING_MIN_VALID_VERSION
is returning a value 1 higher than it should (or at least than it did prior to the upgrade.)
I have been working thru Arshad Ali's
great walk thru example of how to set up a simple example.
I have run the scripts from #1 thru #5 to insert, delete, and update a row in the Employee table in both a SQL Server 2008 and a 2012 environment.
In 2008, the following statement returns a 0:
SELECT CHANGE_TRACKING_MIN_VALID_VERSION(OBJECT_ID('Employee'))
In 2012, it returns a 1.
In working thru a few more scripts (6-8) in the tests, I set the retention period to 1 minute to hopefully force a cleanup action. I left for the day and apparently it ran overnight.
In the 2008 instance, the CHANGE_TRACKING_CURRENT_VERSION and the CHANGE_TRACKING_MIN_VALID_VERSION are equal (11). In the 2012 instance, the CHANGE_TRACKING_MIN_VALID_VERSION is one higher (12) than the CHANGE_TRACKING_CURRENT_VERSION (11). This could have
an impact to the synchronization process when a database is idle for extended periods of time. And we have found that process could get caught in a loop, especially when the following test is performed to determine if a re-initialization, as opposed to synchronization,
is required:
IF CHANGE_TRACKING_MIN_VALID_VERSION(object_id(N'dbo.Employee')) > @sync_last_received_anchor
RAISERROR (N'SQL Server Change Tracking has cleaned up tracking information for table ''%s''...
Has anyone else experienced this change in behavior? Does anyone have an explanation?
sql-server sql sql-server-2012 -
SQL Server 2012 Express error 9002 while restoring a backup from 2008
Hi all,
I have installed SQL Server 2012 Express on my laptop operating with win 8. Then I took the backup in my old laptop with SQL Server 2008R Express / Windows 7 and tried to restore it to the new one.
After it restored it produced an error messaging saying that restore failed. The error code was 9002 and it says due to NOTHING. I checked the log file it is a file of 1024 kb size, not big. When I installed the SQL 2012 I disabled the autogrowth of the
log file (exactly same setting as I had with 2008) The log is not big. I tried to further shrink, no change.
Moreover the db is already there with full records, I can manipulate it. Even take a back w/o problems. What is this issue? Is it resolved?
thanksan error messaging saying that restore failed. The error code was 9002
and it says due to NOTHING. I
select *
from sys.messages
where message_id = 9002
=> "The transaction log for database '%ls' is full due to '%ls'. "
Is your disk may low on free space?
Olaf Helper
[ Blog] [ Xing] [ MVP]
Maybe you are looking for
-
How can I remove "Album Artwork" from my iPhone and iPad?
I've posted about this before in other threads, but the silence from Apple has been deafening, Others in the community have agreed with the request but haven't been able to answer it. I thought a thread of its own might get attention, since Apple wo
-
Can I simultaneously configure a device to more than one task?
Can I simultaneously configure a device to more than one task? I am trying to trigger on some of the input data. When I tried to configure the same device to more than one task, I get an error: Error -10408 occurred at Digital Group Config. Possible
-
Reading contents of called standard program
Hi Experts, Calling Program: Zreport Called Program: Standard report (Note: with no Start-of-selection event. So, no Spool!). I need to read the content of one of the intrnal table of the called program inside my Zreport. Kindly guide how can I achie
-
When there is nothing in a particular folder stop with all the activity already!
When I open a folder that has nothing inside it, there are two places on the screen that are whirring non-stop. In the middle of the window, it keeps saying something like "exploring, blah, blah". Also, in the bottom left corner of the window, there
-
Hi technocrakes.. I am a starter in mySAP CRM. I need sum help from u guys.. Can neone send me CRM cookbook?? And if possible Middleware cookbook and PCUI cookbook. thanks, gaurav