Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 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 | Upcoming TechTalks
Since last week we get multiple SQL errors with our AX 4 SP2 and SQL Server 2008R2 environment.
Some Sessions where I run batch jobs for multiple hours on the server at night don't have any problems. Other batch-session on the same server stop within irregular intervals. Sometimes they run over 4 hours, sometimes they stop after 15 minutes.
In the AOS Logfile it seems that the errors always appear a few seconds after full hours, for example at 03:00:33, 09:00:59, 19:00:56, 22:01:34.
I don't have batch-jobs in Dynamics AX which run at that times, so I think it's a problem with the sql server, maybe when the sql server is making backups for the transaction files.
The errors also appear on some clients running Windows 10. They delete the error message in the client an continue working in the same session without any problems.
Any ideas what could be the problem or where I can start searching for errors?
Ein Fehler ist aufgetreten:Benutzerkennung: AdminUhrzeit: 09:01:10 31.10.2018Version: Microsoft Dynamics 4.0 (Erstellungsnummer 2503.362)Datenbank: Microsoft SQL ServerSQL-Anweisung: [Kennung=0, Wiederverwendet=Nein]Fehlertext: [Microsoft][ODBC Driver Manager] Die Verbindung ist nicht geöffnetSQL-Fehlercode: -101016
Object Server 03: Fatal SQL condition during login. Error message: "[Microsoft][ODBC SQL Server Driver]Anmeldungstimeout abgelaufen"
Object Server 03: SQL diagnostics: [Microsoft][ODBC SQL Server Driver]Anmeldungstimeout abgelaufen. Connect information was: Userid = , Database = [Dynamics_AX_4_DATABASE], Server = [SQLSERVER], DSN = , Other = 
Object Server 03: The database reported (session 2 (NAME)): [Microsoft][ODBC Driver Manager] Die Verbindung ist nicht geöffnet. The SQL statement was: "SELECT ...
Object Server 03: Dialog issued for client-less session 2: Cannot select a record in User Information (UserInfo). User ID: , .Error accessing database connection.
Error Message in the Client:
SQL-Fehlerbeschreibung: [Microsoft][ODBC Driver Manager] Die Verbindung ist nicht geöffnet
SQL-Anweisung: SELECT ...
Ein Datensatz in ... kann nicht ausgewählt werden. Priorität: 0, . Fehler beim Zugriff auf die Datenbankverbindung.
Hello EDV Abteilung,
Has your organization recently disabled TLS 1.0 on the servers. If so you might want to confirm all the effected servers have the TLS 2.0 supporting SQL components installed. for example they would require the ODBC 11 drivers. Check out the blog below for some additional information.
Hope this helps!
I found out the problem. It was caused by a 100% CPU workload caused by another SQL instance running on the same database server which was used for our WSUS Server. The 100% CPU workload appear every full hour when the server checks for new updates. Then the Dynamics database could not execute the querys an run into a timeout. After stopping the WSUS i don't have problems anymore.
Business Applications communities