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

Similar Messages

Slow printing on windows 2008 std, R2 and windows 2012

Hi All,
I have a print server which is configured on windows 2008 R2. We are experiencing slow printing when printing directly from the server or from a client through the server. Small sized files prints fast, anything which has image takes a long time. All the
printers in our organization are Xerox Colorqube 9303. When installed the driver directly on to windows 7 32 bit PC, it prints without any delay. Also, when prints from the server a 2 MB file becomes 15 MB or more while sending. We have tried PCL6 and PS drivers.
To replicate it, i have installed a windows 2012 server ended up with the same result. Installed windows 2008 standard 32 bit with SP2 and the result remains same. Also tried it on windows 8, 64 bit without any luck. So effectively, it works fine only when
directly installed on a windows 7 PC. I have disabled all three: disabling TCP Chimney Offload, RSS, Receive Window Auto-Tuning .
After shooting the print, if you observe the printer properties, it sends data at a very low rate which results a 10 MB documents prints take around 10 minutes. At the same time, file copying from the server to and fro is working normally. All these servers
are directly connected to the cisco 6509 core switch. All the above tests were performed on the same physical switch. The server and clients are on the same network (subnet).
Have anybody come across to a similar issue. Any useful suggestions would deeply appreciated.
Thanks,
Prince Mathew

Hi Prince Mathew,
Based on your description, this issue seems that it’s related to this specific model printer (Xerox
colorqube 9303). Please install the latest version of the driver and the firmware from Xerox website, and then check if this issue still exists.
If it still persists, please clear Printer Spooler Files and enable the Spooler Service again.
For details, please refer to.
1. Click Start, run "Services.msc" (without the quotation marks).
2. In Services list, please double click "Printer Spooler". Then click
Stop, and then click OK.
3. Please locate to: "%WINDIR%\system32\spool\printers", delete all files in this folder.
4. Click Start, run "Services.msc" (without the quotation marks). In Services list, double click
"Printer Spooler". Click on Start. In the Startup Type list, make sure that "Automatic" is selected and click OK.
Then check if this issue can be solved.
Hope this helps.
Best regards,
Justin Gu

Resore SQL server 2008 SP3 database to SQL server 2008 R2 SP1

I have a dump from a SQL server 2008 SP3 server and I'm trying to restore it to SQL server 2008 R2 SP1 server but getting the error:
Msg 3241, Level 16, State 0, Line 2
The media family on device 'E:\Work\backup.bak0' is incorrectly formed. SQL Server cannot process this media family.
Msg 3013, Level 16, State 1, Line 2
RESTORE FILELIST is terminating abnormally.
Are these versions incompatible or is it just a problem with the file? If they are incompatible, I could upgrade my target server to SQL server 2008 R2 SP2, would this help?
The exact version info is as follows:
Source server: Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64) Sep 21 2011 22:45:45 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2)
Target Server: Microsoft SQL Server 2008 R2 (RTM) - 10.50.1617.0 (X64) Apr 22 2011 19:23:43 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Thanks in advance for your help.

SQL server 2008 SP3 is technically a lower version than 2008 R2 SP1
but it was released after it.
The service packs release date don't matter, only the major+minor build versions are important; restore should work in your constellation.
During FTP transfer the file could be damaged, that's possible. The backup file could be also "blocked" by OS because it was download from a different server; then you have to unblock it like every other download file.
Olaf Helper
[ Blog] [ Xing] [ MVP]

SQL 2012 Database Availability Group - Force Automatic Failover

Hi All,
I'd appreciate some help in understanding the following scenario in my test environment.
I have created a DAG with 2 replica servers (both of which are HyperV VM's running W2012 Std).
From a client PC in my test lab, I can connect to the virtual listener of my DAG and confirm via the "select @@servername" command that I am connecting to the primary replica server.
Using the Failover Wizard, I can easily move to primary instance between my 2 nodes and the command above confirms that the primary replica server has changed. So far so good.
What I wanted to test, was what would happen to my DAG in the event of a complete loss of power to the server that was acting as the primary replica server. At first, I thought I would stop the SQL Server service on the primary server, but this did not result
in my DAG failing over to the secondary replica. I have found out that the only way I can do this is by effectively shutting down the primary server in a controlled manner.
Is there any reason why either stopping the SQL Server service on the primary replica, or indeed forcing a power off of the primary replica does not result in the DAG failing over to the secondary replica?
Thanks,
Bob

Hi,
I would verify if Database Availability Group means AlwaysOn Availability Group.
How did you set the FailureConditionLevel?
Whether the diagnostic data and health information returned by sp_server_diagnostics warrants an automatic failover depends on the failure-condition level of the availability group. The failure-condition level specifies what failure conditions
trigger an automatic failover. There are five failure-condition levels, which range from the least restrictive (level one) to the most restrictive (level five). For details about failure-conditions level, see:
http://msdn.microsoft.com/en-us/library/hh710061.aspx#FClevel
There are two useful articles may be helpful:
SQL 2012 AlwaysOn Availability groups Automatic Failover doesn’t occur or does it – A look at the logs
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx
SQL Server 2012 AlwaysOn – Part 7 – Details behind an AlwaysOn Availability Group
http://blogs.msdn.com/b/saponsqlserver/archive/2012/04/24/sql-server-2012-alwayson-part-7-details-behind-an-alwayson-availability-group.aspx
Thanks.
Tracy Cai
TechNet Community Support
Hi,
Thanks for the reply.
It's an AlwaysOn Availability Group.
In my test lab, I have changed the quorum configuration to a file share witness and that has allowed an automatic failover when I turn the primary replica server off (rather than power it off).
I'll take a look at the links you provided.
Regards,
Bob

Crystal reports 2008 sp3 : An error has occurred while attempting to load t

Hello,
Please forgive me for posting in the CR .NET forum because we are using the full Crystal Reports 2008 product and I did not see a category for it. If there is a better forum for this question, please let me know or feel free to move it.
We are having trouble deploying our crystal reports 2008 reports to a Windows Server 2008 R2 server in an aspx application...
I have been working on this issue for 4-days and cannot seem to make any progress, so I would really appreciate your help.
Our Environment:
Development Computer (32-bit, WinXP)
VS2008 (fully updated, was not installed with its Crystal Reports feature)
Crystal Reports 2008 SP3 (downloaded and installed "cr2008_sp3_fullbuild")
Database Server (64-bit)
"SERVER2" is a Microsoft SQL Server 2008 server, fully updated
Web Server (64-bit)
"SERVER3" is a Microsoft Server 2008 R2 Web server.
We have an application that is installed on the Web server and it pulls data from the database server.
The webpages are accessing the database properly. There is a ShowReport.aspx webpage that has the
CrystalReportsViewer on it. We send parameters and logon information to ShowReport.aspx. ShowReport
works properly on our development computer and the report looks good, but it fails on the web server.
We downloaded CRRuntime_12_3_mlb.msi (X86) from SAP/CR and installed it on the web server without any issues.
Our application pool on the web server for this application is set to 32-bit mode. When I launch the
application, it works properly with the database and displays data on web pages, but when I try to
view a report on ShowReport, I get the following error message:
An error has occurred while attempting to load the Crystal Reports runtime.
Either the Crystal Reports registry key permissions are insufficient or the Crystal Reports runtime is not installed correctly.
Please install the appropriate Crystal Reports redistributable (CRRedist*.msi) that contains the version of the Crystal Reports runtime (x86, x64, or Itanium) that is required.
According to everything that I have read, I have properly matched the DLLs: On the development computer, "cr2008_sp3_fullbuild" was installed; On
the web server, "CRRuntime_12_3_mlb.msi (X86)" was installed. They are both Crystal Reports 2008 and not .NET. CR.NET was not installed on our development computer, so our application was built with full Crystal Reports 2008 SP3. On our development computer, .ENGINE is 12.0.2000.0 and
the same version is on the web server.
So, I am completely at a loss as to why we are encountering this error. Help, Please!!!
Thank you in advance,
Mike

Hi Mike,
Did you set your project for X86 mode only? If not do so and rebuild and deploy your app.
Thank you
Don

Xcelsius 2008 SP3 + SAP BW Integration

Hi All,
We are at BO Enterprise Server Ver 3.1 SP2 Fix Patch 2.5 on OS: AIX 5.3, Xcelsius 2008 SP3.1 and BW 7.0
Xcelsius is unable to connect to BW. Msg we receive is..... "The system you are currently connected to is not BW 7.02 or newer. Please disconnect and choose a different system".......Our BW upgrade is not scheduled soon.
As a work around QaaWS was opted to access live data. While accessing Enterprise server, we got a msg....... "you are trying to connect to a server which version is superior to XI 3.1. you may encounter unexpected issues. We recommend to connect to an XI 3.1 server"...... We proceeded and successfully create WSDL URLs but Drop down list of "Method" found to be emptywhen tried access it in Data Manager in Xcelsius.
How to make Xcelsius work in our set up?
Thanks in advance for any help.
Venkat

Vankeet,
Did Xcelsius ever worked with your current existing BW netweaver 7 system?
There are some prerequisites are mentioned in this SAP Note:
Have a look at them...
Note 1400236 - Prerequisites for Xcelsius usage with NetWeaver BI/BW
[https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1400236]
Regards,
Bashir Awan

Oralce EPM Fails to install Weblogic on Windows Server 2008 R2 x64

I've run the installer on Windows Server 2008 R2 x64 and it fails to install Weblogic. I don't have MIDDLEWARE_HOME/oracle_common. Config tool log says missing jars. When I go back to install and choose products individually, Weblogic Server is gray. When I click on Weblogic Server, the message at the bottom says can not be installed.
I have checked that I have extracted the following assemblies:
Oracle Hyperion Enterprise Performance Management System Installer, Fusion Edition Release 11.1.2.0.0
Hyperion Enterprise Performance Management System Foundation Services Release 11.1.2.0.0 - Parts 1 - 4
Oracle Hyperion Enterprise Performance Management System Additional Content Release 11.1.2.0.0
I have run this same set of files on another server and Weblogic was installed. Am I missing something?

I am not sure if it is your problem but I don't think R2 is officially supported, I did have problems with it when I first installed 11.1.2 so I installed with R1 SP2.
Cheers
John
http://john-goodwin.blogspot.com/

SQL Server 2008 R2 SP3 compatibility with TFS 2012?

Hi all,
I have a client who is planning on upgrading from SQL Server 2008 R2 SP2 to SQL Server 2008 R2 SP3 but wants to make sure that their installed Team Foundation Server 2012 databases will be ok?
I have found a Microsoft article saying that TFS 2012 support SQL Server 2008 R2 SP2 but nothing about SP3.
Thanks for your help!
Martyn

Hi Martyn,
According to this
article, Team Foundation Server 2012 (TFS 2012) requires SQL Server 2008 R2 SP1 or SQL Server 2012. From my point of view, it means that we need to run at least SQL Server 2008 R2 SP1 when using TFS 2012, and TFS 2012 can work with SQL Server 2008
R2 SP1 later version (contains SQL Server 2008 R2 SP2 and SQL Server 2008 R2 SP3).
In addition, we recommend you install the latest released service pack for your SQL Server, as service pack includes a number of important fixes that TFS could benefit from.
For TFS issues, for quick and accurate response, I would like to recommend that you ask the question in the Visual Studio Team Foundation Server forums at
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=vstfs . It is appropriate and more experts will assist you.
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.

Upgrade to SP3 from sql server 2008 R2 SP2 and SharePoint server 2010 known issues

Hi Guys,
We are planning to upgrade SQL server to SP3 from 2008 R2 SP2 and would like to known if there are any known issues with SharePoint 2010 server and office web apps.
Though I was searching blogs and forums and could not find any noteworthy but wanted to look if any noted SharePoint issues after the upgrade.
VM

Hi Venu,
There should no issue for SharePoint 2010 with install SP3 for SQL2008R2 (also like comments mentioned in article below), I searched from internal and internet, there seems no document/article mentioned the known issue for SharePoint about this, you can
back up your environment and test the SP3 in a test environment before touching the production environment.
https://habaneroconsulting.com/insights/SharePoint-SQL-Server-Support-Matrix#.VSTY-nkfr4Y
http://blogs.msdn.com/b/glsmall/archive/2014/12/03/list-of-fixes-in-sql-server-2008-r2-sp3.aspx
Thanks
Daniel Yang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Do I need to install x64 and x86 versions of SQL Server 2012 SP2?

Hi,
I have installed x64 version of SQL 2012 SP2. Do I need to install x86 version of SP2 as well?
(I have some x86 components installed as well that came with various things like SSDT-BI and/or Visual Studio installations.)
When I click "SQL Server Installation Center (64-bit).lnk" shortcut and run "Installed SQL Server features discovery report", it says "Microsoft SQL Server 2012 Setup Discovery Report".
When I click "SQL Server Installation Center.lnk" shortcut and run same, it says "Microsoft SQL Server 2012 Service Pack 1 Setup Discovery Report".
Both reports say the same thing: the installed version is 11.2.5058.0, which is SP2.

Hi,
I have installed x64 version of SQL 2012 SP2. Do I need to install x86 version of SP2 as well?
(I have some x86 components installed as well that came with various things like SSDT-BI and/or Visual Studio installations.)
When I click "SQL Server Installation Center (64-bit).lnk" shortcut and run "Installed SQL Server features discovery report", it says "Microsoft SQL Server 2012 Setup Discovery Report".
When I click "SQL Server Installation Center.lnk" shortcut and run same, it says "Microsoft SQL Server 2012 Service Pack 1 Setup Discovery Report".
Both reports say the same thing: the installed version is 11.2.5058.0, which is SP2.
Hello,
No you dont have to install X86 version
SQL server 2012 installable will install SQL server as per process architecture of your machine. If it is 32 bit machine it will install 32 bit version and for 64 bit it will install 64 bit version. installable has facility for both
Even on 64 bit machines some files, which always work in 32 bit compatibilyt mode, will be installed as well andand they go to SQL server (X86) folder. BIDS, SSIS always by default works in 32 bit compatibility mode.
If report says version as 11.2.5058 it means component is patched to SP2
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

SQL 2012 database behaves differently with a unique index and ignore_dup_key = on when inserting data. It works on SQL 2008 db

If you have a table with a unique index and ignore_dup_key = on and you INSERT rows into that table with an ORDER BY clause (because you want to control which of the duplicate
key rows gets inserted), the wrong row gets inserted in SQL2012. It works correctly in SQL 2008.
We have recently migrated a database from SQL 2008 to SQL 2012. We do have few other dbs which are in compatability mode 100. The above operation works fine
in SQL 2008 dbs but not SQL 2012.
I've even tried applying the latest patch for SQL 2012 SP2 with CU2. Still the problem exists. I'm going to call MS support, but want to know if anyone has come across this problem ?

The MS documentation doesn't guarantee that the first row of the duplicates will always be inserted and the next duplicate row(s) get(s) ignored. Where did you find it in the MS documentation? I think you were just lucky that it was always inserting the
first row in SQL 2008 (and ignoring the rest of the duplicates) - I don't think this is guaranteed
Satish Kartan http://www.sqlfood.com/

Sharepoint 2007 and SQL 2008 SP3 on Windows Server 2008 Enterprise SP2 (64-bit)

Is there any documentation we can check if SQL 2008 SP3 is compatible with Sharepoint 2007 SP2 or SP3? Both Sharepoint and SQL servers are running on separate Virtual machines (Windows Server 2008 Enterprise SP2(64-bit)). Currently DB is running on
SQL server 2008 SP2, and we would like to have SP3 loaded on it, but want to find if there is any compatibility issue?
Thanks in advance!
mh

I'm not aware of any known issues with SQL Server 2008 SP3 and SharePoint 2007. I did a quick check and saw one person reporting an issue with their Central Admin site after applying the SQL Server update, but that's it.
With that being said, I would strongly encourage you to test out the application of that SQL Server service pack in a non-production environment well before you apply it in production. There is always a chance that your environment has something set up in
it that would cause an unexpected issue, and the best way to get an idea of whether or not an issue exists is by doing it somewhere else first before you do it in prod.
John
MCITP and MCTS: SharePoint, Virtualization, Project Server 2007
My books on Amazon: The SharePoint 2010 Disaster Recovery Guide and
The SharePoint 2007 Disaster Recovery Guide.
My blog: My Central Admin.

Error while trying to upgrade SQL 2008 (SP2) to SQL 2012: There was a failure to calculate the applicability of setting LICENSEPATH.

Hi,
I am trying to upgrade one of our SQL Server Enterprise (2008 (SP2)) to 2012. I am using the upgrade option but it gives me the following error:
Error Code 0x85640002: There was a failure to calculate the applicability of setting LICENSEPATH
We have downloaded the image from our Volume Licensing account. Also, the same image was used to install SQL 2012 on Windows Server 2012 R2 servers without any issues.
Below is the install summary.txt. I have tried everywhere but no go. Would really appreciate any assistance.
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2057043966
Exit facility code:            1380
Exit error code:               2
Exit message:                  There was a failure to calculate the applicability of setting LICENSEPATH.
Start time:                    2014-02-28 10:58:49
End time:                      2014-02-28 10:58:58
Requested action:              RunRules
Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0x0BA02FC6%400x294A9FD9&EvtType=0x0BA02FC6%400x294A9FD9
Machine Properties:
Machine name:                  xxxxxxx
Machine processor count:       2
OS version:                    Windows Server 2008 R2
OS service pack:               Service Pack 1
OS region:                     U.A.E.
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Package properties:
Description:                   Microsoft SQL Server 2012
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
SPLevel:                       0
Installation location:         D:\x64\setup\
Installation edition:
User Input Settings:
ACTION:                        RunRules
CONFIGURATIONFILE:
ENU:                           true
FEATURES:
HELP:                          false
INDICATEPROGRESS:              false
INSTANCENAME:                  <empty>
PID:                           *****
QUIET:                         true
QUIETSIMPLE:                   false
RULES:                         GlobalRules
UIMODE:                        Normal
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140228_105848\ConfigurationFile.ini
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               The rule result report file is not available.
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingApplicabilityException
    Message:
        There was a failure to calculate the applicability of setting LICENSEPATH.
    HResult : 0x85640002
        FacilityCode : 1380 (564)
        ErrorCode : 2 (0002)
    Data:
      SettingId = LICENSEPATH
      WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingApplicabilityException@2
      DisableWatson = true
    Stack:
        at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
        at Microsoft.SqlServer.Configuration.BootstrapExtension.ValidateChainerSettingAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
    Inner exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingValueException
        Message:
                There was a failure to calculate the default value of setting LICENSEPATH.
        HResult : 0x85640001
                FacilityCode : 1380 (564)
                ErrorCode : 1 (0001)
        Data:
          SettingId = LICENSEPATH
          WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingValueException@1
        Stack:
                at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.CalculateValue()
                at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates()
                at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.Publish(Publisher publisher)
                at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
        Inner exception type: System.ArgumentException
            Message:
                        Culture ID 3072 (0x0C00) is not a supported culture.
                        Parameter name: culture
            Stack:
                        at System.Globalization.CultureInfo..ctor(Int32 culture, Boolean useUserOverride)
                        at System.Globalization.CultureTable.GetCultures(CultureTypes types)
                        at Microsoft.SqlServer.Configuration.SetupExtension.LcidUtilities.GetLangPackParentFolderForLcid(String lcid)
                        at Microsoft.SqlServer.Configuration.SetupExtension.LcidUtilities.GetLcidFolder(ServiceContainer context, String baseFolderFullPath)
                        at Microsoft.SqlServer.Configuration.SetupExtension.LicensePathSetting.DefaultValue()
                        at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallFunctionWhileAutosubscribing[T](SubscriberDelegate
subscriberDelegate, Int32 priority, AutosubscribingFunctionDelegate`1 function)
                        at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.CalculateValue()
Regards,
Mohammed

Culture ID 3072 (0x0C00) is not a supported culture.
                        Parameter name: culture
This appears to be the root problem. It seems that the regional settings on this machine is messed up. 0x0C00 is an unusual LCID, they do not normally not end in two zeroes.
is there a custom culture installed on this machine?
Review the regional settings and also check the System locale. If it looks spooky, set it to Arabic - U.A.E. if this is where you are located.
Erland Sommarskog, SQL Server MVP, [email protected]

DeadLocks on Query Notifications with SQL Server 2008 SP3

Hello,
according to this article https://support.microsoft.com/kb/975090 the issue with deadlocks on query notifications should be fixed with SQL Server 2008 SP3 (10.0.5500.0). But we still get deadlocks in the following manner:
<resource-list>
<keylock hobtid="72057598393909248" dbid="5" objectname="MyDB.sys.query_notification_1411013420" indexname="cidx" id="lock1731c1f00" mode="RangeX-X" associatedObjectId="72057598393909248">
<owner-list>
<owner id="process573dc8" mode="RangeX-X"/>
</owner-list>
<waiter-list>
<waiter id="process58ddc8" mode="RangeS-U" requestType="wait"/>
</waiter-list>
</keylock>
<keylock hobtid="72057598372872192" dbid="5" objectname="MyDB.sys.query_notification_253437289" indexname="cidx" id="lock800c8780" mode="RangeS-U" associatedObjectId="72057598372872192">
<owner-list>
<owner id="process58ddc8" mode="RangeS-U"/>
</owner-list>
<waiter-list>
<waiter id="process573dc8" mode="RangeS-U" requestType="wait"/>
</waiter-list>
</keylock>
</resource-list>
Is there any need to install another fix?
Thanks in Advance!

Hello,
SQL Server 2008 SP4 and all cumulative updates of SP3 do not have fixes related to deadlocks.
Maybe the following workarounds and solutions can help in your scenario.
http://stackoverflow.com/questions/3707137/understanding-deadlocks-with-sql-server-query-notifications
Deadlock Prevention. In case you need to lock multiple conversation groups in a transaction, you need to take the same order to lock the different conversation groups in all transactions, otherwise you will have a deadlock issues.
Source:
http://blogs.msdn.com/b/kangmo/archive/2008/12/17/a-brief-guide-on-sql-server-service-broker.aspx
Try to may transactions more simple and shorter.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL 2012 and later will fail to publish a database for any tables with a default constraint that references a user defined function.

Script will create database, 3 database objects and publish.
The error is due to the generation script to create the conflict tables that is not stripping out default constraints that reference a UDF.
As you can see below, the failure is on the generation script for the conflict table.
The conflict table should be a bucket table that shouldn’t enforce data integrity.
See how the default constraints for the columns someint and somestring were stripped out of the generation logic however the default constraint that utilizes a UDF persist and uses the same object name that was used on the production table (The
bold line) , this occurs if I explicitly name the constraint or let the system generate the name for me like in the example posted.
  The only way I could see getting around this right now is to drop all default constraints in the system that uses a UDF, publish then add the constraints back which is vulnerable to invalid data and a lot of moving
steps. This all worked with SQL 2000, 2005, 2008, 2008r2, it’s stopped working in SQL 2012 and continues to not work in SQL 2014.
Error messages:
Message: There is already an object named 'DF__repTable__id__117F9D94' in the database.
Could not create constraint. See previous errors.
Command Text: CREATE TABLE [dbo].[MSmerge_conflict_MergeRepFailurePublication_repTable](
        [id] [varchar](8) NULL CONSTRAINT [DF__repTable__id__117F9D94] DEFAULT ([dbo].[repUDF]()),
        [somedata] [varchar](64) NULL,
        [rowguid] [uniqueidentifier] ROWGUIDCOL NULL,
        [someint] [int] NULL,
        [somestring] [varchar](64) NULL
Parameters:
Stack:    at Microsoft.SqlServer.Replication.AgentCore.ReMapSqlException(SqlException e, SqlCommand command)
   at Microsoft.SqlServer.Replication.AgentCore.AgentExecuteNonQuery(SqlCommand command, Int32 queryTimeout)
   at Microsoft.SqlServer.Replication.AgentCore.ExecuteDiscardResults(CommandSetupDelegate commandSetupDelegate, Int32 queryTimeout)
   at Microsoft.SqlServer.Replication.Snapshot.YukonMergeConflictTableScriptingManager.ApplyBaseConflictTableScriptToPublisherIfNeeded(String strConflictScriptPath)
   at Microsoft.SqlServer.Replication.Snapshot.BaseMergeConflictTableScriptingManager.DoConflictTableScriptingTransaction(SqlConnection connection)
   at Microsoft.SqlServer.Replication.RetryableSqlServerTransactionManager.ExecuteTransaction(Boolean bLeaveTransactionOpen)
   at Microsoft.SqlServer.Replication.Snapshot.BaseMergeConflictTableScriptingManager.DoConflictTableScripting()
   at Microsoft.SqlServer.Replication.Snapshot.MergeSmoScriptingManager.GenerateTableArticleCftScript(Scripter scripter, BaseArticleWrapper articleWrapper, Table smoTable)
   at Microsoft.SqlServer.Replication.Snapshot.MergeSmoScriptingManager.GenerateTableArticleScripts(ArticleScriptingBundle articleScriptingBundle)
   at Microsoft.SqlServer.Replication.Snapshot.MergeSmoScriptingManager.GenerateArticleScripts(ArticleScriptingBundle articleScriptingBundle)
   at Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.GenerateObjectScripts(ArticleScriptingBundle articleScriptingBundle)
   at Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.DoScripting()
   at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.DoScripting()
   at Microsoft.SqlServer.Replication.Snapshot.MergeSnapshotProvider.DoScripting()
   at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot()
   at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun()
   at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: MSSQLServer, Error number: 2714)
Get help: http://help/2714
Server COL-PCANINOW540\SQL2012, Level 16, State 0, Procedure , Line 1
Could not create constraint. See previous errors. (Source: MSSQLServer, Error number: 1750)
Get help: http://help/1750
Server COL-PCANINOW540\SQL2012, Level 16, State 0, Procedure , Line 1
Could not create constraint. See previous errors. (Source: MSSQLServer, Error number: 1750)
Get help: http://help/1750
Pauly C
USE [master]
GO
CREATE DATABASE [MergeRepFailure]
ALTER DATABASE [MergeRepFailure] SET COMPATIBILITY_LEVEL = 110
GO
USE [MergeRepFailure]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
create view
[dbo].[repView] as select right(newid(),8) as id
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE FUNCTION [dbo].[repUDF]()
RETURNS varchar(8)
BEGIN
declare @val varchar(8)
select top 1 @val = id from [repView]
return @val
END
GO
create table repTable
id varchar(8) default([dbo].[repUDF]()),
somedata varchar(64) null,
rowguid uniqueidentifier ROWGUIDCOL default(newid()),
someint int default(1),
somestring varchar(64) default('somestringvalue')
GO
insert into reptable (somedata) values ('whatever1')
insert into reptable (somedata) values ('whatever2')
go
/*test to make sure function is working*/
select * from reptable
GO
/*Publish database*/
use [MergeRepFailure]
exec sp_replicationdboption @dbname = N'MergeRepFailure', @optname = N'merge publish', @value = N'true'
GO
declare @Descrip nvarchar(128)
select @Descrip = 'Merge publication of database ''MergeRepFailure'' from Publisher ''' + @@servername +'''.'
print @Descrip
-- Adding the merge publication
use [MergeRepFailure]
exec sp_addmergepublication @publication = N'MergeRepFailurePublication', @description = N'@Descrip',
@sync_mode = N'native', @retention = 14, @allow_push = N'true', @allow_pull = N'true', @allow_anonymous = N'true',
@enabled_for_internet = N'false', @snapshot_in_defaultfolder = N'true', @compress_snapshot = N'false', @ftp_port = 21,
@ftp_subdirectory = N'ftp', @ftp_login = N'anonymous', @allow_subscription_copy = N'false', @add_to_active_directory = N'false',
@dynamic_filters = N'false', @conflict_retention = 14, @keep_partition_changes = N'false', @allow_synctoalternate = N'false',
@max_concurrent_merge = 0, @max_concurrent_dynamic_snapshots = 0, @use_partition_groups = null, @publication_compatibility_level = N'100RTM',
@replicate_ddl = 1, @allow_subscriber_initiated_snapshot = N'false', @allow_web_synchronization = N'false', @allow_partition_realignment = N'true',
@retention_period_unit = N'days', @conflict_logging = N'both', @automatic_reinitialization_policy = 0
GO
exec sp_addpublication_snapshot @publication = N'MergeRepFailurePublication', @frequency_type = 4, @frequency_interval = 14, @frequency_relative_interval = 1,
@frequency_recurrence_factor = 0, @frequency_subday = 1, @frequency_subday_interval = 5, @active_start_time_of_day = 500, @active_end_time_of_day = 235959,
@active_start_date = 0, @active_end_date = 0, @job_login = null, @job_password = null, @publisher_security_mode = 1
use [MergeRepFailure]
exec sp_addmergearticle @publication = N'MergeRepFailurePublication', @article = N'repTable', @source_owner = N'dbo', @source_object = N'repTable', @type = N'table',
@description = null, @creation_script = null, @pre_creation_cmd = N'drop', @schema_option = 0x000000010C034FD1, @identityrangemanagementoption = N'manual',
@destination_owner = N'dbo', @force_reinit_subscription = 1, @column_tracking = N'false', @subset_filterclause = null, @vertical_partition = N'false',
@verify_resolver_signature = 1, @allow_interactive_resolver = N'false', @fast_multicol_updateproc = N'true', @check_permissions = 0, @subscriber_upload_options = 0,
@delete_tracking = N'true', @compensate_for_errors = N'false', @stream_blob_columns = N'false', @partition_options = 0
GO
use [MergeRepFailure]
exec sp_addmergearticle @publication = N'MergeRepFailurePublication', @article = N'repView', @source_owner = N'dbo', @source_object = N'repView',
@type = N'view schema only', @description = null, @creation_script = null, @pre_creation_cmd = N'drop', @schema_option = 0x0000000008000001,
@destination_owner = N'dbo', @destination_object = N'repView', @force_reinit_subscription = 1
GO
use [MergeRepFailure]
exec sp_addmergearticle @publication = N'MergeRepFailurePublication', @article = N'repUDF', @source_owner = N'dbo', @source_object = N'repUDF',
@type = N'func schema only', @description = null, @creation_script = null, @pre_creation_cmd = N'drop', @schema_option = 0x0000000008000001,
@destination_owner = N'dbo', @destination_object = N'repUDF', @force_reinit_subscription = 1
GO

More information, after running a profile trace the following 2 statements, the column with the default on a UDF returns a row while the other default does not. This might be the cause of this bug. Is the same logic to generate the object on
the subscriber used to generate the conflict table?
exec sp_executesql N'
select so.name, schema_name(so.schema_id)
from sys.sql_dependencies d
inner join sys.objects so
on d.referenced_major_id = so.object_id
where so.type in (''FN'', ''FS'', ''FT'', ''TF'', ''IF'')
and d.class in (0,1)
and d.referenced_major_id <> object_id(@base_table, ''U'')
and d.object_id = object_id(@constraint, ''D'')',N'@base_table nvarchar(517),@constraint nvarchar(517)',@base_table=N'[dbo].[repTable]',@constraint=N'[dbo].[DF__repTable__id__117F9D94]'
exec sp_executesql N'
select so.name, schema_name(so.schema_id)
from sys.sql_dependencies d
inner join sys.objects so
on d.referenced_major_id = so.object_id
where so.type in (''FN'', ''FS'', ''FT'', ''TF'', ''IF'')
and d.class in (0,1)
and d.referenced_major_id <> object_id(@base_table, ''U'')
and d.object_id = object_id(@constraint, ''D'')',N'@base_table nvarchar(517),@constraint nvarchar(517)',@base_table=N'[dbo].[repTable]',@constraint=N'[dbo].[DF__repTable__somein__1367E606]'
Pauly C

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

Similar Messages

Maybe you are looking for