Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Dynamics CRM 8.2 on-pr...
Customer experience | Sales, Customer Insights,...
Unanswered

Dynamics CRM 8.2 on-prem: different SQL servers on the dev and prod systems

(0) ShareShare
ReportReport
Posted on by Michael.Matsiy 55

Hi 

I faced a situation when I have different SQL servers installed on the server which is using for the Dev organizations and on the server for the others organizations.

On the dev, we have SQL server 12.0.2000.8 and on the other one 13.0.5102.14.

Which kind of problems I can get while delivering? 

Also, sometimes I'm getting issues related to the records with ComponentState = 2 that are stored in the DB and do not give me the ability to import solutions if I don't remove them. Could it be related to the different SQL servers case?

  • Johao Larios Profile Picture
    Johao Larios 1,795 on at
    RE: Dynamics CRM 8.2 on-prem: different SQL servers on the dev and prod systems

    Hello Michael,

    For the plugin issue, have you tried by upgrading the version in visual studio?

    docs.microsoft.com/.../tutorial-update-plug-in

    I think you should open a case with Microsoft Support to get that fixed if the issue is still happening when you upgrade the plug in version within VS.

    Regards

  • Michael.Matsiy Profile Picture
    Michael.Matsiy 55 on at
    RE: Dynamics CRM 8.2 on-prem: different SQL servers on the dev and prod systems

    Hi Johao!

    The issue with a component state is the following:

    1. I'm unregistering existing plugin assembly (usually plugins, but not workflows)

    2. I'm trying to import a new version of a managed solution to the target environment. This version contains the same plugin assembly but with some modifications that are not compatible with a previous version. e.g. step was renamed/removed. or something that usually throws an exception while importing.

    3.  I'm getting an error while importing like "There should not be more than one component instance for a solution being upgraded"

    The way how I'm resolving it:

    After removing there are a lot of images, messages, plugin types, assemblies that have component state 2 or overwrite time is not default one. After removing all of them I can import my managed solution without any issues.

    To import solutions I'm using a package deployer

    Please let me know if you need additional details

  • Johao Larios Profile Picture
    Johao Larios 1,795 on at
    RE: Dynamics CRM 8.2 on-prem: different SQL servers on the dev and prod systems

    Hello Michael!

    Thanks for reaching out. We strongly recommend have the same SQL version between the different environments that you may have in your deployment.

    However, the issue related to componentState =2 I don't think is related to that fact.

    These is the list of the component states:

    0 Published

    1 Unpublished

    2 Deleted

    3 Deleted Unpublished

    What kind of issues are you getting ?

    regards

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans