Expression Web Cannot Ftp Into My Website
Expression Web Reports, View a Web Site Summary. Web site reports contain information about your Expression Web website and can provide detailed records about its related pages, elements, and links. Expression Web compiles these reports as you create your site to help you analyse the performance of your web site. Chapter 10 Managing and Publishing Your Work. This page serves as the companion web page for Chapter 10 of Expression 4 Web Step by Step. After you’ve taken all the time and trouble to create a Web site and get everything set up the way you want, you are probably going to want people to be able to access it. Publishing Your Web Site with Expression Web 1.0 or 2.0. Publishing with Expression Web 4.0. Now that you have finished designing your site you will need to publish it for the world to see. The screenshots for this tutorial were done with a system running Windows Vista and Expression Web 2.0. Yours may look slightly different.
Some of our developers use Microsoft Expression Web to author their ASP and ASP.NET web applications. Our web servers are all built on Windows Server 2008 R2 and IIS 7.5 and come in a group of separate Development, Testing and Production servers. The goal is for the developers to check out their source code to their workstation, then publish to Development, then Testing and then finally to Production using Expression. We are connecting with the web servers by exporting the IIS drives as file shares that the developers can then map or use in Expression. This works for one group of servers but not for another. When we try to publish from the Development server to the Testing server we get the following error:
I'm not really sure how to interpret this error but I'm going to go with 'the directory the file share is exposing to Expression is already being used by IIS as the location for a web site' which if that is a correct interpretation makes this feature pretty useless (wouldn't every website you'd want to publish to also be served by IIS?). I have tried looking through the Event Log on the server and compared the IIS configuration between the two server groups and cannot find anything immediately obvious. I would rather avoid the other connection methods (WebDAV, FTP, SFTP and Frontpage Extensions if possible).
How can I setup our web servers so our development teams can work on a website in Development and then publish it to Testing or Production without resorting to manually copying files or running a script? As someone who is not terribly familiar with Windows and IIS am I 'just doing it wrong'?
kcekce1 Answer
I ended up going to Microsoft's support for this. Here's what was going on:
At some previous point FrontPage was used to manage a site or sites within the main IIS directory (W:WWWDevelopment_Intranet) on the Development Server (IISDEV). FrontPage keeps track of all its metadata with a number of files (see List of Special Files and Directories Maintained by FrontPage for details) that were left in the directory. This causes Expression to detect that the site or a portion of it is managed by FrontPage and therefore invalidates it as a File System Publishing target; however we can't publish to the directory using the FrontPage Server Extensions (FPSE) because while the metadata files are still there the actual FPSEs are not installed since FrontPage has been depreciated since 2006.
The FPSE metadata files are not just limited to one 'site' in the sense of your folder path. As I understand it, if somewhere further down the directory tree from Development_IntranetUnrelated_Site there are leftover files, publishing to your site at Development_IntranetSite_I_Actually_Care_About will fail since the whole thing is contained in a single IIS Site. We discussed writing a script that recursively descended through the directories deleting the FPSE metadata files however there is the danger that the sites still depended upon code and other other information stored on them. You can 'de-couple' individual folders in Microsoft Expresson by right clicking the site and selecting Convert to Folder.
An additional concern is that Expression always tracks the full path for publishing so if we want to publish a file from IISDEVWWWDevelopment_IntranetSite_I_Actually_Care_Abouttest.html to IISTESTWWWTesting_IntranetSite_I_Actually_Care_Abouttest.html, what you actually end up with is your file being published to IISTESTWWWDevelopment_IntranetSite_I_Actually_Care_Abouttest.html. The whole idea of working in your Development server and then publishing to your Testing server only works for subsites as long as the full path is identical.
During our testing our support engineer and I noticed that Expression was slow when editing and manipulating files. Apparently every time you change directories, manipulate a site file or do some other action it 're-scans' the entire site directory. It sounds like it doesn't keep a cache and/or doesn't intelligently update it as you work with the site's files. Either way, he said for a site of our size (larger than 1GB) that we are pushing up against the performance limits of Expression and that we should not be surprised if it runs slow or crashes. Fantastic.
The final nail in the coffin here is that Microsoft Expression Studio was deprecated in 2010 and it's functionality has been rolled into Visual Studio 2012.
kcekce
Not the answer you're looking for? Browse other questions tagged windows-server-2008-r2iisiis-7 or ask your own question.
Historically I've always uploaded my website via FTP since my server does not have front page extensions and nor will it.
Using the latest release of Visual Studio 2012 (11.0.51106.01 Update 1) (although I think this issue is for all of 2012), I cannot publish my website!
The error message is
2>Unable to add 'file' to the Web site. FTP Passive mode is not available
I will also point out that my connection validates so I don't think the error message is anything but clear and meaningful!
So, I have 3 questions.
- Is this something I'm doing wrong or a fault with Visual Studio 2012?
- Should I be trying to do this via passive mode or should I be updating my web server to enable 'active mode'?
- Is FTP still an acceptable method or should I be investigating the Web Deploy option?
5 Answers
Open your publish profile
PropertiesPublishProfilesyour_profile_name.pubxmlAdd
<FtpPassiveMode>False</FtpPassiveMode>to<PropertyGroup>Save file and publish again.
As a workaround, publish the site to a filesystem (ie, save it locally), and then use another FTP client to transfer it. It's not great at all, but, if you're desperate and out of options then it may be a solution, however temporary.
As an actual fix, it's down to the server to enable this. In my case, it turned out to be a firewall problem (gave incoming permissions to FileZilla Server) and not using a custom port range in FileZilla server (under passive)! This suggests it was a port issue!
However, this doesn't explain why you can or can't turn off/on passive mode in VS 2012 but could in earlier releases.
Expression Web Cannot Ftp Into My Website Free
DaveDaveYou can also do this (I was getting the same error as yours):
1 - Build > Publish 'project'.
2 - Uncheck the Passive Mode.
It should work after 5 simple steps (IIS7.5):
- Make sure passive mode is selected
- Make sure to configure data channel port range in IIS application FTP Firewall Support section (e.g. 5000-6000)
- Make sure that port range 5000-6000 is open on the firewall (Allow inbound connections on port range 5000-6000)
- net stop ftpsvc
- net start ftpsvc
If you have acces to the server. You have to add the svchost.exe to the 'Allowed Programs' in Windows Firewall.
Look at this film. Its at the end.youtube film
This worked for me.