Hi -
I've got the FTP all set up, but I keep getting this error when I try to upload...
Error while uploading. The Program could not create a catalog.
HELP!
I can get the FTP to work with your Direct FTP, but I can't find a way to export Visual SIte Designer to the other Direct FTP.
Thanks!
Lisa
I've got the FTP all set up, but I keep getting this error when I try to upload...
Error while uploading. The Program could not create a catalog.
HELP!
I can get the FTP to work with your Direct FTP, but I can't find a way to export Visual SIte Designer to the other Direct FTP.
Thanks!
Lisa
Hi Lee,
If you can get it to work in direct ftp then I would suggest trying to use passive mode in VSD. Have you tried it?
If you need an example how to upload your site with direct ftp.
http://www.coffeecup.com/direct-ftp/help/tutorials/
should be the same setting in both!
If you can get it to work in direct ftp then I would suggest trying to use passive mode in VSD. Have you tried it?

If you need an example how to upload your site with direct ftp.
http://www.coffeecup.com/direct-ftp/help/tutorials/
should be the same setting in both!
I'm not sure I'm having the exact same problem as Lisa but it sounds pretty similar.
When I attempt to upload my VSD site via VSD using the same settings I've always used I'm now getting the following error:
"Error: The program could not access the catalog on the server. Several things may be responsible for this issue so you should try connecting again later."
I believe I'm using the latest build of VSD: Version 6.0, build 6
When I test the connection within VSD it passes the "server test and logon" portion but then fails at the 2nd "folder creation" test.
I'm a little puzzled because these are the settings I've always used to upload via VSD. I did try switching passive on and off and it's made no difference.
I'm fairly certain the server I'm uploading to is functioning properly because I just updated and uploaded my store associated with this site via SCC Pro and everything uploaded fine.
I'm not sure when this issue started because I haven't updated this site for awhile. I use ~LunarPages for hosting and I do know they very recently upgraded the cpanel interface. I was initially thinking maybe some of the read/write permissions for my folders on my server got messed up somehow but if that were the case I don't think I'd be able to upload via SCC. I can also connect to the server via Direct FTP.
Any thoughts????
When I attempt to upload my VSD site via VSD using the same settings I've always used I'm now getting the following error:
"Error: The program could not access the catalog on the server. Several things may be responsible for this issue so you should try connecting again later."
I believe I'm using the latest build of VSD: Version 6.0, build 6
When I test the connection within VSD it passes the "server test and logon" portion but then fails at the 2nd "folder creation" test.
I'm a little puzzled because these are the settings I've always used to upload via VSD. I did try switching passive on and off and it's made no difference.
I'm fairly certain the server I'm uploading to is functioning properly because I just updated and uploaded my store associated with this site via SCC Pro and everything uploaded fine.
I'm not sure when this issue started because I haven't updated this site for awhile. I use ~LunarPages for hosting and I do know they very recently upgraded the cpanel interface. I was initially thinking maybe some of the read/write permissions for my folders on my server got messed up somehow but if that were the case I don't think I'd be able to upload via SCC. I can also connect to the server via Direct FTP.
Any thoughts????
With my server I have to be logged in to upload. Open the server site on one window, and browse to the httpdocs folder. Open your web site in another window, then open CC VSD. Set your FTP setting and test it first. Save each setting with a new file name until you get a test with all OK's. Then try to upload the site. Good Luck!
Tim Banish Sr wrote:
With my server I have to be logged in to upload. Open the server site on one window, and browse to the httpdocs folder. Open your web site in another window, then open CC VSD. Set your FTP setting and test it first. Save each setting with a new file name until you get a test with all OK's. Then try to upload the site. Good Luck!
With my server I have to be logged in to upload. Open the server site on one window, and browse to the httpdocs folder. Open your web site in another window, then open CC VSD. Set your FTP setting and test it first. Save each setting with a new file name until you get a test with all OK's. Then try to upload the site. Good Luck!
I've never had to be logged in before. Once you correctly enter the settings VSD logs in and uploads for you (at least it always has for me). I haven't changed any settings or anything recently other than upgrading to SCC PRO. I don't know why that would have anything to do with it.
As I stated before I know lunarpages has just upgraded cpanel and done some stuff with our server. I THINK I read something about there being a PHP upgrade as well...but not sure. I sort of ignored it since half of it is over my head anyway! Since SCC and FTP have been working fine I had no reason to suspect any issue with VSD.
I haven't poked around my server file permission/folder settings yet to see if anything changed. I was sort of waiting to see if maybe someone else was having the same issue. With my luck I'll end up changing something on the server end and breaking everything!
I'll give your suggestion a try see if it fixes my issue and post later! Thanks!
So I've tried some suggestions including:
rechecking my settings, reinstalling VSD, turning off my all antivirus programs, and I've toggled "passive mode on and off"
I still can't upload via my site via VSD.
I don't know what is going on since these are the same settings I've always used.
Grrrrr....I guess it's time to open a support ticket. I HATE being beat!
rechecking my settings, reinstalling VSD, turning off my all antivirus programs, and I've toggled "passive mode on and off"
I still can't upload via my site via VSD.
I don't know what is going on since these are the same settings I've always used.
Grrrrr....I guess it's time to open a support ticket. I HATE being beat!

Hi everyone. First let me apologize to Lisa..I didn't mean to come in and hijack the thread. I was just posting here because I was having similar issues with VSD.
That being said, I wanted to come back and post what I ended up figuring out in my case. I absolutely hate when you are reading a forum thread that perfectly describes your situation and then it just ends with no update on what the resolution ultimately was.
For no apparent reason the built in FTP function in my VSD 6.0 build 6 just suddenly stopped working. The same settings that always worked suddenly didn't work anymore. Stranger still was the fact that I could access my server just fine with Direct FTP and I could also upload perfectly fine in SCC Pro.
I tried all the suggestions:
Finally I decided to stop pulling my hair out and step back and look at things from a different perspective. Since I knew I could access and write to the server via FTP in Coffeecup Direct FTP and SCC PRO using basically the same settings I was pretty sure it was nothing on the server end. I began to think what I had changed/installed recently and what was different between the two programs with working FTP and the stubborn VSD.
The only thing I had really changed on this machine recently was downloading and installing SCC Pro. It seemed pretty odd to me that this was around the same time these issues with VSD began.
I then realized one major difference between the Direct FTP/SCC Pro installation and VSD. I realized VSD was installed on my 2nd hard drive. Now keep in mind it's ALWAYS been there...and it's always worked. Since I was pretty much out of ideas I decided to try something on a hunch. I uninstalled VSD yet again and I did a clean reinstall. I had already done this previously but I had always simply reinstalled to the same drive VSD was on. This time instead of installing it on the backup/2nd hard drive I installed to the main C: drive. As soon as I did this VSD was back to working properly again!
Being the curious glutton for punishment that I am, I decided to uninstall VSD from the C: drive and install it back on the 2nd hard drive again. I expected VSD's built in FTP to NOT work again, but it still works. Odd!
This is purely speculation on my part, but I think my issue with the built in FTP in VSD stems from the fact that I had it installed on a different hard drive than SCC Pro. When I recently downloaded SCC pro I let it install to my C: drive. I believe the VSD FTP issue probably had something to do with a registry error or conflict or possibly some sort of licensing issue perceived by the VSD program. As soon as I installed it onto the C: drive with SCC Pro everything went back to normal.
Although I could easily upload my sites via Direct FTP as a workaround I still love the built in FTP and wanted to figure out a solution. This probably isn't an issue many of you will encounter but I thought I'd post it just in case. I had about 4 days off and on trying to figure this out...so even if ONE person can avoid the headache I'll be happy.
That being said, I wanted to come back and post what I ended up figuring out in my case. I absolutely hate when you are reading a forum thread that perfectly describes your situation and then it just ends with no update on what the resolution ultimately was.
For no apparent reason the built in FTP function in my VSD 6.0 build 6 just suddenly stopped working. The same settings that always worked suddenly didn't work anymore. Stranger still was the fact that I could access my server just fine with Direct FTP and I could also upload perfectly fine in SCC Pro.
I tried all the suggestions:
-
- I verified my settings over and over again.
- I tried passive on and off.
- I contacted my hosting provider to make sure my permission settings were correct and that my ftp settings were correct.
- I turned off ALL security software, antivirus software and firewalls.
- I deleted all server profiles within VSD and made new ones
- I unistalled and reinstalled VSD
- I swore...and pounded the desk with my fist
Finally I decided to stop pulling my hair out and step back and look at things from a different perspective. Since I knew I could access and write to the server via FTP in Coffeecup Direct FTP and SCC PRO using basically the same settings I was pretty sure it was nothing on the server end. I began to think what I had changed/installed recently and what was different between the two programs with working FTP and the stubborn VSD.
The only thing I had really changed on this machine recently was downloading and installing SCC Pro. It seemed pretty odd to me that this was around the same time these issues with VSD began.
I then realized one major difference between the Direct FTP/SCC Pro installation and VSD. I realized VSD was installed on my 2nd hard drive. Now keep in mind it's ALWAYS been there...and it's always worked. Since I was pretty much out of ideas I decided to try something on a hunch. I uninstalled VSD yet again and I did a clean reinstall. I had already done this previously but I had always simply reinstalled to the same drive VSD was on. This time instead of installing it on the backup/2nd hard drive I installed to the main C: drive. As soon as I did this VSD was back to working properly again!
Being the curious glutton for punishment that I am, I decided to uninstall VSD from the C: drive and install it back on the 2nd hard drive again. I expected VSD's built in FTP to NOT work again, but it still works. Odd!
This is purely speculation on my part, but I think my issue with the built in FTP in VSD stems from the fact that I had it installed on a different hard drive than SCC Pro. When I recently downloaded SCC pro I let it install to my C: drive. I believe the VSD FTP issue probably had something to do with a registry error or conflict or possibly some sort of licensing issue perceived by the VSD program. As soon as I installed it onto the C: drive with SCC Pro everything went back to normal.
Although I could easily upload my sites via Direct FTP as a workaround I still love the built in FTP and wanted to figure out a solution. This probably isn't an issue many of you will encounter but I thought I'd post it just in case. I had about 4 days off and on trying to figure this out...so even if ONE person can avoid the headache I'll be happy.
Thank You Dr James For Posting...you da man
Dr.James... if I understand correctly, the SCC Pro will always automatically install to your C drive in a pre-destined folder system. It looks as if you chose to install your FTP to another directory as you just explained.
Glad to hear that you worked all that out and everything is up and running for you now.
As to answers and solutions, just remember that none of the mods or advisors in here are CC staff, and most of our knowledge is gleaned from an accumulation of time spent in here. The CC team pop in on a fairly regular basis, but luckily they spend most of their time developing software. If you have a real issue, take it to the Help Center where you will find someone truly qualified to respond. Just put in a ticket and you will be contacted at the earliest...
Glad to hear that you worked all that out and everything is up and running for you now.
As to answers and solutions, just remember that none of the mods or advisors in here are CC staff, and most of our knowledge is gleaned from an accumulation of time spent in here. The CC team pop in on a fairly regular basis, but luckily they spend most of their time developing software. If you have a real issue, take it to the Help Center where you will find someone truly qualified to respond. Just put in a ticket and you will be contacted at the earliest...
Janys Hyde wrote:
Dr.James... if I understand correctly, the SCC Pro will always automatically install to your C drive in a pre-destined folder system. It looks as if you chose to install your FTP to another directory as you just explained.
Dr.James... if I understand correctly, the SCC Pro will always automatically install to your C drive in a pre-destined folder system. It looks as if you chose to install your FTP to another directory as you just explained.
Yes I believe the default setup for SCC PRO and most of CoffeCup's programs is to install on your C: drive. However I didn't "install my FTP" to another directory. That statement is pretty misleading. I was experiencing issues with Visual Site Designer's built in FTP program within VSD. True...I did happen to have Direct FTP installed in another location but that's irrelevant because Direct FTP is Coffee Cup's stand alone FTP program. Where (or even IF) it is installed has nothing to do with whether or not the FTP upload function WITHIN Visual Site Designer works.
Long story made short is my drive I'm currently using as a backup drive was my C: drive long ago. It became my M: drive when I updated to a larger HDD. I had just kept VSD installed on the same hard drive and when I updated to a new version of VSD I'd continue to install to M: rather than C:
When I later bought SCC, SCDesigner, and Direct FTP I installed them to the C: drive. This has been a perfectly stable and fine setup for well over a year. Everything worked fine until (perhaps coincidentally) my recent update to SCC Pro. For whatever strange reason my technical problems boiled down to the fact that I had Visual Site Designer installed to a different hard drive/location than my other Coffee Cup programs. I just wanted to point out the solution I ultimately encountered because many of us here look for a similar resolution before asking for help.
Janys Hyde wrote:
As to answers and solutions, just remember that none of the mods or advisors in here are CC staff, and most of our knowledge is gleaned from an accumulation of time spent in here. The CC team pop in on a fairly regular basis, but luckily they spend most of their time developing software. If you have a real issue, take it to the Help Center where you will find someone truly qualified to respond. Just put in a ticket and you will be contacted at the earliest...
As to answers and solutions, just remember that none of the mods or advisors in here are CC staff, and most of our knowledge is gleaned from an accumulation of time spent in here. The CC team pop in on a fairly regular basis, but luckily they spend most of their time developing software. If you have a real issue, take it to the Help Center where you will find someone truly qualified to respond. Just put in a ticket and you will be contacted at the earliest...
I'm not sure whether this directed at me or more of a general statement for all, but I absolutely agree. I understand this is a user forum and that CC staff only pop in from time to time. In fact that's why I came here first. I did open a support ticket and ask for help but only after seeing noone else in the forums had experienced this same issue. I realize this isn't a tech support forum but many of us help each other out and many of us encounter situations and circumstances CC support couldn't imagine in their worst nightmares

I never bother with opening a support ticket until I'm sure I can't handle the problem on my own...even with great companies like Coffeecup. In my experience you can often find a solution by searching or asking before wasting support's valuable time is ever necessary. The bottom line is I searched all over the forums and support articles and then posted here and asked for feedback in the forums. When it was clear I was experiencing "a real issue" and it was something weird that I couldn't fix with the normal recommendations, I bit the bullet and opened a support ticket. I fact I opened one with CC and my hosting provider.
Opening these tickets and getting support feedback was very valuable because it helped confirm that it wasn't an issue with my server or hosting and it was likely some issue with my PC. It was up to me to figure out what exactly that problem was. When I posted my fix for this issue I wasn't intending to imply that I was upset with CC or these forums for not giving me an answer. Instead I was trying to post my fix and hopefully help prevent someone else from going through a few days of frustration. Honestly this was such a weird fluke that I thought posting an outline of my line of thinking and what I tried along the way would be of benefit.
I did manage to figure it all out and that's why I posted here. I wanted to post my fix for anyone who was following along or who may stumble across this thread in the future because they are having similar issues. Nothing is worse than when someone starts a thread about an issue, posts a few times, and then never updates whether the issue was resolved or how.
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.