I'm getting the following error message every time I open AECOsim SS6 in Archtectural mode
"Microsoft Visual Basic
Run-time error "453":
Can't find DLL entry point GetLocaleInfoA in kernel32"
Does anyone know what this means, and how to fix it ?
Regards
Michael.
AECOsim SS6
WIndows 10
Larry
I have all the latest Windows updates installed.
This error only comes up in Architectural mode. It doesn't show up when I use AECOsim in Microstation mode.
When I select the "debug" button this pops up and AECOsim crashes
I have also included the exception log file, if that helps
Michael.2804.Exception.log
Michael,,
Since you have reinstalled Windows 10, would you go back and try this again? I know you set it in Properties on the launch icon, but I have seen this fix issues like this. You only have to do this once.
Thanks,
Michael, I found this in the exception log - Exception String: 'Access Violation' Go to the ABD icon on your desktop and right-click and "Run as Administrator" one time. This should toggle permissions on everything so that the program has access to everything it needs. Let me know if this fixes the issue. Thanks Michael, Larry
Michael,
Are you running a 32-bit version or 64-bit version of Microsoft Office?
I already tried this without success.
And I'm running a 32bit version of Microsoft Office.
Michael
Is it a Local Installation or a Web-based Installation?
Local installation.
It was suggested during our Department Conference Call this week to check your Regional System Settings for which List Separator symbol you are using. Maybe try clicking the "Reset" button to restore the Default values.
This was suggested based on an old issue which was fixed by doing this.
Please let us know your results.
Tried this. No difference.
Which project are you selecting when you open a drawing?
Will you create a new project just for testing and see if you still get the error?
User - BuildingDesigner
Project - Building Template_AU, Building Template_NZ and a newly created GMBTest.
All 3 projects have the problem
I thought I might try it other computers in the office. Same error message pops up.
MickyKom,
Would you please try your workflow using Building Template_US in order to eliminate suspicion of the dataset? I have tried it in _US, _AU, and _NZ and cannot reproduce the error.