2008 R2 upgrade to SQL 2012 validation error - No Features Selected

I need a work-around for a known bug. Some features of Server 2008 R2 Enterprise install an instance of SQL Server. I'm attempting to upgrade the in-place instance to SQL 2012 Express. After selecting 'Upgrade', it returns this error:
Upgrade to SQL Server 2012
There are validation errors on this page. Click OK to close this dialog box. Review errors at the bottom of the setup page, then provide valid parameters or click Help for more information.
There are no features selected for upgrade.
In researching, I find this is a known problem in which the hotfix is available in a cumulative update. The 2419 build updates the released 2100 build. My problem now is that applying the cumulative update requires that SQL 2012 already be installed.
What is the correct procedure for upgrading the in-place SQL instance to 2012 SQL Express?
Beware of unmoderated moderators in the Expression Web forums.

One of us is confused.... likely me. The SQL currently installed is the built-in SQL of Windows Server 2008 R2 Enterprise. It is not SQL Enterprise. I understand it to be a limited variation called SSEE, SQL Server Embedded Edition.
I believe the installation of this variation can be triggered by installing IIS or WSUS. The instance name is Microsoft##SSEE.
Nevertheless, there must be a proper way to install SQL 2012 Express, migrate, and uninstall the Windows Internal Database SQL 2005. Where can I find the correct procedure for upgrading the in-place SQL instance to 2012 SQL Express?
Hi backup,
According to your description, I recommend you install SQL Server 2012 Express directly. Before installing, you should note the
hardware and software requirements, for example, you need to download and install Microsoft .Net Framework 3.5 SP1 and Windows Installer 4.5.
There is a process of installing SQL Server 2012 Express, you can review it.
http://www.jsinh.in/2012/09/install-sql-server-2012-express-step-by-step/
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Similar Messages

After Upgraded to SQL 2012 Iam getting several Errors in SCCM 2007

After I upgrade my sql 2008 to sql 2012, I am getting several errors in SCCM 2007.Please find the below screen short
Configmgr reporting service point - Critical
SMS-Collection-Evaluator -critical
SmS-dstribution Manager -Critical
SMS-SRS reporting point -critical
SMS-Discovery Data manager -critical
SMS-Status Manager -critical
SMS policy Manager -critical
How can I resolve this issue.

I updated the path still I have the same problem...several error message found in SCCM server.please find the below one error message
On 7/21/2013 10:51:16 AM, component SMS_DISCOVERY_DATA_MANAGER on computer DCD-SCCM reported: SMS Discovery Data Manager failed to process the discovery data record (DDR) "", because it cannot update the data source.
Possible cause: On a Primary site, it is probably a SQL Server problem.
Solution:
1. Review the immediately preceding status messages from this component about SQL Server errors.
2. Verify that this computer can reach the SQL Server computer.
3. Verify that SQL Server services are running.
4. Verify that SMS can access the SMS site database.
5. Verify that the SMS site database, transaction log, and tempdb are not full.
6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console.
If the problem persists, check the SQL Server error logs.
Possible cause: On a secondary site, SMS Discovery Data Manager probably cannot write to a file on the site server, so check for low disk space on the site server.
Solution: Make more space available on the site server.
how can I resolve the issue??

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

SQL 2012 - SSIS Error -The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.

Hi guys
Trying to run this package on SQL 2012 agent and getting below error . No more details I could find so far.
The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.
About Package - Its connecting to different version (2000,2005,2008,2008R2,2012) servers and putting Jobs information into one Database table.
Any workaround or fix ?
Thanks
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

New package or one that used to work? Connecting how? How does it poll?
On the surface it is an error from a memory space of the binary/non-managed code, so nothing can be really concluded based on what you decided to share with us.
Arthur My Blog
So Same package is working fine from my local machine which has SQL 2008 R2 and SQL 2012 installed. I am trying to push the package on server which has sql server 2012 Installed .
I don't see any error .
I ran package manually from server using SQL Data tools and ran successfully...
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

Help -- sql 2008 SP3 (x64) and sql 2012 R2 SMO

We have a sql 2008 x64 sql server with SP3. We need to upgrade a third-party app (related to our SAN) and it needs to install
a. Microsoft Visual C++ 2012 Redistributable Package (x64)
b. Microsoft SQL Server 2012 CLR Types (x64)
c. Microsoft Sql 2012 R2 Management Objects (x64)
Are there any known compatibility issues installing these on a sql 2008 SP3 server?
TIA,
edm2

Hello,
The components you post above are stand-alone packages that provide additional value for Microsoft SQL Server 2012. The installation of these components will not effect the previous installed SQL Server instance.
SQL Server Management Objects (SMO) is a .NET Framework object which can will work with SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012. You can download the SQL Server Management Objects (SMO) and the requisite CLR Types from
the following link:
Microsoft® SQL Server® 2012 SP1 Feature Pack
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

SCOM 2012 R2 Report Server component install to SQL 2012 Sp1 error?

Hi All
Im having issues installing SCOM 2012 R2 Report Server component to a SQL 2012 Sp1 Server (which is a Windows 2012 R2 Standard server). Im trying to install to the SQL Default server instance, note that the server also has a named instance
which hosts the SCOM databases. SQL Reporting Services is up and running fine (can access the web urls etc). Im also using the SCOM install account wich has full SQL and SCOM Server admin rights for the install. Ive checked that the Firewall
is off locally on the SQL Server, Ive also checked that the existing SCOM components are all in a Healthy state in the SCOM console.
The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
Configurations document for further information.
Ive attempted the install on a standalone SQL Server away from the SQL Server hosting the SCOM databases, but encounter the same error. The full SCOM MSI Installer log details are below, line that appears most relevant is below but unsure why
this would be the case (same account that I used for SQL install etc). Any help much appreciated! : )
Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:51:46]: Debug: :CheckPrerequisites: IsComputerNameValidTitle: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :<![CDATA[CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x86: 0CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x64: 0]]>
[11:51:46]: Debug: :
[11:51:46]: Debug: :CheckPrerequisites: AVIcodeAgentCheck: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Always: :CheckPrerequisites: Return Value 0
[11:51:46]: Always: :Entering Page: AdditionalPrerequisitesPage
[11:51:48]: Always: :Entering Page: ShortEulaPage
[11:51:48]: Always: :Displaying localized EULA for localization: en
[11:51:48]: Always: :Displaying Eula: C:\Users\opsmgr\AppData\Local\SCOM\Setup\en\eula_en_notice.rtf
[11:51:49]: Info: :Info:User has agreed to EULA.
[11:51:50]: Always: :Entering Page: SelectManagementServerForReporting
[11:52:08]: Info: :Info:Management Server matches the current version of setup.
[11:52:08]: Always: :Entering Page: SelectReportingInstance
[11:52:08]: Always: :SQL Server SRS Instance (escaped name) RS_MSSQLSERVER
[11:52:08]: Info: :Attempting to get the SSRS version from:
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER:__NAMESPACE
[11:52:08]: Debug: :Path is
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\V11:MSReportServer_Instance
[11:52:08]: Always: :SRS instance on WDC-SYSSQL01. Version 11.0.3000.0.
[11:52:08]: Always: :No SRS instances on WDC-SYSSQL01.
[11:52:08]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:08]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:08]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:08]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:11]: Info: :Attempting to check SRS version
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:11]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:28]: Info: :The user canceled setup
[11:52:28]: Always: :Begin: Property bag dump.
[11:52:28]: Always: :SetupStartTime = 26/03/2014 11:51:38
[11:52:28]: Always: :Collection ProtectedProperties (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = ActionAccountPassword
[11:52:28]: Always: : [1] = DASAccountPassword
[11:52:28]: Always: :DefaultLogName = C:\Users\opsmgr\AppData\Local\SCOM\Logs\OpsMgrSetupWizard.log
[11:52:28]: Always: :DefaultLogPath = C:\Users\opsmgr\AppData\Local\SCOM\Logs
[11:52:28]: Always: :path = F:\Setup\AMD64\
[11:52:28]: Always: :setupexepath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :ArchitectureIs64Check = True
[11:52:28]: Always: :OperationManagerAgentInstalled = 1
[11:52:28]: Always: :Collection ListOfSupportedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMCONSOLE
[11:52:28]: Always: : [1] = OMSERVER
[11:52:28]: Always: : [2] = OMWEBCONSOLE
[11:52:28]: Always: : [3] = OMREPORTING
[11:52:28]: Always: :install = 1
[11:52:28]: Always: :installpath = C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[11:52:28]: Always: :EulaFilesPath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :HealthServiceTypeId = AB4C891F-3359-3FB6-0704-075FBFE36710
[11:52:28]: Always: :hsPort = C51B7833-DA54-1653-D8FD-1A738EF8DED5
[11:52:28]: Always: :ServerBlockReason = A Operations Manager agent was found on this computer. Please remove the agent and then run Setup again.
[11:52:28]: Always: :ScreensLoaded = 1
[11:52:28]: Always: :Collection ListOfSelectedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMREPORTING
[11:52:28]: Always: :OMREPORTING = 1
[11:52:28]: Always: :SelectDatabaseInstanceReloadScreenInformation = 1
[11:52:28]: Always: :ReloadPrerequisitesPageChoice = PrerequisitesProgressPage
[11:52:28]: Always: :LoadedPrerequisiteXmlFile = True
[11:52:28]: Always: :PrerequisitesCheckXMLLoaded = True
[11:52:28]: Always: :CountFilteredPrerequisites_Failed = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Warning = 0
[11:52:28]: Always: :CountFilteredPrerequisites_PassedWithChoices = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Passed = 10
[11:52:28]: Always: :PrerequisiteState = Passed
[11:52:28]: Always: :XmlFilteredPrerequisites_Passed : Begin XML property
[11:52:28]: Always: :<?xml version="1.0" encoding="utf-8"?><Root><Title TitleText="OMREPORTING"><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="memoryCheckTitle" descriptionBody="" descriptionTitle="ReportingMemCheckPassed" resolution="ReportingMemCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ntfsCheckTitle" descriptionBody="" descriptionTitle="ntfsCheckPassed" resolution="ntfsCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="DriveSpaceCheckTitle" descriptionBody="" descriptionTitle="ServerDriveSpaceCheckPassed" resolution="ServerDriveSpaceCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="OSVersionCheckTitle" descriptionBody="" descriptionTitle="OSVersionCheckPassed" resolution="OSVersionCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="WindowsInstallerCheckTitle" descriptionBody="" descriptionTitle="WindowsInstallerCheckPassed" resolution="WindowsInstallerCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="RemoteRegistryCheckTitle" descriptionBody="" descriptionTitle="RemoteRegistryCheckPassed" resolution="RemoteRegistryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="PendingRebootCheckTitle" descriptionBody="" descriptionTitle="PendingRebootCheckPassed" resolution="PendingRebootCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ActiveDirectoryCheckTitle" descriptionBody="" descriptionTitle="ActiveDirectoryCheckPassed" resolution="ActiveDirectoryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="IsComputerNameValidTitle" descriptionBody="" descriptionTitle="IsComputerNameValidPassed" resolution="IsComputerNameValidResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="AVIcodeAgentCheck" descriptionBody="" descriptionTitle="AVICodeAgentCheckPassed" resolution="AVICodeAgentCheckResolution" /></Title></Root>
[11:52:28]: Always: :End XML property
[11:52:28]: Always: :ManagementServer = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :DefaultSDKMachine = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :UserCanceledInstall = 1
[11:52:28]: Always: :InstallSuccess = 1
[11:52:28]: Always: :End: Property bag dump.
[11:52:28]: Debug: :CEIP disabled. CEIP data will NOT be sent.
[11:52:28]: Always: :Application Ended: Successful
[11:52:28]: Always: :
[2014-03-26T11:52:28.4724357+00:00]: Always: Trace Session Ended

Hi,
According to the error message:
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
The issue is SQL report server database related, I would like to suggest you create a new report database for SCOM and then check the reuslt. Please refer to the below links and follow it to set up SCOM 2012 R2:
http://blogs.technet.com/b/kevinholman/archive/2013/01/16/opsmgr-2012-sp1-quickstart-deployment-guide.aspx
In addition, here is thread for your reference also:
http://social.technet.microsoft.com/Forums/en-US/3f883b7f-5a33-49f0-a40d-f3311e68609d/unable-to-connect-to-the-data-access-service-installing-report-server?forum=operationsmanagerreporting
Regards,
Yan Li
Regards, Yan Li

SQL 2012 installation Error-The MOF compiler could not connect with the WMI server

Hi all,
I am getting below error while installing SQL 2012 Dev edition in Win 8.1 Pro.
I am facing lot of issues while installing SQL 2012 in Win 8.1 Pro.Any other steps we need to take to install SQL 2012 in Win 8.1.
Thanks in advance.

Installation:
Installation for SQL Server 2012
Hardware and Software Requirements for Installing SQL Server 2012
Installing the .NET Framework 3.5 on Windows 8 or 8.1
About "The MOF compiler could not connected with the WMI server" error message:
Please, verify the Windows Management Instrumentation has status "started" and is set with Startup Type "Automatic". (Alberto Morillo, SQLCoffee.com).
José Diz Belo Horizonte, MG - Brasil

SQL 2012 Installation Error

Good Day
I am trying to install SQL 2012.
during the installation process it halts and I receive the following message:
TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
Setup encountered a failure while running job UpdateResult.
Error code 0x876E0003.
I have spent hours looking through help blogs and other resources trying to find answers and help but have not been able to find a solution..!
Any advise or how to work around this would be greatly appreciated!
Thank you.

Hi BrendanDev,
According to the error message, the issue may occur due to the permission issue with Windows update.
In this case, If you have the DefaultSetup.ini file in the \x86 or \x64 folders at the root level of the SQL Server source media, please open the DefaultSetup.ini file, and then add the UpdateEnabled or UpdateSource parameters to the file. If the DefaultSetup.ini
file does not exist, we can create it and copy it to the \x86 and \x64 folders at the root level of the SQL Server source media. And then we need to modify the "DefaultSetup.ini" file and set the switch "UpdateEnabled=False" which skips the product updates
in the installation.
For the detailed information, please refer to the link below:
http://blogs.msdn.com/b/petersad/archive/2011/07/13/product-update-in-sql-server-code-named-denali.aspx
If you need more assistance, please feel free to let me know.
Regards,
Heidi Duan

PL/SQL - inline validation errors check

Hello,
does there exist any function (PL/SQL) which tell me that inline validation errors were displayed or not?
Now I use "Condition Type -> No Inline Validation Errors Displayed" but I need to check it in "PL/SQL expression".
Is it possible?
regards,
Jarek

OK,
I found it.
Following function gives you number of validations errors:
wwv_flow.g_inline_validation_error_cnt
regards,
Jarek

DQS Client doesn't upgrade after SQL 2012 SP1 CU4

One of my clients just has the DQS client tool installed and not DQS Server. After realizing he was trying to connect to DQS servers on a higher version he went and ran the CU4 update to get his DQS client in compliance. After running the service
pack, his SSMS was properly upgraded but the older DQS client is still there. Has anyone run into this issue? I tried to have him upgrade the dlls but the dqsinstaller.exe isn't on his machine since he didn't install DQS server. Is there
a special step that is required to upgrade the client?
Chad Dotzenrod SWC | TECHNOLOGY PARTNERS 1420 Kensington Road, Suite 110 Oak Brook, Illinois 60523-2144 http://www.swc.com

This issue can be closed. My client did the following: 1)Uninstalled the SQL 2012 SP1 service
pack 2)Ran windows update service that had issues in the queue 3)Re-Ran SQL 2012 SP1 CU4 with success.
Chad Dotzenrod SWC | TECHNOLOGY PARTNERS 1420 Kensington Road, Suite 110 Oak Brook, Illinois 60523-2144 http://www.swc.com

Move databases AND upgrading to SQL 2012

Hi! I want to move my SCOM databases (DW and OM) from a SQL 2008R2 cluster to a SQL 2012 cluster. Is this possible, and how do I do it in the easiest way with as little downtime as possible?
Any tips og walkthroughs appreciated.
Best regards
Rune Haugen
Norway

Hi,
Please refer to the links below:
Moving the Operational Database
http://technet.microsoft.com/en-us/library/hh278848.aspx
How to Move the Data Warehouse Database
http://technet.microsoft.com/en-us/library/hh268492.aspx
Make sure you back up them before moving.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Full-text search not available after upgrade from SQL 2008 R2 Std to SQL 2012 Std

We upgraded our production SQL Server from 2008 R2 Std to 2012 Std last week, and the installation logs show everything was successful, but now we are unable to do any searches against our full-text indexes. The resulting error is as follows:
"Full-Text Search is not installed, or a full-text component cannot be loaded."
When executing the query "SELECT FULLTEXTSERVICEPROPERTY('ISFULLTEXTINSTALLED')", the result is "0". The "Full-Text Daemon Launcher service is also running. When running installation again to add the feature, it shows
"Full-Text and Semantic Extractions for Search" as being installed and unavailable for selection in the list of features to add. As a side note, we did the same upgrade in our identical QA environment before production and everything was successful
and full-text searches are working correctly. We have run the "Repair" routine in the SQL Installation Center and it did not correct the problem.
The full-text catalogs still appear when browsing through the GUI in SSMS or querying sys.fulltext_indexes and sys.fulltext_index_columns. It is not possible to view the properties of the catalog in SSMS, though, as the GUI throws an error and an empty
dialog box is shown. Any other thoughts?
Thanks,
AJ

I have no idea what is going, but assuming that it is a little pressing to get this fix, I think the best path in this case is to open a case with Microsoft.
Erland Sommarskog, SQL Server MVP, [email protected]

Error restoring SQL 2008 R2 DB into SQL 2012: BACKUP LOG cannot be performed because there is no current database backup.

I have a SQL 2008 R2 database that I am trying to move to 2012. Made a full backup of the database in 2008 R2. Recovery model is Simple, compatibility level is 2008 Went to 2012, created a dummy database, did Tasks--> Restore -->
Database , located the backup file, selected it, changed the file locations and tried to restore the backup (with overwrite option), got the following error:
BACKUP LOG cannot be performed because there is no current database backup.
This is a simple task that has always worked in 2008 R2. Does anyone know what the problem is and a possible solution?
Thanks

Hi,
This error occurs when the database recovery model has been changed to Simple and/or the recovery model has been changed back to Full but a full backup has not been performed since the change.
If a full backup has been performed, the following conditions will require that another full backup be taken:
· The recovery model had been changed without taking a full backup
· A SQL maintenance plan task had changed the recovery model (reindexing can cause this)
· A backup specifying TRUNCATE_ONLY had been run on the database
· The database was detached from another server and attached to the current server
Additionally, if we take full database backup after the Database is set to readonly, Then transaction log backup we will end up with this error. This is expected behavior. I have list an example within the link below.
Please check above conditions and fix your issue, if you have any concern, please let me know.
Example:
BACKUP LOG cannot be performed because there is no current database backup.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/b5c36e60-836f-4c9e-b9d7-3fb3f3ee4d37/backup-log-cannot-be-performed-because-there-is-no-current-database-backup
Thanks
Candy Zhou

Using MSXML2.ServerXMLHttp in MS SQL 2012 - receiving error "The Parameter is incorrect".

I have a procedure used to make http post requests to a REST web service external to my SQL server, using MSXML2.ServerXMLHttp via POST request. This procedure works without issue in SQL 2008 r2, but upon upgrade to 2012, begins to fail with the message
: "The Parameter is incorrect."
It is failing when I attempt to exec the 'send' method on line 137. I cannot find any documentation about how the MSXML2.ServerXMLHttp object needs to be treated differently in 2012. I found a similar question here: http://social.technet.microsoft.com/Forums/sqlserver/en-US/a6de1eea-5fe9-4087-809b-524c98f20a4d/msxml6dll-methodsend-dont-work-in-windows-server-2012-and-sql-2008r2?forum=sqlxml
But it isn't resovled - just indications to file a bug report - and one solution that says to just copy the DLL from 2008 over to 2012 to fix the issue. Is that really the right solution here or does someone have information on how to do this properly with
2012?
Here is my procedure:
CREATE procedure [dbo].[HTTP_REQUEST](@response varchar(4000) out,
@method varchar(64),
@p1name varchar(256) = null,
@p1value varchar(max) = null,
@p2name varchar(256) = null,
@p2value varchar(max) = null,
@p3name varchar(256) = null,
@p3value varchar(max) = null,
@p4name varchar(256) = null,
@p4value varchar(max) = null,
@p5name varchar(256) = null,
@p5value varchar(max) = null,
@p6name varchar(256) = null,
@p6value varchar(max) = null,
@parent_table varchar(30) = null
As
Declare
@obj int
,@hr int
,@status int
,@msg varchar(255)
,@apiKey varchar (64)
,@params varchar (max)
SET @apiKey = (Select a.default_value from T_DEFAULTS a WHERE a.parent_table = @parent_table AND a.field_name = 'm2apiKey')
SET @params = ''
If @apiKey is null
Begin
select @msg = 'Invalid mail2 APIKey'
RAISERROR(@msg, 11, 2) WITH SETERROR
return -101
End
If @method is null
Begin
select @msg = 'No valid mail2 API method provided'
RAISERROR(@msg, 11, 2) WITH SETERROR
return -101
End
exec @hr = sp_OACreate 'MSXML2.ServerXMLHttp', @obj OUT
if @hr <> 0 begin Raiserror('sp_OACreate MSXML2.ServerXMLHttp.3.0
failed', 16,1) return end
exec @hr = sp_OAMethod @obj, 'open', NULL, 'POST', 'http://api.someapiurl.net/REST/', true
if @hr <>0 begin set @msg = 'sp_OAMethod Open failed' goto eh end
exec @hr = sp_OAMethod @obj, 'setRequestHeader', NULL, 'Content-Type',
'application/x-www-form-urlencoded'
if @hr <>0 begin set @msg = 'sp_OAMethod setRequestHeader failed' goto
eh end
--Set Timeouts
exec @hr = sp_OAMethod @obj, 'setTimeouts',NULL,5000,5000,10000,10000
if @hr <>0 begin set @msg = 'sp_OAMethod setTimeouts failed' goto
eh end
--Add Method
SET @params = '&method='+@method
--Add API key
SET @params = @params + '&key='+@apiKey
--Add p1 if present
IF @p1name IS NOT NULL
BEGIN
SET @params = @params + '&' + @p1name + '=' + @p1value
END
--Add p2
IF @p2name IS NOT NULL
BEGIN
SET @params = @params + '&' + @p2name + '=' + @p2value
END
--Add p3
IF @p3name IS NOT NULL
BEGIN
SET @params = @params + '&' + @p3name + '=' + @p3value
END
--Add p4
IF @p4name IS NOT NULL
BEGIN
SET @params = @params + '&' + @p4name + '=' + @p4value
END
--Add p5
IF @p5name IS NOT NULL
BEGIN
SET @params = @params + '&' + @p5name + '=' + @p5value
END
--Add p6
IF @p6name IS NOT NULL
BEGIN
SET @params = @params + '&' + @p6name + '=' + @p6value
END
--SELECT @params
--Send the request
exec @hr = sp_OAMethod @obj, send, NULL, @params
if @hr <>0 begin set @msg = 'sp_OAMethod Send failed' goto eh end
--Get the status
exec @hr = sp_OAGetProperty @obj, 'status', @status OUT
if @hr <>0 begin set @msg = 'sp_OAGetProperty read status failed on get status' goto
eh
end
if @status <> 200 begin set @msg = 'sp_OAMethod http status ' +
str(@status) goto eh end
if @status = 200 begin print 'sp_OAMethod http status is 200:Successful ' +
str(@status) + @params end
exec @hr = sp_OAGetProperty @obj, 'responseText', @response OUT
if @hr <>0 begin set @msg = 'sp_OAGetProperty read response failed on get response text error code' + convert(varchar,@hr) goto
eh end
exec @hr = sp_OADestroy @obj
return
eh:
exec @hr = sp_OADestroy @obj
Raiserror(@msg, 16, 1)
return
Many thanks for the input -
Chris

How can I fix the problem? changing the OS? I just bought the new server. I do?
thanks
Miky
Rambaldi

SCOM 2012 R2 installing on SQL 2012 SP1 - Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Hi,
I am getting an issue during a SCOM 2012 R2 installation while creating the SCOM DataWarehouse database. Setup seems to timeout during creating the datawarehouse database. I can see all database files created in windows explorer on the SQL server before
setup rolls the SCOM install back.
Has anyone seen this issue before or know how to help resolve it?
Appreciate your help, below is the SCOM installation log:
Thanks
Marc
[13:27:27]: Always: :Creating Database: OperationsManagerDW
[13:35:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:43:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:51:29]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:59:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:07:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:15:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:23:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:31:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:39:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:47:33]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :DB operations failed with SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.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.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Error: :Error:Failed to execute sql command. Setup has reached maximum retry limit.
[14:55:33]: Warn: :Sql error: 11. Error: -2. Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :Exception running sql string
DECLARE @sql NVARCHAR(MAX);
SET @sql = 'CREATE DATABASE ' + QUOTENAME(@DatabaseName) + '
    ON PRIMARY(NAME=MOM_DATA,FILENAME=''' + REPLACE(@Filename, '''', '''''') + ''',SIZE=' + CAST(@Size AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@FileGrowth AS VARCHAR) + 'MB)
    LOG ON(NAME=MOM_LOG, FILENAME=''' + REPLACE(@LogFilename, '''', '''''') + ''',SIZE=' + CAST(@LogSize AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@LogFileGrowth AS VARCHAR) + 'MB)';
EXEC(@sql);: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.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.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Always: :Failed to create and configure the DB with exception.: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion
of the operation or the server is not responding.
[14:55:33]: Always: :StackTrace:   at System.Data.SqlClient.SqlConnection.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.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
String logPath)
[14:55:33]: Always: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Always: :InnerException.StackTrace:
[14:55:33]: Error: :CreateDataWarehouse failed: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or
the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.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.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
String logPath)
   at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.OMDataWarehouseProcessor.CreateDataWarehouse()
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Error: :FATAL ACTION: CreateDataWarehouse
[14:55:33]: Error: :FATAL ACTION: DWInstallActionsPostProcessor
[14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate returned false.
[14:55:33]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Data Warehouse Configuration
[14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate for OMDATAWAREHOUSE failed.... This is a fatal item. Setting rollback.
marc nalder

Hi,
Based on the log, I recommend you use the following way to test SQL connectivity.
You can use a UDL file to test various connectivity scenarios, create a simple text file, rename the extension from TXT to UDL, fill out the necessary information on the connection tab then test the connection, and troubleshoot as necessary
if it fails to connect.
For more information, please review the link below:
The easy way to test SQL connectivity
http://blogs.technet.com/b/michaelgriswold/archive/2014/01/06/the-easy-way-to-test-sql-connectivity.aspx
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.

2008 R2 upgrade to SQL 2012 validation error - No Features Selected

Similar Messages

Maybe you are looking for