Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
In server Visual studio is showing displaying following error . I have tried to restart all the necessary services but still facing the same issue
And the front end is displaying error as follows.
Build all your models. After succesful build, do database sync. Does it solve your problem?
Hi Nikolaos Mäenpää,
Even after building My own model with references with the database sync option was selected still displaying the same error.
Can full build solve this problem??
Build of all custom models, followed by FULL database sync should do it.
By the way, I can't read the error message in your first screenshot, the image is too blurry. Could you share it in text format?
System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at Microsoft.Dynamics.Framework.Tools.ProjectSystem.DevFabricDebuggingHost.WarmupAppPool(Int32 RetryCount)
at Microsoft.Dynamics.Framework.Tools.BuildTasks.SyncEngineWrapper.Sync(CancellationToken cancellationToken) 0
Did the full sync help? Or are you not able to sync?
If the first suggestions did not help, next we need to understand a bit more about the system. Did it work before? What did you do in the system before it stopped working?
Error 500 may be caused by many reasons.
Is the time zone of your client PC and host the same.
Here is a link about various solutions for your issue.
I received the same error on full sync as well.
It was working fine till yesterday
And what did you change yesterday before it stopped working? Did you already try restarting the VM?
There were some changes done in the report and after that, we did deploy the report and it was working fine.
yes, I tried to restart the VM but still, the same error pops up
Ok. Did you already check WillWU's suggestion? It points to a blog, which points to a community discussion.
You could also check the event logs on the machine to try to find more information about the error.
Anyway, if you can't get around the issue, you can always redeploy the machine. That takes only a few working hours from your side. So if you think that searching for an answers takes more than a few hours of your time, I suggest you to redeploy.
Yes I tried for WillWU's Solution and while checking logs I got the following information from it
So, the AOS can't connect to the database. Could you please share the full error description from the event log?
Is the SQL Server service running on the machine? If you open SQL Server Management Studio, can you access AxDB database?
Yes, I'm able to access axdb from SQL server and detail of error log as follows:-
Log Name: Application
Source: Microsoft Dynamics 365 for Finance and Operations
Date: 10/23/2019 4:35:28 PM
Event ID: 110
Task Category: None
The description for Event ID 110 from source Microsoft Dynamics 365 for Finance and Operations 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.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
AX is shutting down due to an error.
Error during initialization of Message Broker. Please verify that your AOS instance has connection to the AOS Database. Error messages follow:
Could not execute operation against the SQL Database.
Cannot open database "AxDB" requested by the login. The login failed.
Login failed for user 'axdbadmin'.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Dynamics.Ax.Xpp.Messaging.MessageBrokerStartupException: Could not execute operation against the SQL Database. ---> System.Data.SqlClient.SqlException: Cannot open database "AxDB" requested by the login. The login failed.
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.ExecuteAction[TResult](Func`1 func)
at Microsoft.Dynamics.AX.Data.Sql.SqlDataAccessManager.OpenConnection(SqlConnection conn)
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.Dynamics.AX.Data.Sql.SqlDataAccessManager.HandleException(ExceptionDispatchInfo edi, SqlExecutionInfo execInfo)
at Microsoft.Dynamics.Ax.Xpp.Messaging.MessageBroker.RegisterInternal(String path, MessageReceivedHandler handler, Boolean isQueue)
--- End of inner exception stack trace ---
at Microsoft.Dynamics.Ax.Xpp.Messaging.MessageBroker.Start(String connectionString)
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object parameters, Object arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
at Microsoft.Dynamics.AX.AOS.StartupInternal(String Arguments)
<Provider Name="Microsoft Dynamics 365 for Finance and Operations" />
<TimeCreated SystemTime="2019-10-23T16:35:28.727638400Z" />
<Data>AX is shutting down due to an error.
at Microsoft.Dynamics.AX.AOS.StartupInternal(String Arguments)</Data>
Have you perhaps changed the password of axdbadmin user?
Can you login to the database using axdbadmin user and the password from LCS?
No, I have not changed.
Yes I can log in the database using an admin
And by "using admin" you mean using axdbadmin account, and password from LCS? And being able to see tables and data in AxDB database?
My next suggestion is to redeploy the system. Most likely that's the cheapest way for you to get rid of the issue.
Redeploy means deleting and deploying again.
So first Stop - Deallocate - Delete the current system.
Then deploy it again, configure your VS workspace, get latest, build and sync.
Also please be aware that all your pending changes on this machine will be lost. So make sure you have checked everything in version control that you want to keep.
Ah, wait, now i know! :)
Your system is a Microsoft managed Tier1 dev system.
We had similar issue after last weekend in our system. Microsoft can fix it (and you can't).
You must raise a support case with them.
Here's the response that I got from them.
"Thank you for raising this incident and for making us aware of this issue - please note that the issue is caused by Azure security requesting TLS1.2 , while some of our requests we made from the DEV environment need to have TLS 1.1 and TLS 1.0 - we are working to release a fix for PU29, 30, 31, but until this is released, I have raised an internal ticket for us to fix it manually. "
edit: sorry, I think it's not applicable to you after all. Our issue was "503: Service unavailable" and we noticed TLS related errors in the event log. So most likely your problem is not the same.
Business Applications communities