When a Microsoft SQL Server backup is restored, it often includes the users that were associated with the database at the time of the backup. If the backup is used to restore on a new server, then there’s a good chance that the database users will be “disconnected” from the SQL Server users (if they exist at all). Fortunately, restoring access is simple.
I recently had to install an old piece of software on our (headless) Ubuntu 20.04 Linux system. Our first hurdle was binaries not executing properly — on attempting to run executables, the error No such file or directory would appear. This was corrected by installing lsb-core:
$ sudo apt install lsb-coreThe software we wanted to use had copy protection, specifically Macrovision’s FLEXlm license manager (now with Flexera Software). Our FLEXlm-protected software was provided with a node-locked license and this was tied to a specific MAC address on our machine. It’s possible to ask FLEXlm what’s the HostID (MAC address(es)) that it sees by running:
$ lmutil lmhostid
lmutil - Copyright (c) 1989-2006 Macrovision Europe Ltd. and/or Macrovision Corporation. All Rights Reserved.
The FLEXlm host ID of this machine is ""Unfortunately, the software was unable to “see” our Ethernet adapter due to older versions of the software looking for Ethernet adapters starting with eth. The reason? systemd uses an alternative naming convention, formally part of the predictable network interface names, that essentially means Ethernet devices will start with en instead of the “traditional” eth prefix. We therefore needed a way of getting FLEXlm to see the Ethernet adapter.
As I have mentioned on my previous post, I have discovered an interesting bug while exporting a fixed width file using DMF within Dynamics 365 Finance and Operations. The bug occurs when you specify the row delimiter as {CR}{LF} or even {CR} on your fixed width file settings. In either instance, the file gets exported without a carriage return ({CR}) thus ignoring the row delimiter setting for the fixed width file. The exported file therefore wouldn’t be formatted as you would want, potentially causing readability issues for some text editors or applications that depend on the {CR}{LF} combination. In this post, I’ll take a deeper look into this and how I solved it by integrating a fix within the Logic Apps process required for exporting the data.
Fixed width a.k.a. fixed-character file is a file that is not delimited. That is, a file which contains rows and columns where the columns are not delimited by any special characters like commas (comma separated files .csv) or tabs (tab delimited files) but the columns are broken down based on the character length of each field/column.
I have been working on a requirement recently that involves importing a fixed width character file in D365 F&O via DMF by way of Logic Apps. There had been a couple on challenges on this one and I have Googled / Binged about it and found forums where people have had to find alternative solutions, thinking that it’s impossible (for example, this question from the Microsoft Dynamics Community Forum).
I’ve also read many similar blog posts where some people say that they have asked the customer to change the file format. Like this one from before.
We did complained to Microsoft about one year ago because we had the same issue, and as I see it stills hasn’t been fixed, so I wouldn’t believe it will be at least solved in a short time. Sorry to not bring to you a solution, in our case we had to change the file format.
But I’ve been wondering why the customer has to change the file format? Can the developer not create a solution?