Make sure you are an administrator”, try to run Visual Studio as an administrator and just enter the local computer name in the Server field, and the IIS site name. There is also no way to change the port to avoid potential conflict with other applications.When publishing to localhost with this setup, if you encounter error ERROR_USER_NOT_ADMIN with the message “Connected using the Web Deployment Agent Service, but could not authorize. To use the service, select the Remote Agent Service option during installation:This is the Web Deploy configuration to be used:Account: an account with administrative privilegesThe only limitation is that, with this setup, Web Deploy now runs on port 80, instead of the default port 8172, which is the case if Web Deploy is installed on Windows Server. So what did I do wrongly?The answer, after half a day of trying various suggestions with much frustration, came from this article. Simply put, the Web Deployment Handler – the module which links Web Deploy with IIS and shows the configuration menu – is only available on server editions of Windows. On client SKUs such as Windows 7, only the Web Deployment Agent service, a lite version with basic features, is available. I followed the troubleshooting guide here to no avail, The menu was always present during my other installations of Web Deploy on Windows Server, leading to a typical Web Deploy configuration dialog:Visual Studio Publish / Web Deploy Winhost > Authoring Tools > Visual Studio > Visual Studio 2005/2008 Deploying a Visual Studio 2008/2005 or Visual Web Developer 2008/2005 web projectWithout this menu, it seems impossible to configure Web Deploy and make use of it.
0 Comments
Leave a Reply. |
Details
AuthorKarthic ArchivesCategories |