Tim Wappat has given us something precious. I am late to the party, though.
I didn’t realise that Microsoft Dynamics GP 2018 R2 shipped with a VS Tools version that’s incompatible with anything above Visual Studio 2015.
This realisation hit me when I tried to install and configure GP 2018 R2 on my virtual machine for an upgrade project.
Obviously, the first place to search for a resolution was our GP forum. This post by Richard Wheeler pointed me to the right direction. Tim’s Visual Studio extension saved me from going insane.
Thank you so much, Tim!
Melissa Coates (Coates Data Strategies) has published an updated end-to-end diagram of Power BI. This is extremely useful to someone who would like to learn, understand and to present the capabilities of Power BI to any potential client.
She is generous to let us use the PDF version of this diagram. Find it here: Updated Version of the Power BI End-To-End Diagram.
Please remember to give her a shout out.
I’ve been absent from blogging for an obscene amount of time. Have been MIA on forums, my blog, pretty from every public medium. Except Twitter, of course.
A lot happened in the last 2 years.
The Good: My primary job now revolves around an incredible mining solution named PLODtrack. For those who are interested in knowing about that, follow the link.
The Bad: It has got absolutely no affiliation with Dynamics GP, which means I’ve not been working on GP projects for the last 2 years.
The Ugly: Several. I don’t even know from where to start.
Silverlining: I’ve gained precious experience in the last 2 years. Both professionally and personally. That’s going to drive me from now, until god knows when.
Assurance: I’ve not stopped pursuing Dynamics GP. I’m very much a Dynamics GP consultant at heart and mind. I’ve got that going for me outside of my work hours. And I have absolutely no intention of drifting away.
So, long story short, I shall try to keep this blog alive with some really nice posts. Hopefully won’t take much time from this post till the next.
I’d like to thank those who still visit some of my posts and keep this blog going.
Another off-topic post from me. And this time, it is for a very interesting issue.
I was trying to install and configure a new virtual machine for Kubuntu 18.04 LTS on my Mac, using Parallels Desktop v13. The installation went on well. My new Kubuntu VM was ready for configuration. All done, except Parallels Tools.
Every time I tried to install Parallels Tools, I received a fatal error and the installation would abruptly stop. Searching this on the Parallels Forum lead me to this post: Fail to build kernel modules on Linux kernel v4.15+.
Trust me, I’m no good at Linux at all. I’m just beginning to explore. So whatever was discussed on this forum post was beyond my limited knowledge. However, on page 2 of this post, there was a link provided which took me to Rudolf Ratusinski‘s step-by-step guide on how to hack Parallels Tools installer and make it work.
Here’s the original link: Parallels Tools fix for Ubuntu 18.04 and other Linux distributions with Kernel version >= 4.15
I must admit. Even I was able to follow the steps and succeed in installing Parallels Tools on my Kubuntu 18.04 VM.
It’s worth noting that Parallels is yet to release a fix for this issue. This hack shouldn’t even be required, had Parallels addressed it straightforwardly.
Till we receive one from them, you may want to read Rudolf’s hack first before trying to install Parallels Tools.
Thanks Rudolf. I really appreciate your time and effort to share this crucial hack with all of us.
I’m slowly moving away from Windows. However, being a Microsoft Dynamics GP consultant, that’s not entirely possible. I’ve been working hard to overcome every single roadblock since the last couple of years.
One major gripe, among several others, was the inability to connect the SQL Server instance on my Windows 10 virtual machine, mounted using Parallels. Until now.
Microsoft released SQL Server Operations Studio, which is still under preview, for us to connect to a SQL Server from Windows, Mac OS or Linux. I now have the choice to work from either my Mac OS or my Windows 10 VM.
However, there are some steps we must follow to successfully connect to a SQL Server instance on a virtual machine. This post, from Anton Sizikov, is probably the easiest one to follow. Following the steps explained on this post, Connecting SQL Operations Studio to SQL Express Server in Parallels VM, I was able to successfully use my SQL Server Operations Studio to connect to my VM SQL Server. Below is the SQL Ops Studio in all its “dark theme” glory:
I couldn’t use my Mac more than pretty much for just browsing, emailing and other daily digital chores. This is one huge step forward to start utilising it well.
Word of Caution: This article contains a procedure to edit/change Windows Registry. Please take necessary precaution before attempting this.
I received an error this morning while trying to connect to one my clients’ server. The message as follows:
With the help of one of my contacts at the client site, also upon searching and following the link provided in the message itself, couple of help pages stood out:
- CredSSP updates for CVE-2018-0886
- CredSSP encryption oracle remediation
For those who would like to see the solution immediately without having to go through the details from above links, I shall brief the solution itself here.
There are basically two solutions:
- Run “Windows Update” on the remote server (or the workstation) to which you are trying to connect. This will ensure that you have the latest patch on the remote box and you wouldn’t be facing this issue again. This would work provided your machine also has got the latest updates applied.
- For those who cannot update the remote box for some reason(s), you would have to create a new registry entry as shown below:
Once above registry key is created, you must restart your workstation / client / computer without fail.
All good now to successfully connect to the remote box again.
A note of thanks to Dave.
I’m blogging after a painfully long time. And, I’d like to share something really interesting that happened on my MacBook Pro this week.
I reset my Mac with Mac OS High Sierra (10.13.4) and all of a sudden, all my notifications stopped working. The Dock labels would show, sound would be there, yet mysteriously, banners wouldn’t come. Upon checking the notification area, there wasn’t any recent notifications listed at all. Baffling, to say the least.
Then I chanced upon this apple support forum discussion, Mail notifications | Official Apple Support Communities.
Despite the discussion being for Mail App, the solution given on this discussion worked for me for all apps’ notifications.
Solution is quite simple; change the alert notification from “Alerts” or “Banners” to “None” and change it back. Easy, isn’t it? Not exactly. I had to do this for all of my apps, using the notification centre.
I can’t complain though. It’s working now, that’s all I need.
If someone’s having same issue and is looking for a solution, look no further. Check out the discussion on Apple Support Forum (link provided above).