LYNC stopped working when i changed the service account for LYNC instance in a cluster. Kindly help.
Thanks,
SKB7.
↧
SQL Server service account change for LYNC Instance
↧
SQL Server 2012 SP1 on Windows Core Operating System
I installed SQL Server 2012 enterprise on Windows 2008 R2 Server core
It installed fine with the RTM version of SQL server 2012.
I then wanted to run the SP1 install. The install ran successfully but the SQL Server build number still shows up as RTM version instead of SP1.
Any suggestions on how to uprade to SQL 2012 SP1 on Windows Core.
thanks in advance
venk
↧
↧
Can we use the same instance name while reinstalling SQL server 2008 r2 ?
I am trying reinstall SQL server 2008 r2 and while creating SQL server instance getting the error SQL server instance already exists as a cluster resource.
↧
2012 SP1 hung. Looks ok after reboot - how can I be sure?
I am running SQL 2012 dev on a Win7 x64 SP1 machine (8GB RAM, plenty of drive space).
I launched the SQL 2012 SP1 install via Windows Update as the only update to apply at 15:29.
At 17:30 I viewed the log files and the last entry was at 15:48
The next morning, there was still no further activity so I rebooted the machine.
I launched SSMS and ran select @@VERSION with the following result:
Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Oct 19 2012 13:38:57
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Local apps connect and run correctly. I have not excercised all items (SSIS, AS, etc. yet) and was hoping I could get some guidance to determine the actual status of all components.
Here are the last few lines from Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20121130_152701\MSSQLSERVER\Detail.txt
(01) 2012-11-30 15:48:06 Slp: Invoking QueryServiceStatusEx Win32 API
(01) 2012-11-30 15:48:06 Slp: Sco: Attempting to close service handle for service MSSQLSERVER
(01) 2012-11-30 15:48:06 Slp: Sco: Attempting to close SC Manager
(01) 2012-11-30 15:48:06 Slp: Sco: Returning service process id 6192
(01) 2012-11-30 15:48:06 Slp: Waiting for nt event Global\sqlserverRecComplete to be created
(01) 2012-11-30 15:48:06 Slp: Waiting for nt event Global\sqlserverRecComplete or sql process handle to be signaled
Here are the last few lines from Windows\Temp\SqlSetup.log
11/30/2012 15:27:02.183 Attempting to launch user requested workflow from media
11/30/2012 15:27:02.183 Media source: d:\f9206b2e021d74585a7f\
11/30/2012 15:27:02.184 Install media path: d:\f9206b2e021d74585a7f\x64\setup\
11/30/2012 15:27:02.184 Media layout: Full
11/30/2012 15:27:02.185 Attempting to get execution timestamp
11/30/2012 15:27:02.185 Timestamp: 20121130_152701
11/30/2012 15:27:02.186 Attempting to run user requested action from media ScenarioEngine.exe
11/30/2012 15:27:02.186 Attempting to launch process d:\f9206b2e021d74585a7f\x64\ScenarioEngine.exe
The folder d:\f9206b2e021d74585a7f\ was not removed (and occupies about 1.1 GB including subfolders).
Here is the version info from the SSMS About dialog:
Microsoft SQL Server Management Studio 11.0.3000.0
Microsoft Analysis Services Client Tools 11.0.3000.0
Microsoft Data Access Components (MDAC) 6.1.7601.17514
Microsoft MSXML 3.0 4.0 6.0
Microsoft Internet Explorer 9.0.8112.16421
Microsoft .NET Framework 4.0.30319.296
Operating System 6.1.7601
So, any guidance to determinig if everything really made it to SP1? I can provide more from any of the log files if needed.
Best,
Scott
↧
Domain, local group, or SID account
Hi,
I need advice on how to correctly apply permissions to a SQL Server instance. Does this sound correct?
1) Apply local permissions to the local group (e.g., SQLServerMSSQLUser$compername$instance) when possible.
2) Apply other local permissions to the service SID (e.g., NT SERVICE\MSSQL$instance).
3) Apply domain level permissions (e.g., remote servers and active directory) to the domain service account.
Is a service SID ever used when setting permissions in AD?
We had a SQL Server failing to use NTLM or Kerberos. The SPNs were wrong. (No idea how that happened.) We fixed them manually. We granted the domain service account the rights to handle the SPN. (Not tested yet.) I'm not an AD person, so I don't know what account is really correct to use in this case.
I also noticed that the service SID value for the SQL service is the same across machines if they have the same instance name. I suppose that if this SID could be used in AD, then it would apply to all servers with that instance name?
Is there an easy way to test if the all the permissions are in place? Our group policy is customized in the OU for SQL Servers so that the local group rights installed by SQL are not removed. (Policy might be okay most of the time, but that does not mean it's been okay all of the time or the machine was not in the wrong OU at some point since the SQL install.)
Can group policy remove rights from a service SID in the same way as other accounts?
Thanks
Randy in Marin
↧
↧
Any reason NOT to only upgrade SSIS, SSRS, and SSAS Servers to 2012 while leaving Database engine at 2008 R2?
Can anyone tell me why it would or would not be a bad idea to only upgrade SSIS, SSRS, and SSAS servers to 2012 while leaving the database engine at 2008 R2?<o:p></o:p>
Due to the changes in licensing I was wondering if this might be a viable option.
Thank you!
<o:p></o:p>
↧
sql server 2008 R2 installation fails
please help me!
i get the below error
SQL Server 2008 R2 Setup has encountered an error.
Problem signature:
Problem Event Name: SQL100MSI
Problem Signature 01: 10.50.2500.0
Problem Signature 02: Unknown
Problem Signature 03: sqlncli.msi
Problem Signature 04: 0x162A16FE
Problem Signature 05: 0x1645
Problem Signature 06: Install_sqlncli
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033
Additional information about the problem:
LCID: 1033
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
i have the following description in the summary
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): -2068052371
Exit facility code: 1212
Exit error code: 1645
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: 2012-12-03 10:42:11
End time: 2012-12-03 10:53:50
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SqlSupport_KatmaiRTM_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: xyz
Machine processor count: 4
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 1
Installation location: SOFTware\MS SQL Server 2008 R2 64bit Ent Edition\x64\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: domain\sqlsvr
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\20121203_104042\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
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: domain\sqlsvr
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: domain\sqlsvr
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: DOMAIN\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\20121203_104042\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\sqlncli_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SqlWriter_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SqlSqmShared_Cpu64_1.log
MSI error description:
Configuration status: Passed
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\sqlncli_Cpu64_1.log
MSI error description:
Configuration status: Passed
Feature: Integration Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\sqlncli_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\OWC11_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\trin_aide_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SSCESqlWbTools_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SSCRuntime_Cpu32_1.log
MSI error description:
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\sqlncli_Cpu64_1.log
MSI error description:
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SQLSysClrTypes_Cpu64_1.log
MSI error description:
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\sqlncli_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\trin_aide_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SSCESqlWbTools_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SSCRuntime_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\BestPracticesPolicies_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\msreportviewer90sp1_Cpu32_1.log
MSI error description:
Configuration status: Passed
Feature: Client Tools SDK
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\sqlncli_Cpu64_1.log
MSI error description:
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\sqlncli_Cpu64_1.log
MSI error description:
Configuration status: Passed
Feature: SQL Server Books Online
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\BOL_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x1645
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121203_104042\SystemConfigurationCheck_Report.htm
Description:
↧
The credentials you provided for analysis services service are invalid. To continue, provide a valid account and password for analysis services service.
Hi
I'm trying to install powerpivot with sharepoint integration mode on a server using sql server 2012 installation wizard.
I type in a domain user name and password and I get the error message :
The credentials you provided for analysis services service are invalid. To continue, provide a valid account and password for analysis services service.
Error result: -2068578304
Result facility code: 1204
Any ideas on how to get around this problem?
I changed my password to s a strong type password. It made no difference.
The server is a domain member server.
↧
Spawned SQL Server 2008 R2 SP2 installation freezes during ExecuteStandardTimingsWorkflow
We have an InstallShield installation package that spawns an installation of MS SQL Server 2008 R2, depending on what components the user selects to install. This has worked fine, but now we need to support Windows Server 2012 and Windows 8, so we want to
distribute SP2 of SQL Server 2008 R2 Express Edition instead of the original SP1. The only difference made to the installation package is to replace the redistributable of SQL Server R2 Express Edition SP1 with SP2. If the SP1 version is used Windows 2012
and Windows 8 will popup a message saying that there is compatibility issues with that version of SQL Server.
When the installation package use SQL SP2 the SQL Server installation starts, extracts files etc and and begins the installation, but then freezes at the step ExecuteStandardTimingsWorkflow displayed in the installer UI.
There is no significant CPU usage and no increase in memory by any process like msiexec or similar and there is no error message displayed.
It is not possible to cancel the installation either (cancel button disabled). Reviewing the SQL Server log files shows the following lines in the Detail_ComponentUpdate log
2012-08-23 08:33:06 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\9.0
2012-08-23 08:33:06 Slp: Sco: Waiting for service 'msiserver' to accept the stop request.
2012-08-23 08:33:06 Slp: Sco: Returning service status Running
2012-08-23 08:33:11 Slp: Sco: Returning service status Running
2012-08-23 08:33:16 Slp: Sco: Returning service status Running <- repeated indefintely until the installer is killed in task manager
When using SP1 the same log files says the following
2012-08-23 11:00:57 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\9.0
2012-08-23 11:00:57 Slp: Sco: Waiting for service 'msiserver' to accept the stop request.
2012-08-23 11:00:57 Slp: Sco: Returning service status Stopped
The problems appears to be that the installer cannot shutdown the msiserver service and just loops indefinitely.
The following conditions apply to all tested machines which is Windows 8, Windows Server 2012 RC, Windows Server 2008 R2
Machine is clean, no existing versions of SQL Server exists prior to installation. All security updates etc. applied.
Logged in user is local administrator.
Installation is successful if the SP1 version of SQL Server 2012 is used instead of the SP2 version
The SP2 version can be installed successfully from the command prompt (run as administrator). In this case I use the following command
line (replaced password with ****):
SQLEXPR_x86_ENU.exe /ACTION=install /INSTANCENAME=PRODACAPO /IACCEPTSQLSERVERLICENSETERMS /HIDECONSOLE /QUIETSIMPLE /SECURITYMODE=SQL /SAPWD=**** /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM"
Display language is US English and SQL Server package is US English. Input/keyboard language is Swedish.
Windows Installer service cannot be shutdown from services as Stop and Restart options are disabled.
No summary.txt file is created when the installation freezes
Are there any changes in the behavior of the installation package from SP1 to SP2? Since SP1 works it seems that InstallShield cannot be blamed for this problem? However, installing from the command prompt works which means that the problem seem to lie in with
how the SQL installation is spawned from InstallShield. Currently this problem is preventing us from supporting Windows Server 2012 and Windows 8 properly.
If you need any log files or other info I can provide that promptly.
Related problems for other users:
http://stackoverflow.com/questions/11741803/fail-to-install-sql-server-2008-r2-as-a-feature-pre-requisite-in-a-wix-project
http://social.msdn.microsoft.com/Forums/en-NZ/sqlsetupandupgrade/thread/ce69b4e1-939f-4a64-9b44-e6ffdad3b9c8
The SP2 redistributable I use can be downloaded from here (SQLEXPR_x86_ENU.exe):
http://www.microsoft.com/en-za/download/details.aspx?id=30438
Thanks
Fredrik
Frede
↧
↧
Redistribute SQL Server 2012 Express
Hi!
Where can I find information regarding redistribution rights for SQL 2012 Express? Are there differences between 2008 and 2012 in terms of redistribution?
What is the best way to redistribute SQL 2012 Express when I require the end-user installation to use a specific configuration? Config-file based installation?
↧
Which version of .net is required to install SQL 2008 R2 Exp. DB Engine Only? .Net 2.0 SP2 or 3.5 ?
Microsoft download page says .Net framework 2.0 or later another page says .net 3.5. Which one is right?
I try to install in a pure XP machine. I got the alert from SQL Server Setup saying that
SQL Server Setup cannot continue until the following programs are installed. After installing
the programs, restart the computer if required, and the restart SQL Server Setup.
Microsoft .Net Framework 2.0 SP2 is available at: http:://go.microsoft.com/fwlink/?LinkId=159826
Microsoft Windows Installer 4.5 is available at: http:://go.microsoft.com/fwlink/?LinkId=159623
I installed .Net framework 2.0 SP2 and WI 4.5 then SQL Server installed (Database engine only) successfully without any issue.
-Ganesh
↧
Failed to launch Execute Package Utility
Hi,
I am unable to open "Execute Package Utility". It is throwing below error.
The program has failed to Load the library "C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\dts.dll".
My OS is 64 bit and below are the orders of path in environment variable
C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;
C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;
C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;
C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;
Can anyone let me know how to fix this issue?
Thanks in advance.
--
Harry
↧
SQL 2012 update to Sp1 error
012-12-04 10:16:11.54 spid5s Starting u_Tables.SQL at 04 Dec 2012 10:16:11:543
2012-12-04 10:16:11.54 spid5s This file creates all the system tables in master.
2012-12-04 10:16:11.55 spid5s drop view spt_values ....
2012-12-04 10:16:11.58 spid5s Creating view 'spt_values'.
2012-12-04 10:16:11.69 spid5s drop table spt_monitor ....
2012-12-04 10:16:11.70 spid5s Creating 'spt_monitor'.
2012-12-04 10:16:11.72 spid5s Grant Select on spt_monitor
2012-12-04 10:16:11.73 spid5s Insert into spt_monitor ....
2012-12-04 10:16:11.75 spid5s Error: 25641, Severity: 16, State: 0.
2012-12-04 10:16:11.75 spid5s For target, "package0.event_file", the parameter "filename" passed is invalid. Target parameter at index 0 is invalid
2012-12-04 10:16:11.75 spid5s Error: 912, Severity: 21, State: 2.
2012-12-04 10:16:11.75 spid5s Script level upgrade for database 'master' failed because upgrade step 'u_tables.sql' encountered error 25641, state 0, severity 16. This is a serious error condition which might interfere with regular
operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective
actions and re-start the database so that the script upgrade steps run to completion.
2012-12-04 10:16:11.76 spid5s Error: 3417, Severity: 21, State: 3.
2012-12-04 10:16:11.76 spid5s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL
Server Books Online.
Any suggestions what can be done? - Im am able to start the service with net start mssql$sql2012 /t902 and when starting it without /t902, i get 3547 Error.
↧
↧
Error when attaching SQL2000 Database to SQL2005 Instance
Hi,
I haven't been able to find any good information about what to do with this situation. I have a SQL 2000 database that I copied to a machine that has SQL 2005 on it. I received an error when I attached it. I then tried to restore it from .mtf backup... similar error. It is as follows:
TITLE: Microsoft SQL Server Management Studio
------------------------------Restore failed for Server '<SERVERNAME>'. (Microsoft.SqlServer.Smo)
------------------------------
ADDITIONAL INFORMATION:An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
Possible schema corruption. Run DBCC CHECKCATALOG. (Microsoft SQL Server, Error: 211)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=211&LinkId=20476
------------------------------
BUTTONS:OK
------------------------------
Does anyone have any suggestions on what to do from here? At this point I can't even detach it, since it appears to be replicated. I cannot access the database in order to turn off replication.
Any input would be greatly appreciated.
Thanks!
↧
SQL Server 2012 stops running after setup files are copied.
SQL Server 2012 setup stops running after setup files are copied.
I've experiencing the same issue on two different machines. Both are 64 bit running Server 2008.
On both of them I tried installing using the files from the ISO. I initially used winzip to extract the files. The setup was running fine, but the SQL Server engine had an error when it installed. Then using the Add/Remove programs i uninstalled all of the SQL Server 2012 applications, including the setup files.
Now when i try to install using the "New SQL Server stand-alone..." wizard it will copy the setup files and then the wizard never comes back. I've tried mounting the ISO, extracting with winrar, Burning the ISO to a dvd and downloading the 3 files. I also tried mounting ISO of the version that was just recently released. I run into the same issue with all of them.
Thanks for the help.
↧
Network segmented with hardware firewall SQL & AD
Hello there,
I have hardware firewall(Cisco ASA) between internal SQL Server and Active Directory. I am interesting if port filtering is supported between SQL Server and AD and if yes, which port should I left open for them to operate correctly ? Both servers are 2008 R2.
↧
sql 2008 sp2 uninstall process silently
How to rollBack SQL Service pack SP 2 in SQL Server 2008 running on Windows 2008 silently or using command Line to Previous states( SQL Server 2008 sp1 or SQL Server 2008 without service pack)
Thanks in advance!!
Ravinder Singh chauhan
↧
↧
Baseline configuration analyzer - Analyze_SQL_Server_Replication
Hi,
I ran the Microsoft Baseline Configuration Analyzer 2.0 on a SQL Server 2008 environment.
we included Analyze_SQL_Server_Replication since we have replication configured and running for this server (transactional, the second server is doing a pull subscription from this one).
But in the report it says 'Replication is not configured'
why did the Analyzer not see the replication set up on that SQL Server instance?
thank you
I ran the Microsoft Baseline Configuration Analyzer 2.0 on a SQL Server 2008 environment.
we included Analyze_SQL_Server_Replication since we have replication configured and running for this server (transactional, the second server is doing a pull subscription from this one).
But in the report it says 'Replication is not configured'
why did the Analyzer not see the replication set up on that SQL Server instance?
thank you
↧
SQL Server Maintanance questions
Dear Friends,
Could you please guide me in below questions
I am planning to to turn the below items OFF to my production server Database.
-auto shrink
-auto create statistics
-auto update statistics
-auto close
Question 1: Do i need to restart SQL Agent or will this affect the GUI connected to this database
Qustion 2: Do i need to restart the services connected to this Database
Question 3 :What will happed to Database if i turn 'auto shrink OFF' to 'auto shrink ON'. I mean, Will database goen offline
Thanks in Advance
Parixit
↧
Not able to install MS SQL SERVER 2008 on WINDOWS 8
3 TIMES I TRIED TO INSTALL MS SQL 2008.......SAME MESSAGE AGAIN.........FIRST TIME ATTEMPTED TO PERFORM UNAUTHORIZED OPERATION AND NOW......MOF ERROR......
PLZ HELP !!!!
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: 2012-12-05 18:39:10
End time: 2012-12-06 00:47:42
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xE32A4906%400x08A3AE96
Machine Properties:
Machine name: VINAY-MACBOOK
Machine processor count: 2
OS version: Windows Vista
OS service pack:
OS region: India
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: G:\vinay\sql\x86\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: NT AUTHORITY\SYSTEM
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: Vinay-MacBook\Vinaypreet Singh
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\ConfigurationFile.ini
ENABLERANU: False
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\SYSTEM
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: G:\vinay\sql\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: Vinay-MacBook\Vinaypreet Singh
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x0A2FBD17@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\Detail.txt
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x0A2FBD17@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x0A2FBD17@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\Detail.txt
Feature: Analysis Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x0A2FBD17@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\Detail.txt
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x0A2FBD17@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\Detail.txt
Feature: Integration Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x0A2FBD17@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\Detail.txt
Feature: Client Tools Connectivity
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x0A2FBD17@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\Detail.txt
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x0A2FBD17@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\Detail.txt
Feature: Client Tools SDK
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x0A2FBD17@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\Detail.txt
Feature: Business Intelligence Development Studio
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x0A2FBD17@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\Detail.txt
Feature: SQL Server Books Online
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121205_183802\SystemConfigurationCheck_Report.htm
↧