Starting problem

[dl6lbi]

Hello Jordi,

I have been experiencing the following problem for some time now. The startup process is cancelled with an error message: Access violation msjetoledb40.dll

After confirming this error message, the interface must be reloaded via "Options/ Reload new interface". This occurs daily when the programme is started for the first time.

vy 73 de Ingo

[dl6lbi]

Hello,

this problem also occurs with the current beta version, namely with every start of the programme


73 Ingo

[EA3GCV]

Hello,

The msjetoledb40.dll is a system file. Many other Window users are experiencing this after a Windows update:

https://techcommunity.microsoft.com/t5/a...-p/1588064

I suggest to try to repair your operating system by opening a CMD console with administrator rights then type:

SFC /SCANNOW

This will repair corrupted files. Restart and try. If this doesn't solve the issue follow the instructions given in the previous link about reverting the DLL version. Or restore your operating system to a previous state. Probably a Windows upgrade caused this issue. But this has nothing to do with Swisslog.

73

[LB2TB]

Subject: Access Violation Error in msjetoledb40.dll


Hi everyone,

I’m experiencing the same access violation error in msjetoledb40.dll that Ingo mentioned. It occurs whenever I launch the program, and I’m also on the latest Windows 11 update. Running SCANNOW didn’t resolve the issue.

As a temporary fix, I’ve been clicking "OK" on the error and using Options -> Restore Desktop. I believe it’s more of a Windows/access issue rather than a problem with Swisslog. I’m hopeful for a solution soon from Microsoft, as it may affect multiple programs.

Update: Running Swisslog as Administrator resolves the error; however, high-security settings may be inconvenient for users.

[EA3GCV]

Hi Lars,

Thank you for the tip! Running Swisslog as administrator is ABSOLUTELY SAFE! Swisslog doesn't harm anything to the operating system. In certain scenarios, running as administrator is mandatory to avoid many issues.

73

[dl6lbi]

Hello everyone,
the problem could not be solved by anything, sfc/scannow, did not help and all attempts via Microsoft help did not help either.
In the end I restored an older backup. This solved the problem.
73 de Ingo

[EA3GCV]

Hello Ingo,

Thank you for informing on this! That's why it's very important to perform frequent backup copies. Very weird things may happen suddenly!

73 and glad you solved it.