.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

compatibility of publication

Posted By:      Posted Date: October 12, 2010    Points: 0   Category :Sql Server


I am getting the following error while trying to create new publication

Publication 'testdb_pub' cannot be added to database 'testdb', because a publication with a lower compatibility level already exists. All merge publications in a database must have the same compatibility level.

Yes initially i was having replication with 80 compaitbility mode and then i changed it to 100(using sp_changemergepublication) before adding new publication...

but it still throws error....

Any suggestions TIA

View Complete Post

More Related Resource Links

Reporting Services SQL 2005 .Net 4 compatibility?


I've been working on my first asp.net application and for the most part it's been pretty smooth.  Right now I'm having trouble getting reporting services working under SQL Server 2005.  I developed the site with Visual Studio 2010 and didn't think about any of the .Net 4.0 compatibility issues that have arisen.  I'm having no problems with the site communicating with SQL Server 2005 for the regular database stuff.  The only problem I'm having is with setting up Reporting Services.  I have the .Net 4.0 framework installed on the server, however Reporting Services is still using 2.x.  I'm not sure if this is a problem with SSRS or with IIS.  When i go to localhost/Reports it's reading my web.config for my application and throwing an error: "Parser Error Message: Unrecognized attribute 'targetFramework'."  This is referring to a line in my web.config where targetFramework is set to 4.0.

Software that I'm using:

  • Visual Studio 2010
  • SQL Server 2005 Standard
  • IIS 7.0
  • .Net 4.0

Any suggestions?  

CLR Inside Out: Ensuring .NET Framework 2.0 Compatibility


If we learned only one thing about compatibility in the past few years, it is that compatibility is much more than avoiding breaking changes. On the Microsoft®. NET Framework and Visual Studio® teams, we do our part to ensure that the products we build are stable platforms that developers can truly rely on.

Jesse Kaplan

MSDN Magazine March 2006

Info about Silverlight compatibility

Where is Silverlight compatibility across other platforms, such as Mac, Linux and mobile devices. Does it still lag behind the current Windows builds?   Timothy Johnson www.wearefound.com

Transactional Publication With Article Using DATE Datatype Causes Snapshot Agent to Fail with Error

So I am using SQL Server 2008 Enterprise Edition (64Bit) and have run into a strange problem that is baffling me. I have two tables that I need to replicate.  They are identical in specification except the name (one is for monthly stats and one daily stats) CREATE TABLE [dbo].[statsDailyLite]( [EntryDate] [date] NOT NULL, [SetID] [int] NOT NULL, [ProductID] [smallint] NOT NULL, [Hooks] [int] NOT NULL, [AdViews] [int] NOT NULL, [Clicks] [int] NOT NULL, [UAdViews] [int] NOT NULL, CONSTRAINT [PK_statsDailyLite] PRIMARY KEY CLUSTERED ( [EntryDate] ASC, [SetID] ASC, [ProductID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90) ) GO CREATE TABLE [dbo].[statsMonthlyLite]( [EntryMonth] [date] NOT NULL, [SetID] [int] NOT NULL, [ProductID] [smallint] NOT NULL, [Hooks] [int] NOT NULL, [AdViews] [int] NOT NULL, [Clicks] [int] NOT NULL, [UAdViews] [int] NOT NULL, CONSTRAINT [PK_statsMonthlyLite] PRIMARY KEY CLUSTERED ( [EntryMonth] ASC, [SetID] ASC, [ProductID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90) ) GO They both conatin a thousand or so test rows of data, and they are both in a transactional publication going to another SQL 2008 box. Now when the tables are empty

Compatibility problem: an "sql server 2008 R2" db backup cannot be restored to an "sql server 2008"

To verify if the "2008 R2" version can be restored back to a "2008" dbserver I make an experiment:  construct a database on R2 version ( version : 10.50.xxx )  and backup it; then I try to restore the db backup to a "sql server 2008" db-server ( version : 10.0.xxx ) but get failed. Error message is as shown: The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.2531. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.   Originally I want to upgrade a "2008" server to "2008 r2" , but this problem withdraws me: if I do so , I am afraid all the existing clientuser's dbs cannot be backed up to themselves if they don't have "2008 r2" locally:   if a database is backed up under "2008 r2" environment whereas client user only has "2008" db server, does it mean he cannot restore it anymore?   So I wonder if there is an approach that helps me to create a "backward-compatible" database; when creating database on wizard there is an option to choose "compatibility level" but I don't think it meets my requirement..    Anyone can help me on this ??    

Master page... How to set compatibility mode in IE8

Hi..Im using this code in master page <head><meta http-equiv="X-UA-Compatible" content="IE=7" /></head>In IE7 all my content is perfect..In IE8 itz not perfect so i write the above code but still not working? what to do? 

Transactional publication with updatable subscriptions in SQL Server 2005, SvPk 2

Subscription to "Transactional Publication with Updateable Subscriptions" works only one way.  Changes take effect on subscriber, but the subcriber is unable to update data on publisher.   I have Sanpshot Agent process running under SQL Server Agent service account with login 'sa.'  All agents are running at the Distributor (Publishing Server.)   The subscriber is unable to connect to the Distributor using the SQL Server login.    Following is the error message I get:   Creating Subscription(s)... - Creating subscription for 'SQL3' (Warning) Messages Unable to set the Publisher login for the updatable subscription. You may have to set this up directly on the Subscriber machine using sp_link_publication. (New Subscription Wizard)------------------------------ADDITIONAL INFORMATION:An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)------------------------------MSDTC on server 'SQL3' is unavailable.Changed database context to 'DB_SQL1_to_SQL3_on_3'. (Microsoft SQL Server, Error: 8501)For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3054&EvtSrc=MSSQLServer&EvtID=8501&LinkId=20476   Please suggest procedure to end this dilemma.  The link has no info available.

Report Builder 3.0 'backward' compatibility??

I've been asked to deploy Report Builder -- a new deployment, it's never been deployed before. Can RB 3.0 create reports against all versions of SQL Server -- 2005, 2008, and 2008 R2?? I understand that they might not be backward-compatible with earlier versions of Report Builder. Can Report Builder 3.0-created reports be used and seen within WSS 3.0 running on SQL 2008?? -- what would be necessary to make this happen?? The present reporting server files installed to the Citrix servers and SharePoint server are SQL 2008 Reporting Services files (10.x), I imagine installing Report Builder 3.0 would be compatible?? Thank you, Tom

problem of compatibility of dll

Hi guys! I'm doing a c# project where i need to access the terminal service profile path and the home directory of active directory. i saw that i needed the tsuserex.dll and the tsuserex.dll.mui i need to do regsvr32 tsuserex.dll i have an error message : the module "tsuserex.dll" may not compatible with the version of Windows that you're running. Check if the module is compatible with an x86 (32-bit) or x64 (64 bit) version of regsvr32.exe. I did'nt saw any tsuserex.dll for 32 bits or the one that I've downloaded was invalid... For you information, I'm currently running on windows 7 32 bits. If you need more information don't hesitate to ask :) Thanks

Backward Compatibility of Windows Mobile 6 application

Hello, I have a app developed to run on Windows Mobile 6 (using VS 2008).  The requirement now is to get it running on Windows CE 5.0. (basically backport it to the very old version of windows mobile OS as the client is reluctant to upgrade the mobile OS) I did some research but havent found a convincing solution yet and still dont know whether this is even possible.  If it is possible, can you please let me know the detailed procedure? My environment details are: Win 7 (64 bit), running Visual Studio 2008. The application uses SQL CE 3.5. Thanks, P Joe      

add new article to existing publication

I have an existing publication with 10 articles configured for Transactional replication. The replication is running fine. Now I wish to add another table (article) to this publication. My requirement is to ensure that I don’t need to generate a snapshot of all the articles being published, if I add a single article only that particular article should be published.

Linq forward compatibility issue

In Linq 3.5 I used to be able to do this, but the code in bold is no longer compatible in Linq 4.0, Is there another way to declare the query variable prior to assigning it (PLEASE DO NOT SUGGEST TO DECLARE AS VAR, IT DOES NOT WORK AND CAN NOT BE DECLARED AS NULL):   ProjectArtifactsDataContext dbProjectAttributes = new ProjectArtifactsDataContext();IQueryable<ProjectArtifacts.Defect> query1 = null;   This type of declaration allowed me to create aggregate and complex queries such as         if (UserControlHost.ShowMyItemsOnly)        {            Guid currentUserId = (Guid)Membership.GetUser(Membership.GetUser().UserName).ProviderUserKey;            query1 = dbProjectAttributes.Defects.Where(defect =>                 defect.Active == true && defect.AssignedTo == currentUserId);        }         else        {            if (FilterInactive == true)                que

Compatibility issue between Job and SSIS Pacakge

HI All, I have created package in SSIS which process the cube in Incremental mode,but what problem i am facing when i run the package first,its runs successfully but not updated the cube while when i run the package secind time it upload the data in to the cube and this happens regulrly. This happens with processing mode too.  Kindly Suggest what mistake i have commited.   Shraddha  

Outer join operators *= and =* are not supported in 90 or later compatibility modes Upgrade issue

Hi all In processes of upgrading SQL Server 2000 to SQL Server 2008 I held up with one issue I am not a good pragrammer If some helps me how to modify this query,realy it help for me. "Outer join operators *= and =* are not supported in 90 or later compatibility modes" Here this query SELECT Brnd.Name, Dev.Devype FROM Prd,PrdRel, Rel, RelVer, DevSoft, DevCla, Dev, Brnd,OVer WHERE Prd.ID = PrdRel. Product AND Rel.ID = PrdRel.Release AND RelVer.Release = Rel.ID AND DevSofte.ReleaseVersion = RelVer.ID AND DevSoft.DeviceClass = DevCla.ID AND DevCla.ID = Dev.DeviceClass AND Brnd.ID = Dev.Brand AND OVer.ID =* Dev.OSVersion AND RelVer.Latest = 'Y' AND Prd.ID = @Product AND Rel.OS IN (@OS) Please some help me how to code  to come out from the problem. your help going to be greate for me.  SNIVAS

MSSQL Server 2008 Workgroups install to Win 7 - Compatibility issues

I attempted to install MSSQL Server 2008 Workgroups from the DVD to a Win 7 workstation.  Error "This Program has known compatibility issues.  The directions are to download the MSSQL Server Service Pack.  I downloaded SP 1 and SP 2.  Neither SP will install.  The DVD install also has a run option displayed along with the Compatibility message.  I select "Run" and it appeared to install, with Start\Programs\Microsoft SQL Server 2008\Configuration Tools\ SQL Server Installation Center 64bit.  However, running the 64bit installation process results in no change.  My question is how to install the MSSQL Server 2008 Workgroups on the Win 7 machine.  I would appreciate your thoughts.

Compatibility of microsoft SQL Server Maneger Studio in Windows 7 Starter

In the Windows 7 Starter I can´t start maneger studio

Databases running in compatibility range, upgrade recommended.

I am running Windows Server 2008 R2 and Sharepoint foundation 2010. Both the server install and sharepoint are new and I don't understad why I am getting the the following notification in my Sharepoint Central Administration Console: The SharePoint Health Analyzer has detected some critical issues that require your attention. View these issues. When i clicked view issues two issues which are as follows: 1.   Title Databases running in compatibility range, upgrade recommended. Severity 2 - Warning Category Configuration Explanation The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range: SharePoint_Config_53245559-f688-46f8-9c1e-e6a5553fd80b, SharePoint_AdminContent_bdba18ef-0884-4062-ad0e-0e3674b9d814, WSS_Content, WSS_Logging. Remedy To achieve optimal results from these databases, use Upgrade-SPContentDatabase to upgrade Content databases, or psconfig.exe to upgrade other databases.  For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142697". Failing Servers   Failing Services SPTimerService (SPTimerV4) Rule Settings View The problem is when i go to the links under the Remedy headings they are both not providing me with any clear solutions. For the first pro
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend