Business Central On Premise Installation on Three Servers

airam
Member Posts: 91
Hi, we're trying to install Business Central On Prem on different servers but we're getting these errors:
- when trying to open the client:
"Microsoft Dynamics 365 Business Central Server is currently not ready to serve requests. Try again later, or contact your system administrator."
- event viewer of the nav server:
"The description for Event ID 705 from source MicrosoftDynamicsNavServer$BC140 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer."
- event viewer of the sql server:
"Login failed for user 'domain\machine$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]"
we're running the services with a domain account with full permissions
any hints pls?
Thanks!
- when trying to open the client:
"Microsoft Dynamics 365 Business Central Server is currently not ready to serve requests. Try again later, or contact your system administrator."
- event viewer of the nav server:
"The description for Event ID 705 from source MicrosoftDynamicsNavServer$BC140 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer."
- event viewer of the sql server:
"Login failed for user 'domain\machine$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]"
we're running the services with a domain account with full permissions
any hints pls?
Thanks!
0
Answers
-
As always with these kind of errors, these are kind of hard to diagnose remotely:
1.) Check Windows Login is enabled on SQL Server
2.) Check if TCP is enabled on SQL-Server (should be in your case)
3.) Check is the Service user has permissions on SQL-Server (try giving it Sysadmin for testing)
4.) Double and Tripple-Check the Service user Credentials
5.) Make sure the Service user is allowed to "login as Service"
6.) If that doesn't help try running the BC Service as NetworkService.
/Wisa
Austrian NAV/BC Dev0 -
thanks for your feedback, however unfortunately all the above were correct and still have the same issue0
-
we managed to solve this, by assigned the domain account admin rights, unfortunately this was not the preferred way but that was the only solution we found.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions