fuel9 / DisplayMonkey

Display Monkey digital signage solution
Other
128 stars 51 forks source link

Underlaying connection was closed powerbi ? #183

Open Plesmanweg opened 4 years ago

Plesmanweg commented 4 years ago

Hello,

I have the problem in powerbi that when me or an colleague wants to add an power bi frame in displaymonkey it now gives an error.

It says: The underlying connection was closed: An unexpected error occured on a send.

Does someone know how to solve this problem? Is there something with the powerbi server or something? i hope someone can help me :)

moeman2323 commented 4 years ago

I started experiencing the same issue a few weeks ago. I thought it was just the IIS server so I rebooted it last night and I am still experiencing the same issue. If anyone has any ideas, it would be greatly appreciated as I cannot edit or add any PowerBI frames.

Plesmanweg commented 4 years ago

thanks for your reaction. My it-colleague thinks it could have something to do with microsoft and it's removal of tls 1.0 and 1.1 out of it's systems. But i don't know if or how displaymonkey works with tls? And are the people behind displaymonkey working on a new version? or will the 2019 version be the last one?

Plesmanweg commented 4 years ago

I started experiencing the same issue a few weeks ago. I thought it was just the IIS server so I rebooted it last night and I am still experiencing the same issue. If anyone has any ideas, it would be greatly appreciated as I cannot edit or add any PowerBI frames.

My colleague found an sollution: https://docs.microsoft.com/nl-nl/mem/configmgr/core/plan-design/security/enable-tls-1-2-client follow that link and you can find what to do. You have to add some registry keys to de displaymonkey server

Plesmanweg commented 3 years ago

Here by an new sollution. When there is dotnetframework 4.7 installed on de displaymonkey server you also have to change it in de web.config files in both folders in: displaymonkey_management Folder add orchange following Only changing the version from probabaly 4.5.x to 4.7.1 depending on the dotnetframework installation version.

<compilation targetFramework="4.7.1">
      <assemblies>
        <add assembly="System.Data.Entity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
      </assemblies>
    </compilation>
    <httpRuntime targetFramework="4.7" maxRequestLength="1048576" executionTimeout="120000" />
        <authentication mode="Windows" />

Displaymonkey Folder add following

 <system.web>
    <compilation targetFramework="4.7" />
    <httpRuntime targetFramework="4.7" />
    <authentication mode="Forms">