Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Suggested answer

GP Deploy Reports Creates Bad SSRS Data Connections and Excel ODC files

Posted on by 670

HI, 

I recently performed an upgrade/migration of GP.  Everything seemed fine.  Then we found that client connections to SSRS and Excel reports did not function off of the SQL server.  I was able to correct the SSRS connections by modifying the company connections in SSRS easily but, for Excel, all of the ODC files must be corrected with a string that includes the domain name.  There are 13 companies.

Redeploying reports does not fix the issue because the ODC files seem to use the SQL server instance name but, don't included the domain name.

I thought I could address the issue by adding host records in the HOSTS file but that didn't work.

If I manually correct the ODC file, most reports test will function either immediately or by allowing the Excel file to reference the connection in the ODC file depending on how the Excel report was created.

Is there an easy way to change the ODC files?  It seems like an application bug to me.

I have been researching PowerShell but, that isn't my forte.  the thought of manually correcting 2,942 files is unpleasant.

If I change the Source, it works

From Source=server_name\MSSQLSERVER2019
To Source=server_name.domain.name\MSSQLSERVER2019

I also noted that post failure, if I try to correct the connection, the SQL Server Query connect GUI truncates the source string so, for the key reports in each company, the users can't self help.  But that is not a GP BUG.

Categories:
  • Tim Andaya Profile Picture
    Tim Andaya 670 on at
    RE: GP Deploy Reports Creates Bad SSRS Data Connections and Excel ODC files

    Suggesting it to IT.  I'll post back if it works.

    Thank you.

  • Suggested answer
    RE: GP Deploy Reports Creates Bad SSRS Data Connections and Excel ODC files

    Other than having to switch the data connections on Excel Reports from SQLOLEDB to SQLNCLI11, for TLS 1.2, which we did in the Oct., 2022 release of Dynamics GP, we usually don't have to manually enter the domain name in the data connection to make the reports work.

    Thinking you may be running into more of an DNS issue on the environment, such as specifying a default domain to search.  If this isn't setup, you need to provide the domain name for it to search.

    This article touches on what I'm thinking, to give you an idea:

    learn.microsoft.com/.../configure-domain-suffix-search-list-domain-name-system-clients

    You can edit the registry on one computer and test it to make sure it works or not, then if it does, maybe use group policy or something to make the changes on remaining computers.

    I'm not 100% sure if this will fix the issue, but it does sound like more of an AD/DNS issue.

    Maybe others in the Community have run into the same thing and can share..........

    Thanks

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

Product updates

Dynamics 365 release plans