web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Management Reporter an...
Microsoft Dynamics SL (Archived)

Management Reporter and SL 2015

(0) ShareShare
ReportReport
Posted on by David Callery 1,141

Trying to install MR CU14 (new install) after upgrade to Dynamics SL2015.  Upgrade went fine and SL is working.  Installing Management Reporter returns the following error when trying to configure:

Error The Database selected to be configured is NOT a valid Microsoft Dynamics SL Application database.

 


I have not encounter this before, any suggestions?

Thanks

*This post is locked for comments

I have the same question (0)
  • Butch Adams Profile Picture
    Butch Adams 4,763 on at

    This is off the top of my head, but it sounds like you have a database in your configuration that might have been deleted but not removed from the domain and/or company tables.

  • David Callery Profile Picture
    David Callery 1,141 on at

    Thanks Butch, I will check that.  I was able to uninstall the CU14 release and go back to CU12 and had no issues

  • Butch Adams Profile Picture
    Butch Adams 4,763 on at

    I don't remember what version I was working with when I saw this. It might have been more recent than CU12 but I can't swear to it.

    CU14 has been a good version for us so far. I hope you can chase it down.

  • Community Member Profile Picture
    Community Member on at

    I ran into this issue just recently. In my case in the SL System database DOMAIN table was a record entry of a non SL App database. In this case it was the actual name of the Data Mart Database. How the heck it got there I am not sure. But it's presence reeked havoc as three triggers were created on the SIVSystem acctsub table. A trigger for delete, insert and update were all created with the name of the DM database.

    I removed the DOMAIN record, but was unaware of the triggers. The client was unable to post until the triggers were disabled.

  • Becky K Profile Picture
    Becky K 102 on at

    CU15 and a hot fix are also out.  So far I have applied these to a few clients and they are seeing performance improvement and some of their issues resolved.  

  • JackWoods Profile Picture
    JackWoods on at

    I had the same thing kind of databases in the domain table that didn't exist any longer.  I removed the two records and then it went through fine.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans