I'm attempting to move my long-running WC 5.x application from my old Win 2008/32 server to Win 2019/64. It's working fine in Win 2008 Server in COM mode.

When I set it up per the manual configuration and hit the site with a test page, it fires up the instances fine but does not respond to the request so I'm debugging it in file mode.

It turns out that the temp message file that WC is looking for seems to be getting plunked into the wrong path.

Running it in file mode for debugging (using Template=CC5 for the template prefix in file mode) I'm expecting WC to place the message files into the specified [wwcgi] Path location: Path=D:\Webs\Apps\CondoApp\Temp\ - but it's placing the files into the parent directory D:\Webs\Apps\CondoApp\TempCC5_19_53d6b61d.tmp - as if it's losing the last backslash of the path (and using the intended target directory as part of the file name)... although the wcerrors.txt file goes into the correct location.

If I rename the tmp file to CC5_19_53d6b61d.tmp (by removing the prefix) and copy it to the temp directory, webconnect finds the messaging file and responds appropriately.

Thoughts on how I can correct it?

Rick:

Any idea why WC is losing the "" in the temp pathname as described below? The environment is Win 2019/x64 and it's using WWWC 5.x

It's looking for the temp file under D:\Webs\Apps\CondoApp\TempCC5_19_53d6b61d.tmp (no slash after 'temp') instead of under D:\Webs\Apps\CondoApp\Temp\CC5_19_53d6b61d.tmp (slash after 'temp')

Works fine under Win2008/16

Suggestions would be appreciated.

TIA