Unable to create website error (NEW) - security

I copied my ClickOnce deployment to my C:/Inetpub/ folder on my webserver and I deleted my Virtual directory. I deleted the WpfApplication1 folder beneath wwwroot in Win Explorer. Then I turned on Web Sharing for this folder. Then I viewed my IIS Manager and this new Share name appeared under wwwroot.
So now under Inetpub folder on my web server I have the following directory path:
C:\Inetpub\WpfApplication1\
with contents:
Application Files
publish.htm
setup.exe
WpfApplication1.application
Next, I remapped both the publishing and installation URL's for the project to http://myserver/WpfApplication1/
And I clicked Publish Now.
But after I performed a Publish Now operation, I got the following error on my development server (D610-M):
Error 1 Failed to connect to 'http://myserver/WpfApplication1/' with the following error: Unable to create the Web site 'http://myserver/WpfApplication1/'. The Web server does not appear to have any authentication methods enabled. It asked for user authentication, but did not send a WWW-Authenticate header. 1 1 WpfApplication1
On my webserver, when I click Browse from the IIS Manager on the WpfApplication1 directory, it shows me the Install page. But after I click the Browse button, it returns an error which says:
The remote name could not be resolved: 'd610-m' (D610-M is the name of my development server).
How do I fix this?

Try using the IP address of the machine instead of the DNS name...

Related

Http 403 error in Microsoft edge

I was getting "HTTP 403 error Microsoft Edge can’t get to this page", while launching an application from IIS in Windows 10. Please suggest a solution for this.
thanks
If all permissions are set and even though your website shows 403 forbidden, most likely the default page is not set for your website. With IIS, you can configure the default document as follows.
Connect to IIS.
Expand the sites and select the desired website.
From right hand side feature view, click on Default Document.
Set your desire default page and save the settings.
While you browse any website, IIS searches for the default page to be displayed. If the first default document is not available, IIS will look for the next default page from the list. When IIS is unable to find any match and directory listing is enabled for that particular website, IIS will show you the list of folders. If directory listing is disabled, IIS will return an HTTP Error 403 - Forbidden message to the browser.
If an empty application gives you a 403 I can think of two immediate reasons.
The permissions are wrong. You might need to give the application pool user (IIS AppPool\NAMEOFAPPPOOL with recommended configuration) read permission to the directory.
You don't have any content. If you try to access a directory in IIS you will get a 403. Add a file and try to access that directly, or a Default.aspx or index.html file to the directory you're trying to access.

page is not displaying, php project on iis

I have done all IIS and PHP manager configuration
and created one website called website1 and I set the ip address and name website1.net in host file, when I click browse in IIS the result is page cant be displayed. any solutions ?

Using Umbraco with Subfolders

I have built an Umbraco project (7.2.2) on my local machine and it all works well. I now want to copy it to our test server running IIS 7.5.
I have created a Virtual Folder in IIS under the default web site and copied the project across. The url I am using is www.ourserver.com/testumbraco. I can access the content ok but if I try to login to edit the content I get a blank page (umbraco#/login/false) and shortly afterwards it returns to the login page with Session timed out.
If I Inspect the page I can see that some resources have failed to load with Error 404. It is looking for www.ourserver.com/umbraco and not www.ourserver.com/testumbraco/umbraco.
Is there a configuration setting I need to change to make this work properly?
Thanks in advance for any suggestions.
You need to update the umbracoPath setting in the web.config

Error in non existent global.asa

I have a user's website giving an error in a global.asa file but it does not exist in their web root. It looks like the account has been hacked as it's giving an error about not connecting to a server, and at the same time I see the firewall block outbound connection requests.
msxml3.dll error '80072efd'
A connection with the server could not be established
/LM/W3SVC/6510/ROOT/global.asa, line 66
I've deleted the IIS instance and had the control panel recreate it, but the issue still exists. I've even created a dummy asp file which only displays some text and it happens.
I'm at a loss where this could be being picked up and looking for suggestions. Where might this be set?
I've had the same problem on a w2k3 server (iis6) with many sites, where just one had the fake global.asa;
I've not still found cause but a workaround solution, for me, has been:
open MMC Console (IIS manager)
stop IIS
double click on Web Sites (confirm reload offline configuration)
under every site delete "ghost" global.asa (that you don't find under phisical websites folder)
start IIS

Uable to access sharepoint site

I turned on directory browsing (in IIS) for my sharepoint site, then turned it off again and now every time I try to access the site through a web browser I get 404 error, page cannot be found.
I know it's something to do with authentication but don't know where to start looking/fixing ?
Can you give a bit more background? Do you get 404's for all pages? Can you hit layouts pages? E.G:
http://YOURSITE/_layouts/settings.aspx
404's in SharePoint shouldn't be taken at face value. Check your ULS logs in:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS
We ran into a smiliar issue yesterday
More of a work around this:
Rather than try to figure out what permissions to set/reset, just delete the web application, specifying Yes to 'Delete IIS Web' sites and No to 'Delete content databases'.
This will keep the content database (with all your content you can't currently access).
Then create a new web application with the same name and host header and enter the existing content database name.
This should then recreate the IIS web app with correct permissions and connect to the existing content database.

Resources