Classic asp with vbscript code in Umbraco 8.6.1 - geting error 80004005 in the code trim(request("EmailID"))
I have an umbraco 8.6.1 website. I need to add a new folder into it which is done in classic asp with vbscript code. Added the umbracoReservedPaths in the config also. Page loads, but upon form submit, i get error code 80004005. The code in that line is trim(request("EmailID")).
What else I have to add to make it working along with the Umbraco site?
Can't see the code, does request("EmailID") have a value or can it be null ? Try Trim("" & request("EmailID")) this way a null gets converted to an empty string.
Since your getting an error message on a specific line it look to me like a syntax error which has nothing to do with Umbraco. But could be wrong ...
Classic asp with vbscript code in Umbraco 8.6.1 - geting error 80004005 in the code trim(request("EmailID"))
I have an umbraco 8.6.1 website. I need to add a new folder into it which is done in classic asp with vbscript code. Added the umbracoReservedPaths in the config also. Page loads, but upon form submit, i get error code 80004005. The code in that line is trim(request("EmailID")).
What else I have to add to make it working along with the Umbraco site?
Can't see the code, does request("EmailID") have a value or can it be null ? Try Trim("" & request("EmailID")) this way a null gets converted to an empty string.
Since your getting an error message on a specific line it look to me like a syntax error which has nothing to do with Umbraco. But could be wrong ...
The post is happening and there is data too. Getting error when we try to get that data using the request() functionality
Hi Dawn
Ahh, classic ASP, not seen that for a while!
Perhaps this is related?
https://stackoverflow.com/questions/5914928/classic-asp-running-in-integrated-pipeline
would it be possible to run the classic asp site as a virtual folder with it's own app pool?
regards
Marc
Yes, created separate virtual directory for the asp folder and it is working now without affecting any umbraco functionality
is working on a reply...