Security :: Publishing Application On Windows Server 2008 And IIS 7
Dec 12, 2010
i published an application on windows server 2008 and IIS 7 i am facing a problem when user are trying to access the server or the web application in address they put ip address of the server /application a pop up screen asking for username and password problem IIS on windows server 2008 ..the server is configured it s making me crazy it s asking users for username and password
We have a shared drive where web applications are published to. When I attempt to publish I get the following error:
------ Publish started: Project: XXX.Web, Configuration: Release Any CPU ------ Connecting to T:WebSitesXXX...
Unable to create the Web site 'T:WebSitesXXX'. The path 'T:WebSitesXXX' does not exist or you do not have access. The system cannot find the path specified.
Details
OS: Windows 7 IDE: Visual Studio 2008 (running as administrator) Path exists? Yup.
I assume it's some permissions issue, but I have no idea where to start.
I have created a web app using Visual Studio 2008 Express Edition and have come to the point where I need to publish the site onto my server (which is running window server 2008). I found that the publish function is not limited in the express edition, so published the app to a local file and FTP'd the contents across to my server. I then setup a website through the servers IIS manage and pointed it to the folder containing the FTP'd files.
My question is, how do I run the app? Do I need to point to a specific file?
I have tried to view a number of the files in browser directly from the IIS but keep getting the same standard connection error i.e. "Internet Explorer cannot display the webpage"
I have never used IIS Manager before and I can't find a resource which gives me a step by step guide to setting up a new site which has been created by Visual Studio 2008 Express Edition, are there any config changes needed.
Currently we are running an application build in VB6,ASP,Commerce Server2000 and Sql Server 2000. This application is running in Windows 2000 server.Now we are planning to migrate Windows server 2000 to Windows 2008.Will this application run in Windows 2008 or do we need to upgrade this application to dotnet and Sql 2008?
I've developed my .net web application in Visual Studio 2005. It's been running in production on a hosted server. We recently brought in-house our own servers and configured one as a web server. I am trying to set up my web application over there and am getting your typical errors like the resource cannot be found. If you could point me to a good link, that would be great, too. I know I am having very elementary problems like creating the correct virtual directory, etc.
I'm trying to get an asp.net application up on IIS on a Windows Server 2008 machine. I can hit the app from localhost, no problem. But I can't access the app using the server's domain name either locally or from another machine on the network.But here's the odd part. I can access a normal file on IIS using the domain name, both from a browser running on the server and from a browser running on another machine on the network. Here's a synopsis ("http" converted to "htp" below because I don't have enough points to have all these links in my message):
From IE on the server itself: works htp://localhost/foo.htm works htp://localhost/App works htp://test.foo.com/foo.htm dead htp://test.foo.com/App From IE on another machine: works htp://test.foo.com/foo.htm dead htp://test.foo.com/App
Can anyone explain why the following happens:My ASP.NET application requires access to Application event log.When I access web application initially, it returns "Security" exception (which is expected, as I haven't granted permissions to write to Application event log yet). Then I give read/write permissions to IIS_IUSRS group on the following registry key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetserviceseventlog. As a result of this action my web application starts working.Now I remove those permissions I've granted to IIS_IUSRS group. But my web application keeps working (although I'd expect "Security" exception raised again)So, why web application keeps working, although permissions to write to Application loghave been removed?
I am running a web application in vs-2008 on windows 2003 server.While execution of .net application, I am getting an error as"Unable to start debugging on the web server. Unable to connect to the web server. Verify that web server is running and that incoming HTTP requests are not blocked by firewall."
I want to execute some powershell commands on a remote windows 2008 machine. Right now i am using psexec to run the powershell from c# asp.net application. I would like to know is there any way to execute powershell commands without using a third party tool like psexec?
I have a web app, can upload images when running it on the local development machine, but when runnign it on WebServer 2008, it gives me an error saying "access is denied". I konw it is something to do with security, but how do I make it such that an internet user can have acces to it. The folder is located in: c:inetpubsiteimages494
We have a web application that makes a call to a remotely hosted ASMX service that worked in Server 2003 under IIS6. We are now migrating it to a Server 2008/IIS 7 setup and it doesn't appear that the application makes the call to the remote web service anymore. We ran Wireshark and don't see any traffic to the service URL. It seems to throw a 404 error without trying to connect.
Is there some security policy or restriction in Server 2008 or IIS 7 we need to set to allow an ASP.NET application make a call to a remote web service? We are using Network Service as our application pool user, but also tried using Local System as a troubleshooting step. In addition, the same code works if run from a console application on the server instead of the web application.
Is there some setting under IIS7 or server 2008 that would be causing this?
we have a web application that one company prepared for us. this application read connection string from registery key in hkey_local_machine and connect to sql server 2005 database. It worked correctly in windows server 2003. we changed our Server'OS to windows server 2008. but we have a problem to login. after try to login we see this error: Server Error in '/dabir' Application. Login failed for user ''. The user is not associated with a trusted SQL Server connection. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: Login failed for user ''. The user is not associated with a trusted SQL Server connection. Source Error:
We have a working version of application (Intranet) with uses Windows Authentication deployed in Windows 2003. The application uses HttpContext.Current.User.Identity.Name to get the logged-in user. Here impersonate is turned off.Right now, we are move to Windows 2008 RC2 where this Windows Authentication problem arised. I have Digest Authentication and Windows Authentication enabled. And also I have enabled Anonymous Authentication enabled to avoid the Login dialog of IIS in the end-user IE. Now I am getting HttpContext.Current.User.Identity.Name as Empty. When I impersonate using username and password, I am used to login using that user but all the users uses the same user to login.Does any has solution for this?Deployment Server - Windows 2008 RC2 (IIS 7.5)Development - Windows 7 (IIS 7.5)I am new to IIS 7.5. Please give me a solution
Microsoft Visual Studio 2010 was being used along with SQL Express for website development on the Operating System, Windows Server 2008 R2 Enterprise Edition of Intel Xeon CPU @ 2.13 GHz (2 Processors) containing 12 GB RAM with 64-bit Operating System. Website was developed along with the databases of SQL Express with the help of Visual Studio. Whether the developed website along with the databases may be used on the Operating System, Windows 7 of 64-bit? The website will used within Intranet. Which Operating System and configuration to be used for the Intranet Website?
I've installed IIS for Windows Server 2008 SP2 and Windows 7. In both instances, I can't get even the simplest of ASP.net scripts to work (note: I'm ftping the published files from Visual Web Dev 2008 Express on XP):
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.
Source Error
[Code]....
Line 36: ASP.NET to identify an incoming user.Line 37: -->Line 38: <authentication mode="Windows"/>Line 39: <!--Line 40: The <customErrors> section enables configuration Source File: C:inetpubwwwroot estweb.config Line: 38
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a
<customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
I just downloaded and installled the Microsoft Windows Azure SDK yesterday for the first time and I am having issues running the application as I all I am getting is 503 errors. I run Windows Server 2008 R2 on my development machine and even tested it on another co-workers 2008 R2 and couldn't even compile the application. He got this error instead "A problem occurred while trying to set the "References" parameter for the IDE's in-process compiler. Error HRESULT E_FAIL has been returned from a call to a COM component."
From within my Windows Server 2008 R2 Hyper-V Virtual Windows 7 x86 enviroment, I was able to successfully build and run the Windows Azure SDK and it even showed the base ASP.NET application.So my question is, does the Windows Azure SDK for Visual Studio 2010 w/ Visual Studio 2010 SP 1 installed not work under Microsoft Server 2008 R2?
I have looked at all the posts I can find on this problem and tried everything I can think of, but still the problem persists. I am getting really sick of it.was working fine for the last year until an update to MS Office 2007 caused a lot of problems (automatic update). After checking posts here, I removed it completely. No change. I then tried all the things I could find on other posts, also no change. Today, I removed VS and the Web Authoring Component and re-installed. Still no go.
Does anyone have a fix for this problem. It seems that it has been around a long time, but is still giving problems. I even saw one suggestion to reformat the drive! You've got to be joking!
I am looking at developing using Visual Studio 2010/2008 and SQL Server 2008 on Windows 7. Should I be able to do this on Windows 7 Professional, or do you need Windows 7 Ultimate?
I'm about to start a new module in my existing web application project (already completed 3 modules), due to more data entry and volume of data handling my PM informed me to go this module on windows application (vb.net), but i'm requesting him to go with web application since i'm much familiar in web applcation and all my completed module on web.
But he is thinking on performance part too, if i get some idea / suggestion on the same so that i can clear and i will go with either option.
The module is Service Billing with LPO Control, Billing, Proforma, eBilling, eApproval, online billing etc.
One customer set up an IIS 7 on a Windows 2008 machine. Forms Authentication works fine on my local IIS 6.0 and also on a shared server I used for testing. On the new machine there is no way no access the password protected area despite a succesful login.
Is there any settings I should ask my customer to check out on the server ? Or is there something different for IIS 7 I should see in my web.config ?
My website security is configured with "Windows Integrated Security" only (anonymous is disabled).
I also want to set a specific account to run the w3wp.exe process using the Application Pool Identity to a domain account.
Running directly from the server works without any problem but from remote computers I always get the authenticaion window then the 401.1 error (after 3 attempts).
It seems that its the combination of "Windows Integrated Security" along with the "Application Pool Identity" that causes the problem. When I disable one of the two it works properly.
My server is Windows Server 2003 R2, running IIS 6.0.