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.
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.
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.
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.
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.
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).
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:
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:
Have you faced this issue?
If so, what did you do to resolve it?
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.
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.