Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Niels Haasnoot 7 posts 57 karma points
    Aug 10, 2023 @ 09:16
    Niels Haasnoot
    0

    Newsletter Studio after publishing not working in IIS

    Hi, after I publishing the Umbraco (v11) website with Newsletter Studio (v11) to IIS, I get a bunch of console errors (500) when I opening Newsletter Studio.

    Error opening Email dashboard:

    Failed to load resource: the server responded with a status of 500 (Internal Server Error) - /umbraco/backoffice/NewsletterStudio/Workspace/GetDashboardOverview/
    

    Error opening Campaign:

    GET /umbraco/backoffice/NewsletterStudio/Campaign/GetByKey/1fc4ee6f-7395-4ece-b747-e1a981461a0f?e=12747708-5071-4098-82c5-d3cded0a276a 500 (Internal Server Error)
    

    Any suggestions to solve this? On development/IIS Express it's working. Checked permissions already, but maybe i'm missing something.

  • Markus Johansson 1924 posts 5831 karma points MVP 2x c-trib
    Aug 10, 2023 @ 21:40
    Markus Johansson
    0

    Hi!

    Sorry to hear that you're seeing issues while trying to move to IIS.

    My first guess is that there might be some files or folders missing in the artifacts that you are trying to run on IIS. I would recommend:

    • Compare your App_Plugins folder to see if there is anything missing
    • Look in the trace look and see why you are getting these 500-errors (Settings -> Logs in the backoffice or /umbraco/logs on disk). Please share any error message that might help me understand more about the problem.

    Talk to you soon again!

  • Niels Haasnoot 7 posts 57 karma points
    Aug 23, 2023 @ 09:10
    Niels Haasnoot
    0

    Hi! After looking into the differences between the app_pool settings, I was able to find the wrong setting.

    "Enable 32-Bit Applications" was set to True, where it should be on False.

    That solved my issues and the console errors. There was no further info available in the logging.

  • Markus Johansson 1924 posts 5831 karma points MVP 2x c-trib
    Aug 23, 2023 @ 09:17
    Markus Johansson
    0

    Hi!

    Ohh, so the only problem you had was with the Newsletter Studio-package and switching this setting to False solved it?

    It feels like this might have also caused some kind of restart or cache-reset but I'm glad that the change solved your problem and thanks for sharing your solution!

  • Niels Haasnoot 7 posts 57 karma points
    Apr 03, 2024 @ 10:45
    Niels Haasnoot
    100

    Hi Markus, this issue was a while ago, but we just had to migrate to another IIS environment and stumbled accross the same errors.

    Last time we changed a number of things at the same time, including the 32bit setting on the app pool. I concluded that this was the cause, but this was not the case.

    It's stupid that we didn't check this out.

    In the end it turns out that our custom theme.json file was missing from the App_Plugins folder and was causing the errors above.

  • Markus Johansson 1924 posts 5831 karma points MVP 2x c-trib
    Apr 03, 2024 @ 11:48
    Markus Johansson
    0

    Hi again Niels!

    Thanks for the update!

    It's indeed the most common problem that some files get lost in the publish process, like in your case the theme.json file.

    Great to hear that you finally figured out the underlying issue.

    Cheers!

Please Sign in or register to post replies

Write your reply to:

Draft