Webserver IIS problem with Model Directory

Question

question

Nil Ns asked Sep 10 2024 at 1:11 PM Logan Gold commented Sep 18 2024 at 3:59 PM

Webserver IIS problem with Model Directory

Hello,

I need help with the WebServer. At first, the installation worked perfectly, and I could access the models without any problems. But after following the steps to use IIS, when I try to check which models are available, none show up.

I have reviewed the entire procedure to make sure everything is correct, and when I open FlexsimWeb, the login panel appears where I can enter my username and password. However, once inside the Web Server view, the model dropdown is empty.

I have checked to make sure it's not an issue with folder access permissions, but I haven't been able to fix it (everyone has permission).

Does anyone have any idea what I could do?

Thank you very much.

Software Version:

FlexSim 24.2.1

webserver iis webserver iis

· 5

Logan Gold ♦♦ commented · Sep 18 2024 at 3:59 PM

Hi @Nil Ns, was Ben Wilson's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always comment back to reopen your question.

1 ·

Jason Lightfoot ♦♦ commented · Sep 10 2024 at 1:42 PM

You may need to add iuser to the folder permissions - I'm a little bit hazy on this as it's a long time since I set it up for IIS.

0 ·

Nil Ns Jason Lightfoot ♦♦ commented · Sep 10 2024 at 2:27 PM

Thanks, Jason. We set access permissions for all users, but it doesn’t work. Do you know what else it could be?

0 ·

Jason Lightfoot ♦♦ Nil Ns commented · Sep 11 2024 at 9:59 AM

I would take a look at this link about securing resources for IIS access.

1 ·

Show more comments

Answer 1 · 2024-09-10T16:18:16Z

Ben Wilson answered Sep 10 2024 at 4:18 PM

If this is the latest IIS on Win 11, the slashes aren't handled correctly. Please see Paul's Answer here.

Paul mentions you could use either Apache or Nginx as a proxy instead of IIS until a fix is released that addresses this issue.

question