We are setting up new Content Delivery server for Tridion 5.3 SP1 environment.
New website is created for HTTPS upload, as per the instructions given in the instruction manual. When we browse httpupload website from content delivery server using localhost:20000/httpupload.asp sometime it gives 500 error or sometime it given 403 error. Can someone let us know exactly were we are going wrong. Even we tried accessing httpupload.asp from different machine there also it gives 500 error.
Note : Modify permissions are given to IUSR AND IWAM user on work folder.
Make sure you have enabled directory browsing in IIS.
Also make sure that the 'asp' extension is present in the Extensions in IIS.
Related
I created a Windows Server 2008 virtual box with IIS7. I have two websites configured, one is my actual development site and the second is a test site to help troubleshoot this issue.
Website 1 (WS1) - the root of this website is on a drive which is mapped to my development machine (Mac Book Pro). The mapping seems to be working and I can access all files fine (W:\www\dev.frogquest.com).
Website 2 (WS2) - is a very simple website with one ColdFusion page just to prove that everything works. It's root is a local directory on the C:\ drive of the VB (C:\sites\localtestsite.com).
I've added host file entries for both sites (127.0.0.1 ...)
WS1 - Throws a Server error when I try to access it...
HTTP Error 500.19 - Internal Server error
The requested page cannot be accessed because the related configuration data for the page is invalid
Here's what I've tried so far...
Uninstalled both .NET 4.5 and URL Rewrite 2, rebooted, reinstalled .NET 4.5, rebooted, reinstalled URL Rewrite 2 Module… retried… FAIL! I took these actions because of information I found here...
HTTP Error 500.19 on IIS7 "Malformed XML" in web.config
Per the same article as above, I tried deleting the web.config file. Strangely, this had no impact, even after restarting the website, restarting the virtual box instance, etc... which I've done frequently btw just to rule that out.
I tried adding IIS_IUSRS to the WS1 directory, but because it's a mapped drive I didn't get a "Security" tab. So, this was fruitless. This was per this article...
IIS 7.0 Error - 500.19 Internal Server Error
I tried playing with the AppPool security, changing it from "pass-through authentication" to connecting as the administrator of the machine. When I clicked "Test Settings" I did get different results, but they didn't have any material affect in the actual server response. I have screenshots of the test setting results.
I copied the contents of WS1 into WS2 and this works! So, it has something to do with the fact that it's a mapped drive and very likely a permissioning issue in my opinion.
I am now out of ideas and in need of competent help and fresh ways of thinking about this!
UPDATE: Adding a screenshot of the actual error for more info...
IIS does not support any type of mapped drive,
https://support.microsoft.com/en-us/kb/257174
You will have to use the recommended workarounds, such as UNC paths.
A customer gets a 403 error when trying to install our VSTO ClickOnce application. We are hosted on GoDaddy IIS7.
"Downloading (one of our files ending in .deploy) did not succeed. System.Net.WebException: The remote server returned an error (403): Forbidden."
FWIW I've made sure all files needed for the installation are present in the remote directory. The publish from Visual Studio succeeds without any errors.
The installer is hosted on GoDaddy, and it has all the correct ClickOnce MIME types set. We didn't modify any of these.
BTW, could not find the ClickOnce error log! Searching online reveals that the log is located in Temporary Internet Files by default, but it was not there. We don't have our own custom log file location set, and we'd prefer not to set up a custom location for the customer's log if we can just grab the default one instead. It doesn't sound as though the log file provides any additional information beyond the stack trace revealed by the "Details" button in the error dialog, anyway.
Sounds like there is no read access to this file for your customers.
Try to download the file directly.
I have migrated our company web apps from Windows Server 2003 to Windows Server 2008 R2. The are all .Net 2.0 classic web apps. They all seem to work fine, except when accessing any resource with a path starting with /Reports/...
In one app the physical path on disk is c:\Websites\app_name\WebService\Reports... In this reports folder PDF files are dynamically generated and written to disk. They can be accessed via a URL such as this:
http://domain_name/Reports/xxxx.pdf
where /Reports is a virtual directory mapping to the physical path above. This worked fine on 2003 server & IIS6 but on IIS7.5 & 2008 R2 I keep getting the following error:
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested URL: /Reports/xxxx.pdf
I have another web app that generates the reports dynamically and streams them directly to the client browser for saving to the local disk, rather than being written to disk on the server. Similar to the above example, the page that generates the report is found under path as follows:
/Reports/Viewer.aspx
In this case there is no virtual directory being used. The URL referenced in the browser is:
http://another_domain_name//Reports/Viewer.aspx
Once again I get the same error message as above... HTTP 404 - The resource cannot be found.
I have tried all the permission settings under the sun to try and get it working but to no avail. I've use built in accounts, created new accounts with permissions from very minimal right up to full admin rights. I've also played with the new AppPool Identities with no success. It doesn't seem to matter what permissions I set specifically on the directories, or the accounts configured for the app pool or basic settings on each website itself.
Once thing I have discovered though, is that whilst the browser is getting the HTTP 404 error, there is no record of this request appearing in the IIS log files for each website!! This is really confusing me, as I would definitely expect to see a failed 404 log entry on the requested resource.
Something else to note, I'm running SQL Server 2008 Enterprise on this machine with Reporting services installed and enabled. It's a stretch, but could there be some contention over the /Reports path in my websites vs something else running on the machine? I'm using different bindings/host headers for each individual domain and website running on the server.
Check Reports folder conflict. And remember, Google is faster than SO.
IIS gives 404 errors for more than just File Not Found these days - so it doesn't give away too much to attackers. Have a look at the event log (application), and also try accessing it from the server itself.
The other thing to check is that your IIS app pools are correctly configured - especially with the correct pipeline mode and .NET framework version.
At a command prompt, type:
netsh http show urlacl
See if there are any bindings with /reports/ --maybe a left over from a SQL Server Reporting Services install?
v/r
BK
I am building an asp.net web application which has been working on local and staging. however, when i deployed to live, there is a little weird issue occurred. below is the live environment details.
live environment:
Server 2003
IIS 6
when the request url is below, if page not found, it will redirect to page 404 configured in the IIS.
"http://www.xxxx.com/folder1/default.aspx"
however, when the request url is below (with a dot in the folder), it will show a IIS default 404 message which is "The system cannot find the file specified." which isn't what i configured in the IIS and it seems like it skips all the http handlers and modules. Therefore, my custom http handler stop working with this kind of url.
"http://www.xxxx.com/folder.1/default.aspx"
My guess it something to do with the IIS setting. i have have several research, there is no other issue like me.
appreciated if anyone can help. Thanks a lot.
Dion
One of the possible reason could be tool such as UrlScan - you need to explicitly configured it to allow dot(.)s in the url - this can be done by editing <Windows Folder>\system32\inetsrv\urlscan.ini and setting AllowDotInPath=1
I don’t know anything about deploying a website, so I probably made some stupid mistake.
Anyways, I opened IIS 7 manager, created new virtual directory ( via Add Application ) and pointed it to physical directory where Visual studio saved my Web project. But when I tried to request an .aspx page, browser reported the following error (I won’t post the whole error, but just the interesting bits):
Handler: Not yet determined
Config Error: Cannot read configuration file due to insufficient permissions
Logon User: Not yet determined
A) why is handler not yet determined? As far as I know, IIS7 does have Asp.Net handler registered?!
B) Why wouldn’t IIS have sufficient permissions? Does that mean I should give IIS higher privileges? Or does Asp.Net runtime have insufficient permissions?
C) Could the error also be due to the fact that perhaps it expected the user to authenticate itself? I’m assuming this due to Logon user not yet being determined?
D) And finally, any ideas how to make it work?
thanx
error code:0x8007000d
I started playing with permissions and all the stuff about access issues to web.config or applicationhost.config anyway those did not change the error.
while I was playing with my web.config I deleted rewrite tags from my config file and error changed. then I installed "web platform installer" and installed url rewrite module for IIS and played with some configuration now my site is working. it took about one day to find out this issue I hope it helps someone.
Does the identity of your IIS application pool have sufficient rights to access the folder that is hosting your site?