2012 frontend 2008 R2 backend.

We are getting ready to install a new Reporting Server and would like that to be a SQL 2012 but the reporting databases will reside on a SQL 2008 R2 server. Is there backward compatibility from 2012 to 2008 R2??

Hi Highly Disturbed,
Based on my test, the earlier versions of SQL Server Database Engine that can be used to host the SSRS report server databases. For example, In SQL Server 2012 Reporting Services, we can use either SQL Server 2008 or SQL Server 2008 R2 to host the databases.
However, when upgrade the existing ReportServer database and ReportServerTempDB database on the SQL Server 2012 by restore from a backup, we cannot use this existing database for Reporting Services 2008 R2 and get the following message: The database version
does not match your reporting sevices installation. And the initialization failed.
In this case, you can host the ReportServer database and ReportServerTempDB database of SSRS 2012 on SQL Server 2008 R2 database engine by creating a new database from Reporting Services 2012 Configure Manager. But you cannot use the existing database of
SQL Server 2008 R2 upgrade to SQL Server 2012.
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu

Similar Messages

W32time NTP server Windows Server 2012 o 2008 R2

Hello All
I have a one problem, I have configured of NTP Server of this way, but when restarted server the time not changed, The server not to synchronized with NTP server.
1. Run Regedit
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W32Time\Parameters\Type
Change from NT5DS to NTP
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W32Time\Config\AnnounceFlags
Edit the DWORD Value to 5. notice that the default value is “a”
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W32Time\TimeProvides\NTPServer\Enabled
Change the value from 0 to 1
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W32Time\Parameters\NtpServer
Change from time.windows.com,0x1 to the IP address of NTP time Server. For example, 1.pool.ntp.org,0×1
Net Stop W32time /Net Start W32time
Some have idea about of this problem?
Hugo Monge

Hi Hugo,
>>W32time NTP server Windows Server 2012 o 2008 R2
Before going further, what does this mean?
Regarding how to configure an authoritative time server in Windows Server, the following articles can be referred to as reference.
How to configure an authoritative time server in Windows Server
http://support.microsoft.com/kb/816042
Configuring a time source for the forest
https://technet.microsoft.com/en-us/library/cc784800(v=ws.10).aspx
Best regards,
Frank Shen
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]

SQL Server 2012 DB Engine does not start (clean install with server 2012 and 2008 R2)

I'm trying to do clean installation of SQL server 2012 on Server 2012 (which is runnning as a VM on ESX server) and getting this "wait on the DB engine recovery failed" message. Initially, I though this issue was related to some permission issues
but changing the permission or service accounts didn't help. I'm not seeing any "denied" messages in the log files either. Even with Server 2008 R2 (clean built VM), the installation gives the exactly the same error messages.
My setup is purely for test purpose; so, the security is not a concern. Can someone help or give me a clue where to look?
(Summary)
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2014-05-28 17:12:12
End time: 2014-05-28 17:19:47
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: WIN-1V3VKPV5Q19
Machine processor count: 1
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: E:\x64\setup\
Installation edition: Evaluation
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x64
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x64
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$TESTDB
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: TESTDB
INSTANCENAME: TESTDB
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$TESTDB
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: WIN-1V3VKPV5Q19\Administrator
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\SystemConfigurationCheck_Report.htm
(Error Log)
2014-05-28 17:17:26.64 spid8s 0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2014-05-28 17:17:26.73 spid9s Starting up database 'model'.
2014-05-28 17:17:28.24 spid9s Error: 9004, Severity: 23, State: 6.
2014-05-28 17:17:28.24 spid9s An error occurred while processing the log for database 'model'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
2014-05-28 17:17:28.24 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
(Details)
(01) 2014-05-28 17:17:28 Slp: Exception type: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException
(01) 2014-05-28 17:17:28 Slp: Message:
(01) 2014-05-28 17:17:28 Slp: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
(01) 2014-05-28 17:17:28 Slp: HResult : 0x851a001a
(01) 2014-05-28 17:17:28 Slp: FacilityCode : 1306 (51a)
(01) 2014-05-28 17:17:28 Slp: ErrorCode : 26 (001a)
(01) 2014-05-28 17:17:28 Slp: Data:
(01) 2014-05-28 17:17:28 Slp: SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2014-05-28 17:17:28 Slp: WatsonConfigActionData = INSTALL@CONFIGRC@SQL_ENGINE_CORE_INST
(01) 2014-05-28 17:17:28 Slp: WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2014-05-28 17:17:28 Slp: Stack:
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.ConfigSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean useInstallInputs)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.DoCommonDBStartConfig(ConfigActionTiming timing)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2014-05-28 17:17:28 Slp: Watson Bucket 1
Original Parameter Values
(01) 2014-05-28 17:17:28 Slp: Parameter 0 : SQL Server 2012@RTM@
(01) 2014-05-28 17:17:28 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart
(01) 2014-05-28 17:17:28 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart
(01) 2014-05-28 17:17:28 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
(01) 2014-05-28 17:17:28 Slp: Parameter 6 : INSTALL@CONFIGRC@SQL_ENGINE_CORE_INST
(01) 2014-05-28 17:17:28 Slp:
Final Parameter Values
(01) 2014-05-28 17:17:28 Slp: Parameter 0 : SQL Server 2012@RTM@
(01) 2014-05-28 17:17:28 Slp: Parameter 1 : 0xD15B4EB2
(01) 2014-05-28 17:17:28 Slp: Parameter 2 : 0xD15B4EB2
(01) 2014-05-28 17:17:28 Slp: Parameter 3 : 0x4BDAF9BA@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 4 : 0x4BDAF9BA@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
(01) 2014-05-28 17:17:28 Slp: Parameter 6 : 0x9C5770A6

Hi Nababoya:
As you are telling this is a test installation process...
In the logs i m seeing the error message "An error occurred while processing the log for database 'model'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.".
1) If the SQL Services was installed successfully and SQL Service was not able to start because of model database issue...
    1.1) If you have model database SQL back file, start the SQL Server in single user mode with minimum configuration and try to restore MODEL database
http://blogs.msdn.com/b/sqlserverfaq/archive/2011/05/11/inf-hey-my-sql-server-service-is-not-starting-what-do-i-do.aspx
    1.2) If you don't have backups., try to rebuild the system databases but make sure that you are not losing any data critical data on master and SQL Jobs on MSDB
http://msdn.microsoft.com/en-us/library/dd207003%28v=sql.110%29.aspx#RebuildProcedure
2) As if this is a new installation try to repair the instance with the help of setup media file
3) If the repair option fails., the last option wipe out the complete SQL Server components from Services.msc and Registries and start new installation.
4) Make sure when you are doing un-installation all the required SQL Server components on services.msc should be in stop state.
Hope this helps and let me know any questions...
Thanks,
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

Powershell commands for VM backups in 2012 vs 2008

I have a powershell routine that is used by task scheduler that will shut down one or more Hyper-v VMs from a list, create a backup of the VHD file(s) then restart the VM(s). It works great in 2008 but when I copied it over to a 2012 host, it
didn't do anything. I was wondering if powershell commands from 2008 still work in 2012 or if they've been completely rewritten. If they are the same, then I'll assume "operator error" and keep trying. If they have changed, then
I know that I'll be spending my week googling around for how to use the new commands. Thanks.

Hello
You can use below powershell comand for Server 2012 host.
$backuppolicy = New-WBPolicy
Get-WBVirtualMachine | Add-WBVirtualMachine -Policy $backuppolicy
$targetfolder = New-WBBackupTarget -NetworkPath
\\FileServerName\e$\BackupFolder -Credential (Get-Credential)
Add-WBBackupTarget -Policy $backuppolicy -Target $targetfolder
Set-WBSchedule -Policy $backuppolicy -Schedule 12:00,09:00
$backuppolicy
Set-WBPolicy $backkuppolicy
Start-WBBackup -Policy $backuppolicy
http://get-itlabs.com/ucretsiz-windows-hyper-v-server-2012-r2-backup/
Ersin CAN - TAT MCSE - Private Cloud. www.get-itlabs.com

Create shortcut and run BI Frontend tools without Backend installation

I have new machine, I want to install BI 7.0 frontend only. Is it possible to run BI frontend (Bex Analyser, WAD, Web Analyser) without installing Backend. Using start menu, I am trying to create shortcut for BI front end tools on the desktop. which is asking for system information. but it doesn't give any popup for to enter system information. Where and How to enter system information ?

I am not sure if i get your qustion properly,when you say Back end ,you mean BW system??
You need BW system some where on this planet for your front end to work,its not imperative to have BW box on to your desktop.
Front end-Bex talks to BW and for that BW needs to be installed somewhere ,you can connect to BW box from anywhere with front end using local network where the BW system is installed or remote access or portal.
Hope it Helps
Chetan
@CP..

Moving from 2012 to 2008

Hi,
We need to move all our reports, SSIS packages and DB components which are now in SQL Server 2012 to SQL Server 2008. Is this possible?
We are not downgrading our server(2012) but rather moving into a different server(2008)
We have not used any of the new features in our DB Components or reports or packages.

If reports/packages were created using SSDT (SQL Server Data tools) BI 2012 IDE then its not possible to donwgrade them to 2008 version.
Similarly a SQLServer DB created using SSMS 2012 in 2012 instance cannot be backedup and restored to earlier version instance.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Downgrade of SSIS packages from 2012 to 2008

Team,
We have put all our efforts to develop SSIS 2012 solution and now customer requirement changes and they wants to implement ETL in SQL 2008R2.
Is there anyway by which we can convert existing SQL 2012 packages to SQL 2008R2 , to meet the deliverables. please advice.

Not possible to downgrade packages created in a higher version. The inverse can be done though by upgradation
So in your case best bet is to keep SSIS inside SQL 2012 version and use other parts ie relational database etc in SQL 2008 R2
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Reassigning volumes to 2012 from 2008

I am putting up some 2012 File Servers. I am going to move the volumes from the 2008 file servers to 2012 (reassign them at the SAN).
I looked up NTFS volume changes between 2008 and 2012 and didnt see anything that would cause an issue, but I want to make sure.
Is anyone aware of any file system problems that will arrise from attaching a 2008 volume to 2012.

is it just standard LUN presented to the current server, if so i don't see an issue with though, just make sure you have a valid backup first.
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
My Blog
LinkedIn:

Downgrade HPC cluster from Windows Server 2012 to 2008 R2

Hi,
We have a customer that have bought a system with HPC Windows Server 2012 and need to downgrade to HPC Windows Server 2008 R2.
The customer thas gotten a Windows Server 2012 OEM DVD, so my question is how can we install the system with Windows Server 2008 R2, what are the practical steps like, where to find software, licenses keys etc...
Thanks for reply.
/Regards Andreas

Hi,
For the HPC question, please post in HPC support forum:
Windows HPC Server
http://social.microsoft.com/Forums/en-US/home?forum=windowshpcitpros
Thanks for you cooperation and support.
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.

Downgrading from Server 2012 to 2008

I have already purchased Server 2012 standard 64 bit and installed it only to find out that the software I am running only accepted Server 2008. How do I downgrade to Server 2008. Also, will I be able to use the 2012 when my software accepts
it? Thanks.

I recommend you install Hyper-V role on your Server 2012 (Std comes with license for 2 VMs), setup a Server 2008 VM for your legacy software, and put serious consideration into dumping the software that does not work on Server 2012. Server 2012 has been
out for 3 years. A software vendor who has not kept up is not worth keeping.
And yes, you can downgrade to server 2008, although this is a horrible idea. By downgrade, I mean install Server 2008 from scratch, and get a 2008 license key from Microsoft under the same 2012 Std purchase.
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable)

Load data from 2012 to 2008

If i create a ssis package and have a source of sql 2012 to destination sql 2008 in my dataflow, will this work? The ssis package would be created for sql 2012 and installed on the sql 2012 server.

Yes, it will work.
That is just data to be moved from SQL 2012 to SQL 2008. So you are good to go.
Cheers,
Vaibhav Chaudhari
[MCTS],
[MCP]
Thanks!!!

SQLCLR "Create Assembly" validation in SQL 2012 vs 2008

Greetings, all.
Could someone describe how the assembly validation steps in SQL 2012 have changed relative to SQL 2008R2?
My understanding thus far is that the .NET 4.0 SQLCLR runtime requirement now precludes the use of mixed-mode assemblies. If a CREATE ASSEMBLY validation failure result includes messages such as the detection of unmanaged pointers, is that indicative of
the cut-and-dried, no-way-around-it discovery of a mixed-mode assembly that can
never be registered in SQL 2012?
I have a third-party assembly which registers and operates normally in SQL 2008R2, but when I try to create the assembly in our SQL 2012 test environment, it fails validation, with mostly "Unexpected type on stack" or "Unmanaged pointer found"
errors. I'm suspecting these errors are why the assembly won't register even though CORFLAGS indicates it is a "Pure IL" assembly (and I realize CORFLAGS can be faked).
Are there any options available? The assembly in question is Oracle.DataAccess.dll, and is part of an assembly that (as one might imagine) collects certain data from Oracle in a SQLCLR method as part of one of our business reporting requirements.
It appears at the moment I may be forced to modify the tool to use the now-deprecated Microsoft Oracle data client, which I am loathe to do for it having been deprecated and much slower than the Oracle-provided version.
If there is no workaround, I would respectfully suggest that the "upgrade advisor" team include this kind of review when inspecting existing databases containing .NET assemblies. If we ultimately cannot register this particular third-party assembly
(which has been part of a working component for several years), it will be a *huge* detriment to our database migration - a far cry from the minor warning about certain geography types provided by the upgrade advisor. It would represent a significant breaking
change for our environment.
Thanks for any information that could be provided.

Thanks for your reply.
Yes, you are correct in that SQL Server wants to use only "Pure IL" assemblies rather than mixed-mode assemblies. However, when an attempt is made to register an assembly in the SQLCLR that is "mixed mode" (not pure IL), the Verifier respoinds with "Unverifiable
PE/Native code stub." This is not the error I am receiving with the assembly in question.
SQL2012 and SQL2008R2 do not support the same version of the .NET runtime in the SQLCLR subsystem. The former supports 4.0, while the latter supports 2.0 through 3.5. So it is not possible to create a test case with precisely the conditions you specify -
that is, using the same version of .NET in SQL2012 and SQL2008R2 - unless there is some undocumented startup switch or configuration file modification that can be made of which I am not aware.
The failure mode I am seeing is specifically tied to the reference of unmanaged
code references, eg unmanaged pointers. The 2.x assembly registered an working in SQL2008R2 (and its predecessors) contains multiple references to functions with unmanaged pointers, yet registers and works properly when the assembly is CREATED with PERMISSION_SET
= UNSAFE. I expect the same behavior in SQL 2012 - an assembly with references to things like unmanaged pointers should still verify when PERMISSION_SET = UNSAFE is specified.
This is why I am questioning whether the semantics of PERMISSION_SET = UNSAFE in conjunction with the CREATE ASSEMBLY statement have changed between SQL2008 and SQL2012. To me, it appears that SQL2008R2 and its predecessors verified assemblies via the internal
equivalent of a PEVERIFY /MD when PERMISSION_SET = UNSAFE is used, and PEVERIFY /IL when it is not. In SQL2012, it appears that the equivalent of PEVERIFY /IL is done
regardless of the presence of PERMISSION_SET = UNSAFE. This, to my understanding, is contrary to the whole point of PERMISSION_SET = UNSAFE.
PEVERIFY /IL on the previous version of the assembly generates precisely the same kinds of errors generated by the CLR Verifier in SQL2008
without PERMISSION_SET = UNSAFE. When the latter is specified, the assembly registers and works normally. I contend that the CLR Verifier in SQL2012 is ignoring the PERMISSION_SET = UNSAFE qualifier, and hence my search for more information
about how the semantics of this command may have changed specifically for SQL2012.
IF there is an unsupported/undocumented method of allowing the SQLCLR to support both .NET 4.0 and .NET 2.0, I would be very interested in exploring how to leverage it.
Thank you for your interest.

Combine Adobe AIR frontend and XCode backend?!

Hi all,
I am fairly new to the Adobe AIR and the whole ActionScript/Flash development,
so please do not judge me so hard. Before the question a little background, I have
developed an application in XCode (Objective C) for Mac OS X, the same application
was parallelly implemented for windows as well so, now we are looking into the
possibilities to have only one user interface for both and we are considering using
the Adobe AIR for this purpose. The question is how do I integrate the already
existing XCode project to the new Adobe AIR (it is a flex project really, developed
on flash builder ide) interface?
Thank you in advance for any hints!
Best Regards
Lubo

This idea is obsolete, I didn't work it out in detail may be if someone else has tried it can post some sample code, I will be most interested. Till then I will mark it as resolved

SharePoint 2013 OS: Windows Server 2008 R2 vs Windows Server 2012 Standard

Hi Team,
We are thinking on upgrading from SharePoint 2010 to SP 2013 soon. I have been researching about the server OS I should install as host, and it seems that SharePoint 2013 is fully compatible by now with both Windows Server 2008 R2 Standard + SP1 and
Windows Server 2012 Standard. In my opinion we should go with server 2012, but Windows server 2008 is the norm here at our organization and our Infrastructure team seems reluctant to upgrade servers to 2012 yet.
My question is, what SharePoint or Windows 2012 features will we miss if we decide to stay on Windows 2008? What are the perks (selling points) of going with 2012 over 2008? (besides the obvious Microsoft support range extension).
Thanks!
-Rob.

If you stay on Windows Server 2008 R2 you will enter the extended/out of support phase sooner, of course. You will miss out on IIS improvements, although in practical terms it may not mean much.
There are extra patches required for a 2008 R2 deployment that are not needed on 2012 for SharePoint 2013. But other than that, I think the other big issue is that mostly in the community, you'll find people running Server 2012 which means issues are better
'known' by the community, versus 2008 R2 in combination with SharePoint 2013.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SharePoint 2010 + SQL 2008 + DPM 2012 Backup Failures

I have a single SharePoint 2010 WFE and a SQL 2008 server backend. Since configuring DPM to run the SharePoint backup through the WFE, I have had no success with backups.
DPM Reports:
The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError: The writer experienced a non-transient error. If the backup process
is retried, the error is likely to reoccur. (0x800423F4))
Event Log on SQL Server Reports:
Log Name:      Application
Source:        SQLWRITER
Date:          4/24/2014 4:44:17 PM
Event ID:      24583
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      srv-sql-01
Description:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 319
Error state: 1, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
SQLSTATE: 42000, Native Error: 103
Error state: 3, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: The file that starts with '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy334\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content30_1.mdf
' is too long. Maximum length is 259.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="SQLWRITER" />
    <EventID Qualifiers="0">24583</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-24T21:44:17.000000000Z" />
    <EventRecordID>293470</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-sql-01</Computer>
    <Security />
</System>
<EventData>
    <Data>ICommandText::Execute</Data>
    <Data>0x80040e14</Data>
    <Data>SQLSTATE: 42000, Native Error: 319
Error state: 1, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
SQLSTATE: 42000, Native Error: 103
Error state: 3, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: The file that starts with '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy334\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content30_1.mdf
' is too long. Maximum length is 259.
</Data>
    <Binary>53514C434F4E4E43313236330000000053514C434F4E4E433132323800000000</Binary>
</EventData>
</Event>
Followed by:
Log Name:      Application
Source:        VSS
Date:          4/24/2014 4:44:17 PM
Event ID:      8229
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      srv-sql-01
Description:
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
   PostSnapshot Event
Context:
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server 2008 R2:SQLWriter
   Writer Instance ID: {18aa641d-ffcd-44be-84eb-77867e909c51}
   Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
   Process ID: 6036
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">8229</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-24T21:44:17.000000000Z" />
    <EventRecordID>293471</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-sql-01</Computer>
    <Security />
</System>
<EventData>
    <Data>0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
</Data>
    <Data>
Operation:
   PostSnapshot Event
Context:
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server 2008 R2:SQLWriter
   Writer Instance ID: {18aa641d-ffcd-44be-84eb-77867e909c51}
   Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
   Process ID: 6036</Data>
    <Binary>2D20436F64653A20575254575254494330303030353239392D2043616C6C3A20575254575254494330303030333336352D205049443A202030303030363033362D205449443A202030303030323630342D20434D443A202022433A5C50726F6772616D2046696C65735C4D6963726F736F66742053514C205365727665725C39305C5368617265645C73716C7772697465722E65786522202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
</EventData>
</Event>
When I run vssadmin list writers after the error, the "SqlServerWriter" show a State of [11]. I can restart the service and the error clears up showing stable, but the next time I run the backup it fails again.
From the error, it almost sounds like the path is too long. This doesn't totally make sense to me considering the database was successfully backed up before I tried to back it up as a SharePoint database.
Any suggestions would be appreciated.

Got the issue solved.
DPM has issues with DNS Aliases for SQL.
To get this issue sorted out i used the old HOSTS file to point the right name to the right SQL server.

2012 frontend 2008 R2 backend.

Similar Messages

Maybe you are looking for