Changes between Initial Version and Version 5 of Ticket #545


Ignore:
Timestamp:
2026-06-08T09:17:32-03:00 (3 weeks ago)
Author:
Jeff McKenna
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #545

    • Property Cc Alberto Bianchi added; TC Haddad removed
    • Property Priority major → blocker
    • Property Component MS4W - Base → MS4W - MapServer
    • Property Summary Mapserv startup crash on Win Server 2016 → mapserv.exe startup crash on Win Server 2016

  • Ticket #545 – Description

    initial v5  
    1 Mapserv.exe in MS4W 5.2 unfortunately seems to crash on startup on Windows Server 2016 (which admittedly is close to EOL in 2027).
     1`mapserv.exe` in MS4W 5.2 unfortunately seems to crash on startup on Windows Server 2016 (which admittedly is close to EOL in 2027).
    22
    33The final MS4W 5.2 install startup page will show "Internal Server Error" in place of the main OpenLayers map, and any click to view the demo WMS, WFS, etc. will also result in a 500 server error.
    … …  
    99and
    1010
    11 [client 127.0.0.1:49757] End of script output before headers: mapserv.exe
     11`[client 127.0.0.1:49757] End of script output before headers: mapserv.exe`
    1212
    1313
    … …  
    2020mapserv.exe "QUERY_STRING=map=D:\www\tests\test.map&mode=map"
    2121
     22{{{
    2223Error message produced from this failed test is:
    2324"The application was unable to start correctly (0x000a200)"
     25}}}
    2426
    2527Going back in the release history shows that the Windows Server 2016 will successfully run the MS4W 5.2 Beta 1, and that the incompatibility with this OS arose in the betas and release candidates that followed.