DBForge for SQL - Startup Optimization Failed

Discussion of open issues, suggestions and bugs regarding database management and development tools for SQL Server
Post Reply
papker
Posts: 4
Joined: Mon 06 Feb 2017 18:44

DBForge for SQL - Startup Optimization Failed

Post by papker » Mon 11 Jul 2022 15:12

I have been plagued with slow startup of DBForge for quite a while now. Since 6.2.22 was newly released, I downloaded and installed hoping to fix this issues, however it failed the install optimation.

"Startup Optimization failed"
c:\windows\Microsoft.Net\Frameworks64\v4.0.30319\ngen.exe
failed to compile Devart.DBForge.commonServices.dll

The time to startup dbForge is 2 min 7 seconds.

This is in the application event log:
Application: dbforgesql62.tmp
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 79E9876D

Faulting application name: dbforgesql62.tmp, version: 51.52.0.0, time stamp: 0x2a425e19
Faulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x62a06d32
Exception code: 0xc0000005
Fault offset: 0x0001876d
Faulting process id: 0x3f88
Faulting application start time: 0x01d8953457f3e277
Faulting application path: C:\Users\*******\AppData\Local\Temp\is-VVKHR.tmp\dbforgesql62.tmp
Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso20win32client.dll



I reinstalled several times with the same result. Is there a way to get around this?

dzhanhira
Devart Team
Posts: 239
Joined: Mon 26 Oct 2020 13:49

Re: DBForge for SQL - Startup Optimization Failed

Post by dzhanhira » Thu 14 Jul 2022 10:59

Hi there,

Kindly be inormed that those errors are possible, it all depends on the environment. Please try to disable image generation.

papker
Posts: 4
Joined: Mon 06 Feb 2017 18:44

Re: DBForge for SQL - Startup Optimization Failed

Post by papker » Tue 26 Jul 2022 20:29

Fair enough, however the program takes over 90 seconds to load!

Since the optimization fails, Is there a way to improve on that? I already tried the second option of optimizing afterwards, but haven't noticed much if any improvement. I also install 6.2.52 to test.

Post Reply