VMM 2008 R2 SP1 support SQL 2008 R2 SP2?

I plan to install service pack SP2 to SQL 2008 R2 SP1 which host OM and VMM Database. Does VMM 2008R2 SP1 support this version of the SQL server?
As i know OM2007R2 supportes SQL2008R2 SP2 since CU4.

Is SQL Server 2008 R2 SP1 supported on Windows Server 2008 R2 SP1? I've found this website
You have mentioned windows Server 2008 R2 SP1, it works and supported.
https://msdn.microsoft.com/en-us/library/ms143506(v=sql.105).aspx
If you are talking about Windows Server 2008 then you might need SP2
SQL Server 2008 R2 is not supported on:
Any version of Windows Server 2008 less than Windows Server 2008 Service Pack 2

Similar Messages

Moving Service Manager Database From SQL 2008 R2 SP2 to SQL 2012 SP1

Hi Guys,
Just looking for some clarification about moving our Service Manager 2012 R2 database to a new SQL Server.
Our Service Manager database is currently on a remote SQL server, shared with other databases, running SQL 2008 R2 SP2. It was originally setup this way as we only deployed Change Management but we are now wanting to deploy everything, fully
utilising SCSM/Orchestrator and Cireson's suite. Due to the limited resources available on that SQL server we are seeing performance issues before even getting it all up and running.
I want to move the Service Manager database to a new dedicated SQL server running SQL 2012 SP1. I am aware of the official DB move procedure but it does not specifically mention moving up SQL versions. I have seen some comments around here that
it is fine to do but some feedback would be good, it is not something I have done before.
All servers in this are fully patched Windows 2008 R2. Also, we do not currently have a Data Warehouse so do not need to worry about that. It was dropped and uninstalled before upgrading to Service Manager 2012 R2 and will be reinstalled after this DB move
using a separate dedicated SQL server.
Thanks, Chris.

As long as your collations and permissions are the same as before it
should not be a problem. That sad i could not find any other documentation saying it's not supported.
I have moved SCSM databases between different SQL-versions before and it has worked fine if the collations etc are correct.
Cheers,
Thomas Strömberg
System Center Specialist
Blog:
Twitter: LinkedIn:
Please remember to 'Propose as answer' if you find a reply helpful

Error 2915 in VMM 2008 R2 SP1

Hi,
I receive errors 2915 in VMM 2008 R2 SP1 while VMM tries to Refresh Host:
Error (2915)
The WS-Management service cannot process the request. Object not found on the host1.domain.lab server.
(Unknown error (0x80338000))
Recommended Action
Ensure that the agent is installed and running. If the error persists, reboot omicron3.jg2.local and then try the operation again.
My Hyper-V host: Windows 2008 R2 SP1 on HP DL380p G8.
I have tried solution from: http://support.microsoft.com/kb/976640 but with no luck. Could you help me with this problem?

Any help will be appreciated.

SQL 2008 SP1 to SQL 2008 R2 Upgrade

I have a SQL server running SQL 2008 SP1 and am trying to upgrade to SQL 2008 R2. The server has an installation of SCOM 2007 R2 with CU4 on it with reporting services and SCOM data warehouse
The SQL upgrade advisor runs and tells me that Custom report items were detected on the report server and 3x Custom extensions or assemblies were detected on the report server
If I actually try to run the upgrade I get a 2 failures in the Upgrade Rules check:
No Custom Security Extensions and No Custom Authentication Extensions
I can see that the file rsreportserver.config has the custom entries relating to the scom data warehouse user so it is possible to change this file back to the original config file that was present before installing scom data warehouse and then run the sql
upgrade and then put the config file back?

Hi Mickpell,
Me too facing the same issue while upgrading from SQL 2008 SP1 to SQL 2008 R2. Getting below error:
No Custom Security Extensions and No Custom Authentication Extensions
Did u follow the steps you mentioned and it is Success???. Could you please confirm. If it was success, I can proceed with the same steps. Thanks in advance!!! I am
using SCOM 2007 R2 CU5. Should I download latest Hotfix Utility or CU2 utility is enough???
Regards, Suresh

Transact-SQL debugger not working in SQL Server 2008: "...debugger does not support SQL Server 2005 or earlier..."

I have recently installed SQL Server 2008. When I try to execute a query against an Access database, I receive this debugging error:
"Unable to start Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)"
Nor will the query execute; I get a transport-level error 0. Any thoughts?

Hi Davidmhjr,
>>Unable to start the Transact-SQL Debugger. The Transact-SQL Debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors).
Have you tried to restart the server once you have installed SQL Server 2008? As Naomi N mentioned please check the version of SQL Server you are using.
If you tried to connect to SQL Server 2005 from SQL Server 2008 SSMS, you would not be able to debug and get this error, it happens because T-SQL debugger includes both server-side and client-side components. The server-side debugger components are installed
with each instance of the SQL Server 2008 Database Engine. The client-side components are installed when you install the SQL Server 2008 client-side tools.
So it works with SQL Server 2008 only so far. Another way is you can triy to use SQL Server 2005 SSMS to connect to SQL Server 2005.
More information about configuration requirement to run T-SQL debugger as below, please refer:
There are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. However, to run the Transact-SQL debugger when SQL Server Management
Studio is running on a different computer from the instance of the Database Engine, you must enable program and port exceptions by using the Windows Firewall Control Panel application on both computers.
On the computer that is running the instance of the Database Engine, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add the program sqlservr.exe to the exceptions list. By default, sqlservr.exe is installed in C:\Program Files\Microsoft SQL Server\MSSQL10.InstanceName\MSSQL\Binn, where InstanceName is MSSQLSERVER for the default instance, and the instance name for
any named instance.
•If the domain policy requires network communications to be done through IPsec, you must also add UDP port 4500 and UDP port 500 to the exception list.
On the computer that is running SQL Server Management Studio, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add program ssms.exe (SQL Server Management Studio) to the exceptions list. By default, ssms.exe is installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE.
Hope it is helpful.
Regards, Amber zhang

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

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

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

Lots of Warning 1706 logged on VMM 2008 R2 Sp1

Hi,
I have VMM 2008 R2 Sp1 server with 3 Hyper-V hosts connected. In VM Manager event log I have noticed lots of 1706 warnings:
"Job <Id> (Refresh virtual machine) failed to complete".
Is it anything dangerous for my servers? Should I troubleshoot it?

There are also "Job <Id> (Refresh host) failed to complete" 1706 warnings logged. Could anyone help me with this? How to troubleshoot this problem?

How to move VMM 2008 R2 Sp1 server to new machine

Hello,
I need to move/migrate VMM 2008 R2 Sp1 installation (server, not database) to new machine. New machine has several different roles installed so backup/restore method is not possible. New server will have different name.There are also several Hyper-V hosts
and library servers connected to old VMM.
Do you have any good step-by-step for this?
Robert Mandziarz | IT Administrator:
CodeTwo
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer
faster.

Hi,
Thank you for your posting in Windows Server Forum.
From your description it seems that you have 50 RDS User CAL, if I am wrong then please correct it. If you are using RD User CAL then you can track per User CAL and also generate a report by
RD Licensing Manager. But for tracking RD User CAL, the system must be domain joined as it won’t work with workgroup mode. After creating report you can have the CAL details and to retain\migrate and activate again you need to contact MS clearing house.
Please check below article for more information.
Track the Issuance of Remote Desktop Services Per User Client Access Licenses
http://technet.microsoft.com/en-us/library/cc754625.aspx
Migrate Remote Desktop Services Client Access Licenses (RDS CALs)
http://technet.microsoft.com/en-us/library/dd851844.aspx
Hope it helps!
Thanks,
Dharmesh

Frequenet dead locks in SQL Server 2008 R2 SP2

Hi,
We are experiencing frequent dead locks in our application. We are using MSSQL Server 2008 R2 SP2 version. When our application is configured for 5-6 app servers, this issue is occurring frequently.
But, when the same application is used with the MSSQL Server 2008 R2 or SQL Server 2012, we don't see the dead lock issue. From the error lock and sql trace, the error message is thrown for the database table JobLock. We have a stored procedure to insert/update
for the above table when the job moves from one service to other. The same procedure works fine when used with the 2008 R2 and SQL Server 2012 Version.
Is the above issue related to the hotfix from the below url?
http://support.microsoft.com/kb/2703275
Following error message is seen frequently in the log file.
INFO : 03/24/2014 10:26:30:290 PM: [00007900:00005932] [Xerox.ISP.Workflow.ManagedActivity.PersistInTransaction] System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 62) was deadlocked on lock resources with another process and has been
chosen as the deadlock victim. Rerun the transaction.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   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.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Practices.EnterpriseLibrary.Data.Database.DoExecuteNonQuery(DbCommand command)
   at Microsoft.Practices.EnterpriseLibrary.Data.Database.ExecuteNonQuery(DbCommand command, DbTransaction transaction)
   at Xerox.ISP.DataAccess.Data.Utility.ExecuteNonQuery(TransactionManager transactionManager, DbCommand dbCommand)
   at Xerox.ISP.DataAccess.Data.SqlClient.SqlActivityProviderBase.ActivityReady(TransactionManager transactionManager, Int32 start, Int32 pageLength, Nullable`1 ActivityID, Nullable`1 JobId, String ContentUrl, Nullable`1 PrevWorkStep, Nullable`1
CurrentWorkStep, String Principal, Nullable`1 Status, Nullable`1 ServerID, String HostName, Nullable`1 LockUserID, Nullable`1& ErrorCode, Byte[]& Activity_TS)
   at Xerox.ISP.DataAccess.Domain.ActivityBase.ActivityReady(Nullable`1 ActivityID, Nullable`1 JobId, String ContentUrl, Nullable`1 PrevWorkStep, Nullable`1 CurrentWorkStep, String Principal, Nullable`1 Status, Nullable`1 ServerID, String HostName,
Nullable`1 LockUserID, Nullable`1& ErrorCode, Byte[]& Activity_TS, Int32 start, Int32 pageLength)
   at Xerox.ISP.DataAccess.Domain.ActivityBase.ActivityReady(Nullable`1 ActivityID, Nullable`1 JobId, String ContentUrl, Nullable`1 PrevWorkStep, Nullable`1 CurrentWorkStep, String Principal, Nullable`1 Status, Nullable`1 ServerID, String HostName,
Nullable`1 LockUserID, Nullable`1& ErrorCode, Byte[]& Activity_TS)
   at Xerox.ISP.Workflow.ManagedActivity.<>c__DisplayClass2f.<ActivityReady>b__2d()
   at Xerox.ISP.Workflow.ManagedActivity.PersistInTransaction(Boolean createNew, PersistMethod persist)
ClientConnectionId:9e44a64f-5014-4634-9cee-4581e1b9c299
I look forward to the suggestions to get the issue resolved. Your input is much appreciated.
Thanks,
Keshava.

If you are having deadlock trouble in your SQL Server instance, this recipe demonstrates how to make sure deadlocks are logged to the SQL ServerManagement Studio SQL log appropriately using
the DBCC TRACEON, DBCC TRACEOFF, and DBCC TRACESTATUS commands. These functions enable, disable, and check the status of trace flags.
To determine the cause of a deadlock, we need to know
the resources involved and the types of locks acquired and requested. For this kind of information, SQL Server provides
Trace Flag 1222 (this flag supersedes 1204, which was frequently used in earlier versions of SQL Server.)
DBCCTRACEON(1222,
-1);
GO
With this flag enabled, SQL Server will provide output in the form of a deadlock graph, showing the executing statements
for each session, at the time of the deadlock; these are the statements that were blocked and so formed the conflict or cycle that led to the deadlock.
Be aware that it is rarely possible to guarantee that deadlocks will never occur. Tuning for deadlocks
primarily involves minimizing the likelihood of their occurrence. Most of the techniques for minimizing the occurrence of deadlocks are similar to the general techniques for minimizing blocking problems.

How to connect sql server 2008 r2 sp2 with vs2013 ultimate?

how to connect sql server 2008 r2 sp2 with visual studio 2013 ultimate?

Hi Shahzad,
>>how to connect sql server 2008 r2 sp2 with visual studio 2013 ultimate?
Based on your issue, if you wan to connect the sql server 2008 r2 sp2 from VS2013 IDE. I suggest you can try the Ammar and darnold924's suggestion to check your issue.
In addition, I suggest you can also refer the following steps to connect the sql server 2008 r2 sp2 with visual studio 2013 ultimate.
Step1: I suggest you can go to VIEW->SQL Server Object Explorer->Right click SQL Server->Add SQL Server.
Step2: After you connect the SQL Server 2008 r2 sp2 fine, I suggest you can go to VIEW->Server Explorer-> right click the Data Connection->Add Connection.
And then you can create the connect string in the Add Connection dialog box.
Hope it help you!
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Upgrating SQL Server 2008 R2 SP2 to SQL Server 2014 Standard "UpgradeFeatureSpecificRules: KJRTMUpgradeBlockRule"

I've been searching for HOURS how to resolve this issue:
I am trying to upgrade SQL Server 2008 R2 (Express Edition with advanced services) to SQL SERVER 2014 Standard edition, my first issue was to update the 2008 R2 to Service pack 2 on the first FEATURE RULE TEST, at this time on it's keep saying this:
======================================================================================
Rule Check Result
Rule "SQL Server 2008 R2 Service pack 2 or later is requered for upgrade.: failed.
This SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the require service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or lager to the selected instance and the shared features.
=====================================================================================
This is the Configuration Report issue:
Microsoft SQL Server 2014 - System Configuration Check Report
UpgradeFeatureSpecificRules: SQL Server 2014 Setup configuration checks for rules group 'UpgradeFeatureSpecificRules'
KJRTMUpgradeBlockRule
Checks if the currently selected SQL Server 2008 R2 features to upgrade are at the supported service pack. Failed The SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the
required service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or later to the selected instance and the shared features.
====================================================================================
I try after hours and finally did install the Upgrade Advisor and got not issues, the last choice I was to uninstall the Management Studio because in other upgrade express versions got blocked, but in this new version of SQL Server 2014 I don't see any way
out!!!
Thanks.

Hi again
This is the scenario:
-I have installed the SQL SERVER 2008 R2 With Advanced services (version 10.50.1600.1), and now my guest decide to upgrade to an STARNDARD version which nowadays Microsoft is offering the 2014 version.
-As all IT Support and DBA I try to upgrade to SQL 2014 to check and see with requirements were missing or updates. The first check report only ask to upgrade to SQL SERVER 2008 R2 SP2 (version 10.51.2500.0) which I found in the optional update list and
resolved immediately with the Windows Update service.
-Finally, I realise doing the discovery report (suggested in the last post) is that Windows update only download the service pack 2 for SQL Server 2008 instead of the 2008 R2 (I downloaded manually) then the version was upgrade to 10.52.4000.0
Next time I might download the updates manually and not loosing a lot hours with Windows Update, another point very important is that when SQL Server 2008 R2 is installed, create the Microsoft SQL Server 2008 folder at all programas in the Startup menu:
with the SQL Server Installation Center, but there is not one R2, when you execute this one just show the 2008 installed features.
Now we are on 12.0.2000.8
Thanks anyway and all of you for your interest!!!

Do I need to install Security Hotfix (KB2977319) after Cumulative Update 12 for SQL Server 2008 R2 SP2

HI,
I have installed Cumulative Update 12 for SQL Server 2008 R2 SP2 on my SharePoint instances. This was to resolve a known issue faced with the instance. CU12 helped resolve the issue. My company is rather strict regarding security hotfixes. But I am
not sure if this particular hotfix [Security Hotfix (KB2977319)] is required if the instance has CU12 applied.
Tested this on a Lab server, the installation did run fine, the summary log also stated that the KB is applied. But the Build Number did not change. Hence the doubt.
Overall summary:
Final result:                  Passed
Exit code (Decimal):           0
Exit message:                  Passed
Start time:                    2014-09-06 10:31:21
End time:                      2014-09-06 10:55:49
Requested action:              Patch
Instance SPNTSQLTRN overall summary:
Final result:                  Passed
Exit code (Decimal):           0
Exit message:                  Passed
Start time:                    2014-09-06 10:48:08
End time:                      2014-09-06 10:55:45
Requested action:              Patch
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL2008
Type:                          RTM
Version:                       10
SPLevel:                       2
KBArticle:                     KB2977319
KBArticleHyperlink:            http://support.microsoft.com/?kbid=2977319
PatchType:                     QFE
AssociatedHotfixBuild:         0
Platform:                      x64
PatchLevel:                    10.52.4321.0
ProductVersion:                10.52.4000.0
GDRReservedRange:              10.50.4001.0:10.50.4199.0;10.50.4200.0:10.50.4250.0
PackageName:                   SQLServer2008-KB2977319-x64.exe
Installation location:         e:\ac2af22d88ee645b5b32b5c178\x64\setup\
Please inform if I need to apply the hotfix on CU12. Thanks in advance.
John S

Yes you must install Security update mentioned in KB 2977319 it is important for SQL Server to be patches with this security update. Without this it could allow an attacker to compromise your system and gain control over it.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Microsoft SQL Server 2008 R2 SP2 - Express Download Link Broken

Hello there
I am installing Backup Exec 2014 and during the installation I need to provide the EXE from the "Microsoft® SQL Server® 2008 R2 SP2 - Express" installer (German version). Unfortunately the link is broken, even when I navigate from the download
page to the SQL Express download page (http://www.microsoft.com/de-de/download/details.aspx?id=30438) I always get:
We are sorry, the page you requested cannot be found.
I cannot find the German installer anywhere else in the internet, and as I just had to uninstall the old backup solution to be able to start the installer from the new one it is quite important that I get this file as quick as possible so I can get the backup
running again.
Any idea what I could do or where I could find the installer?
Thanks for you help.
Kind regards
Phil

Hello Phil,
yes, seems to be broken.
Download 2008 R2 SP1 (http://www.microsoft.com/de-DE/download/details.aspx?id=26729) and apply SP 2 afterwards.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Cannot find service {0}. Parameter name: SQLWriter SQL Express 2008 R2 SP2

Hi, installing SQL Express 2008 R2 SP2 onto Windows Server 2012 R2.   I had previously removed SQL Express 2012 due to failed install due to incompatibility with our SAN.   (I had uninstalled it via Programs & Features,
and also by following Shanky's tips. http://social.technet.microsoft.com/wiki/contents/articles/24364.sql-server-troubleshooting-could-not-find-database-engine-startup-handle-error-during-installation.aspx).
This is what's in Detail log:
014-10-07 13:12:00 Slp: Parameter 5 : SqlEngineConfigAction_install_confignonrc
2014-10-07 13:12:00 Slp: Parameter 6 : 0x50806C41
014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL
Server.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2014-10-07 13:12:02 Slp: Cannot find service {0}.
The SqlEngineConfigAction_install_confignonrc part is what is in the background before the
Cannot find service {0}. Parameter name: SQLWriter pops up.
And in Event Viewer:
Log Name:      Application
Source:        Microsoft-Windows-RestartManager
Date:          10/7/2014 1:11:48 PM
Event ID:      10010
Task Category: None
Level:         Warning
Keywords:
User:          SYSTEM
Computer:
Description:
Application 'C:\31f53f2e988a36f2c31e\x64\setup100.exe' (pid 688) cannot be restarted - Application SID does not match Conductor SID..
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-RestartManager" Guid="{0888E5EF-9B98-4695-979D-E92CE4247224}" />
    <EventID>10010</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-10-07T20:11:48.532980400Z" />
    <EventRecordID>4538</EventRecordID>
    <Correlation />
    <Execution ProcessID="732" ThreadID="2548" />
    <Channel>Application</Channel>
    <Computer></Computer>
    <Security UserID="S-1-5-18" />
</System>
<UserData>
    <RmUnsupportedRestartEvent xmlns="http://www.microsoft.com/2005/08/Windows/Reliability/RestartManager/">
      <RmSessionId>0</RmSessionId>
      <Pid>688</Pid>
      <FullPath>C:\31f53f2e988a36f2c31e\x64\setup100.exe</FullPath>
      <DisplayName>Managed SQL Server Installer</DisplayName>
      <AppVersion>0</AppVersion>
      <AppType>5</AppType>
      <TSSessionId>2</TSSessionId>
      <Status>67108865</Status>
      <Reason>1</Reason>
    </RmUnsupportedRestartEvent>
</UserData>
</Event>
Found one article saying you can get this if previous version not fully removed, and to do a repair of the previous version, but as I said I uninstalled it and followed all steps for cleanup, so nothing to repair.

Here is the ERRORLOG file from C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log. At the bottom I am seeing the error you said before was a SAN issue. I had hoped that issue was only with
SQL 2012, but it appears it is even with 2008?
If that is still the issue, I'm trying to understand if by the articles, if the SAN conflict is an OS issue or an SQL issue?   In other words, is it because the OS is Server 2012?   Or would this still occur if I install SQL
2008 on Server 2008 R2?    I don't know that they will be willing to upgrade the SAN, and I don't really want to fool with a .VHD (virtual disk) as a workaround speaks of.
If you're asking if I did this from your article: select startup account for Database Engine services as NT Authority\SYSTEM
, I don't recall what I did this last time. I was doing that the last few days, but I think I didn't switch it to that once, just to see if I would have success. I don't know if that was this last time or not when I switched it.
Is there anywhere I can check that after the fact?
014-10-08 12:53:09.84 Server      Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)
Jun 28 2012 08:36:30
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2014-10-08 12:53:09.84 Server      (c) Microsoft Corporation.
2014-10-08 12:53:09.84 Server      All rights reserved.
2014-10-08 12:53:09.84 Server      Server process ID is 2640.
2014-10-08 12:53:09.84 Server      System Manufacturer: 'IBM', System Model: 'IBM System x -[7870AC1]-'.
2014-10-08 12:53:09.84 Server      Authentication mode is WINDOWS-ONLY.
2014-10-08 12:53:09.84 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-10-08 12:53:09.84 Server      This instance of SQL Server last reported using a process ID of 2848 at 10/8/2014 10:56:44 AM (local) 10/8/2014 5:56:44 PM (UTC). This is an informational message only; no user action is required.
2014-10-08 12:53:09.84 Server      Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-10-08 12:53:09.84 Server      Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q SQL_Latin1_General_CP1_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
-T 902
-d c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\master.mdf
-l c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf
2014-10-08 12:53:09.86 Server      Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically.
After the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2014-10-08 12:53:09.86 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-10-08 12:53:09.86 Server      Detected 16 CPUs. This is an informational message; no user action is required.
2014-10-08 12:53:10.00 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-10-08 12:53:10.01 Server      Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-10-08 12:53:10.01 Server      Lock partitioning is enabled. This is an informational message only. No user action is required.
2014-10-08 12:53:10.03 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2014-10-08 12:53:10.05 Server      Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No
user action is required.
2014-10-08 12:53:10.06 spid7s      Warning ******************
2014-10-08 12:53:10.06 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-10-08 12:53:10.06 spid7s      Starting up database 'master'.
2014-10-08 12:53:10.08 spid7s      Error: 5178, Severity: 16, State: 1.
2014-10-08 12:53:10.08 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector
size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2014-10-08 12:53:10.09 spid7s      Error: 5178, Severity: 16, State: 1.
2014-10-08 12:53:10.09 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector
size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2014-10-08 12:53:10.09 spid7s      Error: 5178, Severity: 16, State: 1.
2014-10-08 12:53:10.09 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with
sector size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2014-10-08 12:53:10.09 spid7s      Error: 5178, Severity: 16, State: 1.
2014-10-08 12:53:10.09 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with
sector size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.

VMM 2008 R2 error 2921

When attempting to
converts windows 2000 with SP4 physical machine to VM using VMM 2008 R2. I
receive this error. I am login domain admin account and make sure the account
has right on the folder. Why I get this message?
Error (2921)
VMM cannot complete the operation on the file
C:\Users\administrator.PAYROLL\AppData\Local\Temp\SCVMM.1fca7033e3\boot.wim on
the hsamgmtsvr01.hsapayroll.com server. One of the following system errors
occurred: a file is read-only, the specified path is a directory, or Virtual
Machine Manager does not have the required permissions.
Recommended Action
Ensure that the path is valid and VMM has the appropriate rights to perform
this action.<o:p></o:p>
Bob Lin, MCSE & CNE Networking, Internet, Routing, VPN Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Install and Configure Windows, VMware, Virtualization and Cisco on http://www.HowToNetworking.com

Hi Sir,
Please try to add VMM Service account to Local System admin account of source computer .
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

VMM 2008 R2 SP1 support SQL 2008 R2 SP2?

Similar Messages

Maybe you are looking for