iisnode encountered an error when processing the request.

HRESULT: 0x6d
HTTP status: 500
HTTP subStatus: 1013
HTTP reason: Internal Server Error

You are receiving this HTTP 200 response because system.webServer/iisnode/@devErrorsEnabled configuration setting is 'true'.

In addition to the log of stdout and stderr of the node.exe process, consider using debugging and ETW traces to further diagnose the problem.

The node.exe process has not written any information to stderr or iisnode was unable to capture this information. Frequent reason is that the iisnode module is unable to create a log file to capture stdout and stderr output from node.exe. Please check that the identity of the IIS application pool running the node.js application has read and write access permissions to the directory on the server where the node.js application is located. Alternatively you can disable logging by setting system.webServer/iisnode/@loggingEnabled element of web.config to 'false'.

iisnode encountered an error when processing the request.

HRESULT: 0x6d
HTTP status: 500
HTTP subStatus: 1013
HTTP reason: Internal Server Error

You are receiving this HTTP 200 response because system.webServer/iisnode/@devErrorsEnabled configuration setting is 'true'.

In addition to the log of stdout and stderr of the node.exe process, consider using debugging and ETW traces to further diagnose the problem.

The node.exe process has not written any information to stderr or iisnode was unable to capture this information. Frequent reason is that the iisnode module is unable to create a log file to capture stdout and stderr output from node.exe. Please check that the identity of the IIS application pool running the node.js application has read and write access permissions to the directory on the server where the node.js application is located. Alternatively you can disable logging by setting system.webServer/iisnode/@loggingEnabled element of web.config to 'false'.

Vis huskeliste Tilføj arrangement

Ret info
Sidst rettet
27/1 2023

Midtdjurs Vinfestival

Horstvedvej 11
8560 Kolind

Viser 1 event fra/efter 2. jun. 2024

8. Mar Gastronomi

Midtdjurs vinfestival 2025

Lørdag den 8. marts 2025, kl. 13-17.

Pris: Entré: 150 kr Køb/bestil billet

Arrangør: Midtdjurs Vinfestival. Kolind+, Bugtrupvej 33, Kolind

Hej og velkommen til Midtdjurs Vinfestival - hvor vin, samarbejde og lokal passion forenes for tredje år i træk!.

Tag med os på en udsøgt rejse gennem vinens verden, når vi igen åbner dørene for en uforglemmelig smagsoplevelse den 8. marts 2025. Midtdjurs Vinfestival er ikke bare en begivenhed; det er en fejring af vores fælles kærlighed til vin, lokalforankring og det gode samarbejde mellem vores fire dedikerede lokale vinimportører.

Vores vision er klar - at præsentere et mangfoldigt udvalg af vine, nøje udvalgt fra nogle af verdens mest ikoniske vinregioner. Hver af vores fire lokale vinimportører vil fremvise deres stolthed og passion gennem nøje udvalgte vine fra Frankrig, Italien, Californien, Danmark og Sydafrika. Glæd dig til at opleve unikke smagsnuancer, subtile aromaer og historier fra vinmarker verden over.

Midtdjurs Vinfestival er ikke blot en lejlighed til at smage på fantastiske vine; det er også en mulighed for at møde de dedikerede folk bag vinene. Vores lokale vinimportører og forhandlere står klar til at dele deres ekspertise, historier og passion for vin med dig.

Sæt allerede nu kryds i kalenderen den 8. marts 2025 og vær med til at skabe en uforglemmelig dag fyldt med vin, fællesskab og lokal stolthed. Vi glæder os til at byde dig velkommen til Midtdjurs Vinfestival - hvor vinens verden møder vores lokale hjerte! *

OBS - Billetprisen stiger til 200kr. 31. december 2024

Vis kort

Husk

Glem

iisnode encountered an error when processing the request.

HRESULT: 0x6d
HTTP status: 500
HTTP subStatus: 1013
HTTP reason: Internal Server Error

You are receiving this HTTP 200 response because system.webServer/iisnode/@devErrorsEnabled configuration setting is 'true'.

In addition to the log of stdout and stderr of the node.exe process, consider using debugging and ETW traces to further diagnose the problem.

The node.exe process has not written any information to stderr or iisnode was unable to capture this information. Frequent reason is that the iisnode module is unable to create a log file to capture stdout and stderr output from node.exe. Please check that the identity of the IIS application pool running the node.js application has read and write access permissions to the directory on the server where the node.js application is located. Alternatively you can disable logging by setting system.webServer/iisnode/@loggingEnabled element of web.config to 'false'.