wc.dll not executing on Win2008/64 Michael Hogan (Ideate Hosting)
All
Oct 25, 2014 @ 04:46pm
Hitting a scriptmapped url, I get "The current Web Connection request took too long to process on the server and we had to abort it."
Since I'm getting this response, it appears that wc.dll is running even though I don't see it pop up in the task manager. The temp directory is not getting written to, although I have triple-checked the path in both ini files and I'm not getting a warning about temp directory permissions from wc.dll.
Not quite sure where to go from here, but I'll search further.
Michael
www.WebConnectionHosting.com
Re: wc.dll not executing on Win2008/64 Rick Strahl
Michael Hogan (Ideate Hosting)
Oct 27, 2014 @ 12:36am
On the same page also check the temp path, and make sure the temp path matches with what you have in your FoxPro server's .INI file.
+++ Rick ---
I'm having a bit of a problem migrating an app to a new Win2008/64 server. I used the console install and I set directory permissions to the temp directory. I'm first trying to get it running in file mode.
Hitting a scriptmapped url, I get "The current Web Connection request took too long to process on the server and we had to abort it."
Since I'm getting this response, it appears that wc.dll is running even though I don't see it pop up in the task manager. The temp directory is not getting written to, although I have triple-checked the path in both ini files and I'm not getting a warning about temp directory permissions from wc.dll.
Not quite sure where to go from here, but I'll search further.
West Wind Technologies
Making waves on the Web
from Maui
Re: wc.dll not executing on Win2008/64 Michael Hogan (Ideate Hosting)
Rick Strahl
Oct 28, 2014 @ 08:51am
Probably permissions. I suggest to bring up the ISAPI Admin path (Web Connection Module Administration) and check what account the Server account is running under. Make sure that account has rights to write to the temp folder.
On the same page also check the temp path, and make sure the temp path matches with what you have in your FoxPro server's .INI file.
+++ Rick ---
I'm having a bit of a problem migrating an app to a new Win2008/64 server. I used the console install and I set directory permissions to the temp directory. I'm first trying to get it running in file mode.
Hitting a scriptmapped url, I get "The current Web Connection request took too long to process on the server and we had to abort it."
Since I'm getting this response, it appears that wc.dll is running even though I don't see it pop up in the task manager. The temp directory is not getting written to, although I have triple-checked the path in both ini files and I'm not getting a warning about temp directory permissions from wc.dll.
Not quite sure where to go from here, but I'll search further.
Michael
www.WebConnectionHosting.com