Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
YouTube Security VideosNutanix advances legacy and AI app management with AMD(01.10.2026 um 16:00 Uhr)
•
YouTube Security VideosPC-WELT: 32 TB SSD-Speicher in der HMX 6!(01.10.2026 um 16:15 Uhr)
••••
Videos & KonferenzenPC-WELT: 32 TB SSD-Speicher in der HMX 6!(01.10.2026 um 16:15 Uhr)
••
Sicherheitslücken (CVE)USN-8857-1: KCoreAddons vulnerability(01.10.2026 um 12:48 Uhr)
•••
YouTube Security VideosNutanix advances legacy and AI app management with AMD(01.10.2026 um 16:00 Uhr)
•
YouTube Security VideosPC-WELT: 32 TB SSD-Speicher in der HMX 6!(01.10.2026 um 16:15 Uhr)
••••
Videos & KonferenzenPC-WELT: 32 TB SSD-Speicher in der HMX 6!(01.10.2026 um 16:15 Uhr)
••
Sicherheitslücken (CVE)USN-8857-1: KCoreAddons vulnerability(01.10.2026 um 12:48 Uhr)
•••
Intelligence View
⚡ tsecurity.de Intelligence

Recovery of Microsoft Dynamics NAV 2002 R2 and SQL Server

Recovery of Microsoft Dynamics NAV 2009 R2 and SQL Server 🇪🇸 Leer este post en español 🎯 Objective of the process Restore the Microsoft Dynamics NAV 2009 R2 env…

Beitrag
0
Seite
0
↗ Quelle (dev.to)
Social ReaktionenReagiere als Erste:r — dein Feedback zählt!




Recovery of Microsoft Dynamics NAV 2009 R2 and SQL Server



🇪🇸 Leer este post en español









🎯 Objective of the process



Restore the Microsoft Dynamics NAV 2009 R2 environment that stopped working due to a critical failure in the SQL Server 2008 R2 (x86) instance on a server upgraded to Windows Server 2022 Datacenter.









🧩 Original Environment





  • ERP: Microsoft Dynamics NAV 2009 R2 (version 6.00.32012)


  • Database: SQL Server 2008 R2 Express (32-bit)


  • Server: Windows Server 2022 Datacenter (virtual machine)


  • NAV Client: Classic and RTC


  • Database restored: Existing .mdf and .ldf files from the previous instance









⚠️ Issues Found




  1. SQL Server 2008 R2 x86 did not start



Key ERRORLOG messages:




  • TDSSNIClient initialization failed with error 0x139f

  • Unable to initialize SSL support

  • security.dll missing or corrupt



Dependency Walker showed multiple missing dependencies (API-MS-WIN-CORE-*).




  1. Repair and installation of SQL Server 2014 failed



The installation returned errors in critical services (Database Engine, Reporting Services, etc.).



After repair and reboot, the service could not start due to encryption errors (schannel.dll, bcrypt.dll, etc.).




  1. SQL Server 2014 started but with severe errors



It searched for .mdf and .ldf files in internal build paths like:




   E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\






This caused the service to shut down automatically.









🔄 Change of Strategy



The following steps were decided:




  1. Completely uninstall SQL Server 2014.

  2. Install SQL Server 2008 R2 (x64).

  3. Manually restore the databases from the .mdf and .ldf files.









🔧 Actions Taken






SQL Server



Executed:




CREATE DATABASE [DBName]
ON (FILENAME='...mdf'), (FILENAME='...ldf')
FOR ATTACH;






Confirmed data paths in:


C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA







  • Copied xp_ndo_x64.dll into C:\Windows\System32.

  • Executed:



EXEC sp_addextendedproc 'xp_ndo_enumusergroups', 'xp_ndo_x64.dll';









  • Loaded manually from the Classic client: Tools > License Information > Import

  • The old license only allowed 2 companies. After importing the correct license, this was fixed.







🔐 Permissions and Errors Fixed



Initial errors:



❌ xp_ndo_enumusergroups – access denied


❌ VIEW SERVER STATE – required by the NAV client



Solution:




-- For a specific user
GRANT EXECUTE ON xp_ndo_enumusergroups TO [DOMAIN\user];
GRANT VIEW SERVER STATE TO [DOMAIN\user];

-- Or for all users:
GRANT EXECUTE ON xp_ndo_enumusergroups TO [public];
GRANT VIEW SERVER STATE TO [public];












🧪 Connectivity from NAV Client




  • Classic client connected successfully from the server.


  • From other machines, it failed due to:




    • Closed port

    • SQL Browser service stopped

    • User without permissions








Checked configuration and confirmed client used:




SERVER:7046/DynamicsNAV






Instance was accessible after fixes.









✅ Final Result




  • Complete recovery of SQL Server 2008 R2 x64 instance.

  • NAV runs correctly from Classic and RTC clients.

  • All databases restored with their original license and fully functional users.









📁 Files Used





  • NAV2009R2_Data.mdf / NAV2009R2_log.ldf (NAV database)


  • xp_ndo_x64.dll (required extended procedure)


  • .flf NAV license file









🛠️ Recommendations




  • Always back up .mdf, .ldf, and .flf license files.

  • Document the exact recovery process for future failures.

  • Avoid newer SQL Server versions with NAV 2009 unless compatibility is guaranteed.

  • Ensure ports and services (SQL Browser, SQL Server) are always active.

🔍 CTI & Forensik

Cyber Threat Intelligence & Forensik

Bedrohungsgraph · ATT&CK-Mapping · Exploit-Belege
CTI Threat Relationship Graph
Akteure · Techniken · Beziehungen
2 Knoten · 1 Relationen
CVE / Incident Threat Actor Software MITRE ATT&CK CWE Weakness IoC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Recovery of Microsoft Dynamics NAV 2002 R2 and SQL Server

Thematisch verwandte Begriffe: Recovery, Microsoft, Dynamics, 2002 · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

💬 Kommentare werden geladen…
Zum Aktualisieren ziehen
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag