BC14, Business Central, Error, Event Log, Failed to reach status, How To, Information, On this Server, Running, Symbol Reference

Update Symbol Reference & Error: Failed to reach status ‘Running’ on this server – Additional information may be in the event log of the server

Some time while working we notice below error; Server Instance fails to start.

One of my reader requested solution from me.

So, to generate error I have intentionally created the error to explain the process.

You should pay attention to the message, as it says Additional information may be in the event log of the server.

All errors represented in Error log, sometimes is too technical and don’t give right clue.

There could be other reason, I am representing one general error.

When this happens, series of error messages are generated. All of them may not be helpful to find exact error.

But if you seriously scan each error, something always you can find which can help you in identifying the error or cause of same.

Just like below message, here we can identify that error is in Page 41, due to which Metadata is not updated correctly, leading to failure to starting the Server Instance.

Once you fix the error, you may get error for another object and similarly you can fix that too.

Alternatively, you can compile all objects and find errors in objects modified by you and get done in one shot.

Once all error is resolved, you will be able to start the Server Instance.

If you don’t get modifications to objects available in your AL you can run below command, make sure you Run as Administrator.

Switch to Installation folder by default: –

C:\Program Files (x86)\Microsoft Dynamics 365 Business Central\140\RoleTailored Client

And execute below command:

Finsql.exec Command=generatesymbolrefrence, Database=<Your BC Database>, ServerName=<Your SQL Server Name>

After this you should be ok to start your Server Instance and see modification in AL Project.


Windows Error Reporting and Collecting Crash Dumps

For troubleshooting issues with Microsoft products in general, you can use Windows Error Reporting to report computer problems to Microsoft. Microsoft uses the problem reports to try to match descriptions of each problem to a solution. This feature is enabled by default, and generates detailed reports about the problem.

To troubleshoot application instability issues, we will often need crash dumps in addition. For Microsoft Dynamics NAV, a full crash dump might be required to provide sufficient details to isolate and fix the problem. Once crash dump is collected, contact support and provide the dump. There are number of ways and tools to collect a crash dump, but we’ll look at how to automate this action in a very simple way.

For more details see:- Here