I’ve started working Microsoft Dynamics 365 Business Central for a short time now and have been using both the on-premise and cloud versions and have encountered my first uninformative error message.
I got used to these when working with Microsoft Dynamics GP, and especially the Integration Manager tool, but had hoped that Dynamics BC might have been better in this respect. I am a little late posting this as I’ve been working through a backlog of posts.
This particular error came up when I tried to log into the on-premise version of Dynamics BC:
An error which simply says “something went wrong: an error has occurred” is singularly uninformative, which means starting to investigate from the basics. As this is the on-premise version of Dynamics BC and which is still accessed through the web browser, this means there is a service running, so the first place to start is the Services control panel applet:
As you can see in the above screenshot, the Microsoft Dynamics 365 Business Central service was not running; while the service was set with a Startup Type of Automatic (Delayed Start), which means a 12 second delay after Windows starts, the server had been running for longer than this. The service had failed to start, but there were no error message in the Event log to show why the service had failed.
I manually started the service and was able to access Dynamics BC without further problem. I’ve kept an eye on this over a short period of time and not seen it again, so it looks like a temporary glitch. It is a bit disappointing that the error message was not informative, but I figure that a web application can’t actually determine status of the service, although the message could still have been better than “an error has occurred”.
Microsoft Dynamics 365 Business Central 2022 Wave 1
What should we write about next?
If there is a topic which fits the typical ones of this site, which you would like to see me write about, please use the form, below, to submit your idea.