Closed jmarrec closed 4 years ago
@erikkolderup Just following up on this. Did you ever try @lefticus suggestions above?
Progress! I unzipped the file to the openstudio/bin folder, and the application gets farther and then pops up a dialog box with the message "Measure Manager has crashed, attempting to restart". If I click "ok", then the box pops up a second time. If I click once more, then the application crashes.
In Event Viewer, I see the following warnings and errors. First there are three warnings related to permission settings and then three errors.
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.SecurityAppBroker
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Faulting application name: openstudio.exe, version: 2.9.1.0, time stamp: 0x5de5c0a1
Faulting module name: openstudio.exe, version: 2.9.1.0, time stamp: 0x5de5c0a1
Exception code: 0xc0000005
Fault offset: 0x00000000000f25a3
Faulting process id: 0x2a30
Faulting application start time: 0x01d5dae266a09477
Faulting application path: C:\openstudio-2.9.1\bin\openstudio.exe
Faulting module path: C:\openstudio-2.9.1\bin\openstudio.exe
Report Id: e567f7e1-757e-4892-a63f-1965de342eb4
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: OpenStudioApp.exe, version: 2.9.1.0, time stamp: 0x5de5c35f
Faulting module name: Qt5Core.dll, version: 5.6.1.0, time stamp: 0x5769aa22
Exception code: 0xc0000005
Fault offset: 0x00000000001cf2ee
Faulting process id: 0x2a68
Faulting application start time: 0x01d5dae1ee9a03e4
Faulting application path: C:\openstudio-2.9.1\bin\OpenStudioApp.exe
Faulting module path: C:\openstudio-2.9.1\bin\Qt5Core.dll
Report Id: b4b33c72-6745-421c-8956-b8a8c548ec33
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: openstudio.exe, version: 2.9.1.0, time stamp: 0x5de5c0a1
Faulting module name: openstudio.exe, version: 2.9.1.0, time stamp: 0x5de5c0a1
Exception code: 0xc0000005
Fault offset: 0x00000000000f25a3
Faulting process id: 0x1640
Faulting application start time: 0x01d5dae26cc27cdf
Faulting application path: C:\openstudio-2.9.1\bin\openstudio.exe
Faulting module path: C:\openstudio-2.9.1\bin\openstudio.exe
Report Id: 33d7bc3e-2892-45ce-808c-863a6c311d73
Faulting package full name:
Faulting package-relative application ID:
Thanks, @erikkolderup. That permission error has been reported on several Windows forums but it's unclear if that is the problem now causing measure manager to not start.
There are some changes you can make to the regedit to grant permissions but I'm hesitant to have you try that out. You've already been very patient through the process and don't want to spend more time.
I found someone here in the lab that is running a similar spec machine as yours and I am going to see if I can reproduce the error. If I can reproduce and get the measure manager failure, I'll try the steps and modify regedit and see if that solves it and report back.
@jmarrec @lefticus thoughts on new error messages?
I tried 2.9.1 on the following Dell laptops and could not reproduce the crash.
Latitude E7440
Intel Core i7-4600 CPU @ 2.10GHz
16GB RAM
64 bit x64
Windows 10 Enterprise
Version: 1809
OS Build 17763.914
Latitude 7490
8th Gen Intel® Core™ i5-8350U Processor
16GB RAM
64 bit x64
Windows 10 Enterprise
Version: 1809
OS Build 17763.914
Related to Windows.SecurityCenter.WscDataProtection permission errors your receiving, you can run a simple test and run the OpenStudio Application as Administrator, provided you have the rights to do so. You should be able to right-click the App icon and "Run as Administrator" or you can run a terminal as administrator and launch the App from within the terminal.
@erikkolderup Since OpenStudio Application 1.0 with 3.0.0 SDK works for you, I will work on escalating a PAT installer so you can have a working setup and tools you need.
@tijcolem , Thanks. Running as administrator produces the same error results.
It's not necessary to accelerate PAT installer on my account at this point. My class is using v2.9.1, which seems to work for people. And I use v2.9.1 on my older Dell laptop for the time being for course development.
-Erik
@dmitrysurugin , I'm curious if your problem computer is the same as mine. Here's my system information:
OS Name Microsoft Windows 10 Pro
Version 10.0.18362 Build 18362
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name EK-XPS-2019
System Manufacturer Dell Inc.
System Model XPS 13 7390 2-in-1
System Type x64-based PC
System SKU 08B0
Processor Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz, 1498 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Dell Inc. 1.1.3, 11/10/2019
SMBIOS Version 3.1
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Dell Inc.
BaseBoard Product 06CDVY
BaseBoard Version A00
Platform Role Mobile
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.18362.387"
User Name EK-XPS-2019\erik
Time Zone Pacific Standard Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.8 GB
Available Physical Memory 23.7 GB
Total Virtual Memory 36.5 GB
Available Virtual Memory 26.8 GB
Page File Space 4.75 GB
Page File C:\pagefile.sys
Kernel DMA Protection On
Virtualization-based security Not enabled
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
@erikkolderup
The system information of my laptop is as follows (OS version, system model and processor specs are different):
OS Name Microsoft Windows 10 Pro
Version 10.0.18363 Build 18363
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-KCBS1P8
System Manufacturer Dell Inc.
System Model XPS 15 7590
System Type x64-based PC
System SKU 0905
Processor Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 2592 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date Dell Inc. 1.3.3, 25/09/2019
SMBIOS Version 3.2
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Dell Inc.
BaseBoard Product 0VYV0G
BaseBoard Version A00
Platform Role Mobile
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.18362.387"
User Name DESKTOP-KCBS1P8\surug
Time Zone W. Europe Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.7 GB
Available Physical Memory 10.1 GB
Total Virtual Memory 18.1 GB
Available Virtual Memory 10.7 GB
Page File Space 2.38 GB
Page File C:\pagefile.sys
Kernel DMA Protection On
Virtualization-based security Running
Virtualization-based security Required Security Properties
Virtualization-based security Available Security Properties Base Virtualization Support, Secure Boot, DMA Protection, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control
Virtualization-based security Services Configured Hypervisor enforced Code Integrity
Virtualization-based security Services Running Hypervisor enforced Code Integrity
Windows Defender Application Control policy Enforced
Windows Defender Application Control user mode policy Off
Device Encryption Support Elevation Required to View
A hypervisor has been detected. Features required for Hyper-V will not be displayed.
@erikkolderup @ldmitrysurugin
We released OpenStudioApp 3.0.0 and this should be resolved with that version.
Closed as this is resolved in OpenStudioApp 1.0.0
Hey . I'm having the same problem on my DELL precision 3561 . I9 11generation , and 32giga RAM. the last version work just fine, i just need these version to use it on SketchUp2017 for free . Sowhat was the solution !?
@liloucarter, I was never able to resolve this issue. I could only use later versions of OpenStudio on the computer with this problem.
@erikkolderup thank's for the answer, so there is no way to use open studio with the free version of sketchup 2017 cause the new version deas not support it .
Others may have a solution to getting 2.9.1 to run, but I'm currently using the paid version of Sketchup 2020 with OS 1.1.0.
After looking at the symbols (openstudio.exe!sha1_block_data_order) near a recent crash report, I think this may be the issue causing this crash:
I can reproduce using Intel Software Development Emulator and Ice Lake chipset:
C:\openstudio-2.9.1\bin>\sde-external-9.0.0-2021-11-07-win\sde.exe -icl -- openstudio.exe --verbose -e "puts OpenStudio::openStudioLongVersion"
This does not print out the full string, similar to @erikkolderup's output https://github.com/NREL/OpenStudio/issues/3827#issuecomment-567540859
However, the following command emulating Skylake chipset does run to completion:
C:\openstudio-2.9.1\bin>\sde-external-9.0.0-2021-11-07-win\sde.exe -skl -- openstudio.exe --verbose -e "puts OpenStudio::openStudioLongVersion"
The following chipsets ran to completion:
The following chipsets exhibited the buggy behavior:
Intel's newest desktop processors (Raptor Lake) and upcoming processors also fail to run older versions of OpenStudio.
Building on @macumber's work using the latest SDE (v9.14), here's the full compatibility list. Migrating to newer versions of OpenStudio is strongly recommended:
Code Name | Released | OpenStudio v2.8.1 | OpenStudio v3.5.1 |
---|---|---|---|
Pentium4 | 2000 | SDE-ERROR | SDE-ERROR |
Pentium4 Prescott | 2004 | SDE-ERROR | SDE-ERROR |
Merom | 2006 | SDE-ERROR | SDE-ERROR |
Penryn | 2007 | SDE-ERROR | SDE-ERROR |
Nehalem | 2008 | SDE-ERROR | SDE-ERROR |
Westmere | 2010 | SDE-ERROR | SDE-ERROR |
Saltwell | 2011 | SDE-ERROR | SDE-ERROR |
Sandy Bridge | 2011 | ✔ | ✔ |
Ivy Bridge | 2012 | ✔ | ✔ |
Haswell | 2013 | ✔ | ✔ |
Quark | 2013 | SDE-ERROR | SDE-ERROR |
Silvermont | 2013 | SDE-ERROR | SDE-ERROR |
Broadwell | 2014 | ✔ | ✔ |
Skylake | 2015 | ✔ | ✔ |
Skylake server | 2015 | ✔ | ✔ |
Goldmont | 2016 | SDE-ERROR | SDE-ERROR |
Knights landing | 2016 | ✔ | ✔ |
Goldmont Plus | 2017 | SDE-ERROR | SDE-ERROR |
Knights mill | 2017 | ✔ | ✔ |
Cannon Lake | 2018 | ❌ | ✔ |
Cascade Lake | 2019 | ✔ | ✔ |
Ice Lake | 2019 | ❌ | ✔ |
Cooper Lake | 2020 | ✔ | ✔ |
Snow Ridge | 2020 | SDE-ERROR | SDE-ERROR |
Tiger Lake | 2020 | ❌ | ✔ |
Tremont | 2020 | SDE-ERROR | SDE-ERROR |
Alder Lake | 2021 | ❌ | ✔ |
Grand Ridge | 2021 | ❌ | ✔ |
Ice Lake server | 2021 | ❌ | ✔ |
Raptor Lake | 2022 | ❌ | ✔ |
Sapphire Rapids | 2023 | ❌ | ✔ |
Granite Rapids | 2024 | ❌ | ✔ |
Sierra Forest | 2024 | ❌ | ✔ |
Future chip | ❌ | ✔ |
* SDE-ERROR
means anything from the chip not supporting 64-bit binaries, to incompatible instruction sets
(This was tested using an Intel i9-13900KF
, sde-external-9.14.0-2022-10-25-win
, and OpenStudio v2.8.1
& v3.5.1
)
cc @tijcolem
Are there any workarounds (perhaps thru emulations) to get this to work with newer Intel chipsets? I currently use Sketchup 2017 with a university-made plugin called BESTEnergy that is based on and deals exclusively with OpenStudio v2.9.1.
Tried using the plugin with Sketchup 2022 and latest OpenStudio with no luck. Stuck with using 13700k for the time being, so it'd be helpful if there's a workaround to get the older version to work with new chips.
I think you should try to compile OpenStudio 2.9.1 from source on your machine... This issue is hard for us because we dont have this specific hardware on hand and it affects older versions.
@jmarrec will give it a try if you can help with a simple tutorial on how to compile it on my own system. I know this is not the right place for this kind of requests, but would be of a great help.
I'm on Windows 11, I have Visual Studio and CMake GUI installed, tried fiddling around with the source code with no luck.
@cerahmed For 2.9.1 the OSApp wasn't on this repo, it was still at NREL/OpenStudio.
You want to checkout NREL/OpenStudio at 2.9.X-LTS branch: What's kinda weird at that point in time is that you want to build the cmakelists in the openstudiocore/ subfolder, not the parent one: https://github.com/NREL/OpenStudio/tree/2.9.X-LTS/openstudiocore
There are wiki instructions at : https://github.com/NREL/OpenStudio/wiki/Configuring-OpenStudio-Build-Environments-(2.9.X-LTS)
I am not certain whether you can or cannot build with Visual Studio (MSVC) above version 2013 or not... The officially supported compiler is MSVC 2013. I don't think neither MSVC 2019 nor 2022 offers the VS 2013 C++ build tools in the list of possible "Individual components" (at least not on my machine...). It it fails with a recent MSVC, safest best is to install Visual Studio 2013 Update 5 as indicated though...
The configuration options would look something like that:
git clone git@github.com:NREL/OpenStudio.git
cd OpenStudio\openstudiocore
mkdir build && cd build
cmake -G \"Visual Studio 12 2013 Win64\" -DBUILD_CSHARP_BINDINGS=ON -DBUILD_DOCUMENTATION=ON ^
-DBUILD_TESTING=ON -DBUILD_DVIEW=ON -DBUILD_OS_APP=ON -DBUILD_PACKAGE=ON -DBUILD_PAT=ON ^
-DCPACK_BINARY_DEB=OFF -DCPACK_BINARY_IFW=ON -DCPACK_BINARY_NSIS=OFF -DCPACK_BINARY_RPM=OFF ^
-DCPACK_BINARY_STGZ=OFF -DCPACK_BINARY_TBZ2=OFF -DCPACK_BINARY_TGZ=OFF ^
-DCPACK_BINARY_TXZ=OFF -DCPACK_BINARY_TZ=OFF ../openstudiocore"
Then open MSVC, and load the OpenStudio.sln in that build directory, or just type cmake --build . --config Release --target package
(maybe passing -j X
where X is the number of processors you have, can't never know if it's helpful or not on windows)
Reported on https://unmethours.com/question/41887/openstudio-291-crash-on-startup/