At our company we currently have a Dynamics CRM 2015 instance running, which has all its databases located on our central database server. Recently, we started developing a new solution, this time based on Dynamics CRM 2016, and for this version too we want to have its databases located on our central database server.
However, when I try to install this CRM 2016 instance, the CRM 2016 installer reports the following error (which is correct, as the existing database is from our CRM 2015 instance):
The following databases already exist on the specified SQL Server: MSCRM_CONFIG
Is it supported to deploy two different versions of Dynamics CRM on the same database server, and if so, how?
It's not supported to have two CRM installation (even same version) on the same SQL server instance. Also installing CRM on same server but on separate instances might put you in trouble with for example SSRS Report Connector.
I take it that you currently have your SQL server deployed using the default instance? (ie; you reference you SQL server as <machine_name>)
If you're not in a position to create a new SQL server (the main limitation being licensing) one option you can consider would be to deploy an additional named instance on the existing server. You could then point your new CRM deployment at, for example, <machine_name>\CRM2016
Related
The database for our Dynamics CRM installation is clustered and located on two servers. Somewhere, the MSCRM_CONFIG database is called on one of the SQL instances instead of the cluster, leading to access problems.
I need to correct this and make sure the database is called on the cluster instead. Where can I look for places where MSCRM_CONFIG is called from (config files, services etc)?
What I have tried without success
Looked in the config files for our custom-built CRM-related services
Searched config files in the Program Files\Microsoft Dynamics CRM folder for the name of the instance
Looked at the Deployment Manager for the SQL Server for our CRM Organization
Every Dynamics CRM Server (front-end and back-end as well as servers with the discovery or deployment role) can be expected to open connections to the MSCRM_CONFIG database. This database is needed to get e.g. the organization settings.
The connection string for the MSCRM_CONFIG database can be found on these servers in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM\configdb.
I have installed Oracle 10g database and Oracle 10g developer suite.
I am beginner to use Oracle BI publisher for making reports.
Today i have installed Oracle BI publisher desktop for making reports in ms-word 2007.
when i try to log on in BI Publisher option in ms-word. It ask for username, password & report server.
Should i need to installed the BI Publisher Server to fill up the report server details?
please advice.
Thanks.
Yes, you need to connect to a BI Publisher Server instance to create new reports unless you have a local XML file of sample data from the Server-side Data Model.
With the Template Builder Install you should have a good set of samples.
C:\Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\samples\RTF templates\Balance Letter
This Tutorial from the Oracle Technology Network will move you along nicely working with the sample files noted above.
Creating Report (RTF) Templates with MS Word (This tutorial shows how to work "off-line" with a Sample Data XML file)
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bip/tb4word/tbwordbip.htm
For real work you will need access to a fully installed BI EE environment then you can reach the BI Publisher component (XMLPSERVER)
Username: weblogic
Password: ((PASSWORD))
Report Server: http://NAME:PORT/xmlpserver
For a simple install of BI the URL could be:
http://192.168.56.101:7001/xmlpserver
Without a corresponding server you cannot pull in the data elements defined against the source.
This tutorial will show you much more about BIP.
Getting Started with Oracle BI Publisher 11g (focused on using the Online Report Writer:
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bip/bip11g/gettingstarted/gettingstarted.htm
I'm trying to create a Synch Module using MS Synch Framework wherein records from 2 branches will be synched into a central branch database. I wanted to achieve this with MS Sql Server 2008 R2. I can't seem to figure out the Synch Framework components I need for this project. Our goal is to be able to synch the records over the cloud.
if you look at the documentation, there is a walkthrough on how to do it.
see: Tutorial: Synchronizing SQL Server and SQL Express
don't mind that it says SQL Express, the walkthrough will work with SQL Express, LocalDB, SQL Server and Azure SQL Database as they all use the same SqlSyncProvider.
if the central database is an Azure SQL Database, have a look at these as well: How to: Configure and Execute Synchronization with SQL Azure and Walkthrough of Windows Azure Sync Service Sample
I have two CRM's MS CRM 2011 (on-premise with SQL server 2008) and MS CRM 2011 (in the cloud).
I want to migrate data from on-premise to online using SSIS 2008, were i installed a third party components like "CRM Source Component" and "CRM Destination Component". Here when i'm trying to map all attribute from source to destination except auto generated fields(GUID) or lookup fields in CRM like Accountid, ParentCustomerid, territoryid(which are relationship fields(FK) with other entities) etc., data is moving perfectly else package is getting failed.
Here how can I load these missing attribute values into CRM?
It could be that you are violating the referential integrity constraints. Try removing ( temporarily) all the constraints on the destination tables before executing your package.
Inside the readme file of the ASP.NET Universal providers NuGet package is this quote
The SqlMembershipProvider, SqlRoleProvider, SqlProfileProvider classes that shipped in ASP.NET through version 4 support only Microsoft SQL Server and Microsoft SQL Server Express. They do not support newer offerings such as Microsoft SQL Azure and Microsoft SQL Server Compact.
However, when I run the custom aspnet_regsql scripts for Sql Azure http://support.microsoft.com/kb/2006191 and then point my web.config to the SQL Azure database, ASP.NET membership seems to work correctly.
Can anyone tell me what exactly doesn't work with SQL Azure, that the universal providers enable?
The main difference, as far as I can tell, is that when you connect to Sql Azure you need to implement retry logic. The original providers won't retry when a connection error occurs and this will happen from time to time with SQL Azure.
Also, the original providers don't raise exceptions containing the full SQL error codes so if your database is being throttled you won't know which throttling rule is being applied. At least this is what the SQL Azure support team tell me - I'm currently in the process of upgrading for this reason.
A note of caution: the Universal Providers seem to use a different database schema to the original providers, so you will need to migrate membership data. If you are starting a new project it will be much easier to change these providers before you go live with real users!
the universal providers enable you to use asp.net membership system on sqlazure and also make the implementation sql agnostic. you can take the same app using universal providers and change the datasource to be sql server/sqlexpress/sqlce/localdb etc