Wednesday 17 January 2024

Access Business Central running inside Virtual Box over the internet(Host must have public IP)

 Hello reader,

It took me sometime to achieve the request.

Generally you have a physical server with a public IP. The server could be running many other services.

In my case the server is running an older version of windows server.

So i installed a Virtual Box with new windows server and install Business Central there.

But getting Business Central to be accessible to outside network over the internet is the trick.

If that is your problem then you are in the right place.

I assume you have already installed business central in the VM and it is running

Procedure

Setup Bridged Network to all VM share host’s internet/network
  • You need to first switch off the VM
  • Select the VM inside virtual box menu
  • Select settings
  • Select Network
  • Select adapter 2
  • Make sure network is enabled
  • Select Attached to  = Bridged Adapter
  • Select appropriate adapter in the name
  • Click ok to save


 This step is well explained here

Setup the VM to use static IP address
  • This is the usual process done in the network section


 

Configure Port forwarding between VM application & Host machine
  • This is done using the NAT network on adapter 1
  • Go back to where you setup the abridged network. 
  • Select adapter 1
  • Select Port forwarding
  • Map the host/physical computer IP address(Local IP) to VM static IP set in preceeding step
  • Map the port number for accessing Business Central in VM to a chosen port on the Host
  • Make sure those ports are allowed through the VM firewall settings


 




Configure port forwarding on the Router and firewall for external access. This is done on the Host Network. It also depends on the firewall/router you are using.

Good luck




Tuesday 16 January 2024

ERROR Changing Business Central to NAVUserPassword Authentication "login failed for user 'NT Service\SSISScaleOutMaster150'. Reason: could not find a login matching the name provided [CLIENT:]"

 


Hello reader, I got the above error while attempting to change my Business Central to use NAVUserpassword authentication.

I have gone through the procedure as described by Microsoft BC Manual

However the error kept on persisting. I had to do many things, i cant tell really what worked exactly.

  • First ensure you -> Grant access to the Business Central Server service account. You may read for more on this process.
  • Make sure NT NETWORK SERVICE & your WINDOWS ADMINISTRATOR(If this is the default account you use to login to your business central database instance) account has full access to your Business Central Database.
  • Restart your Business Central Service

That should solve your problem hopefully.


Thursday 4 January 2024

ERROR installing windows server 2019 in Virtual Box "windows cannot find the Microsoft Software License Terms.Make sure the installation sources are valid and restart the installation "

ERROR -windows cannot find the Microsoft Software License Terms.Make sure the installation sources are valid and restart the installation 




Am not sure what caused the problem but various individuals on Microsoft Community say different stuff. 
Here is a solution that worked for me

It's possible the media is corrupt in which case I'd try downloading from another location to avoid the same copy ISP has cached on their systems. some hypervisors such as VMWare add an additional floppy drive that causes install media to look for licensing on floppy, in this case remove the virtual floppy from guest and try again. Also try;
Bypassing 
Easy Install

  • First start VMware Workstation
  • Create A New Virtual Machine
  • Select the option “I will install the operating system later”
  • Then your new virtual machine will be added to your virtual library.
  • Double click on your new Virtual Machine to start it.
  • Then it will prompt that an OS is not installed and provide an option to insert the OS installation media.
  • Simply click on Change CD/DVD Settings to select your ISO media then Restart VM.



Good luck