Windows 10 Creator Update & Dynamics GP


An interesting issue/question was posted on our community forum regarding an error message popping up while exiting GP2015 R2 & GP2016 R2.

Specifically, GP2015/2016 R2 on Windows 10 Creator Update is what seems to be throwing this error while exiting.

Link to original forum post: Windows 10 Creator and GP2015 R2

One member, Ron Koendrink, figured out that it’s Mekorma MICR that’s causing this issue on his environment. Per his update, Mekorma had confirmed that it’s an issue for which a fix was available.

Anyone out there who use Mekorma MICR and planning to upgrade your OS to Windows 10 Creator Update, please contact them and get the fix.

A note of thanks to Ron.

Vaidy

Advertisements

GP2016 DAG Issue


I am wondering whether someone has already faced this issue and has shared his/her knowledge on this.

My issue is with GP2016 VS Tools Dictionary Assembly Generator (DAG), where it takes more than 10 mins to complete generating DYNAMICS.DIC assemblies. Not only that, it also doesn’t generate Application.MicrosoftDynamicsGp.dll in the first attempt itself.

Look at the following screenshot:

Screen Shot 2017-04-28 at 01.29.38 pm.png

First two “successful” attempts of running DAG created only the metadata files and not the actual DLL. I’m running the DAG for the third time, as I write this post.

UPDATE: Third time’s the charm. I am baffled, though.

I have no clue, whatsoever, about why this is happening.

My question(s) to all you guys:

  1. Have you faced this issue?
  2. If so, what did you do to resolve it?
  3. If you have not found any solution (other than running DAG till it creates the DLL), have you already reported this to GP dev team?

Please shed some light on this by sharing your thoughts on the comments section.

Vaidy

Install/Upgrade Error: Input string was not in a correct format


I had to apply GP 2016 YE2016 (16.00.0579) on my GP2016 R2 environment. I had several customisations deployed and wanted to remove them before applying the YE2016 patch.

Obviously, I’d upgrade my customisations to 16.00.0579 once my GP is upgraded. However, while trying to apply YE2016, following error message popped up out of nowhere.

Screen Shot 2017-04-27 at 03.32.02 pm

I had never seen this error before. It was certainly a bit baffling. Not even Google is good compared to our GP community forum to find answers. I came up with this: Installation error ‘Input string was not in a correct format’

Apparently, it was my DYNAMICS.SET that was causing this issue. I removed my customisation dictionaries from GP folder, removed all necessary entries from my SET file. However, I totally forgot to reduce the number of dictionaries at the top of my SET file. Silly me!

Once I corrected my SET file, I was able to apply the YE2016 patch. All was well.

One thing I would like to emphasise here: Those who post questions on our GP forum, please mark the response as “answer” without fail. You would help others who search for an answer. You’d also give due credit to the person who shared his/her knowledge.

Vaidy

Barry Crowell’s Next Post on Dynamics GP & Power BI


Another excellent article from Barry Crowell on Dynamics GP and Power BI:

During my last blog post, I walked you through creating a financial dashboard using Power BI with Dynamics GP data. I have created additional analysis and measures now. If you look closely at the bottom left, you will see two additional reports for Sales Summary and Customer Analysis. Sales Summary The data used from Dynamics […]

via Supercharge Your Dynamics GP Dashboards & Reports with Power BI — My quest in SQL, BI & Dynamics GP

Barry Crowell’s Excellent Dynamics GP & Power BI Post – Multicompany Financial Dashboard


Back in October of 2015, I posted a blog about how to modify Jared Hall’s awesome Excel Financial Dashboard that you can download here. The problem with his solutions is that most Dynamics GP environments are multi-company setups making these dashboards not very functional without navigating and opening multiple Excel spreadsheets to view each company’s […]

via WOW! A Dynamics GP multi-company Financial Dashboard – Part Deux — My quest in SQL, BI & Dynamics GP

Management Reporter CU16 Released


It’s been almost a year since I had posted anything on my blog, due to various reasons. In all honesty, breaking that hibernation was harder than what I expected. Anyways…

Management Report CU16 has been released and is now available for download. Here’s the post from Dynamics CPM Team: Management Report CU16 Now Available

CU16, like my own absence from community activities, has come after almost one year. And this release indeed seems to be substantial. Following is the fixes list:

  1. Change tracking only gets enabled on the first Microsoft Dynamics GP company database.
  2. Wildcards and ranges doesn’t return all valid dimension combinations.
  3. Dimension filter uses an OR condition instead of an AND in different scenarios when two dimensions are specified.
  4. Dynamics GP: Management Reporter is performing a count query before actual query, doubling the query cost with data mart.
  5. Dynamics GP: Management Reporter fact integration slow when posting large Analytical Accounting batches.
  6. Dynamics GP: GP data validation is not working for Microsoft Dynamics GP 2016.
  7. Dimension filter uses an OR condition instead of an AND if using a dimension value that does not exist.
  8. Dynamics GP: Unable to create GP integration with GP 2016 Dexterity Shared Components.
  9. Dynamics GP: Yes/No Analytical Accounting dimension not working or integrating correctly in the Management Reporter data mart.
  10. Report generation fails when using a dimension value setting in the reporting tree based on MainAccount.
  11. MR CU15 Known Issue – @DateLong AutoText header displays day of week in web viewer.
  12. Report generation fails when there is a duplicated name for a dimension value.

I have removed all Dynamics AX related fix references. Full list can be found here: Management Report CU16 Fix List (PartnerSource/CustomerSource Access Required)

About the new features, most important one is the support for HTTPS & SSL deployment, for more data security.

I am gonna go ahead, download CU16 and upgrade my test environment, to experience the fixes and features.

I strongly suggest to whoever still use MR to do the same.

Vaidy

Error while connecting to Management Reporter 2012 CU13


This post just saved my day. Big time!

Ariston Javier Blog's

Error Messages:

System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://Server:4712/InformationService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.123.40:4712
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
— End of inner exception stack trace —
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
— End of inner exception stack trace —

Server stack trace:
at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at…

View original post 162 more words